Drupal now implodes on false_account after upgrade; the end.
* warning: implode() [function.implode]: Invalid arguments passed in .../sites/all/modules/false_account/false_account.module on line 306.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 query: SELECT COUNT(*) FROM d1_false_accounts WHERE in .../sites/all/modules/false_account/false_account.module on line 314.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY created DESC LIMIT 0, 50' at line 1 query: SELECT * FROM d1_false_accounts WHERE ORDER BY created DESC LIMIT 0, 50 in .../sites/all/modules/false_account/false_account.module on line 314.
Also no mails seem to be send anymore to users.
And now its enough after 4 weeks working 10 hours a day without days off; I'll delete the drupal installation, as I have to travel tomorrow. Hasn't changed that much here in 2 years time...
So for the record only, as I have no time anymore to experiment what in this XXX-case could be the cause. But maybe someone understands immediately what is the case. Maybe I'll continue in half a year, if not in another 2 year.
Check the False account
Check the False account project issue queue. If you don't find the same problem reported by someone else, go ahead and file a new bug report!
Hmm
You're giving up on Drupal because a non-essential 3rd party contributed module has a bug?
A lot has changed here in 2 years. And it is good :)
-- David
davidnewkerk.com | absolutecross.com
View my Drupal lessons & guides
yes & no + this module not that instable
Yes, pardon me... It's just too much, I'm beyond overworked.
But what hasn't changed is that there are many errors showing up. Two years ago I'd quit with some user login problems. Yes I could login on an insecure way, but need more security due to the work I do and more nasty people trying to get in. And just had an 'awefull' experience with almost the same issues, now not on an early 5 series, but with 6.8 and 6.9. Just for the login problems2 days work (one can find it all just clicking on my user name + tracking).
"a non-essential 3rd party contributed module" ?
That's just the problem with Drupal; security issues like in the false account module (in a more developed way; its still a very basic module) should be build in /available from day one, as well as that there are some 'chaos-programming' aspects. Not that strange with many different developers and no clear over thought punctual road map. The secure login module for example, didn't work 2 years ago and ain't working on drupal6 either right now & its already half a year waiting for the new release that maybe resolves the issue. Probably it works as one has no other mod's next to only the core modules. Only that secure login and no name redirects, or whatever, could cause conflicts.
BUT FOR THE ERROR OF THE FALSE ACCOUNT MODULE (& the archive): It seemed to be non-essential and on a less important backpage of that module. Later I didn't get those messages anymore (yes I got many other errors; today was maybe 12 hours working on it).