cry for help - sorry if this is in the wrong place.
running drupal cvs

As of this morning (possibly over the weekend) we are getting login errors for many users.
here is the error from the drupal log:
details
Type php
Date Monday, October 24, 2005 - 11:48am
User Famous Guest
Location /user/login?destination=user
Referrer http://forums.fresnofamous.com/user
Message in_array(): Wrong datatype for second argument in /usr/www/users/mydir/myinstall/includes/common.inc(1805) : eval()'d code on line 7.
Severity error

I have not personally had login issues but i have accessed throughout the weekend. We have the hosting company trying to help (pair.com) but for now they are as stumped as we are.

Same error happening on our beta install.

Has anyone had a similar problem?
Suggestions for a fix?

Comments

thinkinkless’s picture

thinkinkless commented

Following up: the hosting company says it is unrelated to anything they have done.

Users are able to get in after the 'i forgot my password' dance but that's it.

QUESTION What would cause some (not all) logins to become corrupt and how do i fix it in a big hurry?

killes@www.drop.org’s picture

killes@www.drop.org commented

Sorry, but cvs has currently a number of issues. i suspect that you use a contrib module which hasn't been updated to use the new forms API. Please confirm and close.

thinkinkless’s picture

thinkinkless commented

Thanks for the reply. It's certainly possible this is from a module but i did not install any new modules over the weekend. this problem only cropped up this morning. We are running forums and polls only at the moment.

Do you have a suggestion for a fix so i can restore logins?

Is there a date set for the code freeze?

pfaocle’s picture

pfaocle
He/Him
Primary language English
commented

Sorry to sound so negative, but perhaps you shouldn't be running Drupal HEAD on a production site? As Killes' mentioned, the current CVS HEAD version of Drupal has many issues, mostly down to some major changes like Forms API. My suggestion would be to restore the site to a previous version from a backup (4.6.3 or CVS pre-Forms API), and continue to update your CVS version either offline or in a test location. Keep checking the CVS log messages and hopefully various fixes will be applied and your site will eventually get sorted. If you are running CVS, ensure you have the latest files.

I can't comment on the postponed code freeze, but I'd guess it'll only be announced when this raft of bugs (in core and popular contrib modules) are sorted out.

thinkinkless’s picture

thinkinkless commented

That's not negative at all - it is sound advice. I actually began to do this before seeing your post. The 4.6.3 install with the freetagging patch was a breeze. The cvs is really great, btw. I look forward to 4.7.

Is there a guide for moving the content and users over from cvs to 4.6.3?
We've only been live for a week or so so there's not too much to move. (users, profiles, forums and polls only)

pfaocle’s picture

pfaocle
He/Him
Primary language English
commented

Is there a guide for moving the content and users over from cvs to 4.6.3?

Not as far as I know, and the times I've tried it I've just ended up with a borked database... if you've tracked the db changes between the versions, you could get back step by step, but I wouldn't like to try it!

We've only been live for a week or so so there's not too much to move. (users, profiles, forums and polls only)

Perhaps build the db back up from scratch, then? We managed to do this with a fairly large site a few months back. Start with a clean 4.6.3 install, get your theme files etc copied over. Set up the site settings (I wouldn't copy over variables table) and all the quick, simple stuff. Then start to move parts of the db over... nodes, users, comments etc. By the way, I really wouldn't advise this either unless you know whats going on in the depths of the Drupal database...

thinkinkless’s picture

thinkinkless commented

Thanks to all for the advice and words of warning. We got 4.6.3 installed and all content and users moved - manually. yup. Hand posted just to be safe. We had to sacrifice previous settings for subscriptions and polls but that's OK since keeping the cvs running smoothly was a bit more than we could reasnoably manage. The biggest pain was comments. 4.6 does not allow for the same author editing so user ids and timestamps had to be changed at the database level.

sangamreddi’s picture

sangamreddi commented

Hi,

use import/export modules to make your work easier. I haven't personally tested yet.

I hope this would easy your process. Have backup's at every intervals it would be safe.
I am sure with drupal there won't be much data loss when compared to other cms.

http://drupal.org/node/31940
http://drupal.org/node/14858
http://drupal.org/node/7780

May be some one can write a piece of code to do this. I am not a programmer.

All the best.

Sunny

Bèr Kessels’s picture

Bèr Kessels commented

So can we close this?
Or is this a dupe of http://drupal.org/node/41317 ?

thinkinkless’s picture

thinkinkless commented
Status: Active » Closed (fixed)

closed