I read already lots of comments and threads in the forum but couldn't get any similar information on what happend on my site.
Basically, I followed the upgrade instructions.
I also made a backup of course (files, DB).
Everythings seems to be okay .. up and running.
Now I recognized, that new user can NOT register.
So - I tested it by myself and indeed:
- the form came up and I was able to fill it out
- Submit has sent me an email with my password and link
BUT
I can not use the username - it is even NOT stored in the MYSQL database.
The link in the email for changing the password directly is on "..=user/660/edit", which is already an existing and active user!!
As I am using the profile module, all profile fields are stored now to this user.
This is horror!!
I rolled back to 4.7 again but need to move to 5.5 urgently!
Any ideas and help are very welcome.
RaRi
Comments
=-=
what version of 4.7 ???????
There have been 10 releases of 4.7 it would help to understand from where exactly you are beginning your upgrade as you may have to chew off smaller pieces because you've waited so long to upgrade and possibly update.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Not really sure .. but I
Not really sure .. but I assume it is 4.7.7.
I normally update regulary.
INSTALL.txt,v 1.29.2.5 2007/06/27
$Id: CHANGELOG.txt,v 1.117.2.12 2007/07/26 19:17:24 killes Exp $
Drupal 4.7.7, 2007-07-26
My site is running with ~ 300 registered users.
mod_rewrite, clean urls
were you using clean urls on 4.7 and not on the 5.5? That could cause this. It is submitting to a mod_rewritten url in the 5.5 install and you don't have "clean urls" enabled on the newer version of drupal.
Local News Platform Built on Drupal
http://sanangelolive.com/
Users table - index missleading
I assume I found the problem:
It works now - I guess.
Somehow the pointer to the user table was missleading to somewhere close to the end of the user table.
Would be nice to know how this can happen.
What I did was using a new database and importing all data from 4.7.7 to the database.
Then running update.php.
But - a few days later I had to import the users table again because of new users in 4.7.7.
So therefore I made an update of the users table (sql insert) only.
I assume that this causes the error because also in the meanwhile, some inactive users were deleted.
Could this be and how can I overcome the problem in the future, by the means of migrating to v6??
(Thanks for all posting to this topic.)
=-=
The site should be set in offline mode so that users can't do anything to change the DB during an upgrade. This would haev stopped users from registering before the update was complete.
set site in offline mode
export DB (backup)
then upgrade/update
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Similar problems
I'm upgrading a site from 4.7 to 5.5 I'm new to drupal, new to the site I'm upgrading.
I've duped the site. I can browse. Everything seems to be working but I can't login as the admin. Nobody can login. I have not FTPed any new modules or files; it's just a straight dupe.
Anything I can do in htaccess or phpmyadmin to fix this issue?
=-=
.htaccess has nothing to do with your login.
upgrading from what version of 4.7 ?
when you state you duped the site does this include the DB ?
did you inspect the users table for user 1?
after duping the site , including DB, did you set set the proper db_url in settings.php ?
have you tried clearing the sessions table in the DB as well as your cache in your browser ?
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
How can I find out which
How can I find out which version? I can login to the existing live site and check but wouldn't know where to look.
Yes, I duped the DB and checked there is a user 1; there's no prefix for the DB so I simply changed the mysql info.
I emptied sessions and when I try to login (whoever developed this put the login and signup into separate "directories") I get Error Code -12263.
update: I searched for that error code. I do all my admin in Firefox (Apple). I tried it in Safari and it gave me more information: unable to establish a secure connection. So apparently the duped domain needs a security certificate. But since I don't need a secure connection for upgrading this site, how can I turn off https? Is there something written in any of the tables that I can edit via phpmyadmin?
=-=
check your CHANGELOG.txt file in your installation
more methods here: http://drupal.org/handbook/version-info
Drupal doesn't default to https, therefore drupal wouldn't handle this unless you've installed a module that is doing this. without a list of all modules running on your site I can't say.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Thanks
The version 4.7.4. The directories on the domain are a huge mess. Further, I couldn't tell from the logs, via the link you included - and thank you for that - because one of the mods is an admin dhtml top menu mod and status report wasn't among the filters. But I do feel good having deleted the contents of the watchdog tables because it was 132,000+ records.
Thank you for also raising the issues of mods because eCommerce is installed and working on the live site. It's that one that is probably 'insisting' on https. I ordered a cheap ssl certificate from godaddy. I'll get that installed and I think I'll be good to go and start updating the site module by contributed module, starting perhaps with eCommerce.
Does module by contributed module sound like a best practice - and slow - way to upgrade?
=-=
The only step you left out was backup
I've learned over time that, regardless of skillset and skill level. Crap happens! I make a backup before I do anything that involves DB manipulation. This includes, updating/upgrading core & modules.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Yes, I left that out because
Yes, I left that out because that's a given in my book. It takes a little bit of extra time but it saves at least a thousand times that time.
I generated the CSR and once I get that certificate in place I will post back here to let you know if that was indeed the issue. I'm pretty sure it is, but there's so much I don't know about the previous devs efforts.
The testing site is working
The security certificate was installed and everything is working. Now onto the upgrade.