Project

General

Profile

Actions

Feature #21618

closed

Save & New Button for t3 CE forgets the previous CE type and starts with "text" Element the second time you click on it

Added by Manfred Rutschmann about 15 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2009-11-19
Due date:
% Done:

0%

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

Description

Create a new text with image ce, press save & new button (the right one) and typo3 starts with a normal text ce. The better one is starting with the same type of ce.

(issue imported from #M12673)


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #29596: When creating content on a page ("Save Document and create a new one") the formerly chosen type of content is forgottenClosed2011-09-09

Actions
Related to TYPO3 Core - Bug #72140: Creating new Content Element with save+new Button fails in third instanceClosed2015-12-10

Actions
Has duplicate TYPO3 Core - Bug #16679: Button for 'Save document and create new one' doesn't load right elementClosedChris topher2006-10-31

Actions
Actions #1

Updated by Chris topher about 15 years ago

The disadvantage with always predefining the type you chose last is, that - if you have last used a typ which you don't need again - you have to change it back again.

Just think of inserting elements which you don't need that often: With your idea you will have to first make extra clicks to choose it AND then make additional clicks to change it back after using it.

All in all I don't think that for an "average" page it makes a big difference whether you have to click everytime you want another element than the one you used before or everytime you don't want a text-element.

Actions #2

Updated by Manfred Rutschmann about 15 years ago

Hello Christopher,

i see this from the other site. when i layout a page and i want a clean layout with a perfect typography, i can not mix various elements. when i make a site it becomes from top to down of the site the same elements, text, or text with images on the left or right side. when i make a tutorial with images i place 10 text with images ce, but when i click on save and new, i think it must be the same element as the last.... when you click in a news record on save an new, you get also a news element... you know? ;-)

Best wishes

Actions #3

Updated by Chris topher about 15 years ago

I see. So the ideal thing would be to make this configurable with a special option.

Actions #4

Updated by Sven Teuber over 14 years ago

I second Manfred. I get feedback from the editors that it is not intuitive if they just worked an a certain content element (say, "image"), and have to manually switch to that element type again after a "Save & New". They intuitively think that the "New"-part has to be context sensitive and "know" they want to insert another element of the same type (another "image").

Editors generally do not think "technical" in terms of "content elements are all the same sort of data, albeit with different properties", but more intuitive like in "I just worked on an image, now I want text, so I have to close the image first". That's one primary thing I learned from giving tutorials and providing end-user-support to about 200 editor's during the last years. :P

So +1 to change this behaviour.

Actions #5

Updated by Chris topher over 14 years ago

Well, as I pointed out above always getting the last used element type again is not the ideal solution.
The best way is to add an option to choose if you want to keep the existing behaviour or if you would like to have the last used element again.
Maybe call it something like options.saveDocNew.rememberLastUsedCEType.

Please create a patch and send it to Core List!

Actions #6

Updated by Simon Schaufelberger almost 14 years ago

Hello,
i also expected to insert the same type again if i use this function

There is also a bug related to that in 4.4.4 and i don't know if i should open another bug report or it is related to this:

if you configured to use the RTE by default and add a new content element with this save and new functionality, the RTE is not loaded in the new ce.

Actions #7

Updated by Stefan Galinski almost 13 years ago

  • Tracker changed from Bug to Feature
  • Target version deleted (0)

Just changed this from bug to feature. Anyone wants to take care of it?

http://wiki.typo3.org/Contribute_Walkthrough

Actions #8

Updated by Alexander Opitz over 11 years ago

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #9

Updated by Sven Teuber over 11 years ago

TYPO3 6.1.1:

- create an element "Bullet list"

- click on "Save and New" - a new element "Bullet list" is created (that's good / expected)

However:

- click on "Save and New" again - a new element "Text" is created

So the error is partially solved (for the first new element), but not gone (consecutive elements still revert to type "Text").

Actions #10

Updated by Alexander Opitz over 11 years ago

  • Status changed from Needs Feedback to New
Actions #11

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.4 (Backend)
Actions #12

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #13

Updated by Benni Mack about 9 years ago

  • Target version deleted (7.5)
Actions #14

Updated by Riccardo De Contardi about 9 years ago

  • Category set to Backend User Interface
Actions #15

Updated by Riccardo De Contardi about 9 years ago

  • Subject changed from Save & New Button for t3 CE starts always with "text" Element to Save & New Button for t3 CE forgets the previous CE type and starts with "text" Element the second time you click on it
  • Category changed from Backend User Interface to FormEngine aka TCEforms

as stated on #29596:

1) It is still present on version 7
2) this happens only the second time you click "save and create new". (3rd comment)

Actions #16

Updated by Riccardo De Contardi over 7 years ago

  • Status changed from New to Closed

I am not able to reproduce it anymore on both version 7.6.16 and 8.7-dev (latest master), so I close it for now.

If you think that this is the wrong decision or experience the issue again then please reopen it or open a new issue with a reference to this one. Thank you

Actions

Also available in: Atom PDF