Tridion unwrapping removes localized / parent files

We are experiencing strange behavior when publishing pages in Tridion.

We have English pages in publication 050 and the same pages are localized in publication 060. Take an example accounts page ( tcm: 120-1234 ) in English and on the same localized page ( tcm: 125-1234 ) in Spanish Publishing ...

When we publish the English page, accounts, it is published successfully, but the local deployer deletes its Spanish page ( tcm: 125-1234 ). When we publish a Spanish page, it deletes its English page ( tcm: 120-1234 ).

We checked the deployment side and confirmed that another file is being removed from the server itself.

Please refer to the deployment log for instructions on how to remove the page. But we don't know why it is deleting another publish file. Is this related to the same page id? I think it shouldn't as it is localized.

DEBUG FSEntityManager - Deleting pagemeta / pageurl / business / accounts.content in tcm transaction: 0-754-66560.

We understand from this log that it was instructed by the deployer, but not sure how or why it was requested. We analyze what the FSEntityManager class does.

Can anyone help me with this?

+3


source to share


2 answers


If the file system is used to store content and metadata, the content of the master or child publications will be written.

To accommodate this, set explicit metadata settings in the cd_storage_conf.xml file to ensure that all metadata does not end up in the same store, for example:



<Storage Type="filesystem" Class="com.tridion.storage.filesystem.FSDAOFactory" Id="defaultFile" defaultFilesystem="false">
    <Root Path="c:\published\localFileSystem" />
</Storage>
<Storage Type="filesystem" Class="com.tridion.storage.filesystem.FSDAOFactory" Id="defaultDataFile" defaultFilesystem="true" defaultStorage="true">
    <Root Path="c:\published\localFileSystem\data" />
</Storage>

<ItemTypes defaultStorageId="defaultFile" cached="false">       
        <!-- Query type mapping is replacement for Query gnenerator. If there was query generator defined in a Broker configuration then  Query type mapping should be binded to default DB. -->
        <Item typeMapping="Query" storageId="defaultdb"/>

        <Item typeMapping="PageMeta" cached="true" storageId="defaultDataFile"/>
        <Item typeMapping="ComponentPresentationMeta" cached="true" storageId="defaultDataFile"/>
        <Item typeMapping="ComponentMeta" cached="true" storageId="defaultDataFile"/>

</ItemTypes>

      

+3


source


It looks like both posts have the same web router. Check Conf store properties and publish paths.



+5


source







All Articles