Bug #20921
closed
Calendar Base items not visible in Workspace Preview until published to Live site
Added by Mark Johnston over 15 years ago.
Updated almost 11 years ago.
Description
Steps to reproduce:
- Custom Workspace
- Editor (even admin) creates a calendar item and saves it
- Generate the workspace preview link and navigate to calendar page
Result:
calendar item not visible in preview
Have attempted to push to workflow step Review or Publish with the same result.
Note in the attached that a version 1.0 calendar record (hidden) is created for the live site, and that record will remain hidden until the item is marked published. What appears to be happening is that the Preview calendar is displaying the live site items only.
(issue imported from #M11780)
Files
- Status changed from New to Closed
- Target version deleted (
0)
It is not possible to preview records like tt_news in the workspace by simple clicking on "Preview record". In addition the calendar extension it self must support workspaces which seems not in your case.
Two claims are being made in dismissing this bug report:
- it is not possible to preview records like tt_news in a TYPO3 workspace, and
- Calendar Base does not support workspaces
Claim 1 is incorrect, as we are using that very functionality regularly on our site, now in TYPO3 4.4.x. As stated in the report, we use the "Workspace preview" capability of the software rather than "Preview record" assumed by the comment to accomplish this feature. (I am writing this note so that anyone who may review this report in the future will not be confused about what is and is not possible using these tools.)
About claim 2, what is the best way to learn what is required for an extension to support workspaces as stated? It is certainly the case that Calendar Base records are kept in a separate version for the workspace and the Live site. What I hear being said in closing this bug report is that it is the responsibility of the extension (in this case Calendar Base) to conform its display to the workspace which is active and not a problem with the workspaces extension. Am I understanding this correctly? Once again, a pointer to what design features an extension needs to incorporate to support workspaces would be appreciated.
- Category set to Workspaces
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 