This forum is for questions about upgrading an existing Drupal site. Don't forget to read the UPGRADE.txt file that comes with every Drupal download.

Can't login after 5.0b1 upgrade...

I've recently upgraded a 4.7.x installation to 5.0 beta.

I realized that I forgot to login as user 1.

Now, when I go to my site, not only is the theme completely missing, but the controls for logging in are completely gone, as well. I can't get in and I can't do anything to change this situation.

Does anyone have any suggestions?

I was using the 'spreadfirefox' theme before this happened.

http://themarkelfamily.com

Problem with Front Page

I have installed Drupal 5.0 on a few sites. On a few of the sites, the nodes are not appearing on the front page if I am not logged in. If I am logged in, no items appear.

I have set the Access Control with anonymous permitted to access content for nodes.

Site in question is www.thenetcastlerock.org

Subscriptions module failure

Hi

I have recently upgraded from Drupal 4.5 to 4.7 and my subscription module stopped working. This is the error I'm getting every time a new post tries to send an email notification:

Easy Drupal Upgrades using Subversion with Vendor Source Tracking

Hey folks, I just upgraded to Drupal 4.7.5 and it was so easy using subversion with tracking of vendor (drupal in this case) sources. I have done this with Wordpress and mediawiki too, as well as drupal modules. I finally decided to blog about how I do my upgrades as I finally fine-tuned the process. For anyone who has worked with branches or tags before this will seem easy, but I find many software developers don't even make use of branches/tags very often (sometimes because they just don't understand it). Here are my instructions on how to upgrade from Drupal 4.7.5 to Drupal 4.7.6 by tracking vendor sources.

It basically just involves 4 steps (assuming your svn server is all set up):

  • Download the new sources
  • Run svn-load-dirs
  • Do an svn merge between the old drupal sources and the new drupal sources, into a working directory of your own drupal sources
  • Inspect changes, fix conflicts, and commit when ready

If you are starting from scratch (ie. you haven't done this before), download drupal-4.7.5 sources and add those to your repository and tag as current. Then follow the steps above (or on my blog

please help ... don't know what to do

Hi,

i've problems with upgrading. The following file contains the errors ...

http://ana-ftp.de.gg/stuff/update.txt

Can anyone helps me with this ?
I tried it with 4.7.x before and there were the same problems. Furthermore when i tried to update this time i haven't added any modules.

When i installed drupal i had to change ini_set() to @ini_set() so it ran well. I guess there is a connection but anyway ... that doesnt help to solve it ...

so ... need help 8(

thanks

upgrading multi site problem

Having some trouble after upgrading from 4.7.4 to 4.7.5

I'm running three sites from the same code/directory. The three sites are defined with their own configuration files within the /sites subdirectory. Each site has its own database.

I was logged in to one of the sites as the admin user when I copied all the files around. Then I ran update.php and it modified the database, I think three changes, but I didn't write it down. No problems during the update.php and everything on that site seems to be working properly.

I assume I have to run the update.php script for the other two sites, but I can't log in to either one. If I try logging in with a bad password it tells me the password is bad. If I use the correct password, nothing happens - I get the login form back.

I tried changing update.php so that access_check = FALSE but that doesn't work. It looks like it's working with the progress bar and everything, but I don't think it does anything - I've run it several times and each time it still things the system module 183 and 184 changes are required. In any event I still can't log in.

So the question is, how can I find the database changes that will be made? I'll make them manually if that will solve my problem, but I don't know what the changes are.

If I make the database changes manually, is there some other file that has to be changed so the update / version status is set correctly?

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal