Acidfree 5.x-1.x-dev (2008-Feb-26). I can create albums and upload pictures, however when I create/edit the album the parent setting is ineffective: I can pick a parent from the dropdown and the choosen parent is still there in the album preview, but after submission the parent setting is gone (it is always set to "root album"). The vocabulary setting for albums is the original one. Nothing is reported by watchdog. If more info is needed please provide indications.

Comments

vhmauery’s picture

vhmauery commented
Status: Active » Fixed

Yup. That would be a regression caused by a fix for the 'editing root album has warnings' bug. Now both should work. Committed fix to CVS.

skizzo’s picture

skizzo commented

thanks. I installed from CVS and run update.php. I am getting the following warnings/errors.
I may be wrong, but I believe I did not missed any previous update.

    * user warning: Table 'drupax.acidfree' doesn't exist query: ALTER TABLE acidfree DEFAULT CHARACTER SET utf8 in /var/www/drupax/includes/database.mysql.inc on line 172.
    * user warning: Table 'drupax.acidfree' doesn't exist query: SHOW FULL COLUMNS FROM acidfree in /var/www/drupax/includes/database.mysql.inc on line 172.
    * user warning: Table 'drupax.acidfree_hierarchy' doesn't exist query: ALTER TABLE acidfree_hierarchy DEFAULT CHARACTER SET utf8 in /var/www/drupax/includes/database.mysql.inc on line 172.
    * user warning: Table 'drupax.acidfree_hierarchy' doesn't exist query: SHOW FULL COLUMNS FROM acidfree_hierarchy in /var/www/drupax/includes/database.mysql.inc on line 172.
    * user warning: Table 'drupax.acidfree' doesn't exist query: ALTER TABLE acidfree ADD COLUMN share TINYINT(1) NOT NULL DEFAULT '0' in /var/www/drupax/includes/database.mysql.inc on line 172.

Update #1
    * Failed: ALTER TABLE {acidfree} DEFAULT CHARACTER SET utf8
    * Failed: ALTER TABLE {acidfree_hierarchy} DEFAULT CHARACTER SET utf8

Update #2
    * Failed: ALTER TABLE {acidfree} ADD COLUMN share TINYINT(1) NOT NULL DEFAULT '0'
vhmauery’s picture

vhmauery commented

I am not entirely sure why you are seeing those errors. Someone else has seen them too, though I don't recall what issue or email it was in. For some reason, the installer tried to run updates that apply to the 4.6.x tree. The schema updates start at 1 and increase with each release. A new install of 5.x should never try to run any updates unless it is trying to upgrade from earlier versions. So I am not sure why you are seeing that. I think you can safely ignore those warnings as long as everything is running okay for you.

vhmauery’s picture

vhmauery commented
Status: Fixed » Closed (fixed)