Bug #5296
Editing form doesn't respect current workspace
| Status: | Accepted | Start date: | 2009-11-10 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Jeff Segars | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Using 4.3 beta 3 (as an upgrade from 4.3 beta 1), Admin logged in to custom workspace. Page appears with workspace content (version active in the workspace), but when a page element is chosen for edit, the editing form shows the Live version. Closing the editing form reverts displayed page to the Live version of the page until refreshed.
Probably related, each save to the content of the page element in the front end editing form seems to create a new versions in the workspace (appears to act as new edit of existing non-versioned page) regardless if an updated version already exists in the workspace.
Related issues
| related to Advanced Frontend Editing - Bug #8970: In Custom Workspace no drag & drop possible, hide and del... | New | 2010-07-21 |
History
Updated by Jan Gebauer over 3 years ago
Hi,
same here with 4.3 final.
It also ignores language settings and always shows the default language in the edit form.
... and the worst:
An editor, who has only rights to edit a workspace, can edit the live version, given he has access to the FE-Edit!
Otherwise, it's a great improvement above the old FE-Edit! Good work guys!
Updated by Jeff Segars over 3 years ago
- Status changed from New to Accepted
- Assignee set to Jeff Segars
I've been investigating the workspace part of this issue and there are some code changes needed in feeditadvanced but the larger problem is that the "version" extension is not loaded in the frontend context due to the doNotLoadInFE flag in ex_emconf.php. Trying to find a workaround for this now...
Updated by Jeff Segars over 3 years ago
I added the first step toward workspace support in r1764. The problem with "version" not being loaded in the frontend still remains, however, As a temporary solution, you can open typo3conf/localconf.php and modify $TYPO3_CONF_VARS['EXT']['extList_FE'] to include the version extension. From my quick testing, it seems to work properly after this.
Updated by Mark Johnston over 2 years ago
Update - seems to have been fixed in my testing with feeditadvanced 1.4.0 on TYPO3 4.4.3, as long as the extension [version] is included in the $TYPO3_CONF_VARS['EXT']['extList_FE'] list in localconf.php