[opencms-dev] Problems with OpenCMS 5.3.4 and templates
Jeff Greer
jgreer at fdusa.com
Fri Apr 23 22:56:01 CEST 2004
Below is what the control code looks like after creating a new page.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE page SYSTEM "/system/shared/page.dtd">
<page>
<elements/>
</page>
Below is what the control code looks like after editing the new page.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE page SYSTEM "/system/shared/page.dtd">
<page>
<elements>
<element name="body" language="en">
<links/>
<content/>
</element>
<element language="en" enabled="true">
<links/>
<content><![CDATA[some data here]]></content>
</element>
</elements>
</page>
Below is my hand edited version of the control code that works.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE page SYSTEM "/system/shared/page.dtd">
<page>
<elements>
<element name="body" language="en" enabled="true">
<links/>
<content><![CDATA[Content coming soon]]></content>
</element>
</elements>
</page>
Below is the control code after using the editor to modify the page after making the page work by hand editing the
control code.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE page SYSTEM "/system/shared/page.dtd">
<page>
<elements>
<element name="body" language="en" enabled="true">
<links/>
<content><![CDATA[Content coming soon]]></content>
</element>
<element language="en" enabled="true">
<links/>
<content><![CDATA[Modified Content coming soon]]></content>
</element>
</elements>
</page>
As can be seen above the original content is kept in a well formed element while the new content gets saved in a
second poorly formed element.
:
> Jeff, Antti,
>
> It's working for us. What problem are you having?
>
> We have seen here that a template prepending "/sites/default" to
> <cms:link> does not work when [a page] is previewed from the "/" site perspective, but it does work when you change
> to the site perspective you are working on.
>
> So, don't prepend "/sites/default" to any of the cms:link in your JSP templates.
>
> Apart from that, no problem except for the language (how does it work?)
>
> --mariano
>
> -----Mensaje original-----
> De: opencms-dev-admin at opencms.org [mailto:opencms-dev-admin at opencms.org] En nombre de Antti Leinonen
> Enviado el: Jueves, 22 de Abril de 2004 04:10 p.m.
> Para: opencms-dev at opencms.org
> Asunto: RE: [opencms-dev] Problems with OpenCMS 5.3.4 and templates
>
> But in our case we also have the default body (about empty as in the welcome
> module), and still it doesn't work.
> Any ideas? Am I forgetting to define the body to be used somewhere?
>
> ++anttileinonen
>
> -----Original Message-----
> From: opencms-dev-admin at opencms.org
> [mailto:opencms-dev-admin at opencms.org]
> On Behalf Of Mariano Barcia
> Sent: 22. huhtikuuta 2004 19:01
> To: opencms-dev at opencms.org
> Subject: RE: [opencms-dev] Problems with OpenCMS 5.3.4 and templates
>
>
> Jeff,
>
> We solved that by making a default body (just like in the "welcome" module),
> but could not make the language feature work.
>
> --mariano
>
> -----Mensaje original-----
> De: opencms-dev-admin at opencms.org [mailto:opencms-dev-admin at opencms.org] En nombre de Jeff Greer
> Enviado el: Jueves, 22 de Abril de 2004 11:54 a.m.
> Para: opencms-dev at opencms.org
> Asunto: RE: [opencms-dev] Problems with OpenCMS 5.3.4 and templates
>
>
> I am seeing this problem also. I have a freshly installed 5.3.4 and each time I use the page editor I have to then
> manually edit the controlcode before the page will show up.
>
>
> Mariano Barcia said:
>> Hello manuel,
>>
>> We are seeing that the v5 "bodies" approach has been replaced by a
> bigger "control-code" that comprises both the
>> meta-data and the various content nodes (elements). The old ctrl-code
> needs to be totally replaced by this new one.
>> The DTD for the new one is /system/shared/page.dtd and you can see an
> example of a ctrl-code in the welcome module.
>>
>> I don't see a better solution than to manually edit the ctrl-code for
> each XML/HTML page :-(
>>
>> IMHO, a migration tool for v5 contents to v6 will be necessary, I'm
> sure this has been planned already but don't
>> know the due date ...
>>
>> --mariano
>>
>> -----Mensaje original-----
>> De: opencms-dev-admin at opencms.org
> [mailto:opencms-dev-admin at opencms.org] En nombre de Manuel Wallnöfer
>> Enviado el: Martes, 20 de Abril de 2004 02:51 p.m.
>> Para: opencms-dev at opencms.org
>> Asunto: AW: [opencms-dev] Problems with OpenCMS 5.3.4 and templates
>>
>> Hi,
>>
>> i have the same problem like Antti.
>>
>> I tried to import a template from the OpenCms 5.0 system but when i
> try to click the button save and exit i get the
>> same error.
>>
>> Can anybody help me how to get rid of this problem........
>>
>> Thanx a lot..
>>
>>
>> manuel
>>
>> ------------------------------------------
>> Manuel Wallnöfer
>> Roseweg 1
>> A - 4111 Walding
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: opencms-dev-admin at opencms.org
>> [mailto:opencms-dev-admin at opencms.org] Im Auftrag von Mariano Barcia
> Gesendet: Dienstag, 20. April 2004 19:10
>> An: opencms-dev at opencms.org
>> Betreff: RE: [opencms-dev] Problems with OpenCMS 5.3.4 and templates
>>
>> Hola Antti,
>>
>> We have discovered the reason for this behavior. Its all in the control-code. Check out the pages in the
>> /release folder, they have an
> adequate control code.
>>
>> It seems that whenever a new XML page is created thru the workplace
> wizard, it still gets created with the old-style
>> control-code. :-/
>>
>> BTW, the control-code explains the elements and available languages
> definition. Still have to figure out how to
>> call the correct language display.
>>
>> HTH,
>> --mariano
>>
>> -----Mensaje original-----
>> De: opencms-dev-admin at opencms.org
> [mailto:opencms-dev-admin at opencms.org] En nombre de Antti Leinonen
>> Enviado el: Lunes, 19 de Abril de 2004 06:56 a.m.
>> Para: opencms-dev at opencms.org
>> Asunto: [opencms-dev] Problems with OpenCMS 5.3.4 and templates
>>
>> Hola.
>>
>> We're trying to build a site on the CVS version of OpenCMS, and currently are facing a rather weird problem with
>> the editor's
> behaviour with templates;
>> We created a new module for the site, and basically everything works
> just fine, creating pages using the templates
>> created under the module, but when trying to actually edit the body
> contents with the HTML editor, the system throws
>> an error every time after save & exit:
>>
>> 2004-04-19 12:48:21 ApplicationDispatcher[/opencms] Servlet.service()
> for servlet jsp threw exception
>> java.lang.NullPointerException
>> at
>> org.opencms.page.CmsXmlPage.initBookmarks(CmsXmlPage.java:487)
>> at org.opencms.page.CmsXmlPage.<init>(CmsXmlPage.java:169)
> at
>> org.opencms.page.CmsXmlPage.read(CmsXmlPage.java:240)
>> at org.opencms.page.CmsXmlPage.read(CmsXmlPage.java:213) at
>>
> org.opencms.workplace.editor.CmsSimplePageEditor.initWorkplaceRequestVal ues(CmsSimplePageEditor.java:132)
>> at
>> org.opencms.workplace.CmsWorkplace.<init>(CmsWorkplace.java:163)
>> at org.opencms.workplace.CmsDialog.<init>(CmsDialog.java:166)
> at
>> org.opencms.workplace.editor.CmsEditor.<init>(CmsEditor.java:146)
>> at
>>
> org.opencms.workplace.editor.CmsDefaultPageEditor.<init>(CmsDefaultPageE ditor.java:103)
>> at
>>
> org.opencms.workplace.editor.CmsSimplePageEditor.<init>(CmsSimplePageEdi tor.java:67)
>> at
>>
> org.opencms.workplace.editor.CmsMSDHtmlEditor.<init>(CmsMSDHtmlEditor.ja va:73)
>> at
>>
> org.apache.jsp.WEB_002dINF.jsp.offline.system.workplace.jsp.editors.msdh
>> tml.editor_html_jsp._jspService(editor_html_jsp.java:56)
>> at
>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:133)
> at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> at
>>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:311)
>> at
>>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301) at
>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
>> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at
>>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:284)
>> at
>>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:204)
>> at
>>
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc her.java:750)
>> at
>>
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDisp atcher.java:636)
>> at
>>
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispat cher.java:546)
>> at
>>
> org.opencms.flex.CmsFlexRequestDispatcher.includeExternal(CmsFlexRequest Dispatcher.java:131)
>> at
>>
> org.opencms.flex.CmsFlexRequestDispatcher.include(CmsFlexRequestDispatch er.java:180)
>> at
>> org.opencms.loader.CmsJspLoader.service(CmsJspLoader.java:405)
>> at
>>
> org.opencms.flex.CmsFlexRequestDispatcher.include(CmsFlexRequestDispatch er.java:311)
>> at
>>
> org.opencms.jsp.CmsJspTagInclude.includeTagAction(CmsJspTagInclude.java: 396)
>> at
>>
> org.opencms.jsp.CmsJspActionElement.include(CmsJspActionElement.java:244 )
>> at
>>
> org.opencms.jsp.CmsJspActionElement.include(CmsJspActionElement.java:189 )
>> at
>>
> org.apache.jsp.WEB_002dINF.jsp.offline.system.workplace.jsp.editors.edit
>> or_005fmain_html_jsp._jspService(editor_005fmain_html_jsp.java:53)
> at
>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:133)
> at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> at
>>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:311)
>> at
>>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301) at
>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
>> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at
>>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:284)
>> at
>>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:204)
>> at
>>
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc her.java:750)
>> at
>>
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDisp atcher.java:636)
>> at
>>
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispat cher.java:546)
>> at
>>
> org.opencms.flex.CmsFlexRequestDispatcher.includeExternal(CmsFlexRequest Dispatcher.java:131)
>> at
>>
> org.opencms.flex.CmsFlexRequestDispatcher.include(CmsFlexRequestDispatch er.java:180)
>> at
>> org.opencms.loader.CmsJspLoader.service(CmsJspLoader.java:405)
>> at
>>
> org.opencms.flex.CmsFlexRequestDispatcher.include(CmsFlexRequestDispatch er.java:311)
>> at
>> org.opencms.loader.CmsJspLoader.dispatchJsp(CmsJspLoader.java:425)
> at
>> org.opencms.loader.CmsJspLoader.load(CmsJspLoader.java:382) at
>>
> org.opencms.loader.CmsLoaderManager.loadResource(CmsLoaderManager.java:2 31)
>> at
>> org.opencms.main.OpenCmsCore.showResource(OpenCmsCore.java:1475)
>> at
>> org.opencms.main.OpenCmsServlet.doGet(OpenCmsServlet.java:102)
>> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> at
>>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:284)
>> at
>>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:204)
>> at
>>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:257)
>> at
>>
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:151)
>> at
>>
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 67)
>> at
>>
> org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCon textValve.java:245)
>> at
>>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:199)
>> at
>>
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:151)
>> at
>>
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 67)
>> at
>>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :184)
>> at
>>
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:151)
>> at
>>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :164)
>> at
>>
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:149)
>> at
>>
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 67)
>> at
>>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:156)
>> at
>>
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:151)
>> at
>>
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 67)
>> at
>> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972)
> at
>>
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206) at
>>
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:83 3)
>> at
>>
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:732)
>> at
>>
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:61 9)
>> at
>>
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:688)
>> at java.lang.Thread.run(Thread.java:534)
>> This occurs not only with the new templates, but also if a Welcome or
> Empty template is copied from the
>> org.opencms.welcome module to the new module and used for a new page,
> the same thing occurs after save and exit.
>> Additionally, the system leaves a locked ~filename -file (filename
> being the name of the edited file), and the now
>> unusable file that was
>> originally edited.
>>
>> If a page is created with the new template, then switched to use the
> empty template from org.opencms.welcome,
>> editing works fine, and
>> afterwards the page can be again switched to use the new template. Hopefully someone has an idea on what's
>> causing this behaviour.
>>
>> Cheers,
>> Antti Leinonen, Digital One
>>
>> _______________________________________________
>> This mail is send to you from the opencms-dev mailing list
>> To change your list options, or to unsubscribe from the list, please
> visit
>> http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>>
>> _______________________________________________
>> This mail is send to you from the opencms-dev mailing list
>> To change your list options, or to unsubscribe from the list, please
> visit
>> http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>> _______________________________________________
>> This mail is send to you from the opencms-dev mailing list
>> To change your list options, or to unsubscribe from the list, please
> visit
>> http://mail.opencms.org/mailman/listinfo/opencms-dev
>
>
> --
> Jeff Greer
> Technical Support Consultant
> Fretwell-Downing, Inc.
> Phone: (913) 239-1214
>
> The information transmitted in this electronic mail message may contain confidential and or privileged materials.
> For full details and
> restrictions
> see http://www.fdgroup.com/emaildisclaimer.html
>
>
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
--
Jeff Greer
Technical Support Consultant
Fretwell-Downing, Inc.
Phone: (913) 239-1214
The information transmitted in this electronic mail message may contain
confidential and or privileged materials. For full details and restrictions
see http://www.fdgroup.com/emaildisclaimer.html
More information about the opencms-dev
mailing list