Issue: Blank page after installing 3.0.0b2

Please check your MySQL error logs. I believe I can reproduce this by doing the following in this order:

1. Have 2.5.7 installed.
2. Upload 3.0.0 Beta 2.
3. Uninstall 2.5.7.
4. Install 3.0.0 Beta 2.

As you can see, step 2 is bad. This would result in:

• The phrases for VaultWiki being missing - causing database errors on all wiki pages.
• The session fields for VaultWiki being missing - causing database errors on every page that tracks the user's location.

This was a known issue in the 3.0.0 uninstall process and is fixed for the next build. You should be able to confirm by checking your MySQL error logs.

You can fix your database by downloading 2.5.7 and uploading its vault/tools directory. Then uninstall VaultWiki in that context, before attempting a fresh installation again.

I did it in a different order... I've uninstalled 2.5.7 then removed all 2.5.7 files and only then uploaded and installed 3.0.0b2.

I've done some more debugging and it seems that I've figured this out... When disabling main init hook it did indeed masked the issue but the actual error was hiding in the other place.

I've then tracked it down to the cache_templates hook. Basically in global.php any code before the line
is executes and anything after that line does not.

I've disabled 'General - Templates & Viewing Modes' module and finally I got the following (very familiar) error:

'Only admins can see this error. Other users can visit the site normally, but your immediate attention is needed in the AdminCP.

Invalid default namespace ID detected. Make sure that you have set up the default namespace via the Namespace Manager. If you have, check that the CES VaultWiki option "Namespace ID of the Default Namespace" matches a namespace ID from left column of the Namespace Manager (default: 6) and is not a forum ID.

If that setting is correct, it is possible that the Namespace Cache is not up to date because of corruption or a recent VaultWiki upgrade. To solve this issue, simply go to the Namespace Manager and select Rebuild All Namespaces.'

After I reset all namespaces, the error message dissapeared and everything worked ok ever since.

So looks like my fault after all for not setting namespaces correctly.. Although it is strange that I was getting blank pages instead or helpful message!

Denis

Ah, thanks for the excellent clarification. We were able to trace the issue further and discovered that the function special_global_state_check attempts to call itself recursively.

Basically:

1. State Check calls namespace error message.
2. Error message requires templates and template fetch is triggered.
3. Template fetch triggers the State Check.
4. State Check calls namespace error message.
5. Error message requires templates. Template fetch was already triggered, so cache is used.
6. Template cache is empty because fetch in step #2 hasn't finished yet. Empty template is output.

This has been fixed for the next build. The state check in step #3 is only supposed to occur if the state check has not yet occurred.