I used the bulk update feature to add aliases to my site. I was notified that 50 aliases were added and assumed the rest would be added via cron. A week later, I found out that no more aliases had been added and finally released I would need to run the bulk update multiple times.
Perhaps I am dense, but I think this could be made more clear via the description of the bulk update checkbox and perhaps in the bulk update documentation. Alternatively, bulk updates could be performed via cron.
Also note that the bulk update documentation in the README.txt distributed with pathauto appears to be outdated.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 229242_better_bulk_update_readme.patch | 1.63 KB | greggles |
Comments
Comment #1
gregglesThanks for letting me know.
Can you propose some improved help text/description for the README?
Comment #2
junyor commented@greggles: It seems like the only bit about bulk updates in the README.txt is the out-dated "Bulk Updates May Destroy Existing Aliases" section. Isn't that obsolete now that bulk updates are done in batches?
I think it would be good if the drupal_set_message informing the user that the bulk update has been performed could also say how many more items need to be updated or could otherwise help the user to know that another update is needed. Ideally, there would be some link/form element the user can easily click to submit another bulk update. That, or actually do bulk updates via cron.
I apologize for not getting back to you sooner. For some reason, I'm not getting some issue updates via mail that I should.
Comment #3
gregglesThanks for the idea. Checking to see how many more aliases needs to be done is an expensive query and would likely cause problems so that is kind of hard to do, though I agree, the present idea isn't great.
I have updated the documentation in the README.txt (see attached patch). Let me know if you think it could be improved further.
Comment #4
junyor commentedLooks good. Thank you!
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.