Feature #33389
Add new content element within container
| Status: | Resolved | Start date: | 2012-01-23 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | Jo Hasenau | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | PHP Version: | |||
| Votes: | 0 |
Description
When adding a new content element within the grid content element the gridcolpos is not set correctly. Thus the new content element is not displays as a child element within the page module overview.
Reproduce:- Add grid element
- Edit grid element and add new child with the "Add element" button above grid elements. (see attachment 1)
New content element is assigned correctly within the grid element but not displayed as a subelement with in page module (see attachment 2).
This is expected behavior because there is no definition to which column the new content element should be added
Solution:
Add new content element should be added to first/any column within the grid container.
This way the new content element is at least be associated with the grid container and can be dragged/dropped accordingly.
History
Updated by Felix Kopp over 1 year ago
Add new element
Grid element col-position is not set at all
Updated by Jo Hasenau over 1 year ago
- Status changed from New to On Hold
- Assignee set to Jo Hasenau
IMHO there should be no "add new" button/icon at all within the grid element itself, which would solve this "bug" as well ;-)
The reason is the same we already have to face with the "sorting" problem: We will need a completely different way of listing child elements, which is currently not provided by the IRRE concept.
So as long as there is no universal solution for these problems, we should just deactivate the button, so that people will just see a list of elements contained by this grid, but without any option to change it.
Updated by Jo Hasenau over 1 year ago
Of course we can keep the rest of the IRRE features, so that users would still be able to edit child elements of a grid container directly within the eidting form.
Updated by Felix Kopp over 1 year ago
I like that!
Perhaps the tt_content table should be removed within List Module as well automatically upon installation of EXT gridelements.
What can I do to support the development or do you already have a technical solution in mind/ready.
Updated by Jo Hasenau over 1 year ago
IRRE and list view are completely different tasks.
Take a look at the current trunk to see a working solution for both and a proof of concept for lists.
I checked in a new ext_tables.php that will disable any movement in IRRE item lists.
Additionally you can set page TSconfig
TCEFORM.tt_content.tx_gridelements_backend_layout.removeChildrenFromList = 1
to remove grid children from the list view.
And finally you should check out the methods makeClip and makeControl of the new class tx_gridelements_dbactionshook, which contain a deactivated proof of concept for a dumbed down list view of grid elements.
Still I think that we should use another concept and therefor need some hooks and/or patches in the db_list code.
Updated by Jo Hasenau over 1 year ago
- Status changed from On Hold to Resolved
Fixed in current trunk.
Updated by Felix Kopp over 1 year ago
Should sorting of grid container elements with children be possible?
Might be confusing if these are spread over several backend-layout columns (different task though).
Updated by Jo Hasenau over 1 year ago
Well - it doesn't hurt that much ;-)
At least not as much as sorting child elements.
This is due to the fact that sorting always works by placing an element behind another one, except the top most element, which will be moved "into" the page.
So if you move an element in the list view you might move it "behind" an element which is not even in the same container (and therefor completely out of scope for the user), while moving elements on the first level will be at least traceable in the page view later on.
On the other hand we could remove the move, moveUp and moveDown icons completely for each tt_content element as soon as gridelements is installed.
But IMHO it would be better to improve the list view so that we could use a kind of nesting for child elements (similar to the view for translated records).
Within the containers you would see the different columns and sorting would be possible within these columns only.