Closed (fixed)
Project:
Acidfree Albums
Version:
5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Oct 2008 at 22:38 UTC
Updated:
16 Nov 2008 at 23:15 UTC
After my last security update of Drupal 5 and doing something like image rotation in the "Album Contents" section
the Gallery produce many errors after submit like:
# warning: Missing argument 2 for node_form_validate() in /usr/share/drupal5/modules/node/node.module on line 2053.
# warning: Missing argument 3 for node_form_validate() in /usr/share/drupal5/modules/node/node.module on line 2053.
# Der Pfad wird bereits verwendet.
# warning: Missing argument 2 for node_form_validate() in /usr/share/drupal5/modules/node/node.module on line 2053.
nothing was done after submit. Also changing image titles aren't working.
The Gallery is unusable in the Contents section.
Comments
Comment #1
eddified commentedI have this same problem. I haven't tried rotating the images in the "album contents" view, but what I have tried (deleting images) does still work, despite the error messages.
The easiest way to duplicate this is actually to not make ANY changes, but just to hit "Submit" anyway. You'll see the error messages, even if you didn't make any changes.
--------------------------------
About the other error message you are getting: "Der Pfad wird bereits verwendet." (which isn't directly connected with acidfree, I don't think -- or is it? not sure)--- I'm getting it as well. Except in English, it's something like "The path is already in use."
If you use the 'pathauto' module (or maybe even if you don't--not sure) and if you don't fix this second problem, then when you do "mass import" of a video, the thumbnail image node won't get created for the video, and you'll never see a thumbnail on it (it won't even be re-generated later). Here's a work around: This problem is caused by an incorrect entry in the url_alias table.
Doing this will prevent the incorrect entry from being inserted again in the url_alias table.
Comment #2
vhmauery commentedI saw this in my installation and was not sure if I was the only one... Glad you posted the bug. I tracked it down to changes in node.module and committed a fix.
Comment #3
eddified commentedI'm glad you figured it out. I spent hours trying to figure out this bug and came up with nothing. I'll need to hear how you managed to fix it sometime. I don't really know how forms work in drupal, and I couldn't figure it out because I had no clue how the form was supposed to look. Apparently the form gave the Node module some tizzy fits... at least that's what I got out of my hours of poking around in the code.
Comment #4
vhmauery commentedTo find the source of the problem, I downloaded drupal 5 versions 7 through 12. My logic was this: album contents worked fine with d5.7, but an upgrade to d5.12 broke it. I took diffs between each of the versions and applied diffs to bisect versions until I tracked down which version had the changes that broke album contents. Then I looked at this diff for any changes that were form related. I backed this change out and viola! The comments in the change were sufficient to tell me how to fix it.
Comment #5
eddified commentedVery interesting. Good work.