Project

General

Profile

Actions

Bug #15955

closed

error message on moving elements in draft workspace

Added by ben van about 18 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Category:
Workspaces
Target version:
-
Start date:
2006-03-31
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Users experience the error messages with workspaces as system errors or bugs. A friendlier notification would be more appropriate. The red circle with the white cross is like a red flag to a bull ;-) The error message when you want to move elements in a draft workspace is this at the moment:

1: Move attempt failed due to workspace restrictions: Record could not be edited in workspace: Online record was not in versionized branch! Could not insert record from table "tt_content" in destination PID "1446" (pr "pages")

These are four messages that all mean the same. This needs to be more decriptive or meaningful. I would suggest to change this to an alert with the exclamationmark icon (instead of red circle/white cross) as used in more places in the backend. F.I. with GDLIB not found. And not using the header "Error", but "Note" The contents of the alert depends on moving content elements or pages.

For contentelements:
1: Move attempt failed due to workspace restrictions: If you want to move content elements within this page you are advised to create a new version of this page.

For pages:
1: Move attempt failed due to workspace restrictions: Moving pages is not possible in a draft workspace unless you create a special branch version.

(issue imported from #M3076)

Actions #1

Updated by Andreas Wolf over 17 years ago

Well, I think this is a serious error - it makes moving pages impossible for people without access to the live-workspace. I have disabled branch-versioning globally because of some other critical bugs (e.g. #3024), so my colleagues are not allowed to create branch-versions.

It should be possible to move a page without creating a branch-version - the only thing neccessary is changing the pid. It doesn't even really affect sub-pages of the moved page as they only refer to their direct parent, which is either moved itself or in the moved branch. Nothing needs to be changed with these pages, so it doesn't hurt them in any way.

Actions #2

Updated by Andreas almost 17 years ago

I'm facing this issue again:

Errors:
1: Move attempt failed due to workspace restrictions: Record could not be edited in workspace: Online record was not in versionized branch! Could not insert record from table "pages" in destination PID "xxx"

Is there any patch or solution out there. Actually it would be urgend. Would sponsor a solution to fix this, so that moving a page or record is possible - should be in the next weeks - August 2007. Sounds like if I'm daydreaming I know ;-)

Actions #3

Updated by Ralf Hettinger almost 17 years ago

Andreas, this issue is (unfortunately not very widespread) known from the very beginning of workspaces:
http://lists.netfielders.de/pipermail/typo3-dev/2006-March/017174.html

I would think that it might be a good idea if you posted your sponsoring suggestion to the corresponding thread at the dev-list...

Actions #4

Updated by Dmitry Dulepov over 16 years ago

Moving items in workspaces is resolved by Kasper in TYPO3 4.2. It is supported only for "Element" versioning type.

When it comes to error messages, it is more difficult because they come from the core and it is not always poissible to determine why exactly moving failed.

Actions #5

Updated by Michael Stucki over 10 years ago

  • Category set to Workspaces
Actions #6

Updated by Michael Stucki over 10 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
  • Target version deleted (0)
Actions

Also available in: Atom PDF