[opencms-dev] Interesting discovery with Import over existing content

[Brendon Price]

Hi List,

Just thought I would let people know that we discovered an interesting
feature of the export and import.

When content is imported the associated content type (page, link, folder
etc) is part of the import, but
the content type launcher is not part of the manifest.xml file. It seems to
work out the correct launcher 
to apply based on the content type which works in almost all cases.

However when you already have a "page" resource (for example
/internet/index.html ). Then you 
import all your content that includes a file of type "link" called
/internet/index.html, you find that
because the resource already existed it updates the resource type (as it
should) but fails to update the
launcher type. So the index.html is launched with the page launcher, which
expects an XML file to render,
so it fails with an XML parser exception.

[18.06.2003 13:47:37] <opencms_critical> [CmsXmlControlFile] Cannot parse
XML file "/internet/index.html". org.xml.sax.SAXParseException: Content is
not allowed in prolog.

This seems to happen if you accidentally overwrite a file that is the same
name but has a different type.
You can correct the issue by deleting the offending cms file from the
cms_resource table, and then re-importing
the content. When the file is imported this time it is associated with the
correct launcher type.

Regards

Brendon Price
Software Engineer
Software Solutions Team
Sytec Resources Limited
	

Important:  This electronic mail message and attachments (if any) are
confidential and may be legally privileged.  If you are not the intended
recipient please contact us immediately and destroy this message.  You may
not legally copy, disclose, disseminate or use the contents in any way.
Thank you.