Bug #30259
closed
List view not loading data on pid 0 after switch from page modul
Added by Simon Schaufelberger about 13 years ago.
Updated over 9 years ago.
Category:
Backend User Interface
Description
After i logged into TYPO3, i am going to the page modul and select the pid 0 in the page tree. On the main frame i now see the message:
"Please click the page title in the page tree to the left to edit page content."
which is ok.
I now switch to the list modul and expect to see all the data on pid 0 but i see nothing (empty right frame).
This is only reproduceable if you switch from the page modul to the list modul. If you go straight to the list modul, i see the data on pid 0.
You can even go to the list modul (see the data), then to the page modul (see the message in the box) and back to the list modul and you will see nothing again.
This happens in latest trunk of TYPO3 4.6 as well in older versions, maybe even until TYPO3 4.3
In TYPO3 4.2 it was working.
- Status changed from New to Accepted
- Priority changed from Should have to Could have
- Complexity set to medium
- Target version changed from 4.6.0-RC1 to 4.6.0
- Target version changed from 4.6.0 to 4.6.1
- Target version changed from 4.6.1 to 4.6.2
- Target version deleted (
4.6.2)
- Status changed from Accepted to Needs Feedback
- Is Regression set to No
Hi,
does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?
- Status changed from Needs Feedback to New
Tested this on current master and on 6.2.9. In both versions I cannot reproduce this. Can you provide more information? Maybe a php error occures in your setup. Can you make sure that you see errors and then post the error message?
well, if it is working in master, fine but in 4.6 it is not working but that version is not supported any more, right? then this can be closed.
- Status changed from New to Closed
As stated, version 4.6 is too old; Furthermore, there there have been no additional reports 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.
Also available in: Atom
PDF