TYPO3 Core

Pascal claims in #8657:
This is also the case for 'Speaking URL path segment' - It is not transferred to the LIVE environment upon publish.

see: http://typo3.org/documentation/document-library/core-documentation/doc_core_inside/4.2.0/view/2/7/

Unique fields like a page alias or user name are tricky in a versioning scenario because the publication process must perform a check if the field is unique in the “Live” situation. The implications of implementing this means that we have chosen a solution where unique fields are simply not swapped at all! It means that publication of a new version of a page cannot and will not alter the alias of the live version. The “Live” unique value will remain until changed in the live version.

You can hide fields with the “unique” keyword when they are offline versions. This is done with the display condition:

'displayCond' => 'VERSION:IS:false',

so, it seems to be a missing feature to me.

Will look into this further, but this is a feature that should be assessed to be added.

I am using workspaces for editors to create/modify content and preview. If they create new pages and include an alias (as per our standard practice), they will need to manually change all of these once the content is released from the workspace. This would seem to be a reasonable, functional, expectation?

I would expect at the very least that any alias that is being updated in a workspace that already exists in LIVE would be locked against an update? It just seems odd that we change change (almost) everything in a workspace except the alias.

Fingers crossed someone can provide a workaround to this, will check out the 'displayCond' config also.

Cheers

Idea: make unique fields like alias unique within all workspaces.
adaption in typo3 4.5 lts that worked for me:

t3lib/class.t3lib_tcemain.php:

1369c1369
< if ($field && $realPid >= 0) { // Field is NOT set for flexForms - which also means that uniqueInPid and unique is NOT available for flexForm fields! Also getUnique should not be done for versioning and if PID is 1 ($realPid<0) then versioning is happening...
--

if ($field) { // Field is NOT set for flexForms - which also means that uniqueInPid and unique is NOT available for flexForm fields! Also getUnique should not be done for versioning and if PID is -1 ($realPid<0) then versioning is happening...

2042c2042,2046
< $whereAdd .= ' AND pid>=0';
---

$tmp = $GLOBALS['TYPO3_DB']->exec_SELECTgetRows('t3ver_oid', $table, 'uid='.intval($id));
if ($tmp⁰) {
$oid = intval($tmp⁰['t3ver_oid']);
$whereAdd .= ' AND uid!='.$oid.' AND t3ver_oid!='.$oid;
}

typo3/sysext/version/class.tx_version_tcemain.php

767c767
< $keepFields = $tcemainObj->getUniqueFields($table);
---

$keepFields = array();

and of course:

unset($TCA['pages']['columns']['alias']['displayCond']);

still relevant?

still relevant, will try for the patch TYPO3 4.5.15. Also, trying to work around issues of appending index on uniquelocal fields for versions of original records.

Michael, please have a look ...

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 10 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 11 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 12 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 13 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 14 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 15 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263

Patch set 16 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/27263