First the UPGRADE.txt file contains the instructions pertaining to a typical Drupal installation, not specific to commons.

Second, the specialized instructions listed at http://drupal.org/node/1409592 say to back up the existing site and then to copy the contents into the document root. Shouldn't the instructions say more about what to do with the existing contents of the site directory? If one leaves everything in place, isn't there a risk of leaving files that are no longer needed or, potentially, that have moved?

Comments

jsibley’s picture

jsibley commented

I decided to move and save everything under my sites directory, delete everything else, and start fresh with the new tarball. I expanded it into the previous commons directory, copied modified the .htaccess file to redirect to www, and copied over the proper settings.php. Then, I ran update.php.

This almost worked. Update did not create a files directory or, of course, any subdirectories under files. I didn't think I had any files to worry about, but a variety of things can go under the files directory, including user photos (under pictures).

I spent quite a while trying to figure out why imagecache wasn't working properly. Eventually, I realized that it wasn't displaying user photos because it couldn't find them. Once I moved them over, imagecache worked fine.

I also then used drush to download a few modules I had been using (e.g., realnames and front) and things are mostly working as expected (I'll ask about the remaining problems in a separate thread).

If anyone can improve on this process, please chime in.

Andrea C’s picture

Andrea C commented

https://network.acquia.com/downloads/drupal-commons/6.x-2.4-release-notes

js’s picture

js commented

I am having problems with Drush after updating.

strpos(): Empty delimiter pm.drush.inc:1013 [warning] -- or a line number close. It will break in more than one place in

function _pm_find_common_path($project_type, $extensions)

and the problem appears to be that the three Commons themes are included in $extensions when $project_type = module.

$path2 = drupal_get_path($project_type, $project);

returns null.

This was my very rough work around:

if ($project == 'commons_origins' || $project == 'commons_connect' || $project == 'commons_roots') {
echo "skip $project\n";
break;
}

js’s picture

js commented

Pressflow is causing a problem.

After updating, I am seeing these two warnings in dblog:

Warning: explode() expects parameter 2 to be string, array given in boxes_footer() (line 155 of ../profiles/drupal_commons/modules/contrib/boxes/boxes.module).
Warning: Invalid argument supplied for foreach() in boxes_footer() (line 155 of ../profiles/drupal_commons/modules/contrib/boxes/boxes.module).

which comes from here:

function boxes_footer() {
// Besure the page isn't a 404 or 403.
$headers = drupal_set_header();
foreach (explode("\n", $headers) as $header) {

This
http://api.drupal.org/api/drupal/includes--common.inc/function/drupal_se...
says that drupal_set_header() should be returning a return delimited string, but my quick test returned an array.
which I now see comes from pressflow's
function drupal_set_header($name = NULL, $value = NULL, $append = FALSE)
moved into /includes/bootstrap.inc (from /includes/common.inc)

As a patch to work around this, I changed the boxes function:

function boxes_footer() {
// Besure the page isn't a 404 or 403.
$headers = drupal_set_header();
$headers = is_array($headers) ? implode("\n", $headers) : $headers; // added to work around pressflow
foreach (explode("\n", $headers) as $header) {