Bug #33329

Content not visible in backend or frontend grid after creating it in the backend grid

Added by Lars Peipmann over 1 year ago. Updated 12 months ago.

Status:Closed Start date:2012-01-20
Priority:Should have Due date:
Assignee:Lars Peipmann % Done:

0%
Category:- Spent time: -
Target version:-
TYPO3 Version: PHP Version:
Votes: 0

Description

Flow:
1. Created gridelements grid
2. Created a new text content element with the "new" icon in the column title of the grid
3. After saving the content element it is not visible in the backend or frontend (just in the list module)

4. With I click to the "Extended" tab in the properties of the page content element I can see the relationship to the right grid container and grid container column (extendedTab.jpg)
5. The mysql table colum `tt_content`.`tx_gridelements_columns` is 0 (tt_content.sql)

6. The content element is visible in the backend and frontend when I created it outside of the grid and moved it via drag and drop into the grid

My setup:
  • TYPO3 version: 4.6.4-dev (Fresh TYPO3 installation with just a few extensions)
  • Root Page > General Record Storage Page: System Folder with the grid elements
  • gridelements v1.2.3 (I had the same problem with v1.1.0, but I didn't test step 5 and 6)

I tried it a few times and every time I had the same results...

extendedTab.jpg (24.8 kB) Lars Peipmann, 2012-01-20 02:21

tt_content.sql (10.8 kB) Lars Peipmann, 2012-01-20 02:21

tx_gridelements_backend_layout.sql (4.1 kB) Lars Peipmann, 2012-01-20 02:21

newIcons.jpg (33.4 kB) Lars Peipmann, 2012-01-20 20:34

History

#1
Updated by Jo Hasenau over 1 year ago

  • Status changed from New to Needs Feedback
  • Assignee set to Jo Hasenau

I tried to reproduce this behaviour but with no "success".

Clicking on any "+"-Symbol except the one at the very top of the page module (that triggers the drag in wizard), always gave me a properly nested grid structure with the new element in place.

Using the drag in wizard always shows the element at the position that I dropped it.

#2
Updated by Jo Hasenau over 1 year ago

Could you try to check if the values shown in your screenshot are already available BEFORE you save the new record for the first time?

#3
Updated by Lars Peipmann over 1 year ago

Jo Hasenau wrote:

Could you try to check if the values shown in your screenshot are already available BEFORE you save the new record for the first time?

Yep, they look the same..

The content element is visible in the grid after a drag and drop from the top (newIcons.jpg: green circle). But its invisible again after editing the text...

One question: I took a short look to the code.

Line 44: $pid = intval(t3lib_div::_GET('DDinsertNew'));
New Line: echo $pid; die(); // Result is "0".. I guess it should be "20" in my case.. The value is to this time already available in $fieldArray['pid']..
Line 45: if ($pid > 0) {

(Source: ./lib/class.tx_gridelements_tcemainhook.php)

I hope this helps?

#4
Updated by Jo Hasenau over 1 year ago

  • Assignee changed from Jo Hasenau to Lars Peipmann

Let's see:
If the element has been positioned via drag in, it will be visible at the desired position.
But if you then open the editing form and then save it again, it will disappear?

This has nothing to do with the DDinsertNew parameter, since it won't be available within the normal editing process.

Actually there should be no change in any field of the gridelements relations (container, column, sorting etc.) unless you change them on purpose.
And I am still not able to reproduce this behaviour on any of our testing servers.

It works with 4.5.x, 4.6.x and AFAICS even with 4.7.x - so I guess there might be a problem especially with your setup.

Or is there anybody else who can confirm this behaviour on another system?

#5
Updated by Jo Hasenau over 1 year ago

I guess it could be a problem with an extension that is using the same hooks as grid elements, so could you try to disable anything but the core extensions and test if the problem remains?

#6
Updated by Lars Peipmann over 1 year ago

Hi Jo,

thank you very much for your responses.

I found my problem (PageTS):

TCEFORM.tt_content.colPos.disabled = 1

After I deleted this row I was able to add content elements to the grids.

Best, Lars

#7
Updated by Jo Hasenau over 1 year ago

  • Status changed from Needs Feedback to Closed

Thx for the info - so I will close this issue.

#8
Updated by BIDAU 12 months ago

Hi,

could you add this information in manual, perhaps in Notes section, in "Important note about the colPos field!".

Perhaps a message like :
Be sure that colPos is not disabled in your PageTS with TCEFORM.tt_content.colPos.disabled = 1

It takes me hours to understand why I can't use grid elements ;)
Thanks for your work on this extension.

Ismaël BIDAU

#9
Updated by Jo Hasenau 12 months ago

But this would be true for any other field of tt_content as well when it is related to gridelements.
And people will disable fields in TSconfig on demand only.

Also available in: Atom PDF