Sitecore Pilipinas

While playing around with the Reflector today,  I chanced about the StringUtil class inside the Kernel. If you are working with a lot of links in Sitecore, you would have encountered the function EnsurePrefix, that takes in a char and a string as arguments; this is one of the members of this class. Aside from this uber useful utility here are a list of what you can also pick up and use inside this sealed class. Function/Method Parameters Description ArrayToString Array, char Makes strings out of Arrays Capitalize string Uppercases the first letter of a string and lowercases the remaining letters. Clip string, int, bool Clips a string at a certain length. The bool argument is for the ellipsis Combine object, object, string Combines the ToString() representation of the two objects separated by a string divider Concat object[] Accepts a collection of objects and concats the ToString() representation of each value Contains str...

Ran across an issue today wherein one of our Content Editors was complaining that their page was not working, i.e. some page scripts where not firing. Upon closer inspection, we found out that their content inside their RTE was missing. We added them back but, it just kept getting stripped-off when we close the editor. This did not happen to us before when we were using SC6.5, so this basically smells more like an upgrade issue. I scanned all of the config changes (I kept a log) and found one curious setting:       <setting name="HtmlEditor.RemoveScripts" value="true" /> This setting was by default removing any embedded scripts inside the RTE. Just turn it off in your CM and keep it on in your CD.

Our internal clients wanted us to secure some of their resources stored in the media library so that only authenticated and authorized extranet users are able to view or download them. Our current setup has the following components, I'll simply focus on the 3rd and 4th points: Sharepoint Workflows on a Sharepoint 2007 Server. This serves as the working repository of the resource owners. Sitecore Sharepoint Integration Framework. This hooks up Sitecore with the designated document library in Sharepoint for all finalized files/documents Integration folder in the Media library Login page to handle the authentication Create your login page. You have the option to create your sublayout for this (mostly to control the page contents etc.) or you can just quickly create one and put it in one of your folders in your solution. I normally use CodeFile directive in my pages as we found it easier to maintain this type of setup in the long run. There are plenty of samples of the login ...

Yey! I just finished 4-day Sitecore 7.0 developer training in Chicago and passed the certification. My thoughts: Over-all good training, Good trainer. I would have hoped they had some printouts as it was pretty tedious to go Alt+Tab'ing the whole time we had to do the exercises. In 6.5 we had all these materials with us.

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 cre...

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.