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

apaderno’s picture

Title: Meta Tags from Teaser » Add a bulk operation to create the meta tag DESCRIPTION from the node teaser
Version: » 6.x-1.x-dev
ilo’s picture

Title: Add a bulk operation to create the meta tag DESCRIPTION from the node teaser » Add a bulk operation to create the DESCRIPTION meta tag from the node teaser
Version: 6.x-1.x-dev »

Moving all feature requests to 3.x according to #640902: Nodewords, future plans and possible Roadmap

hass’s picture

I need to create the description from a custom CCK field. teaser and body is empty.

ilo’s picture

Title: Add a bulk operation to create the DESCRIPTION meta tag from the node teaser » Make bulk operations of automated Meta tags generation.

Hass, 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.

apaderno’s picture

Title: Make bulk operations of automated Meta tags generation. » Make bulk operations of automated meta tags generation

#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.

Starminder’s picture

Priority: Normal » Critical

Changing 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

apaderno’s picture

Project: Nodewords: D6 Meta Tags » Extra meta tags modules

I am moving the feature report to the project that will implement the feature.

j0nathan’s picture

subscribing

zet’s picture

Hi kiam. First of all thanks for your work on this module. Any updates on this issue?

apaderno’s picture

Project: Extra meta tags modules » Nodewords: D6 Meta Tags
Version: » 6.x-1.x-dev

This project is not maintained anymore. Maybe the code will be implemented in Nodewords, if the new maintainers think it is worth implementing it.

DamienMcKenna’s picture

Issue tags: +v6.x-1.12 blocker

Tagging 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.

stillcut’s picture

Is it possible to perform a bulk update with 6.x-1.x-dev at this time ?

Dave Reid’s picture

Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

feature 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?

DamienMcKenna’s picture

Issue tags: -v6.x-1.12 blocker

Taking this off the blockers list.

apaderno’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

I am closing this issue, which is for a not supported Drupal version.