By gurukripa on

I thought it might be a good idea to start a Forum Topic so people can share their experiences with updating from 5.1 to 5.2 so the rest of us can learn..

so pls post ur success - failure - issues - learnings - workarounds - points to note....so it can help the community.

thanks

⋅ Categories: Drupal 5.x

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

On my local PC, where I have test versions of all my sites, plus some others that are still in development, I did this:

  1. Downloaded and unpacked the tar. This created a "Drupal-5.2" directory.
  2. Stopped Apache (so it would release the directory).
  3. Renamed "Drupal" directory (5.1) to "Drupal-5.1".
  4. Renamed "Drupal-5.2" directory to "Drupal".
  5. Copied "files" and "sites" directories from 5.1 to 5.2.
  6. Restarted Apache.
  7. Went to each site and did "update.php".

That's all it took - 5-10 minutes, total. Everything works so far, although I know there are a few bug reports I made that didn't get picked up, so I'll have to track them down and re-apply my patches. I'll hit my live sites after that.

Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database

NancyDru

hgmichna’s picture

hgmichna commented

I think the correct procedure is to use the new 5.2 settings.php file and transplant the few individual lines from the old one.

I don't see why you had to stop Apache. I didn't. I did switch all sites of this multi-site installation into maintenance mode though.

By the way, another nice trick is to make the following change to .htaccess:

DirectoryIndex index.php

Change to:

DirectoryIndex index.php index.htm

Then create a static fallback web page: index.htm

Example: http://winhlp.com/index.htm

Then you can rename index.php to something like: index_off.php

This will instantly stop all Drupal activities and make all users fall back to index.htm. It also prevents that web visitors instantly hop on Drupal while it is still being copied.

Leave the index.htm page in place for the next time. Remember, just renaming index.php will instantly divert all visitors to index.htm.

I'm not as trained as some others here, and the upgrade took me an hour and 10 minutes. Even then I found an error later, concerning access rights for the node_images module, that I had to fix. (node_images seems to run a make directory command even against the sites folder, quite unnecessarily.) There was another error related to the garland-minnelli theme color settings, three missing menu image files.

Hans-Georg

Stephen’s picture

Stephen commented

SUCCESS!, I must admit I had alot of reservations at first. I kept having repeating mental images of everything going horribly wrong and having to start from kilobyte 1 with my site. However, things turned out quite the opposite, they went rather smoothly, with only one minor and easily overcome snag. Here's what I did.

1.) Backed up everything and THEN SOME. I made sure every little thing I had in my directory was backed up not only only my PC, but on my removable hard drive. I verified all the files were in the backups. Then I backed up the database, made duplicates of those as well. (And might I add this, I don't care who you are, or how well versed you are in Drupal or not, whether you've played with you're site a million times and never broken it. BACK UP EVERYTHING!, Its just plain naive to believe that nothing horrible is going to happen.)

2.) I began following the remainder of the instructions located in the UPGRADE.txt (and remember, although its been said many times, Make sure you replace your settings.php file(s), and edit the db_query variable to match your previous settings.php so your site can connect to your database (this is where you're backups come in handy).

3.) When I got to step 10 I ran into a slight snag. I had already logged into the Profile that I first created, the very first one, however it still gave me an access error. I'm not sure as to why this happened. I have fooled around in the coding for the user modules, but I doubt this had anything to do with this. The problem, however, was easily remedied. I merely followed the instructions for just such a case, and edited the access string in the Update.php to read FALSE instead of TRUE, ran the update, then changed it back to TRUE.

4.) After that with some apprehension, I proceeded to re-enable my modules, and then switch over to my custom built them. (I must note here, I'm not sure of the problems that would occur, but for safety's sake, make sure you change your theme to garland, or blue marine, and disable on contrib modules before you start playing around with this update.

All in all, it was pretty straight forward, took about 20mins total, and everything seems to be working fine.

Thx to all those out there that made this update possible!.

-Stevo

wyn’s picture

wyn commented

Everything went completely smooth on my Dreamhosted site.

  1. Backed up the MySQL database
  2. Backed original Drupal directory.
  3. Uploaded 5.2 tarball.
  4. Copied .htaccess, files and sites directories from backup to 5.2 directory.
  5. Re-named directories to make the 5.2 active
  6. Ran update.php
  7. Done and done.

Thanks to all the contributors for their hard work. This was a painless upgrade.

Also, I'm playing with the 6-dev release and the upgrades look very exciting!

mrgoltra’s picture

mrgoltra commented

Good Day,

Where can I download version 6 to test?

Thanks,

Mark

melon’s picture

melon commented

http://drupal.org/download

mrgoltra’s picture

mrgoltra commented

Thank you. I guess I should have browsed the download area thoroughly. Thanks

mfer’s picture

mfer commented

Just following the instructions in the UPGRADE.txt file and all went off without a problem.

--
Matt
http://www.mattfarina.com

bestknight’s picture

bestknight commented

In Upgrade.txt it says:
"9. Re-install contributed modules."

but contributed modules are already in the backed up sites directory...which is supposed to be copied back - restored under step7...

"7. Copy the backed up "files" and "sites" directories to the
Drupal installation directory."

Can anyone please clarify how to exactly "reinstall"the contributed modules?

Or does "reinstall" simply mean reenabling the contributed modules under administration?

Thanks

nels’s picture

nels commented

You need to make sure any contributed modules are also copied over to the modules directory (I use a sub-dir of contrib, so I can find them).

Then re-enable the contrib'd modules in administration.

Hip hop funk at www.vcsb.com *now with 5.2 goodness*

mfer’s picture

mfer commented

Contrib modules should be in the /sites/all/modules or /sites/example.com/modules (where example.com is your domain name). They should not be in /modules.

There are several reasons for this. One, is maintenance. It makes maintenance a lot easier.

--
Matt
http://www.mattfarina.com

mfer’s picture

mfer commented

reinstall has a couple meanings depending on what the upgrade involves. If the upgrade were from something like 4.7 to 5.2 or from 5 to 6 than you would have to download the versions of your modules for that major version, put the files in the right place, enable them, and run update.php. Along with any special instructions that module may have.

Usually, with minor version upgrades (like 5.1 to 5.2) this just involves re-enabling them. To be sure that's all you need to do make sure to read the install, upgrade, and release notes in case there are any additional instructions.

As far as I am aware, in upgrading from 5.1 to 5.2 you just have to re-enable the modules.

--
Matt
http://www.mattfarina.com

CeesT’s picture

CeesT commented

Do not forget the "Important Note" of the News and Announcement page :

Important note
The file settings.php is one of the files containing vulnerable code. It is therefore critical to replace all of your sites' settings.php files in subdirectories of sites with the new one from the archive. After you have replaced the files, make sure to edit the value of the $db_url variable to be identical to the value in your old settings.php. This is the information that determines how Drupal connects to a database.
Wolfey’s picture

Wolfey commented

...so you don't go through what I went through - pages looked just fine for the administrator account, but for guests they looked barren, due to the fact that links to stylesheets, scripts, etc. were broken; even things like menu links were broken (leading to pages like "http://admin", for example - the domain was missing completely). That was the result of just overwriting everything and then running the upgrade script.

Fortunately, I had a recent backup (both database and files) on hand, and restored the site back to its 5.1 state to try this again. This time, though, I followed the instructions, including setting the theme back to Garland, disabling all modules (except those that came with Drupal) and deleting files instead of just overwriting them (excluding the "themes" and "modules" folders - I just overwrote the files for them). When I uploaded the files unzipped from the Drupal 5.2 archive and ran the upgrade script again, everything worked just fine, even after re-enabling my default theme and contributed modules.

I actually have Drupal installed in a subdirectory, which makes it a lot easier to manage things, and thought that was originally why I had the problem after the first upgrade...but since it worked just fine after the second upgrade, I'm guessing it was either a file that wasn't deleted (but should have been), a module that should have been disabled the first time around, or just a glitch, that caused my issue.

GarP’s picture

GarP commented

Everything went very smooth in the upgrade.

So far, the only thing I have found that does not work is the panel module. Have checked user access area, checked panel setup, have check site info area to make sure that start page is name the same as the panel (welcome), and even ran cron, database update script. However, the panel does not display. And, when it is unconfigured, the normal home page (node) shows up.

E G P

GarP’s picture

GarP commented

Wanted to follow up and let everyone know that after I uninstalled and reinstalled the panel module, then built a new "front panel" , everything came up as it had under 5.1. Don't know why the extra steps were required but now everything seems to be operating normal.

EGP

robomalo’s picture

robomalo commented

When I copied settings.php from 5.1 to the 5.2 settings directory, it broke my site. The site couldn't find phptemplate.engine. Then I used the new settings.php from 5.2 and filled out the required fields. That worked.

ubersoft’s picture

ubersoft commented

I upgraded from 5.1 to 5.2 with no problems, except that the comments data in $lists don't seem to update. Specifically I notice that when a node with no comments has a comment added to it, $lists still displays the "Add new comment" link instead of switching over to a comment count (1 comment, 2 comments, etc) -- also, the link that displays the number of new comments added to a node since the last time you visited doesn't display at all.

Odd. Sort of annoying... but everything else works.

tm’s picture

tm commented

I actually did an MySQL upgrade at the same time (since I was already backing up the database). That went fine.

Did 4 upgrades...
1) Got kicked out after replacing the core files (all 4 times). Not a problem, just an annoyance.
2) On installations where the Calendar module was installed, I saw that error that someone mentioned elsewhere. No problems, though.
3) On one installation, a single page was showing naked tags. It was using Filtered HTML for the input, and all the tags were there. The preview showed the teaser page displayed okay, but the full page weirded out. Changing the input to Full HTML worked. I control this page, so I can live with it. Other pages in the database that had similar tagging were okay.
4) Had one core hack (I didn't say that!) to put back (shhh!). Have to learn to do module overrides, one day.

Otherwise, it went fine.

UPDATE: went back to the odd page; had an improper <cite> tag in use; took it out and the page displayed properly. Strange that it showed okay on the teaser, though.

mrgoltra’s picture

mrgoltra commented

This is my first time updating the core.

What I did was read the update manual carefully and before upgrading, I made a checklist then....

1. Downloaded 5.2

2. Prepped 5.2 folder copied necessary files/modules(modified) needed. I had to compare core modified modules such as user and search to make sure nothing major has changed with new version.

3. Backup site

4. Backup database

5. Took Site Offline

6. Disabled non-Core modules

7. Changed My Theme to Garland

8. Copied files over

9. Ran update.php (reset clean URLs)

10. Login user1 with ?= in the urls

11. Enabled Custom Theme.

12. Enabled modules.

13. Tested Site.

12. Put site online.

The only thing I noticed is site has become little slower than before. Well time to troubleshoot.

Just wanted to share my update...

Thanks,

Mark

ZaphMann’s picture

ZaphMann commented

This was my first time updating the core also and I had a problem at the end - see steps 10-12
Because this was a minor upgrade installing 5.2 over 5.1 left contrib modules in tact.
I found the instructions for upgrade confusing because they implied that contributed modules would need reinstalling - and therefore reconfiguring - a huge timewaster. It turns out that they did not.

I also feel that the instructions do not factor in hosted environments, they instruct as if one had direct access to production site, not ftp access, however, again in this case, it didn't matter.

My sequence was:

1. Downloaded 5.2 locally, unzipped it.

2. Backup productioon site

3. Backup production database

4. Ensuring I had my #1 admin password right I logged in as admin#1 to TWO browsers **key

5. Took Site Offline

6. Disabled non-Core modules

7. left My Theme at pushbutton **issue here too

8. FTP'd 5.2 files over the top of my 5.1

9. Tried to run update.php (reset clean URLs) - Could not get in on either browser (safari/firefox) - said site was offline... so after some searching I discovered that
http://www.morethanoil.com/?q=user allows you to log back in.
BTW I was definitely #1 admin user: http://www.morethanoil.com/user/1/ & on search I found that some other people had the same issue... why some??

10. ran update.php and theme (pushbutton) came up without menus... I had to access via
http://www.morethanoil.com/admin/build/modules specifically

11. FTP'd over my custom version of Pushbutton Theme.

12. Enabled modules.

13. Tested Site.

12. Put site online.

Pretty smooth but some panic given the denied access...
thanks to all
Zaph

hallman’s picture

hallman commented

I accidently disconnected myself from my login. When I tried to get back in (using /?q=user), I got the messsage page not found for user/1. Very perplexed. Finally started over and discovered I had not moved the .htaccess file. I was trying to run Drupal without a .htaccess file! The second time around I did it correctly.

Thanks for all the helpful tips on this page.

Judy Hallman

edinjapan’s picture

edinjapan commented

Thanks for the hint about ?q=user. I stayed logged in and followed all the instructions, including changing the updata.php file access check to FALSE. I was still blocked out until I found the quote above.
In my case, I had the .htaccess file--though I didn't copy the old one--was just using the new one. I don't know if this was it issue or not. Everything is now working with the new .htaccess file--go figure.

mrgoltra’s picture

mrgoltra commented

It seems that imagecache module is not working properly. I set it to 50x50 to show on teaser but it does not. deleted current preset and recreated. Noticed that imagecache is not storing the files in its proper directory, nothing is being written. Images on teaser is showing as actual size. I don't know if this is because of cck or imagecache. another issue is CCK image field. I set the max resolution of images uploaded to 250x250 then again it is not resizing the image submitted.

mrgoltra’s picture

mrgoltra commented

.. hard since the search option is not available and doing search via google is time consuming. I would appreciate it someone could message me if they find something similar regarding this issue.

TIA,

Mark

ica’s picture

ica commented

I followed the all of the steps mentioned on the other posts - except deactivating the non core modules
and result was a -sort of- successful update to Drupal 5.1 to 5.2

the site worked fine except only and an important problem is the views.module. Current views worked except the frontpage view is not visible to unregistered users! And to re-edit views are no longer editable or new views can not be set or able to configure

- another words the views settings is blank / missing on
site/admin/build/views
-its not a total *blank* page its just the settings itself

so i have decided reinstall views module -from the server -and database- and a fresh install the module, so
site/admin/build/views
was back and i had to rebuild all the views from fresh on -which i was gain be able to access
site/admin/build/views/add
and built fresh site views.. so the views are back!

I guess the update messed up some parts of the module database or some kind of conflict

just posting that might help if anyone else experiencing the same/similar problem and may follow, consider doing the same

zwadderneel’s picture

zwadderneel commented

The upgrades went fine. I first upgraded our sites on our spike server. Tested. Got some people to check and test with me. Then cheerfully moved to upgrading production sites on our stable server. After that I was asked to upload some images for one of the sites. As user 1 I can see the new images fine, as visitor I can only see the images that were already there, not the just uploaded images. These seem "broken". I checked the directory they were supposed to be in. All there. Permissions correct too. Checked permissions for node access. Fine, fine. @#$%!* Now what? Someone got a helpful hint for me?

zwadderneel’s picture

zwadderneel commented

It was in the access views. All had gone blank. So if this happens for you too, have a look in the access control -> views module

the_therapist’s picture

the_therapist commented

I thought I would share this tidbit in case it helps someone who's going out of their mind right now. I upgraded my Drupal from 5.1 to 5.2 on my development server and everything went flawlessly. I replicated the same actions for the productions server. The front end functioned correctly, all installed modules worked, but in the backend /admin was blank along with /admin/logs/status and a few other seemingly random pages. I tracked it down to two modules, Taxonomy Browser and Taxonomy Breadcrumb. When I unchecked them from the module admin page, which was directly accessible by it's URL despite the blank /admin page, the blank pages then displayed correctly. Still, I couldn't figure out why those two modules were at fault after checking the bug reports, pending feature requests, etc. Add to that the lack of PHP error messages in the logs.

Solution: My development server is right beside me and has a gig of ram. My production server is hosted remotely with a company under a shared hosting plan. They limit PHP's memory for each user to 8 megs. It seems Drupal 5.2 now requires more than this in a number of situations. Thankfully, my hosting company is generous when it comes to .htaccess files and the line "php_value memory_limit 10M" corrects the issue. Yes, 2 megs of ram and Drupal cruises along swimmingly.I imagine some other user can't run their Joomla install because I stole some of their ram. Que sera sera...

Ole Martin’s picture

Ole Martin commented

Most of my sites was easy to upgrade, but one of them(with "Simplemenu" installed) get wrong. Now I have this message:

; $Id: node.info,v 1.3 2006/11/21 20:55:34 dries Exp $ name = Node description = Allows content to be submitted to the site and displayed on pages. package = Core - required version = VERSION ; Information added by drupal.org packaging script on 2007-07-26 version = "5.2" project = "drupal" datestamp = "1185477907" ; $Id: tracker.info,v 1.3.2.1 2007/07/09 03:33:58 drumm Exp $ name = Tracker description = Enables tracking of recent posts for users. dependencies = comment package = Core - optional version = VERSION ; Information added by drupal.org packaging script on 2007-07-26 version = "5.2" project = "drupal" datestamp = "1185477907"

and have tried to reinstalled 5.1.x again. Every others sites was easy so I didn't take back-up of this one. So wat can I do now?

Ole Martin
http://www.drupal.no
http://www.drupal1.no

megg’s picture

megg commented

my upgrade did not go at all well. i followed the instructions in upgrade.txt, but when i run update.php, i just get a blank window. when i try to view my site using another browser (where i'm not logged in as admin), i get the following error message:

Parse error: syntax error, unexpected T_STRING in mysite.com/drupal_cms/sites/default/settings.php on line 127

any idea what i've done wrong?

:((

megg’s picture

megg commented

i did a bit of searching and it seems an unexpected T_STRING usually means a typo, so i re-copied and pasted the $db_url variable, and it did the trick. :)

megg’s picture

megg commented

when i tried to log back in using the useful tip here:
http://drupal.org/node/162826
my site url kept redirecting to www.my-site.com/cgi-system/etc...
my site is currently in a sub-directory, so i had to specify that on line 115 of the settings.php file like this:
$base_url = 'http://www.mysite.com/subdirectory'; // NO trailing slash!

hope that helps anyone who encounters the same set of bizarro problems i did... :)

squadette’s picture

squadette commented

Hello,

I've installed Drupal 5.1 about a month ago on my home page. I have several small but important local customizations. I've kept the Drupal source code under the Git version control system.

Upgrade to 5.2 with took about 10 minutes, and I haven't lost a single line of changes.

I've described the procedure at Version Control Blog: http://versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/

ShutterFreak’s picture

ShutterFreak commented

What I did:

  1. Download and unpack the new drupal-5.2 code.
  2. Run a diff against my current live site code to narrow down the file changes (I run a site with some custom patches)
  3. Create a new folder containing only the modified files
  4. While reviewing the diff, I edited the remaining patches to Drupal core (fortunately only 1 patch)
  5. Created an archive containing the current files that I will overwrite with the Drupal 5.2 reviewed patch
  6. Applied the revised Drupal-5.2 patch
  7. Logged in as superadmin and ran update.php.

    8. It's in the last step that I keep getting a warning that the database scheme is out of sync. To me this means that the update script did not run, although it says it does.

    I then manually ran the code from the DB scheme updates (system update 1022 and comment update 1), but it didn't cure the "One or more problems were detected with your Drupal installation. Check the status report for more information." message. Everytime I run update.php I get to see the same patches to core and comment...

    Where should I look now?

    Update - it now works

    I disabled a couple of non-core modules and this time the update succeeded.

ShutterFreak’s picture

ShutterFreak commented

I disabled most non core modules and redid the upgrade. This worked :)

stinky’s picture

stinky commented

I updated from 5.1 to 5.2, but when running update.php, the page indicated that there weren't any updates. When I view mysite/drupal/admin/logs/status, it indicates I'm running version 5.1. I updated the site by:

a. downloading the new tar file
b. moving over all of my modules/themes/files/ from drupal-5.1 to drupal-5.2
c. using the new 5.2 version of settings.php
d. logging in as admin user and running update.php

thoughts?

TIA

UPDATE

I redid the install without moving modules over and using the basic theme (as indicated in update.txt) and everything worked.

Anonymous’s picture

Anonymous (not verified) commented

The upgrade went more or less smoothly.
I backed up databases, disabled non-core modules, reset theme to garland, copied over sites (but used *new* settings.php, with $db_url lines from the old settings.php).
Ran update.php. It directed me to set $access_check = FALSE in update.php. I did (temporarily).
It wanted to update my database (which I guess is what the update is). I let it. No error messages.

The issues:

1) I couldn't get to the login page, I kept getting the 'offline' page. So I got in this way: mysite.com/q?=user. No big deal.

2) Then I got the modules message about 'some things need correcting' which usually means a cron job hasn't run.
In this case, it wanted to update the database again. The update page said not to do that twice, but I didn't know what else to do, so I let the update proceed again. No apparent problems. All content still there.

3) Calendar module would not re-activate.
"warning: include_once(CALENDAR_PATH/calendar.theme) [function.include-once]: failed to open stream: No such file or directory..."
I'll deal with it later.

4) I had been using a variant of the garland theme called garland_dropmenu, very nice (www.thanhsiang.org/faqing/node/59)
I reverted to this theme but the menus I had created have vanished, in fact I don't see menus as an option now.
Oops, it helps if you re-activate the menu module!

nazirahmed’s picture

nazirahmed commented

I followed the update instructions and everything went fine after updgrade from 5.1 to 5.2 except when I try to create new node or edit the existing categories I am not been able to succeed. Any help in this regard is welcome. My site is located at the following link

http://www.freeonlineserver.com

Thanks in advance.

dixieau’s picture

dixieau commented

Went through all the steps to upgrade and now get the white screen for update.php

BUT when I had unpacked the drupal 5.2 I did so in the sites/all/modules folder (this also happened to my 'live' site which is stuck in limbo while I was preparing a brand spanking new site now both are blipped).

The worse thing trying to resolve this myself I have no backup left of my db that hasn't attempted to be updated, is there anyway to backpedal and remove the /drupal-5.2/ from /modules/ and carry on with the upgrade?

I just can't believe I did it again *idiot*

x2l2’s picture

x2l2 commented

i dont know what happends :(
when i try whit my old database:
Fatal error: Call to undefined function user_access() in /[...]/includes/menu.inc on line 1376

new sites whit no problem....

old site whit old 5.1 files works ok...

but i cant update i allways get errors

if i try to update.php :
Fatal error: Unsupported operand types in /[...]/includes/form.inc on line 341

Boru’s picture

Boru commented

On upgrading from 5.1 to 5.2

The Garland Color Scheme doesn't appear in the configuration options for the Garland theme.

I note elsewhere on the forums someone managed to get it to display by following the advice to ensure the "Color" module was enabled. This doesn't work for me. Any ideas?

Cheers

Brendan

Development machine:
Windows XP
Apache 2.2
MySQL 5.0
PHP 5.2.3

On this machine the color scheme appears with Drupal 5.1 sites but not with 5.2 or with 6.x-dev

The problem has been replicated on two other PCs

Boru’s picture

Boru commented

Seems I was barking up the wrong tree.

Turns out it was a public v private file system issue.

Does anyone know how to get the Garland color scheme configurator to appear with the file system set to private?

Thanks

Brendan

sudhii9999’s picture

sudhii9999 commented

I am not able to display the profile field information as i am used to with 5.1 version using the following code.please help me out

global $user;


profile_load_profile($user->uid);

echo "hi";
echo $user->profile_Fname;
echo "</br>";
echo $user->profile_Lname;
echo "</br>";
echo $user->profile_Cname;
echo "</br>";
echo $user->profile_Pnumber;
echo "</br>";
echo $user->mail;
echo "</br>";
echo $user->uid;
echo "</br>";
echo $user->name;
echo "</br>";

the above script used to work in the desired way but its now not working with the 5.2 version please help me out as soon as possible.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

But it works like this:

<?php
global $user;
$me = user_load(array('uid' => $user->uid));
echo "hi ". $me->profile_Fname .' '. $me->profile_Lname;
echo "<br/>";
echo $me->profile_Cname;
echo "<br/>";
echo $me->profile_Pnumber;
echo "<br/>";
echo $me->mail;
echo "<br/>";
echo $me->uid;
echo "<br/>";
echo $me->name;
echo "<br/>";
?>

Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database

NancyDru

sudhii9999’s picture

sudhii9999 commented

Hey nancyw

Thank alot buddy. I was breaking my head with this problem you really saved my life man.i was running out of time and this problem is making a real mess. i have posted in lot of places but no reply.finally u rescued me buddy.thank you so much

regards
sudheer varma

physiotek’s picture

physiotek commented

hi,

i did the 5.1 to 5.2 without big problems but there is a little thing that is not working anymore: the feed_icons are there but not linked to the feeds...

someone have an idea what can be causing this?

thanks,
pht3k

sudhii9999’s picture

sudhii9999 commented

it works

ica’s picture

ica commented

after the update i started to get manual cron run failure
/admin/logs/updates/check?destination=admin%2Fbuild%2F
gives a blank screen

and also
/admin/logs/updates
gets a blank screen too, i presume related

started to get %2 instead of / slashes
/admin/logs/updates/check?destination=admin%2Fbuild%2Fmodule

somehow a failyre of urlencode i presume
http://api.drupal.org/api/function/drupal_urlencode

looking for some solution i found this
http://www.mojahmedia.net/drupal-cron-run-failed-cron-busy-probably-stuc...

and run the query on mysql

DELETE FROM `variable` WHERE name = 'cron_semaphore';
DELETE FROM `variable` WHERE name = 'cron_last';

its cleaned up the crons and i tried to run cron again but i still get a blank page or 'cron run failed' message

apart from this the site works , but occasionallly gets blank screen or server error on any random page or view than its back again

[Server response is bad.] on blank screen
i have other sites on the same server and its works fine - as its not seems a not related with the server itself

I increased the memory on settings.php to encounter but it did not help

Anyone experienced identical to this and any idea why and how to fix or look?

kornbread’s picture

kornbread commented

I'm sure that this is something simple. What does this step in the instructions mean?

8. Verify the new configuration file to make sure it has the
latest and correct information.

I simply can't figure this out.

Thanks!

Anonymous’s picture

Anonymous (not verified) commented

I guess they are talking about settings.php

It should have the database connection info ( $db_url = etc. )
I think you need to use the new settings.php, so if you want to use the existing database, then copy the old settings.php somewhere or copy the $db_url, etc. from it.

mroots’s picture

mroots commented

Got a blank screen during upgrade

All contributed modules where disabled and the default theme was switched to Garland
Only the install.php would give me a page (already installed plz empty DB...)

The problem was in the settings.php file wich ive updated manualy and had left a $conf setting active for the localizer module
'cache_inc' => 'sites/all/modules/localizer/system/includes/cache.inc'

After commenting this line out I was able to upgrade

genderwarrior’s picture

genderwarrior commented

Did the upgrade and everything went fine, except now non-registered users get the "Welcome to your new Drupal Website" page. It disappears when I log into my accounts. Additionally all of the non-reg user permissions are not working - even though the permissions are all correctly listed in the admin panel.

Any suggestions?

etherphyte’s picture

etherphyte commented

This can be fixed by following the instructions here: http://drupal.org/node/64114

alloo’s picture

alloo commented

i probably missed something, being a total newbie, but I get the message on the upgrade in the adm theme settings:
Fatal error: Cannot redeclare phptemplate_init() (previously declared in /home/mysiteq/public_html/themes/engines/phptemplate/phptemplate.engine:9) in /home/mysiteq/public_html/themes/engines/phptemplate/phptemplate_old.engine on line 9

i see one post of this problem from a few years ago, but it is not clear to me.

it is not a big deal because it is a core installation with no work on it. just testing the waters.

Will

linguaetc’s picture

linguaetc commented

I just upgraded from 5.1 to 5.2 and have a couple of minor issues:

I currently am setting up two websites: linguaetc.com and rdhamilton.com They are being hosted by Bluehost.com

Everything appears to be working in rdhamilton.com (which is not the main domain)

With respect to linguaetc.com I have the following issues:

1. Under logs it is showing version 5.1. When I try to run linguaetc.com/update.php it shows "no updates available" when I drop down the "select versions". rdhamilton & linguaetc have separate databases. rdhamilton databases were updated with rdhamilton.com/update.php and the drupal version in the logs show 5.2

2. I no longer can change the default theme under Administer - Site Builder - Themes. I can successfully change the themes if I do it manually in the Settings.php file located in Public_html/Sites/linguaetc.com/. In rdhamilton.com I can change the themes without any problems.

3. I think the above is a result of how I originally setup drupal. Accordingly, the following points existed prior to the upgrade:
a. the main installation folder is drupal-5.1 (It now holds version 5.2...please see point b. below) which rdhamilton.com points to. With linguaetc.com being the main domain I had setup the files under public_html. The question is whether I can setup a link with linguaetc.com pointing to drupal-5.1 and delete the files under public_html. This would save me the trouble of updating the files twice (and having these problems :-).
b. When I setup drupal-5.1 I left the installation file name drupal-5.1. If anyone has the steps that I need to do after I rename the install file from drupal-5.1 to drupal please let me know. (Somehow I need to advise the database and other files that they should now look in drupal and not drupal-5.1

Thank you.
Richard

Joe Matthew’s picture

Joe Matthew commented

I followed the instructions in the file upgrade.txt, except for the part where it said one backup - made two (just in case). Didn't need either. Worked
like a charm with less than a minute of downtime. As caching was enabled those who were on the page probably didn't even notice!

-------------

Joe@Seoecom.com

Drupal CMS video tutorials

gtcaz’s picture

gtcaz commented

Hi all,

I can't seem to get past a problem with upgrading my database. I keep getting this error:

The update process was aborted prematurely while running update #1022 in system.module. All other errors have been logged. You may need to check the watchdog database table manually.

Watchdog doesn't have anything. Any ideas??

ryivhnn’s picture

ryivhnn commented

Upgrade went without a hitch on one of my sites (bmfm-redplanet.net), easy as.

My other site (alternativebaby.net) seems to have a permanent issue with at least one of the tables (node_access I think). The upgrade knocked off permissions like it had done before, and this time I had to do a bit more than simply hitting the big fat "repair" button in the cpanel. Followed the instructions given in a link in one of the previous posts to fix the permissions issue and after a bit of pissfarting around including following instructions and attempting to use the "rebuild permissions" button in drupal (kept getting zero-sized replies but I suspect that's the crappy server), managed to fix the permissions but am now missing a whack of posts from about 14 weeks ago to now, although new posts are coming through and displaying fine.

It's only anonymous users and possibly normal auth users that are missing the posts, admins etc can see everything fine. Working on that :)

works at bekandloz | plays at technonaturalist

Krickey’s picture

Krickey commented

I have two sites that run drupal. One on the free hosting site 110mb and one on Dreamhost. I upgraded the 110mb perfectly, but my dreamhost will NOT work no matter what I try. I've read the threads about trying to fix it and none work.

I like Dreamhost and I don't want to move to another hosting service, but I will move to a new CMS if I have to. :/

I did the exact same steps for both of them also.
Backed up files and db's.
Uploaded new files
Ran update script

ron_mahon’s picture

ron_mahon commented

Upgrade to 5.2 with no problems added mulitisite moved files directory to “sites/all”. Everything seamed to be working until a site administrator discovered he had restricted access. When this role is logged admin menu does not show..

Checked users perm and that roll has all admin perms

When I tried to look at user settings I get this error?

· warning: realpath() [function.realpath]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/inmrccom:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/inmrccom/public_html/includes/file.inc on line 285.
· warning: realpath() [function.realpath]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/inmrccom:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/inmrccom/public_html/includes/file.inc on line 285.
·
Stumbled around trying to understand this error message not having any luck.

Has anyone had this problem before?

Regards
Ron Mahon
Alias "Link" at
www.The-Villages-info-center.com