RE: Web Content display issues after new instance creation

Mark Clarke, modified 6 Years ago. Regular Member Posts: 107 Join Date: 3/3/12 Recent Posts
Hi all,

I had a single virtual instance and had no problems with child sites. I then created a 2nd instance. Now on the core or primary instance when I create a child site the web content fromt he child site will not be visible to guests but if I add content from the parent of sibling site (created before the new instance) then it displays as intended for guests. 


On the new instance if I create a site and add a page; attempting to drop a web content display portalet on the page does not active any drop targets and I am unable to add the portlet. If its relevant I have the commerce module installed.


Not sure where to look to solve this. Any hints appreciated
Mark Clarke, modified 6 Years ago. Regular Member Posts: 107 Join Date: 3/3/12 Recent Posts
Not sure if this is related to the issue above but we also changed our default language to en_GB. We get errors such as "Invalid title" when capturing web content even though it's valid. (See attached). This doesn't happen all the time and goes away after several attempts to save ... some times.

We also have some content which was added with en_US but this seems to display alright. We did have to add the following properties to portal-ext.properties as all the paths where incorrect for things like the favicon etc and where not displaying properly when en_US was appended to the URLs.

locale.prepend.friendly.url.style=0                                                                         
locales=en_GB

If this is not related to the web content display issue please move to its own thread or let me know and I will start a new thread.
Mark Clarke, modified 6 Years ago. Regular Member Posts: 107 Join Date: 3/3/12 Recent Posts
I restored the entire site to the bundled tomcat and commerce plugin. I replaced the osgi folder with a backup from the production server and restored the database. The problem still exists so I guess it must be some data in the database that needs to be updated.