Bug #19956

Page alias not publishing to LIVE from any workspace

Added by David Wallace about 11 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2009-02-02
Due date:
% Done:

0%

TYPO3 Version:
4.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

NB: relisted as previous issue does not seem to have been addressed (0008657)
This happens for both of the following situations;

1) Update an alias entry for a page that already exists in LIVE, then publish to LIVE
2) Create a new page in a workspace and add a page alias, then publish to LIVE

LIVE editing of page alias works fine, but updates to page alias in any workspace are not transferred during the publish process. The alias will not publish via either the entire workspace publish or individual page publish, no errors are reported by Typo3 during the publishing process.

Create a new page in a workspace and add a page alias, then publish to LIVE. Page alias has disappeared

Original report number 0008657 but no action taken by team. Upgraded report to major as impact on users in workspace is growing.... creating new content in workspace requires manual re-creation of page alias after publishing
(issue imported from #M10330)


Related issues

Related to TYPO3 Core - Bug #45519: Workspace Preview Link Generator problem Closed 2013-02-15
Related to TYPO3 Core - Bug #23870: Field alias not displayed in Workspace Closed 2010-10-29
Related to TYPO3 Core - Bug #66834: Numeric suffix (0) added to unique fields in workspace records Needs Feedback 2015-05-07
Related to TYPO3 Core - Bug #52070: 'eval' => 'unique' and Versioning don't work as expected New 2006-06-26
Duplicated by TYPO3 Core - Bug #18928: Page alias not publishing to LIVE from any workspace Closed 2008-06-09

History

#1 Updated by Marcus Krause about 11 years ago

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

#2 Updated by Martin Holtz over 10 years ago

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.

#3 Updated by David Wallace over 10 years ago

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

#4 Updated by Thomas Trethan about 9 years ago

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 ($tmp0) {
$oid = intval($tmp0['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']);

#5 Updated by Tolleiv Nietsch over 8 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)

would you mind to attach a patch file or push it to git.typo3.org as described in http://wiki.typo3.org/Contribution_Walkthrough_Tutorials

#6 Updated by Tolleiv Nietsch about 8 years ago

still relevant?

#7 Updated by Michael Cannon almost 8 years ago

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.

#8 Updated by Stefan Neufeind over 7 years ago

Michael, please have a look ...

#9 Updated by Michael Stucki about 6 years ago

  • Category set to Workspaces

#10 Updated by Michael Stucki about 6 years ago

  • Project changed from Workspaces & Versioning to TYPO3 Core
  • Category changed from Workspaces to Workspaces

#11 Updated by Gerrit Code Review about 6 years ago

  • Status changed from Needs Feedback to Under Review

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

#12 Updated by Gerrit Code Review about 5 years ago

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

#13 Updated by Mathias Schreiber about 5 years ago

  • Target version set to 7.5

#14 Updated by Gerrit Code Review almost 5 years ago

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

#15 Updated by Gerrit Code Review almost 5 years ago

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

#16 Updated by Gerrit Code Review almost 5 years ago

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

#17 Updated by Gerrit Code Review almost 5 years ago

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

#18 Updated by Gerrit Code Review almost 5 years ago

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

#19 Updated by Gerrit Code Review almost 5 years ago

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

#20 Updated by Gerrit Code Review almost 5 years ago

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

#21 Updated by Gerrit Code Review over 4 years ago

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

#22 Updated by Gerrit Code Review over 4 years ago

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

#23 Updated by Gerrit Code Review over 4 years ago

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

#24 Updated by Gerrit Code Review over 4 years ago

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

#25 Updated by Gerrit Code Review over 4 years ago

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

#26 Updated by Benni Mack over 4 years ago

  • Target version changed from 7.5 to 7 LTS

#27 Updated by Gerrit Code Review over 4 years ago

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

#28 Updated by Benni Mack over 4 years ago

  • Target version deleted (7 LTS)
  • Is Regression set to No

#29 Updated by Gerrit Code Review over 4 years ago

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

#30 Updated by Mathias Schreiber about 2 years ago

  • Status changed from Under Review to New

#31 Updated by Benni Mack over 1 year ago

  • Status changed from New to Rejected

Hey everyone,

this feature has been superseded by the new Page-based URL slug handling. The field pages.alias had various drawbacks and will be removed in TYPO3 v10.0. If you still experience issues with the new handling, please open up a new ticket.

Thanks.
Benni.

Also available in: Atom PDF