[opencms-dev] Importing over existing content

[Paul D. Bain]

Brendon,

         I had difficulty understanding your email. I decided to edit it in 
order to improve its clarity, but I am not certain that the edited content 
expresses your intended meaning. Does the edited email (below) accurately 
reflect your intended meaning?

-- Paul Bain

At Tuesday 7/1/03 04:23 PM, Brendon Price wrote:
>
>[W]e discovered an interesting feature of  .  .  .  export and import.
>
>When content is imported, the associated content type (page, link, folder, 
>etc.) is [also imported], but the content type launcher is not [made] part 
>of the manifest.xml file. [OpenCMS] seems to [infer] the correct launcher 
>to apply based on the content type, which [inference is correct] in almost 
>all cases.
>
>However, [suppose] you already have a "page" resource (for example, a file 
>"/internet/index.html"). [If] you
>import  .  .  .  content that includes a file of type "link" called 
>"/internet/index.html,"  .  .  .  because the resource already exist[s], 
>[OpenCMS] updates the resource type (as it should), but fails to update 
>the launcher type. So the [file] "index.html" is launched with the page 
>launcher, which expects an XML file to render, [causing OpenCMS to fail] 
>with an XML parser exception[, as indicated in the following stack trace:]
>
>[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 [has] 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 [a second] time, it is associated 
>with the correct launcher type.