TYPO3 Core

Possibly related to #5817

Oliver, can you provide more information? Description is too short.

Hello Dmitry. The Sitemap Content Element does not work in the Workspace Context.

Testcase:
Create a Sitemap Content Element in Live WS
Create a Workspace Version of Page with the Sitemap in it.
Check if the Sitemap is being displayed
Publish the Page
Check if the Sitemap is being displayed

But I am not sure if this is still in 4.1.x it was in 4.0.x

Cheers Olivier

I can confirm that. I use custom tt_content.menu elements a lot and if a HMENU within one of those custom menus should display fields from the pages table (e. g. media, description, custom fields) the output will always show the content of the fields from the live version.

But it should display the contents of the current workspace version instead. So when you have a site that uses sitemap elements a lot, the workspace system can`t be used for a staging workflow.

I can confirm this on TYPO3 version 4.3.2.

I've attached the patch that solved this issue for me, can someone (i think I has to be someone from the core team, right?) test it and confirm that it works?

I'm not sure if this is correct diff file, so I'll post how to modify it manually.

The problem was with file typo3/sysext/cms/tslib/class.tslib_menu.php after line 516, before

// Add external MP params, then the row:
if (is_array($row)) {
if ($MP) $row['_MP_PARAM'] = $MP.($row['_MP_PARAM'] ? ','.$row['_MP_PARAM'] : '');
$temp[] = $this->sys_page->getPageOverlay($row);
}

I've placed 4 lines

//Add versioning overlay for current page (to respect workspaces)
if(is_array($row)){
$this->sys_page->versionOL('pages',$row,true);
}

The problem was that array with page record was not overlaid with versioning information. Looks like just 4 lines of code solved the issue.

Committed to trunk rev. 7364