TYPO3 Core

In addition to my bug report, I just downgraded to my original version, and my problems are solved. So I can be pretty sure it is a 4.2 specific bug.

Please deinstall all TYPO3 extensions first. There will be a conflict with one of it.

I was using 4.1.5 and try to update to 4.2.0 and didn't see a page tree as well.
Now I'm trying to upgrade from 4.1.6 to 4.2.1 with the same result. Still no page tree.

This happens with Safari, Firefox

I must say that my server is still using PHP version 5.1.6 on a CentOS system which seems to be too old when using 4.2.x

Did you update your DB after update the source?

I did update the DB.

After updating from 4.1.5 to 4.2.0 I updated my dB.
This time, after updating from 4.1.6 to 4.2.1 I didn't update my dB.

What will happen when I go back to an older version with an updated dB?

You must always update the DB after each change in version.

Try out an empty installation with not installed extensions.

I see what I can do. Right now I have only a few live servers to work on so I must be carefull.
I have a few complicated sites I don't like to mess around with. My nightly update to 4.1.7 went smootly.

Please try again.
When updating DB you have the option to show the performanced SQL-strings.
Can you make a copy of this strings and attach them as txt-file here?

Let's try this out:

Your current TYPO3 installation is configured to behave like version 4.1 of TYPO3. If you just upgraded from this version, you most likely want to use new features as well.
Then: Next - Check all - Show database queries performed - Perform updates!
Result: Update successful but no SQL-strings visible.
Then: Modules - There's a warning to remove the file - Click.
Now it seems like I removed ENABLE_INSTALL_TOOL

Let test this, Page ...

No page tree

Worst case scenario

I was trying to deinstall all TYPO3 extensions and install them back. The right frame remains blank, and the complete site is blank as well.

Now what?

Going back to 4.1.7 and my site is back.
That's why I like Typo3!

Enable the debug and error output in the install tool to make the error messages visible.

I just found in my installation (YAML based TemplaVoila) that the extension pmk_textarea (suggested during install of YAML) was interfering with the prototype.js of the page tree. Removing this extension solved the problem.

I have the described problem too with all old sites.

after updating sites to 4.2.1 instead of the page view there are error messages like "mysql_num_rows(): supplied argument is not a valid MySQL result resource in <b>/Library/WebServer/Documents/typo3_src-4.2.1/t3lib/class.t3lib_db.php</b> on line <b>795</b>"

- I tried out an empty site from 4.1.5 (dummy 4.1.5) with the same result!
so I guess the reason can't be an extension (or not only the extensions)

one site which had been orginally an 3.8. updated to 4.1.6 did show the same error after updating to 4.2. changing back to 4.1.6 all seems to be fine again.

I always used the update wizard from the install tool and did clear the cache!
Calling the tool again didn't solve the problem!

Stupid question, but by updating the database we don't mean the update wizard. The wizard only modifies some small parts of the rendering mechanism and the so-called-compat-version.

By updating the DB we mean the compare-tool in the database-section. After that compare and executing the necessary SQL-statements everything should run fine...

There are no stupid questions,
- only stupid user like me ;)

I really did miss to execute the compare tool for the databases.
And at one site I had some old extensions, after updating all local extensions and changing to 4.2.1 again, this site is ok too.

Now all works fine!

fine - so i can close this issue now.