Completing sign up on site results in blank screen

[brwnie]

Hi there,

When a user registers on the site and completes it, it results in a blank page.

There does not look to be any sign of a registration in users ethier, verified or unverified.

I don't see any output in Apache's error log

[CaMer0n]

Login as head admin, and then go to /signup.php. Check each page/button.

[brwnie]

Says:
Unauthorized access!

After clicking submit

[CaMer0n]

This will need to be troubleshooted via the chatroom. https://gitter.im/e107inc/e107

[Moc]

Check the PHP session save path! :)

[brwnie]

@Moc thanks, ive checked session path is fine and writable, i'm seeing files there created by the host's user.

@CaMer0n kindly did some troubleshooting last night, not sure if he found anything further? :)

[brwnie]

@CaMer0n
I've managed to workaround this, by tweaking settings:
I changed settings in both User Registration/Login and Signup Page Options

Signup Page Options Changed:
Email Confirmation from None to Required
Option to hide email from None to Display
Use COPPA on signup page? to Disabled
Text to display after signup form has been submitted had text, cleared it.

Registration/Login
New user verification method from E-mail Verification to No Verification (testing after changing JUST this did not work, in case it was an email issue)

[Moc]

If you are still experiencing this issue, please visit us in the Gitter chatroom to have this issue debugged. Closing for now.

[CaMer0n]

I recently had this issue on my localhost. I finally traced the cause, but not the fix just yet.

If the signup page contains an error prior to the form, for example, an tag src pointing to a missing image (which loads a SEF URL of the 404 Error page), then the e-token will be refreshed (due to class2 being loaded by index.php [single-entry point of SEFURLS]) and when the form is submitted the token will mismatch and throw an "Unauthorized Access" message.

So, I believe we need to detect that a 404 error has occurred before class2.php is loaded by index.php, to make a flag which the session handler would see and prevent regenerating the token.

see e_TOKEN_DISABLE in index.php and session_handler.php

Any thoughts/ideas @lonalore @Deltik @SimSync @myovchev ?