[TYPO3] "Survey": are you using TYPO3 workspaces?

[christian reiter]

Hello,

Since these client projects started at a time when Typo3 3.6 was coming out,
we have already had to solve this problem anyway, without workspaces. The
strict file separation was simply done with a separation of the staging and
live server, either in two different paths or on two different machines.
Seperation into two servers was the preferred system that these clients were
accustomed to anyway, and some also required it explicitly.

When Workspaces were introduced we evaluated them in comparison to these
projects but it became clear that we would not migrate these existing
clients to the workspace solution.

Being able to control not only the content but also the layout was very
important since it is common that a website or part of a website is
redesigned or has changes to the template, and these need to be evaluated by
the different departments at the client company just like the content.

Right now we simply have the situation that our traditional clients who want
staging are looking in the direction of server separation. This does not
make the workspaces a bad solution, it just means that it is not the right
solution for these specific clients (who are mostly pharmaceutical
companies, and have some requirements that are not typical of most TYPO3 use
cases anyway). Trying to change the workspaces to fulfill our requirements
seems even more complicated than the work we did to set up the page/branch
oriented Test-to-Live server publishing solution for these clients.

Greetings,

Christian Reiter

"Martin Kutschker" <Martin.Kutschker at n0spam-blackbox.net> schrieb im
Newsbeitrag
news:mailman.1.1152271392.18323.typo3-english at lists.netfielders.de...
> christian reiter schrieb:
> >
> > 1.   It must also be possible for a fileadmin/ file that exists on Draft
to
> > be in a different version or  also totally nonexistent on Live, i.e. if
the
> > file is 'recalled' it must not be able to access it on live even in
> > knowledge of the full URL.
>
> You could use a versioned version of a "safe-downloads" extension, where
> the actual files are not simply served via the file system.
>
> > In general, all files associated with the website (all pdfs, images but
also
> > all javascripts, CSS, HTML templates for extensions or content
rendering)
> > must be separable in Draft and Live.
>
> The workspaces are meant for the content, not the layout. But you can of
> course version your TS templates. As there are no means for the WS-API to
> parse the TS content you have to use different versions of HTML-templates
> and resources (CSS, images) yourself.
>
> I cannot think of technical means to achieve your requirements.
>
> > 2. Continuity of anchor links and insert record elements must be given
in
> > all circumstances
>
> I proposed to link against an "object id". The idea will be created when
> the record is created (could very well be the initial uid, but it doesn't
> really matter). This "object id" is shared by all versions of the object.
>
> Now all link creating routines use the "object id" instead of the uid of
> the record. The rendering routines will have to select the correct uid of
> the "object id" based on the context (which workspace, which version).
>
> I thinkt that this scheme could work, but upgrading an existing
installaion
> may be hard or even impossible.
>
> Masi