When upgrading from the latest 5.x CCK to a D-6.5 Drupal running CCK 6.x-2.0-RC10, I get 500 errors during the upgrade process.

I using 1and1.com as my host, and I am consequently unable to get error details.

I have attached an un-upgraded copy of my database.

CommentFileSizeAuthor
#1 lots_of_errors_after_enabling_before_upgrading.png345.44 KBaren cambre
db261144649.zip332.92 KBaren cambre

Comments

aren cambre’s picture

aren cambre commented
Status: Postponed (maintainer needs more info) » Closed (fixed)
StatusFileSize
new lots_of_errors_after_enabling_before_upgrading.png345.44 KB

Rough procedure to generate problem:

  1. Copy 5.x DB to new DB.
  2. Point 6.x site to new DB. (Via /sites/[sitename]/settings.php.)
  3. With no /sites/[sitename]/modules directory present, run upgrade.php. (Will require that change to settings.php to allow login bypass.)
  4. Upgrade runs fine. Now copy cck RC10 into /sites/[sitename]/modules.
  5. Enable Content module in admin/build/modules. Notice all the pretty errors (see lots_of_errors_after_enabling_before_upgrading.png).
  6. Run update.php again, accepting defaults.
  7. Enable Fieldgroup, run update.php again.
  8. Same with Text...
  9. Same with Node Reference...
  10. Same with User Reference...
  11. Same with Number...

...and it worked.

So disregard.

aren cambre’s picture

aren cambre commented

Hmm, well, now I get a 500 error after enabling Views 2.0 final after following the above. I also get a 500 when trying to view admin/build/modules (after enabling Views; didn't happen before), and update.php also fails with a 500.

The first time I got the 500 error, from the report at the very top, I didn't follow your instructions exactly: I upgraded CCK after some other modules. But I am now getting the 500 on the second upgrade attempt when I first strictly followed the CCK upgrade instructions.

Is there some incompatibility between Views 2.0 final and CCK RC10?

yched’s picture

yched commented
Status: Active » Postponed (maintainer needs more info)

Getting errors is normal before running the upgrades. This is true for any module.

There is no known incompatibility between latest Views and CCK.
500 errors are always tricky to debug, could be many things. If we don't have a more specific error message from the PHP or Apache logs, there's not much more we can do to help...

aren cambre’s picture

aren cambre commented
Status: Active » Postponed (maintainer needs more info)

(Updated #2 to add clarity for yched's comment in #3.)

A phpMyAdmin export of all tables is at http://arencambre.com/db234809671.sql.zip.

A copy of my modules directory is at http://arencambre.com/modules.zip. These are site-specific modules, not D6.5 modules.

aren cambre’s picture

aren cambre commented
Status: Closed (fixed) » Active

Changing status because I am not sure what more info I can provide at this point.

aren cambre’s picture

aren cambre commented
Title: 500 error when upgrading from 5.x » 500 error when upgrading from 5.x and enabling Views UI 2.0
Status: Postponed (maintainer needs more info) » Active

The plot thickens.

It appears the problem only happens when using the Views UI module. Simply using the Views module alone does not cause the problem.

I do have one 5.x view, and per http://drupal.org/node/322909, individual views appear to not be upgraded automatically--you have to go through steps other than update.php to upgrade individual views.

Still working...

aren cambre’s picture

aren cambre commented

New development: admin/build/modules never gives me a 500 error unless I enable either Views UI 2.0 and 1. Node Reference RC10 or 2. User Reference RC10. I have all other delivered CCK modules enabled.

update.php gives a 500 error after the "Updating x of y" screen if I enable Node Reference, Number, Option Widgets, Text, or User Reference.

aren cambre’s picture

aren cambre commented

Has anyone been able to reproduce?

aren cambre’s picture

aren cambre commented
Component: upgrade path » General

Upgrading to Views 2.1 did not fix the problem.

aren cambre’s picture

aren cambre commented

Upgrading to Drupal 6.6 did not fix the problem.

aren cambre’s picture

aren cambre commented
Title: CCK RC10 breaks Views UI 2.1 after D5 > D6 upgrade » CCK 6 RC10 incompatible with Views UI 2.1

I re-created the exact same problem on a totally different site that was upgraded from D5. I can provide an SQL GZ of the database upon request.

Something that CCK RC10 is doing on upgrades from D5 is resulting in a database state incompatible with Views UI 2.1. Specifically, I can enable the Views 2.1 module, but I get a 500 error when I try to later enable the Views UI module. The module does not in fact get enabled.

It's difficult for me to diagnose further since I am on 1and1.com.

aren cambre’s picture

aren cambre commented
Title: 500 error when upgrading from 5.x and enabling Views UI 2.0 » CCK RC10 breaks Views UI 2.1 after D5 > D6 upgrade

Oops, title not really correct.

yched’s picture

yched commented

Sorry, but I cannot reproduce with my D5 upgrade setup.
As I explained above, a 500 error provides no meaningful info in itself. "If we don't have a more specific error message from the PHP or Apache logs, there's not much more we can do to help..."

Maybe try latest CCK-dev ? There have been a few changes in the way userref / noderef modules interact with Views.

In #11 : "The module does not in fact get upgraded"
What do you mean exactly ? Which module ? and what makes you think it doesn't get updated ?

aren cambre’s picture

aren cambre commented
Title: CCK 6 RC10 incompatible with Views UI 2.1 » CCK RC10 breaks Views UI 2.1 after D5 > D6 upgrade

yched,

Did you try the database I provided?

As for #11, I just corrected it. Should have written "enabled," not "upgraded." Sorry!

yched’s picture

yched commented

I cannot reproduce with the elements (db dump + modules folder) provided in #4. Really sorry, but this must really be something related to your host, and the error message doesn't provide enough information for me to work with.
Maybe simply try raising PHP's memory ?

Setting title to a less general, less dramatic title, as this has not been reported elsewhere :-(

aren cambre’s picture

aren cambre commented
Status: Active » Postponed (maintainer needs more info)

I whipped up a VM last night, but I haven't had a chance to try it. Changing the status until I can get back with you.

PHP memory has alternately been at 16MB and 24MB with no effect.

hass’s picture

hass commented

I think you need more memory for this two modules... try 32MB or 48MB and check your PHP and Apache logs.

aren cambre’s picture

aren cambre commented

Tried 64MB last night. No bueno.

I am still getting the VM running. (Time was too limited last night.) Once I have that down solidly, I'll try it on the VM. That way I can give you logs.

aren cambre’s picture

aren cambre commented
Title: CCK RC10 breaks Views UI 2.1 after D5 > D6 upgrade » CCK RC10 + Views UI 2.1 + 1and1.com = no work after D5 > D6 upgrade
Priority: Critical » Normal
Status: Postponed (maintainer needs more info) » Active

I got it working locally on XAMPP on Windows Vista with no errors. Looks like this is a problem with 1and1.com, my web host. I checked .htaccess files down to the root of my site, and I checked php.ini, and I could find nothing unusual.

I am OK if you want to close out this issue now.

abx’s picture

abx commented

What PHP version that you use on 1and1? If not 5, then, try it with 5. It's not only version but there is some configuration changed. (Ex. Register Global = Off / On, etc.)

AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php

Just put either line above (I put both and it works fine) into .htaccess.

aren cambre’s picture

aren cambre commented

abx: Thanks. I had it that way originally, and I tried it without that (defaults to PHP4), and nothing worked.

I authored Register globals should be disabled in February. :-)

yched’s picture

yched commented
Status: Active » Closed (won't fix)

OK, closing then. Good luck with this...

aren cambre’s picture

aren cambre commented

For the record, this is still happening with CCK 6.x-2.0 final.

ivanmilos’s picture

ivanmilos commented

Hello!

I had a similar conflict between CCK 6.x 2.0 and Views 2 on a fresh drupal installation. It seems it was somehow caused by DHTML Menu module. Disabling DHTML Menu solved my problem. It was a strange bug. I had the problem only on my live server (a Croatian hosting provider), not on my localhost testing server. Installed PHP and MySQL versions were the same on localhost and on the live server.

So, do you have DHTML Menu installed?

aren cambre’s picture

aren cambre commented

I have not run DHTML Menu and was having the problem with a minimal set of menus.

Thanks for pointing out that module! It appears to be better than the now-unsupported ActiveMenus module.

mirrors’s picture

mirrors commented

Any progress on resolving this? I keep coming up with the same issue on clean installs of CCK and Views. Any help would be useful.

Kingscoop’s picture

Kingscoop commented

Post no 20 solved this issue for me completely. I'm using 1and1 and PHP was 4.4.9

AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php

I had tried the top line previously as recommended elsewhere but that crashed the complete site. Adding the second line has got me going again.

Thank goodness for this forum and the people posting the answers.