AI OnAI Off
Composer not registering content areas
Hi,
I'm experiencing the exact same problem as described (with the exact log).
It has all worked just fine before, and suddenly there's no content areas registered in the composer admin (tho, allready existing page types got its content areas like before). If I try to re-register allready present page types - these content area's dissapear too making the page type unusable.
Things I have done after the content areas worked are installing episerver mail and thus enabling EpiServerCommon. Everything else seems to work, except registering page type content areas.
I suspect it has something with permissions to do. Any suggestions, anyone?
Aug 18, 2009 10:09
Did anyone solve this, or has everyone just stopped making new composer-templates? I get the same error.
Nov 30, 2009 15:29
Hi,
I have the same problem. In my case the problem is authentication. Composer request to template page
(ex. [HOST_URL]/Templates/HomePage/Pages/Home.aspx?DE_VM=2&DE_UID=0d99aab5-7b54-454f-bfdd-9ce72acde67f)
is redirected to login page.
Actuall method responsible from geting page source and regex it is: Dropit.Extension.Controllers.PageCustomData.GetCompiledPageHTML(url, str);
Guys, did you have such problem? Any ideas how we could solve this problem?
Piotr
Jan 13, 2012 10:21
I faced the same problem and even I removed my master page and just narrowed it down to one page, but still the same. I found a work around even though not an ideal solution and I will wait for someone to reply the correct solution.
This is what I did:-
1. Register the page with composer,
2. Go to the PageTypes under CMS Admin.
3. You will find your newly added pagetype with prefix [ExtensionSYS].
4. Add your content areas manually and save them through pagetype options.
5. Do no register it afterward through the composer admin.
7. Under the CMS Edit window -> Composer tab, now you will see your content areas.
Cheers,
Naz
Edited,
Jun 19, 2012 17:27
This thread is locked and should be used for reference only. Please use the Legacy add-ons forum to open new discussions.
Hi
We've had our site up and running for a few weeks with composer and have gotten two page types working with composer, no problems. However this week I started on a third page type. When adding registering the page type in composer in admin mode, no content areas are registered. Even if i strip the aspx down to a single Extension content area, without a master page, the result is the same.
In the log, the following lines are the last after the attempt to register the page type as a composer page type, as well as after clicking "re-register content areas":
2009-05-25 10:17:50,250 [1] INFO Dropit.Extension.Controllers.ContentAreaManager [(null)] - Dropit.Extension.Controllers.ContentAreaManager: Get content area definitions from page type...
2009-05-25 10:17:50,250 [1] INFO Dropit.Extension.Controllers.ContentAreaManager [(null)] - Dropit.Extension.Controllers.ContentAreaManager: Detect 0 areas
2009-05-25 10:17:50,250 [1] INFO Dropit.Extension.Controllers.ContentAreaManager [(null)] - Dropit.Extension.Controllers.ContentAreaManager: Get content area definitions from page type...
2009-05-25 10:17:50,250 [1] INFO Dropit.Extension.Controllers.ContentAreaManager [(null)] - Dropit.Extension.Controllers.ContentAreaManager: Detect 0 areas
2009-05-25 10:17:50,250 [1] INFO Dropit.Extension.Controllers.ContentAreaManager [(null)] - Dropit.Extension.Controllers.ContentAreaManager: Get content area definitions from page template...
2009-05-25 10:17:50,250 [1] DEBUG Dropit.Extension.Controllers.PageCustomData [(null)] - Dropit.Extension.Controllers.PageCustomData: Get Extension HTMLcomplied /Templates/Eidsiva/Pages/ComposerTest.aspx?DE_VM=2&DE_UID=59675227-9bdd-4fe3-8454-bee99bc377ca
2009-05-25 10:17:50,250 [1] INFO Dropit.Extension.Controllers.PageCustomData [(null)] - Dropit.Extension.Controllers.PageCustomData: The signature:<xml id="59675227-9bdd-4fe3-8454-bee99bc377ca"
2009-05-25 10:17:50,250 [1] DEBUG Dropit.Extension.Controllers.PageCustomData [(null)] - Dropit.Extension.Controllers.PageCustomData: