Project

General

Profile

Actions

Bug #11572

closed

Creating new pages in the workspace creates the page also live

Added by Susanne Moog almost 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
Workspaces
Target version:
-
Start date:
2010-12-19
Due date:
% Done:

0%

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

Description

Creating new pages in the workspace creates the page also live,

meaning if I create a new page in a workspace and then switch to live the page is there, too (only hidden).


Files

newpage.PNG (13.2 KB) newpage.PNG Tolleiv Nietsch, 2010-12-19 09:22
out.avi (1.68 MB) out.avi Screen capture of my problem Susanne Moog, 2010-12-19 10:07
11572.patch (630 Bytes) 11572.patch Tolleiv Nietsch, 2010-12-19 10:50
11572_v2.diff (997 Bytes) 11572_v2.diff Susanne Moog, 2010-12-19 11:06
Actions #1

Updated by Tolleiv Nietsch almost 14 years ago

I'd say the data looks fine - there's a workspace-records and a placeholder both have a workspace-id - that's what we're supposed to see. I think this fact that the icon changed is more a GUI issue - so who can we blame for that?

thanks for keeping the eyes open :)

Actions #2

Updated by Susanne Moog almost 14 years ago

I think we are talking about different things (or I don't understand you ;)). I've made a small screen capture so you can see what I mean: The page I create in a workspace should - as far as I understand - not be automatically created live, or should it?

Actions #3

Updated by Tolleiv Nietsch almost 14 years ago

We're talking about the same thing - the page is actually not created in the live-workspace but there's a placeholder which (for some reason) shows up, although he is not supposed to be visible there. But the data itself is right - it's just that the page-tree shows that page also in the Live-workspace. - is there any chance we can move this issue to their bugtracker?

Actions #4

Updated by Susanne Moog almost 14 years ago

I don't think it's a tree bug. I think it's more a core bug, but I'm not really sure because I don't know enough about workspaces yet. Should the function versioningPlaceholderClause (t3lib_befunc) take care of not showing initial placeholders?

Actions #5

Updated by Tolleiv Nietsch almost 14 years ago

yes kind of - I see your point the attached patch fixes it for me. But I'm not sure if this can break anything else. Going to test that on Monday a bit more...

Actions #6

Updated by Susanne Moog almost 14 years ago

Please have a look at my version, too - after thinking a bit about the function I think we don't need the if-statements at all and so far it's working that way for me :)

Actions #7

Updated by Peter Niederlag almost 14 years ago

Old GUI way was to include and show NEW/MOVE PLACEHOLDERS (t3ver_state=1|3) in page-tree of live workspace. Wether showing or not showing them in the GUI is rather a matter of taste(seems nonsense to me, as updates/deletes were not shown) it is quite crucial to keep an eye on the underlaying API IMO. It might as well be useful/required to construct trees/lists for pages/other tables in a preview of a workspace. For this one does need to get those pages/data included (maybe even including applying pid and sorting properly). To me it seems like 'function versioningPlaceholderClause()' should maybe be capable to handle BOTH cases (boolean $includePlaceHolders)?

hth and many thx for your tremendous work! :->,
Peter

Actions #8

Updated by Sonja Schubert almost 14 years ago

  • Status changed from Needs Feedback to Accepted
  • Target version set to 4.5 Beta 3
Actions #9

Updated by Tolleiv Nietsch almost 14 years ago

  • Target version changed from 4.5 Beta 3 to 4.5 RC1
Actions #10

Updated by Tolleiv Nietsch almost 14 years ago

  • Assignee set to Tolleiv Nietsch
Actions #11

Updated by Tolleiv Nietsch almost 14 years ago

  • Status changed from Accepted to Needs Feedback

@Susanne - your patch looks good for me and is working as expected, are you going to create the RFC?

@Peter - it's too late for an API change in 4.5, let's do that in 4.6 - hope that's fine for you?

Actions #12

Updated by Susanne Moog almost 14 years ago

  • Status changed from Needs Feedback to Under Review
Actions #13

Updated by Susanne Moog almost 14 years ago

  • Status changed from Under Review to Resolved
Actions #14

Updated by Michael Stucki almost 11 years ago

  • Category set to Workspaces
Actions #15

Updated by Michael Stucki almost 11 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
  • Target version deleted (4.5 RC1)
Actions #16

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF