Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Not sure if this is related to http://drupal.org/node/1029860
In node_gallery.views_default.inc
$handler->override_option('path', 'ng_sort');
should be
$handler->override_option('path', 'ng_sort/%');
which is why saving on the 'manage images' page is giving a page not found error.
It's 4 in the morning here. I really need to go to bed and I am just learning how to create patches so this is all I can offer for now.
Comments
Comment #1
justintime CreditAttribution: justintime commentedmrwhizkid - while you're not technically wrong, you're not quite right either :)
*IF* we were using the views paths to load up the arguments, then yes, you'd be correct. However, we're not. We manually pass the argument to the view in code. Also, that view has to do only with the sort images tab, and nothing to do with manage images.
However, it is a valid issue we should fix, so I'll leave it open until I have some time for coding later on. I'm just pretty sure that fixing that issue won't help anything you're experiencing.
Comment #2
mrwhizkid CreditAttribution: mrwhizkid commentedHi. Thanks for the response. I discovered today that Pathuato may actually be causing this issue. When a user creates a new album, the system automatically assigns a path to the node. But if the user changes the title on the node, Pathuato (by its default settings) will change the path as well which doesn't seem to update in Node Gallery manage image save settings. When save is pushed, it's trying to find that old path.
The simple solution to this is to set Pathuato so that it doesn't change the path when the node is updated.
Comment #3
justintime CreditAttribution: justintime commentedHmm. Pathauto on it's own shouldn't cause this. Pathauto will create *aliases*, but won't ever disable the node/[nid] links. That's the URL that the manage images redirect tries to send to.
However, if you're running global_redirect, then *that* module will probably cause some headaches. Is that the case?
Either way, sounds like this isn't an NG bug, so I'm bumping it down to a support request.
Comment #4
scroogie CreditAttribution: scroogie commentedComment #5
zengenuity CreditAttribution: zengenuity commented