Bug #92846
closed
Workspace: changes not always listed in workspace modul
0%
Description
Description:
Tested with TYPO3 9.5.22
We have observed that not all changes made on a page in the workspace (e.g. creating, moving, editing etc.) were recorded as changes in the regular workspaces module (WEB - Workspaces). The workspace module simply remained empty for this page, but the page was marked as "edited" (yellow) in the page tree - which is correct, because it was edited.
We do not know what causes this issue. It cannot always be reproduced.
In an emergency, the idea came up to undo the unwanted adjustments in the workspace via the workspace page history. However, this had unwanted effects on the LIVE version of the site, here elements were suddenly missing.
Example:
We edited the page "Showcase" in the workspace: we added a regular "Text and Images"-element.
The page is marked as edited in the pagetree (yellow highlight).
We switch to the workspace module (WEB - Workspaces) and see no changes for "this page" - the module is empty, although the page was edited.
We are not able to undo or deploy the changes easily.
Question:
Why are some changes not recorded in the workspaces module (WEB - Workspaces), does one have to pay attention to something special?
Why does editing the page history in the workspace affect the live version?
Can the regular page history function in the workspace be deactivated?
Files
Updated by Matthias Hinner about 4 years ago
PHP: 7.4
TYPO3 Version 10.4.10
The same behaviour I can see under 10.4. It does not always occur and I could not reproduce it yet.
As a workaround, the release can be done in preview.
Updated by Christian Kuhn almost 4 years ago
- Status changed from New to Needs Feedback
In 90% of cases, this is due to a 'dirty' reference index.
It especially (did) occur when dealing with FAL relations (eg. content element text&images).
The workspace module is quite fragile when the reference index is not clean, and adding FAL relations in workspaces triggered this. The result is that the workspace module itself loads, but the ajax call that fetches changed records fails. This leads to an 'empty' workspace module.
We've had a series of patches to keep the reference index clean when working with FAL in workspaces lately for core v10, but existing instances may need a refindex update run.
Please update your reference index - For example by calling bin/typo3 referenceindex:update on CLI. This should fix all broken refindex entries once. After that, the workspace module will probably work again. If the issue is still reproducible even with clean refindex, we'll have to dig deeper.
Note that these reference index related bug fixes were not applied to core v9, so v10 should be better after fixing refindex once for existing instances.
Updated by David Menzel over 3 years ago
- Related to Bug #93645: Workspace pagination empty and Javascript error: Uncaught (in promise) TypeError: t is undefined added
Updated by Benni Mack about 3 years ago
- Status changed from Needs Feedback to Closed
I close this issue now due to lack of feedback after 3 months. Let me know if you think this decision is wrong, so I will re-open the ticket.