[TYPO3-english] Website Synchronisation

[bernd wilke]

Am 05.06.14 17:11, schrieb Christian Reiter:
> Hi,
>
> Of course if the type of changes that need to be staged fit inside that
> which can be done with workspaces, that is preferrable because it is
> there out of the box.
>
> In the projects where I have worked with content staging, there were
> usually requirements that didn't fit so well with Workspaces although I
> am not up to date with the newest developments.
>
> "Content" as perceived by the users often doesn't consist just of the
> database but also of the files associated with it.
>
> How do I solve situations with workspaces where file contents at the
> same path (images, PDF downloads etc) are different between stage and live?
>
> for example I am updating the pages for a product. There is new text in
> tt_content etc but I am also overwriting "Operating_Manual.pdf" and
> "Packshot.jpg" to reflect the changes, but the files need to remain at
> the same place. I want existing links to the manual (including on
> external sites) to deliver the new version after publishing so the path
> must remain the same.
>
> Can workspaces do that today?
>
> i.e. - "Workspace Stage: fileadmin/products/1/Manual.pdf" has a
> different binary file content than "Workspace Live:
> fileadmin/products/1/Manual.pdf" - possible?
>
> The big advantage of content staging is that it allows the systems to be
> separate and "anything goes" without for instance any extension ever
> having to be "enabled" or "adapted". I remember lots of problems with
> extensions, or relations, that wouldn't play nice with WS and this
> usually involved digging deep into the structures.
>
> With staging servers you can do anything you want and the single
> bottleneck is the implementation of data transfer. No fixing of other
> extensions ever.

just imagine you can upload files but can not rename them afterwards.

the solution is: don't update the file in place but change the CE to 
reference a new file.

using FAL can make the handling easier as one file changed globaly can 
be realized by a new reference in one record instead of changes in all 
records by changing the reference to this file.

bernd
-- 
http://www.pi-phi.de/cheatsheet.html