[opencms-dev] Open CMS Crashes when Viewing Module in Workspace
christian_steinert at web.de
Mon Mar 30 16:41:33 CEST 2009
if you want to edit your files in the system folder and preview the changes at the same time, you could use two separate browsers with separate logins - one for editing and one for viewing. The browser that you use for viewing needs to be logged in too, so that you can see unpublished context, but in this way you have two sessions which can work in different contexts inside of opencms.
At the beginning it also took me a while to understand the idea of a website root - in an opencms session, there is always one site that is active. The folder prefix of that active site will be prepended to the path of each file that is accessed. This means that each website is like a separate name space but it also means that the paths that you need to access a resource and the visibility of resources depends on the site that is currently active for your user.
All this is needed so that one opencms installation can easily serve separate web sites without the templates having to know where each site lies in the opencms file system.
> The system doesn't work if you choose the project '/'. You have to
> select 'sites/default' or where your project is, or use a navigator
> where you are not registered as administrator.
> 2009/3/29 Charles Mason <charlie.mas at gmail.com>
> Hi All,
> I am integrating OpenCMS into a site I am creating and coming up
> against an odd issue. I have a couple of JSP templates in a separate
> module for the site. I can use the Workspace completely normally, but
> us soon as I navigate to the module in the workspace the live site
> crashes. The workspace continues to work so I can edit and publish the
> content, but it flatly refuses to serve any content. Sometimes I get a
> blank page other times I get an exception complaining the page could
> not be found in the VFS. It doesn't record any exceptions in the log
> files. This happens when navigating to any content even static images
> which have nothing to do with the template.
> The only solution is to reload the context in the servlet containers
> manager web app. Once its reload it all works fine, even the newly
> published temlate updates are there. I would really like to solve this
> as it really slows down the development cycle. Is this a known issue?
> I am using the latest release of Open CMS. The Servlet container is
> JBoss Web (not the full JBoss Application Server), which is basically
> Tomcat with some native code (from Apache I think) to more efficiently
> serve static content.
> Any suggestions ?
> Charlie M
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please
> _______________________________________________ This mail is sent to
> you from the opencms-dev mailing list To change your list options, or
> to unsubscribe from the list, please visit http://lists.opencms.org/
Psssst! Schon vom neuen WEB.DE MultiMessenger gehört?
Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123
More information about the opencms-dev