drupal.org - Upgrading Drupal

No update, No errors, No upgrade, No New Modules?

maul421 — Fri, 10 Jul 2009 09:46:34 +0000

Hello all,

I'm a newbie, so I'm probably missing something. However, I have read the documentation and searched around a bit...

After installing 6.12 I was told to upgrade to 6.13. Downloaded, copied everything (backups aren't important at this point for me) pasted the "sites" folder back in the newly updated drupal-6.13 directory.

Jump ahead to update.php, goes fast with no errors. But I'm still in 6.12, and after running cron I'm told to update still. I'm in offline mode, no fancy themes. I've repeated this many times now, with nothing changing, and never any errors.

Likewise, when I downloaded 2 modules, they just never show up in my Modules list. Those were copied into the correct folders and I read the READMEs, nothing tricky, so I'm guessing whatever is preventing me from updating is preventing those from showing up too?

Any ideas? Thanks!

Prior to Upgrade, How do I make a fully working copy of my Drupal 5.1 website?

Stephen Winters — Fri, 10 Jul 2009 04:29:57 +0000

Hi,
I currently have a Drupal 5.1 website that I'm trying to upgrade. Whatever I'm doing isn't working, so I'm asking for some help and direction. In the past I have crashed my Drupal website during an upgrade. It took me a couple weeks to get it up and running again. So I very cautious and don't want to crash my website again. I hope to avoid having my website down again.

This is what I'm trying to do:

The Plan: To avoid having the website down for a time, this time I want to make a fully functional copy of the website before trying to upgrade. I'll upgrade the copy first to work out the bugs, while leaving the main website up and running. Once I get the copy website upgraded and running, then I'll redirect the domain to the copy so that I can upgrade the main website. When I have the main website upgraded and running, I'll transfer the domain name back to the main website.

What I did:
A: Created the Database: I went into phpMyAdmin and created a new database, attached a User name and password, and then (using Operations>"Copy Database To") copied the contents of the main database to the copy database.

after Upgrade to 6.13 and upgrading "Views Module" Story Content nodes lost and other page content

mirrie — Thu, 09 Jul 2009 10:58:04 +0000

This is a desaster. I did a minor upgrade from 6.x to 6.13 and now most of my content is gone. I followed the steps in upgrade.txt and got all the necessary messages for a successful upgrade.
Afterward I was asked to rebuild the content access control permissions. That is when I got stuck.
This I had to abort because it continued endlessly.
But the main problem now is that most of my content is missing. Particularly the story content is lost. Strangely enough some remnants of that story content are still visible in the views I created. But in the Content Admin there are only pages left.
I will now go back to the pre-update state. It is a security update so how can I make that update without loosing all my content?

Please help!

Webform doesn't shown as menu items in new drupal 6.13!

lamp04ka — Thu, 09 Jul 2009 09:21:40 +0000

And the Webform Block doesn't work.

Should i upgrade to drupal 6.x from drupal 5.8

tusharb — Thu, 09 Jul 2009 04:44:08 +0000

Hi All, I had used drupal 5.8 for developing website and now it ready with some contributed modules like(panel which is not available in drupal 6) .Drupal.org not going to support version 5.8 after the end of this year (as per my information) .Now i am thinking about upgrading but it looks difficult to move drupal 6.x because of contributed modules not present with D6.

Again one more think is that all my work with website developing is finished(no more feature).

Is it good idea to upgrade from drupal 5 .8 to drupal 6.x ?
OR
Should i upgrade to some minor version within the drupal 5 (upgrade from drupal 5.8 to drupal 5.19 )?

Please Help me !!!!!!!!!!!!!!

Thanks in advance.

FAQ empty after upgrade from 6.9 to 6.13

Martijn76 — Wed, 08 Jul 2009 15:21:25 +0000

Since I upgraded our website from 6.9 to 6.13 earlier today, my FAQ is completely empty. No questions and no answers... I have checked the database and that still contains everything, however I have no idea how to get it back on my website (sorry I am pretty new to Drupal)

The error I got during the upgrade was:

Drupal database update
user warning: Duplicate column name 'detailed_question' query: ALTER TABLE drupal_faq_questions ADD `detailed_question` TEXT DEFAULT NULL in /usr/home/ws/myusername/www.mywebsite.com/www/includes/database.mysql-common.inc on line 298.
Updates were attempted. If you see no failures below, you may proceed happily to the administration pages. Otherwise, you may need to update your database manually. All errors have been logged.

Main page
Administration pages
The following queries were executed
faq module
Update #6003
Failed: ALTER TABLE {faq_questions} ADD `detailed_question` TEXT DEFAULT NULL
ALTER TABLE {faq_questions} CHANGE detailed_question `detailed_question` TEXT NOT NULL
UPDATE {faq_questions} SET detailed_question = question

Thanks for your help!

Garland theme "washed out" colors & errors

Parabola — Wed, 08 Jul 2009 12:45:34 +0000

Hello,
For the last few versions (I believe it started with 6.10) The garland theme is not displaying properly. The default color scheme is the only one that will load, and its WAY off. I have included a screenshot since I cant explain what its doing. I have deleted the theme folder and re-uploaded a few times. permissions seem to be okay (status report is all green)

PS: This is confirmed with IE7 / IE 8 / Firefox 3 / Chrome

Screenshot of Garland (6.13) (BlueLagoon Color scheme)

http://img33.imageshack.us/i/brokenc.jpg/

And here is the error I get when I try to change color schemes (theres ALOT more lines, but its basically all the same)

warning: getimagesize() [function.getimagesize]: PNG file corrupted by ASCII conversion in /var/www/cms/modules/color/color.module on line 263.
warning: imagecreatefrompng() [function.imagecreatefrompng]: 'themes/garland//color/base.png' is not a valid PNG file in /var/www/cms/modules/color/color.module on line 459.
warning: imagesx(): supplied argument is not a valid Image resource in /var/www/cms/modules/color/color.module on line 460.

Thanks!

6.9 to 6.13 upgrade - all content on white background, without template

jeyro — Wed, 08 Jul 2009 08:22:59 +0000

While generally I have been able to update error free, this time it has gone wrong.
After updating from 6.0 to 6.13 all content appears on white, non formated (non-template) pages. Going back to the previous 6.9 version and its database gave the same error. Now I'm back again at 6.13 with white background/no template pages. There were no error messages during the database updates. All content appears to be working fine.

I suspect that I might have missed downloading/backing up an ftp file (in sites? or a specific setting?) before the update. But I have no idea where the error is. Or is it something inherent to the update? It appears to affect the template only.

Could someone point me into the right direction how to fix this?

Uploading and overriding "Sites" directory a common practice?

Deisun — Tue, 07 Jul 2009 16:15:01 +0000

Title says it all...

With every update to drupal, are you expected to just backup your sites folder and after installing the update, re-upload your sites directory and replace everything thats there?
What if the update has some updates to any files in the sites directory and you replace them with your old sites folder? Wouldn't that screw stuff up?

Forgot to turn off contrib modules before upgrade

Alex Lee — Tue, 07 Jul 2009 14:58:20 +0000

I just upgraded my drupal system from version 6.12 to 6.13.
In the process, I forgot to turn off the contrib modules.
However, after the upgrade, everything seemed quite normal.

Could there be some hidden problems that may occur later?

Any hints could be much appreciated.

What is the upgrade path from 5.1 to 6.13?

Stephen Winters — Tue, 07 Jul 2009 12:47:07 +0000

Hi,
I currently have Drupal 5.1 on one of my websites. I want to upgrade to the latest stable version of drupal, which I believer is 6.13. Which drupal versions do I have to upgrade to. For instance, do I have to upgrade to version 5.2, then to 5.3, then to 5.4, then to 5.5 etc. all the way up to version 5.19, then upgrade to version 6.1, then to 6.2, etc. (Do I have to upgrade my website through all 30 sum new versions (5.x & 6.x) OR are there specific Drupal versions I can skip to . Is there a chart somewhere (which it seems there should be) of which steps (which versions) one needs to upgrade to, which versions can be skipped?

Thanks,

Best Wishes,
Stephen

upgrading disabled modules

omega2 — Tue, 07 Jul 2009 12:28:30 +0000

Hi,

I'd like to upgrade our drupal 5.x site. I'm wondering whether it is necessary to upgrade disabled modules as well. We have a lot of disabled modules at our site so omitting them would significantly save our time..

BTW is it safe to remove the directories containing the disabled modules? I know there may be some remaining tables in the database but just having them there don't bore me.. Is there some other possible problem? BTW there are no modules to uninstall on the uninstall page..

Thank you in advance,

Petr

After upgrade - many block configerations lost

general need — Tue, 07 Jul 2009 09:25:36 +0000

I just upgraded from 6.12 to 6.13

It is not something I enjoy doing and have little experience with it.

All seemed to go ok except that many of my blocks had been moved back to Disabled and many more had 'forgotten' their configerations, eg, only visible on certain pages. I rectified it manually, but I have a lot of blocks and configerations so it was a real hassle.

Did I do something wrong and how can I avoid this in the future?

(also, is there any way besides writing it down which modules I had active before upgrading?)

Upgrade to 6.13 kills books

combatwombat_nz — Tue, 07 Jul 2009 03:26:26 +0000

After upgrading from 6.12 to 6.13, following the UPGRADE.TXT, we have an issue with the Books not appearing in the frontend, but I can still see them in the Books table of the database. And PathAuto is not activating(assigning the path automatically) either. Any ideas?

What's wrong with 6.13 upgrade ??

Junro — Mon, 06 Jul 2009 19:06:42 +0000

Hello, I read a lot of posts with very bad ugly comments on the 6.13 upgrade of Drupal Core.

I upgrade it using the simple method and after upgrade it, in /admin/reports/updates I still have Drupal 6.12.

Error message from drupal_http_request after upgrade 6.12 -> 6.13

letharion — Mon, 06 Jul 2009 18:04:46 +0000

I followed these instructions: http://drupal.org/node/390448

And after running update.php the first
Now I get:
* warning: preg_match() expects parameter 2 to be string, array given in /home/1/t/teamzinzino/www/includes/common.inc on line 492.
* warning: preg_match() expects parameter 2 to be string, array given in /home/1/t/teamzinzino/www/includes/common.inc on line 492.
on ?q=admin/reports/updates

The line is a preg_match on $GLOBAL['db_query'] with makes sense as that is an array and not a string.

What do I do?

4.7 to 5.19 upgrade resulted in blank or "site off-line" screen with no apparent access for admin - please help.

icebox500 — Mon, 06 Jul 2009 17:18:20 +0000

I have created a test box to try a 4.7 to 5.19 upgrade.

I have followed all the steps here: and everything seemed to go smoothly.

HOWEVER: no matter what page I try, I am unable to bring the site back online.
I've gone to /admin, /admin/modules, ?q=user, ?q=admin, etc... and get either a blank page or the "Site is off-line" page.

Additionally, I removed all non-core module folders (and then put them back) to verify that it made no difference.

I appreciate all your advice or tips.

Site Breaking Problem with URL path

matthew111 — Mon, 06 Jul 2009 16:22:24 +0000

My site has a problem with the url path. After upgrading to drupal 6.13 this problem appeared. Throughout my site, the url
path simply appends the destination to the location of the current page, instead of just using the destination.
For example, while on mysite.com/admin/build/block, when clicking configure block it points me to

mysite.com/admin/build/admin/build/block/configure/block/22

You can see if I just remove the first "admin/build/" then it would work, but the problem also prevents me from saving blocks.
With just a few clicks the url path starting from the main navigation menu becomes:
admin/build/admin/build/admin/build/admin/build/modules

I strongly suspect that another problem that I have had is related to this problem, or is causing it.
On some pages (same site) an error message appears and states
"Fatal error: Unsupported operand types in /html/mystuff/includes/common.inc on line 1385"
The function that ends on this line is:
(from the file common.inc)

function url($path = NULL, $options = array()) {
  $options += array(
    'fragment' => '',
    'query' => '',
    'absolute' => FALSE,
    'alias' => FALSE,
    'prefix' => ''
  );

Is it a module that I installed that has broken my url paths or is it something else? How do I fix this problem? Please help :(

Are upgrades reequired

npoleon06 — Mon, 06 Jul 2009 16:02:56 +0000

I am contracted to build a website for a client and I'm considering Drupal. Is upgrading frome version to version required? I want to build on the existing version of Drupal and then never upgrade or change it. Is this possible? Are the modules that I use/include in the original build in danger of (one day) not being supported and/or not working anymore?

When trying to update drupal...

T3hlulzkiller — Mon, 06 Jul 2009 12:45:55 +0000

to 6.13 from 6.12, when I run update.php it redirects to reinstallation? Obviously I don't want to reinstall drupal, what should I do?

thanks.

Module to upgrade Drupal cores / modules like Windows' application

tm01xx — Mon, 06 Jul 2009 10:12:43 +0000

Hi,

I can see that many people are frustrated with upgrading Drupal because it is potentially too much risks of site collapsed after then. Even for expert Drupal guys, the works of upgrading are actually manually from A->Z such as downloading, uploading, backup database, rename folders/files, etc.

It is not good really because it wastes time and high risk of accident so I would like to know if there is any existing module to help developers to upgrade Drupal core / module automatically (the current /update.php doesn't help really)? It would be perfect if it just runs in background like applications in Windows OS (e.g Mcafee anti-virus) and notifies user once if it is done.

Have a nice day!

6.12 to 6.13 update - administration page error

orkuntuzel — Mon, 06 Jul 2009 09:46:21 +0000

Hi!
I know maybe the solution is so simple and I could find it by google but I couldn't !
The problem is, when I upgraded to 6.13, http://www.mysite.com/drupal/admin link stopped working.

After the upgrade process, there wasn't a problem about the admin page but when I uploaded some modules and my theme(acquia_slate), the link stopped working.

the links inside the admin page, for example admin/build or admin/settings have no problem.
Only the admin link...

The IE error report (HTTP 500) says that site might be in maintenance or there's a programming error.

Hope someone will help me
Thanks

Upgrading from 6.12 to 6.13 gives error

kdes — Mon, 06 Jul 2009 08:06:01 +0000

preg_match() expects parameter 2 to be string, array given in /var/www/includes/common.inc on line 492

I get the above error when I try to update drupal from 6.12 to 6.13. I haven't updated the database yet just the codebase and the error shows in the Status report page. I am using a database with table prefixes. Is anyone else getting the same error and is there a fix for this.

update.php -> Select versions -> What these numbers (6000, 6001, 6002, etc.) stand for?

valel46 — Sun, 05 Jul 2009 23:17:35 +0000

Hi,

When I run update.php after upgrading some modules, it says that the version I'm updating from has been automatically detected and that I shouldn't need to select a different version. However, can someone please explain to me what exactly these numbers (6000, 6001, 6002, etc.) stand for? Because it seems that it doesn't detect them automatically, many times under the updated module, it selected "No updates available" even though I just replaced/upgraded the module to a newer version.

For example, for the Rotor Banner module, I upgraded it from 6.x-1.4 to 6.x-2.2. When I run update.php, it still selected "No updates available" for me. And if I pull down the drop down list, I see 6000, 6001, 6200. I'm a bit confused, because these numbers don't seem to match 6.x-1.4 nor 6.x-2.2?