Project

General

Profile

Actions

Feature #16359

closed

"merge version" feature for Web>page

Added by Martin Kutschker almost 18 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2006-07-18
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

It's possible to get stuck with auto-versioning and no restrictions on version types. The editor may end up with the problem that TYPO3 cannot create any new version:

Message: 'Versions found on page, no "Page" versioning possible'

So he has to publish it before he can change the contents again.

A solution and nice feature for other situations is the "merge versions" feature. The idea is that the new page version subsumes and obsoletes the element versions on this page. That is all element versions are merged into one page version.

(issue imported from #M3866)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #15256: Workspaces Usability-ProblemClosed2005-12-04

Actions
Actions #1

Updated by Martin Kutschker over 17 years ago

Dmitry, do you think this is complicated?

IMHO, a merge feature would also create a workaround for the no-moving-of-elements-on-a-page-problem.

Note: the WS versioning type restrictions have to be checked.

Actions #2

Updated by Dmitry Dulepov over 17 years ago

No idea, need to look to the code.

Actions #3

Updated by Tolleiv Nietsch about 13 years ago

  • Category deleted (Miscellaneous)
  • Status changed from New to Closed
  • Target version deleted (0)

Not relevant anymore because page versioning is deprecated and won't be maintained anymore.

Actions #4

Updated by Michael Stucki over 10 years ago

  • Category set to Workspaces
Actions #5

Updated by Michael Stucki over 10 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions

Also available in: Atom PDF