Unable to add users via Admin or using signup page.

[KSSilence]

Hi!

Got a weird problem regarding users in e107v2... I CANT Add users either via the Admin panel under users (Quick user Add) or by using the self signup on the homepage login screen. Both just silently fail or the Login page sometimes returns an error and either way no user is added to the database. the only way i can currently add a user is to manually edit the database in PHYMyAdmin. Ive also noticed as of just recently that some other functions are also causing errors... Attempting to add a link to the links bar on the home page results in an SQL Insert failure message but i cant see why...

Im not getting any relevant errors in the Apache or PHP error logs either!

Try and sign up for yourself here: https://www.4th-id.net and it will either give you a blank page, or return an error stating the user information could not be created.

For reference the Server is a Private VPS Machine (Managed with Remote Desktop) running: Win Server 2012 R2 x64 Apache 2.4.10 x64 PHP 5.5.15 VC11 x64 MySQL 5.6.19 x64

Fresh install of e107v2 thats only hours old and a fresh schema in the database for e107 that was created when i installed e107v2.

Anyone had anything like this before? i know i havent the previous times ive used both e107 and e107v2.

Any ideas guys?

Thanks.

[Moc]

1) Are you using MySQL in STRICT mode?

• Check using: http://stackoverflow.com/questions/7763894/determine-mysql-mode-from-php

If yes, let me know and stop here. No need to proceed with the other instructions. If not, continue with step 2.

2) Please download the latest files from Github first and upload those (make sure you overwrite the existing files).

• Go to https://github.com/e107inc/e107 and hit the 'Download ZIP' button on the right hand side.
• Extract the files and upload them. Make sure you overwrite all the existing files.

2) Enable debug mode in the admin area:

• Go to admin area > preferences > advanced features > developer mode: enable
• Go the /e107_admin/admin.php and change the url to `/e107_admin/admin.php?[debug=basic+]

3) Try and add the user. At the bottom of the page you should see an SQL error. Please copy that in your reply.

[KSSilence]

Running the query from the first link in phpmyadmin results in the following result: STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

I guess that means im in strict mode? Do i need to disable strict mode?

[Moc]

Yep, that's strict mode. Unfortunately e107 v2 doesn't handle strict mode well at this point. I'm working on fixing it. This will take some time.

It would be very useful if you could help me do some testing as well. However, if you want to have things functional as soon as possible, I advise to disable strict mode until the issue is resolved.

Hope this helps. Sorry for the inconvenience.

[KSSilence]

OK thanks for that, and disabling strict mode requires editing my.ini ? im a n00b when it comes to dealing with advanced config of things like mysql and apache. Basic tasks and basic troubleshooting i can do fine, but things like this, im lost...

[Moc]

Selfnote: #713

[Moc]

I would think so yes. I'm sure Google can help you out :)

[KSSilence]

Just made a edit in my.ini that should disable strict mode. If you can try and sign up and consequently log in if the signup appears to work that would be great.

[KSSilence]

Thanks, Signup appears to work for me now, will test the other issues later after i have slept.

PS. Is there a known issue to do with "unsafe scripts" that e107 uses? chrome in particular complains and ive noticed this has been around a while from when i last used e107. You need to load the scripts or the menus wont work, but in doing so, chrome will complain that your webservers SSL is now useless (which it does here because i run SSL on my server).

[Moc]

With regards to the "unsafe scripts", please open up a new issue so we can keep this one focused. This will help with streamlining the issues on Github, making it easier and more efficient to fix issues.

[Moc]

I'm going to close this issue in favour of #713 Please keep an eye on that issue if you wish to follow the progress on the STRICT mode problems.

I'll be pushing out fixes for it over the coming days hopefully.