Sitecore Pilipinas

Part of the extra work in the SC upgrade process is making sure that your modules still work after the upgrade. Since we were using SPIF as one of our major modules, it was important that this was validated and updated as well. From our current 111115 revision, we chose to upgrade to 1.1 rev 130613. Installation was pretty straightforward we followed the SDN instructions nothing difficult there. What struck us though was the note in one of the upgrade path; it says, upon first access, any existing integration folder will be recreated. Whoa! This did not sound too refreshing to us as we already have thousands of references to these integration items. We had to find out a way to sync the refs once the upgrade completes, one route we took was to leverage the SC Links DB. We used the steps below: 1) After upgrade, rebuild the Links DB, since the web DB still contains the current live refs, we can use the media IDs here as refs once the SPIF in master has refreshed. 2) We then created

We hit a snag in one of our instances that we we were upgrading. The upgrade finished but once we we were validating the site, none of the Search Options Dropdown was displaying. I ran a compare on the files from a working copy to that of our instance and could not find any major difference so I suspected this to be data-related. I could not figure out what was different from the working to that  of my instance so I decided to package the Items related to Buckets and install that to my target non-working instance. And voila! it works. I opened up a ticket with Support to get to the root of the issue and provided them with the Buckets package (before I overwrote it). They found out that the /sitecore/system/Settings/Buckets/Settings/Search Box Dropdown was not having any version! They gave it one and the dropdown now works.

Got hit today by this issue when I was validating our latest WFFM installation for our Dev SC7.0 instances. Some existing pages with WFFM forms in them where throwing these exceptions. After a lot of searching and troubleshooting, I remembered that I ran into this issue before; with the Sitecore queries. SC queries in particular do not like "and", "or" and "-" in item names (paths). I suspect, Sitecore.Forms.Core.dll contains a new call using an SC query. Looks like this breaking change was not documented in the SDN. My current alternative is to move these affected forms elsewhere i.e. under items without the prohibited character and words.

This is my first blog and first post, I mainly created this blog to archive all my musings and discoveries mainly in the world of Sitecore.