Project

General

Profile

Actions

Bug #59363

closed

Problem with New Content Wizard when in List mode

Added by Roel Krottje over 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2014-06-05
Due date:
2014-06-30
% Done:

0%

Estimated time:
1.00 h
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

In TYPO3 6.2.3 I'm experience a back-end admin user experience issue.

When in List mode, and after I click on a page so its contents appear at the right, I click the greenish 'Create New Record' icon at the top. When I select "Create a new content element --> Click here for wizard!", and select for instance "Header Only" (or any element for that matter), the Header of the next page changes to "Create new Page Content on root level", instead of "Create new Page Content on Welcome Page", which is the page that I selected.

However, when in Page mode, and I first select a column and then add a new element via the same Click here for wizard option, there's no problem, and everything works out as expected.

Shouldn't - by default, also in the case of List, column #0 be selected? I have a custom Backend Layout configured for this page, and everything works very good - except that I can't use the "Click here for wizard" content wizard when in List mode. Is this a bug or did I mis-configure something? The very same TypoScript setup worked perfectly when used in TYPO3 6.0 or 6.1, but not in 6.2.

Thanks!


Related issues 2 (0 open2 closed)

Is duplicate of TYPO3 Core - Bug #59059: New Content Element gets pid 0ClosedNicole Cordes2014-05-23

Actions
Is duplicate of TYPO3 Core - Bug #59340: New content wizard broken in 4.5.34Closed2014-06-04

Actions
Actions #1

Updated by Roel Krottje over 10 years ago

  • Assignee deleted (Roel Krottje)
Actions #2

Updated by Markus Klein over 10 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (next-patchlevel)

Seems to be a duplicate of #59059, which is already resolved on current master.
Please verify if the patch linked there solves the issue for you.

Actions #3

Updated by Alexander Opitz about 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF