Project

General

Profile

Actions

Bug #50021

closed

Page module: Edit column uses wrong CE's after drag&drop

Added by Bernhard Kraft over 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Start date:
2013-07-15
Due date:
% Done:

0%

Estimated time:
4.00 h
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

When elements get moved around between columns using the page module drag&drop feature there is a problem when using the "Edit all content elements in this column" pencil afterwards.

Way to reproduce:

1. Create a page with two content elements in different columns.
2. Use the "Edit all content elements in this column" pencil in the top right area of a column. This works correctly and only edits the content element in this column
3. Move one of the content elements below the other using the drag&drop feature.
4. Use the "Edit all content elements in this column" pencil of the column with the two elements without reloading the page --> Fail. Only the original content element in the column gets edited.

If the pencil of the afterwards empty column is used the content element which was previously there will get edited.

Proposed solution: After a click on the pencil a AJAX script should get fired to determine all content elements in the specified column and then redirect to tce_db.

Alternative solution: Introduce an option to tce_db to select page/colPos of content elements which should get edited.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #80414: Page Module Drag&Drop: Prevent reloading module frame if content element is dropped at its original positionClosed2017-03-23

Actions
Actions #1

Updated by Philipp Gampe over 11 years ago

  • Status changed from New to Accepted

I can confirm this.

Actions #2

Updated by Mathias Schreiber almost 10 years ago

  • Target version changed from next-patchlevel to 7.4 (Backend)
Actions #3

Updated by Susanne Moog over 9 years ago

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

Updated by Benni Mack about 9 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #5

Updated by Michael Oehlhof about 9 years ago

  • Status changed from Accepted to In Progress
  • Assignee set to Michael Oehlhof
  • Is Regression set to No
Actions #6

Updated by Michael Oehlhof about 9 years ago

  • Assignee deleted (Michael Oehlhof)
Actions #7

Updated by Michael Oehlhof about 9 years ago

  • Assignee set to Michael Oehlhof
Actions #8

Updated by Michael Oehlhof about 9 years ago

  • Status changed from In Progress to Accepted
  • Assignee deleted (Michael Oehlhof)
Actions #9

Updated by Michael Oehlhof about 9 years ago

  • Target version changed from 7 LTS to 8 LTS
Actions #10

Updated by Riccardo De Contardi over 8 years ago

I can confirm with the latest 8.2-dev master

Actions #11

Updated by Riccardo De Contardi over 7 years ago

I can confirm it with the latest 8.7-dev master

Actions #12

Updated by Benni Mack over 7 years ago

  • Target version changed from 8 LTS to Candidate for patchlevel
Actions #13

Updated by Riccardo De Contardi almost 7 years ago

  • Status changed from Accepted to Needs Feedback

At first glance, I cannot reproduce it on TYPO3 8.7.8 and current master 9.0.0-dev. Could you confirm? Thank you!

Actions #14

Updated by Riccardo De Contardi over 6 years ago

  • Related to Task #80414: Page Module Drag&Drop: Prevent reloading module frame if content element is dropped at its original position added
Actions #15

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Needs Feedback to Closed

Page layout reloads after a drop and this fixes the symptom, but the cause is probably still existing.

I close this and ask you to continue the discussion on this topics on #80414 - I've added a relation to this issue to keep track of it.

If you think that this is the wrong decision, please reopen it or ping me.

Actions

Also available in: Atom PDF