Closed exponentcms closed 4 years ago
dleffler@hughes.net
I suspect the server was upgraded to mysql v5.7 and the new default of 'strict' mode prevents creating records. For the fix see http://forums.exponentcms.org/discussion/1556/fix-problems-running-under-mysql-5-7-x
I've escalated this to UK2 2nd line support, still awaiting a response. Peter.
Just to complete the picture from this end: UK2 made the change to strict on MySQL with a PHP update. They are not prepared to revert. As a temporary measure I have moved the database only to my Fasthosts account. Update capabilities are restored, but it runs noticeably slower with the db not in-house at UK2.
Hi Dave. I've not been able to keep tabs on this since a year ago. As we left it, I moved the MySQL database to another platform as the web site host had updated MySQL to enforce Strict. With no access to the actual (shared) server, we've lived with this since - works fine although doing updates is a bit slow!
Is this an issue that you may have resolved in the last year, is it perhaps in 2.5.1? When will that be available please? I'm still at 2.4.2.
I am currently handing over to a new Webmaster, so am trying to sort out what he may need to do!!
Many thanks. Peter.
Hi Dave. I appreciate you're busy, but now I've handed over my webmaster duties I am still left with the responsibility of sorting out this issue. At some point in the not-too-distant future I'd really like to get the database moved back to the same provider as Exponent. Right now the database is on my own account at Fasthosts where I can't allow the new webmaster access.
Please could you let me know if this issue has been resolved in any updates or is it still outstanding? If the latter, when might it be resolved please? It's over a year since the last update.
Thanks. Peter.
There have really been not changes in this area of code. I was able to get my shared host provider to change the my.ini setting since many different apps doe NOT work under mysql strict mode
[mysqld]
sql_mode = 'NO_ENGINE_SUBSTITUTION'
I did try this, but they refused. I can try again, but don't hold your breath! Peter.
Hi Dave. Just looked at the changes in the new release 2.5.x - no mention of this issue so I wondered if there's any plans to fix it in the code please??
I have been around the houses again pn changing sql_mode without success. I've looked at alternative ISPs but am left with Fasthosts hosting the database and the site at UK2. Nobody wants to change their shared servers. The only way I can potentially get everything back under one roof is to rent a VPS and transfer into that. Because this site is for a charity with limited resources, it is doubtful they will fund the somewhat higher costs.
I do hope you can plan this in soon.
Thanks. Peter.
v2.5.1 doesn't include any fix for MySQL 'strict' mode. It's mostly a set of patches but all the files had the copyright updated to 2020 so was released as a full version.
Yes, I understand that and did say so. My question was, do you have any plans to fix this long-standing problem that puts us at the mercy of inflexible ISPs?
Thanks. Peter.
I may have a fix. It seems to work locally. It would be 'shipped' as v2.5.1patch1. Not sure if it'd update an existing database, but would likely work to create a new database, then accomplish a restore database using the .eql file backup.
I've got another fix which should update an existing db to set/change the Nullable field column.
Sounds hopeful. Thanks. I'll probably need to wait a little while depending when you release. This and next month are the peak times for membership renewals, but then it should quieten down. Peter.
Recent code push now works with MySQL in 'strict' mode
At some point in the last month or so, a problem has occurred which has only just been noticed.
It is no longer possible to add new modules to a page. You go through the screen for adding the module, but when you OK back it's not there.
I can send you a login password for user lighthouse - please confirm how to do this securely.
Thanks. Peter.