Upgrading Drupal

I was upgrading from 7.2 to 7.4 through SSH. I made a directory called UPGRADE outside the public_html and saved 7.4 there. I removed the sites folder and copied everything over to public_html using the following command:

cp -R * drupal-7.4 ../../public_html

All files copied over, but none of the subdirectories made it through. I thought the capital R was not recognized by our shell, so I tried lowercase r.

cp -r * drupal-7.4 ../../public_html

I'm running a site using 6.22 with several add-on modules. I'm exploring my options for an upgrade to Drupal 7, but I haven't found a convenient way to determine if 7.x-compatible versions are available for of all of the modules I'm using. My "Available updates" report lists only the 6.x-compatible versions, so I've been manually checking each module's project page for version information. Is there an easier, automated way to find out when all of the modules I need are ready to go?

Hi,

after I upgraded to 6.22 from 6.16 (6.17 has the same problem), users can't logging and work normally.

I have been trying to upgrade my site from Drupal 6 to 7 for a number of days now and each time, I run the update.php, I get errors in the Trigger module and Search module. I have followed everything in the upgrade.txt down to the 'T' and started from scratch each time the update process fails.

This is the error I get in my Trigger module:

Failed: PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'hook' at row 1: UPDATE {trigger_assignments} SET hook=:db_update_placeholder_0 WHERE (hook = :db_condition_placeholder_0) AND (op = :db_condition_placeholder_1) AND (aid = :db_condition_placeholder_2) ; Array ( [:db_update_placeholder_0] => workflow_workflow-pro_tournament_report-1 [:db_condition_placeholder_0] => workflow [:db_condition_placeholder_1] => workflow-pro_tournament_report-1 [:db_condition_placeholder_2] => 4 ) in trigger_update_7000() (line 67 of .../modules/trigger/trigger.install).

And this is the error in the Search module:

Failed: DatabaseSchemaObjectExistsException: Cannot add primary key to table search_dataset: primary key already exists. in DatabaseSchema_mysql->addPrimaryKey() (line 392 of .../includes/database/mysql/schema.inc).

Hello.

Drupal 6 on CentOS 5. Running into issues with recent versions of modules that want PHP 5.2.x while the host has PHP 5.1.6.

Is it enough to take the Drupal server offline, upgrade PHP, and bring Drupla server back online? Is a run of update.php necessary?

Other gotchas, suggestions?

Thanks

At the step, where I start update.php, after looking what to update, the script says that's there's nothing to update and current state report says that I run 7.2 and there's an update to 7.4.

I'm sure I downloaded 7.4 -- I tried 2 times -- zip and tar.

WTF?