I deleted all existing aliases, created new patterns, selected the "Create a new alias. Delete the old alias" option (also tried with the other options), checked each "Bulk generate aliases for nodes that are not aliased" box for each path setting and saved the form. The module reported 0 aliases updated (no errors).
I expected that all the paths would be aliased according to the patterns I have set.
Path aliases can be set but only by editing and saving individual content.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | pathauto_patch_bug_956234.patch | 573 bytes | schuyler1d |
Comments
Comment #1
mt3ch commentedI can also set path aliases correctly from admin/content/node.
Comment #2
gekido commentedFar as I can see with my own usage, the bulk generation only seems to work for nodes / entries that have NO aliases to them at all - ie exactly what it says on the dialog.
"Generate aliases for all existing terms which do not already have aliases."
The 'create new / delete old' setting is for when / if you are manually updating nodes via their appropriate 'edit' page.
If you want to regenerate aliases for content, you need to bulk delete the aliases for that content / type (on the delete aliases) tab first, and THEN go back to the 'automated aliases' page, reselect the types that you want to regenerate aliases for and THEN generate them.
At least from my experience that's how it works anyways ;}
The jumping back and forth between the delete & generate tabs while testing out paths is a bit of a pain frankly, but relatively minor.
Comment #3
edvanleeuwenI have the same issue. When trying the bulk generation with different settings, I noticed that the number of paths generated varied.
@gekido: Before starting every generation, I bulk delete everything.
Comment #4
edvanleeuwenI have done some testing and come up with the following:
- the bulk generation only works when one of the settings change;
- every bulk generation seems to been limited to 50 entries.
Test script:
- deleted all aliases;
- generated using the settings I already had;
- removed the default entry for node and regenerated (50 aliases created);
- removed the default entry for ads and regenerated (50 aliases created);
- removed all further default entry one by one and regenerated (every time 50 aliases were created).
Comment #5
schuyler1d commentedI encountered this issue as well. I don't think it was getting triggered before, but it's possible a mysql upgrade started catching this--otherwise, I'm not certain why it just started happening.
In any case, as gekido notes, when NO aliases need to be updated, there's an error. The included patch fixes that case.
Comment #6
greggles5.x is no longer supported.