- They only showed up on WeBlog pages
- They only showed up when I tried adding a component to any place except the top – if an existing component was there and I’d add it below it would work.
insertRenderingCannot find rendering chrome with unique id: 17A541CA4BC34DCBB60F783861BF3191Sitecore.PageModes.ChromeTypes.Placeholder.Sitecore.
In addition to that, whenever I clicked anywhere on the page to change one of the renderings/ a piece of text, I also get:
Cannot parse command parameters
An error ocurred.
I could however still change things around successfully, whether that’s adding or changing text, image, link or even changing a Datasource using ‘Edit the component properties’.
There were actually two issues I was dealing with here, not one:
- The first issue was known issue: The Page Editor did not save renderings inserted to a placeholder if the placeholder contained renderings that specified the placeholder key using mixed case. (367952)
This issue was actually fixed in SItecore 6.6 Update 4 (as specified on SDN)
- The second error is actually a bug (which has been registered with Sitecore Support).
So the first solution was reasonably simple, the second one a bit confusing. Here’s what was going on:
Widgets in WeBlog are based on the /sitecore/templates/Modules/WeBlog/Blog Sublayout template, rather than the default /sitecore/templates/System/Layout/Renderings/Sublayout template. This was so the output of the widgets can be cached per blog.
Initially I changed the template of the widgets to the default, after that Sitecore Support did come back to me with a possible workaround: a changed version of the /sitecore/shell/Applications/Page Modes/Utility.js file. I have not implemented this (as I didn’t need the caching per blog), so that hasn’t been tested.
Big kudos to Sitecore Support for helping me figure out the cause for these problems.