What are the components you are trying to add. Are they out of the box components.
Make sure that /etc/design/default exists. I would suggest to rebuild that path again and try.
I am trying to add the custom components and not out of box components. As mentioned, once added I can see those components in the parsys - create New list but not in sidekick
I have my own design. /etc/design/<companyname> and mapped to that design in the page properties setting design. I did not set the design path in template but I think setting it at page properties will accomplish the same thing.
I did go and check the design page where it is getting written. I can see the components included there. Thats why I can see it in the parsys - create-New list just doesnot see it in sidekick.
Also weird thing is that was happening on three templates but for two of them when viewed the page in preview mode and again author, sidekick displayed the list but the third template-page still doesnot. Seems a tough issue to crack may be a sidekick js relatred issue but donot know.
Template level component selected for a parsys should be stored under /etc/designs/<YourdesignPath>/TemplateName/<AllAllowedComponent>. Do you see your third template under this path ? Also check if you are getting any JS error while Sidekick is getting loaded.
I'm having a similar problem. I can select the component (simple image) from the dialog while in design mode. When I switch back to edit mode, it's not in the list of components. The list is empty.
I have the same problem, on all content pages. The list of parsys components is complete when I go into design mode, but when I switch pack to edit mode I get a sidekick like this.
That was in Chrome 24.0.1312.57 on OSX 10.6.8.
If I switch for Firefox 17.0.1, the same page, both browsers with fresh clean caches.
Some things to note that might be relevant.
- The tabs at the top are missing so its not just the list of parsys components that are not getting rendered, the container of the parsys components are not getting rendered.
- Also, on Firefox tabs and components loads with a spinner and fades in, on Chrome the spinner starts, but the fade in doesnt happen and the Sidekick opens and closes.
In both browsers the logs have no errors and the strange thing is that the Sidekick has been working perfectly for at least a week on Chrome. I suspect a change I have made somewhere is resulting in the on timeout event that is driving the fade in to fail silently.
Are others on this thread seeing the same problem ?
What browsers are being used ?
If anyone has any suggestions, I'd be interested to hear them, failing that I will see if Chrome's event profiler shows anything up.
Just discovered this is fixed by resizing the Sidekick dialog at the bottom right hand corner. Works every time. I must have been doing it without thinking before.