Upgrading site from 4.7.6 to 5.1

Rest of Drupal is working fine, but AcidFree albums not working - get a "access denied" message.
That message is probably misleading, noticed that when running update.php, even when AcidFree is enabled, it did not update any AcidFree tables.

This also seems to be supported by the log errors, that show:
Table 'drpl.acidfree_album' doesn't exist
query: acidfree_load SELECT * FROM acidfree_album WHERE aid=253 in
/home/user/public_html/includes/database.mysql.inc on line 172

Tried running update.php again - clicked on "Select Versions" - it only shows 1, 2, and No Updates Needed for AcidFree. The acidfree UPGRADE doc seems to suggest that 3 should be value shown in update table?

That's where things are for now...

Comments

vhmauery’s picture

vhmauery commented
Status: Active » Closed (fixed)

If the table does not exist, it means you didn't follow the upgrade instructions properly.

For Acidfree to upgrade properly, you must have Filemanager, Image, Taxonomy, Video, Video_image, Video_upload, and Views.

Then, running the update script should update Acidfree to schema 4.

bwooster47’s picture

bwooster47 commented

I cannot find 5.x version for FileManager - http://drupal.org/project/filemanager - is there one? Which one should I use?

Also: on my Drupal modules admin pages, where it lists all the dependencies, I don't see anything missing (in red color), here's the list shown:

A simple unified media management module for Image and Video modules
Depends on: Taxonomy (enabled), Views (enabled), Image (enabled)

I have no "(disabled)" comment in the module admin page for any modules.
{The docs say Video is needed only if used, I'm not using any video}

Finally - I can visit the acidfree/test page - it shows no errors - would be good if it could detect upgrade failure and report on it on that page.

vhmauery’s picture

vhmauery commented

There is no released Drupal 5 version of Filemanager, but the HEAD version is compatible with Drupal 5.

The reason the dependency does not show in the modules page is because the dependency only exists for the upgrade. After the upgrade, Filemanager can be removed.

bwooster47’s picture

bwooster47 commented

For others who might trip over this, here's all that has to be done:
Was tricky finding the filemanager module, here's the link (seen only when you click on "View all Releases"):
http://ftp.osuosl.org/pub/drupal/files/projects/filemanager-HEAD.tar.gz

Then, even when unpacked (into sites/all/modules), it will not show up in the modules admin page.
Have to create a file "filemanager.info" and put it in sites/all/modules/filemanager, here's a dummy file that can be created, I copied another modules .info file and renamed a few items:

name = Filemanager
description = "Filemanager"
version = "$Name: DRUPAL-5--2-1-1 $"

; Information added by drupal.org packaging script on 2007-04-17
version = "5.x-2.1-1"
project = "filemanager"

Then enable filemanager, run update.php to get acidfree updated, go back to disable filemanager.

So far so good, now dealing with problems with aliases, will probably write a new topic on that, after I understand what is going on, but aliases are behaving very strangely now.
Picture aliases are working fine, but album aliases are all behaving strangely.
For example, all my albums were aliased with "albums/[acidfreepath]/[title]" and I had albums/sunsets as an album, which was an alias to node/129, for example. Now, the alias albums/sunsets does not show in the URL anymore - it works, displays correct album, but it shows album/21 instead of albums/sunsets in the URL.
This page does show the normal grid-view; there were other aliases automatically created, such as acidfree-albums/sunsets, which shows a vertical list view of the albums. This list view is also being paginated incorrectly - have only 4 albums, all show on one page, but it still shows 5 pages to page through, all showing the same 4 albums.

I suspect I'll have to manually change all old album aliases from pointing to node/nnn to instead say album/nn - for example, in the above case, change the alias for albums/sunsets from the current node/129 to be instead album/21.