Issue fork auto_entitylabel-2707027
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
peacog commentedComment #3
dman commentedWould be great, and should be pretty easy to do I believe.
After introducing this module late in a build, I'd really live to be able to apply it retroactively.
Note: it looks like simply re-saving the entity will trigger a re-label. That wasn't explicit, but makes sense I guess.
That may do for now for me, but still, exposing a simple entity action to VOB or Rules would have been nice structure.
Comment #4
mortona2k commentedI think this is a great idea, maybe add the option to the Automatic Label settings form where you can bulk update it for that entity. Adding a config page is another option, where you could manage all entity labels.
Comment #5
mortona2k commentedAs a quick workaround, you can use the content admin page to bulk unpublish and republish content, which will update the title.
Comment #6
antonyanimator commentedAny possible update on this? Unpublish Publish works is good as a workaround but not great
Comment #7
colanComment #10
deaom commentedI added the option to re-save the labels on the auto entity label form for each entity, which then if checked, does the re-saving of entities via batch process in chunks which can also be set (default value is currently set to 50). It is done for comment, media, node and taxonomy term. Not sure if that rounds all of the entities that this module supports. But still needs a review so marking it as that.
Comment #11
Anonymous (not verified) commentedHello,
I have tested changes made in this issue fork and I can confirm that the options that were added are working as they should be and entity labels gets re-saved successfully.
Regarding the code it would be nice if you could provide some comments on the methods in *Batch classes.
The code is pretty much self explanatory, but when I run phpcs --standard=Drupal,Drupalpractice on changes made in this issues fork I get the following notices for each of classes in Batch directory.
Comment #12
colanUpdating status based on my GitLab review and #11.
Personally though, I'm not a fan of adding comments if they don't add value, even though the Drupal coding standards would disagree with me. I'd rather go with the Clean Code philosophy (where the code should be clear enough that comments aren't required), but that's just my opinion. Let's see what the maintainers think. (Oh wait! Turns out I'm one of them.)
Comment #13
deaom commentedI changed my approach in dealing with the loading of the different core entities, so there is no more of the repeating of the class. Also added missing comments. Needs another review, so marking it as that.
Comment #14
Anonymous (not verified) commentedI retested the changes made by #13 and now the duplicates classes are merged into a single class and the comments were also added.
Marking this as RTBC.
Comment #15
colanThanks all!
Comment #16
colanAdded to beta4. If you'd like to see a stable release, please help with issues in #3153250: Roadmap for a stable 8.x-3.x release.