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.
I had this set in previous versions, then it seems the feature went away...now the feature seems to be added back. However, when I look at my content through the SEO Friend meta tags node report, it shows almost all of my content no longer has any meta tags.
I see in content management that I can mass delete meta tags from content. Would it be possible to add a feature to rebuild meta tags from teaser for bulk content? I see no way to fix my hundreds of nodes except one by one. Please help, thanks.
Comments
Comment #1
apadernoComment #2
ilo CreditAttribution: ilo commentedMoving all feature requests to 3.x according to #640902: Nodewords, future plans and possible Roadmap
Comment #3
hass CreditAttribution: hass commentedI need to create the description from a custom CCK field. teaser and body is empty.
Comment #4
ilo CreditAttribution: ilo commentedHass, I'm moving your feature here. This one if for bulk operations.
I'm changing the title of the issue. If we provide a way to rebuild the Meta tags generated automatically (not only description meta tag) we'll have a good code base for import/export/upgrade operations.
Comment #5
apaderno#554284: Add a tool/setting page that allows to do some operations on the meta tags is in someway related to this feature request.
What I mean is that the bulk operation implemented in Nodewords could have a settings page that governs the way the bulk operation is executed.
To make an example, the settings page for the bulk operation could include an option that allows to the administrator user to decide if the meta tag DESCRIPTION content should be overwritten when it is not empty; as the bulk operations are normally batch operations, a user could have changed the meta tag content 2 seconds before the bulk operation could change it.
Comment #6
Starminder CreditAttribution: Starminder commentedChanging to critical - for productions sites like mine, this really needs some priority. Sounds silly, but I have over 2500+ nodes and my SEO is thrashed. Appreciate any thoughts if there is a way to recover other than waiting for this (I know it is a tall order and there are other things to do).
Thanks
Comment #7
apadernoI am moving the feature report to the project that will implement the feature.
Comment #8
j0nathan CreditAttribution: j0nathan commentedsubscribing
Comment #9
zet CreditAttribution: zet commentedHi kiam. First of all thanks for your work on this module. Any updates on this issue?
Comment #10
apadernoThis project is not maintained anymore. Maybe the code will be implemented in Nodewords, if the new maintainers think it is worth implementing it.
Comment #11
DamienMcKennaTagging this. We want the next release to be rock solid, so if you have some time please help test the v6.x-1.x-dev release to see if all of the above issues are resolved.
Comment #12
stillcut CreditAttribution: stillcut commentedIs it possible to perform a bulk update with 6.x-1.x-dev at this time ?
Comment #13
Dave Reidfeature requests != critical
We don't need bulk operations - we already support tokens which supports this use case.
There doesn't seem to be any bulk editing functionality in the 6.x-1.x version, so I'm not sure why this issue is open or active?
Comment #14
DamienMcKennaTaking this off the blockers list.
Comment #15
apadernoI am closing this issue, which is for a not supported Drupal version.