[TYPO3-english] Import-export of *.t3d

[Christian Reiter]

Hi Viktor,

There can of course be problems if you want to publish records from a 
certain database into a system where that same record type is also being 
created and edited in parallel.

Very simply, any random new ID xyz which is a certain record on your 
source system might already be occupied by a different content on the 
live system.
T3D promises to solve this but fails.
When you're doing record publishing, you will either have to overwrite 
the content, or rewrite the IDs on the fly, which may start breaking 
things once you are looking at references that are outside of the 
published changeset. Or you have to link up the servers to synchronize 
ID spaces, at risk of running into collisions/race conditions.

 > That would be perfect scenario. Can you recommend such a nextension? I
 > can't find some in ER...

You might look for "contentstage". However I have no real world 
experience with it.

I've been working with an extension "Test to Live Server Publishing" 
for cross-server content staging which branched out of a client project 
several years ago, this is currently running on 6.2 and 7.2. If you find 
this may be helpful I can of course supply more information.

Best regards,
Christian




Am 15.05.2015 um 12:38 schrieb Viktor Livakivskyi:
> Hi, Christian
>> What you are doing sounds more like "content transfer/publishing" or
>> "content staging" of pages/page trees with their relations, instead of
>> export/import.
>>
>> Are you also creating new pages on the production server you are
>> deploying to, or is it just used for content delivery?
>
> Yes, pages are also created, if needed.
> In a nutshell process is as follows:
> 1. Customer asks for a new functionality, which can be a part of
> existing pages/plugins or it can be some seaparte branch of a website.
> 2. Functionality is created on a dev system and is shown from time to
> time to the customder.
> 3. At the end it is deployed to staging system (code only, content is
> put by hand), where customer adjusts content to his needs.
> 4. As a last step deploy to a live system (code+content) is made
>
>
>> If you are using the production server for delivery (apart from purely
>> FE-created content like forum posts, comments etc) then a solution
>> would be useful, where you can label some pages as "approved for
>> production" and then transfer them to the production server along with
>> all translations, FAL relations, files, IRRE records etc etc.
>> There are some extensions that will do that, I have been working with
>> such scenarios successfully for several years.
>
> That would be perfect scenario. Can you recommend such a nextension? I
> can't find some in ER...
>
>
>> When it comes to T3D export/import my experiences have been negative.
>> I last tried it on 6.2 in March, the result was that FAL relations
>> where not properly imported, references from flexforms got lost and
>> localizations got scrambled, the result was unusable.
>
> I've got same result, which ended up in this topic :)
>
> Thank you.