[TYPO3-dev] CE types not visible in create new CE view (locally reproducable)

[Leo R. Lundgren]

Hello,

I have encountered an issue where if I go to Web>Page, select a page, and click create new CE, there is no contents in the place where one should select the type of CE to add. Under the heading "Please select the type of page content you wish to create", there is nothing, until the next visible text that is the heading "2: Select position" (which contents is actually visible).

This happens with a fresh install of Typo3 4.4, with Postgresql 9 beta 3, PHP 5.2.10, Apache 2.2.11, all compiled using pkgsrc on OS X 10.6.4. I can reproduce the problem locally but haven't tried it on another machine. I can however not reproduce it when I change the database from being Postgresql 9 beta 3 to MySQL 5.0.90, so it seems that it's related to the DBAL, possibly in specific combination with Postgres.


So, no CE types are being shown upon creation of a CE. But there is one way to get them to show. If I clear all caches *right before* clicking the create CE button for the page, the CE types show as normal. However, clearing the cache must be done right prior to showing this page, otherwise they are not shown. This seem to mean that the problem only happens when the cache is used. To clarify; If i clear caches, then go to some other view/page, and then click the create CE button, the problem persists. It's only right after clearing the cache that the clearing helps.


I have come across one way to make the problem disappear alltogether. It's rather silly, but if I change [SYS][errorHandlerErrors] from the default value of 6135 to 6143 (equal to E_ALL), the CE types are shown correctly at all times. It's very possible that other measures would also make the problem not show itself, but this is what I came across and I've verified that this "workaround" is reproducable.

I have turned on statement logging in the postgres DB and can't see any warnings or errors at any time (regardless of whether the CE types are shown or not). I have not logged statements in the MySQL DB yet, because I'd rather let you guys know and take orders on what material you would like to debug this.


So, what's next? What would you like me to do to help you squeeze this possible bug or compatibility issue?


-|