The Great Nodewords Cleanup

This is great news but I'm curious why change the name for just Drupal 7? Personally I think the name for the module is much better as "Meta Tags" rather than "Nodewords" especially considering when you are in the UI, it's called "Meta Tags". Just my 2 cents and could perhaps be less confusing for people as well as only maintaining one project page?

This is great news but I'm curious why change the name for just Drupal 7?

This has been already debated. You cannot change the name of the CVS directory containing a project; you can change the file name used for the module, but that would lead to something like nodewords/metatags.module, which has been reported as confusing for the users.
Apart that, Drupal 7 code is a way different from the code used for Drupal 6, just for the fact Drupal 7 code could possibly use the field API.

Great news! Subscribing.

Happy to see the passion and efforts. Best wishes!

Hi

I'm using 6.x-1.12-beta9 & I'm glad it is mentioned in the introductory text.
An attempted upgrade to a newer version totally messed up the site forcing me to spend days cleaning the tags that had been corrupted. I reverted to 6.x-1.12-beta9, but a number of things dont work, such as displaying description of a content type, even if it has been entered. I have for example a content type "recipes". On its settings page, one can enter the meta tags which would normally appear on the /recipe page, but do not.

The frontpage is ok.

If I remember well, for some specific content pages I was creating recently (recipe content type), the description & keywords could not be saved at all.

I have also seen a number of issues on meta tags not appearing.

My hope is that these issues are resolved.

One question I have is, ... is there any rough idea about when a functioning version 1.2 for D 6.17 could be ready?

Regards & thanks for the good work.

This is awesome, subscribing. I use this module on every site.

Any roadmap/timeframe for this?

subscribe

interested and willing to help, possibly with better documentation

Greetings, It's been a month since this issue was originally posted and I wondering if we can get a status update. My concern is that there are still people confused about which version to use / update / revert back to with this module for Drupal 6. It's a crucial module to Drupal.

I am seeing a lot of postings on: "Still confused about versions!!!" http://drupal.org/node/751054

I am also wondering if you can clarify this as posted on Twitter: http://twitter.com/davereid/status/21854066230
When it's said "staring over with metatags.module", does that mean with Drupal 6 also or just 7 as it contradicts the comment in #2 above or did that just mean for Drupal 7?

This is a great module and would like to be able to continue using it on my sites / and for my clients. I am a front end developer / themer and don't really have the level of PHP knowledge to be able to help out or contribute code but certainly I have added to the issue cue in terms of testing and reporting of issues.

I am also willing to sponsor some part of development for Drupal (v. 6.x only) as that seems to be the most important piece to get working smoothly at this time.

Thanks, Danny :)

(Taken from #864386: Simplify the UI)

My idea:

• General:
  • Provide a hook for modules to define metatags that are available. This should be simple, just define the metatag name and maybe an option to control whether it is used on just the homepage or all pages. Then use drupal_alter() to allow other modules to modify the list.
  • Provide a page that lists all of the defined metatags and give a UI to add more or override default ones (kinda like Views et al).
  • Provide a UI to assign settings for each of the values required for the homepage.
  • I'm still happy with using variables to control general settings, maybe also the homepage's metatag values too, but we'd definitely need a structure for handling the other per-object settings.
  • Tokens support.
• Term pages:
  1. Have a way of assigning defaults for all vocabularies.
  2. On each vocab settings page, display each of the metatag strings as they would currently be assigned via the system defaults in #1 above. Provide checkboxes to allow string to be overridden, so that the new string becomes what is used for all terms within that vocab.
  3. On each term edit page, display each of the metatag strings as they would currently be assigned via the system defaults in #1 and the per-vocab defaults in #2 above. Provide checkboxes to allow string to be overridden, so that the new string becomes what is used for that term page.
• Node pages:
  1. Have a way of assigning defaults for all nodes.
  2. On each content type settings page, display each of the metatag strings as they would currently be assigned via the system defaults in #1 above. Provide checkboxes to allow string to be overridden, so that the new string becomes what is used for all nodes of that type.
  3. On each node edit page, display each of the metatag strings as they would currently be assigned via the system defaults in #1 above and the per-content-type defaults in #2 above. Provide checkboxes to allow string to be overridden, so that the new string becomes what is used for that node.
• By-path:
  • Similar to the existing functionality from Nodewords, provide a UI that allows specific terms to be given . The question is, should this override what is assigned elsewhere, or should this be another way of defining a default that is overridden per-node or per-term?

This is very similar to a plan I had built for a rewrite of the Omniture module at Bonnier, before I left in May.

Great idea. Glad to see the passion.
As far as nodewords by path I think defining a default that is overridden per-node or per-term makes more sense.

Thanks.

subscribing

subscribe

Subscribing.

subscribe

Can we hope some new version for soon?
The fact that we cannot had metatags to a view (because of bug) is so handicaping.

subscribing... this module definitely needs a cleanup

Good to hear. Will there be an upgrade path from nodewords-6.x-[insert-random-number] to metatags-7.x?

I'm more than happy that the most worse maintainer who destroyed this project have left the project. Thank You dave for taking over... Now we have a chance to get a reliable module that does not clutter DB, delete data, broken upgrade paths and tons of other suxxx issues that made upgrades again and again a nightmare... Again THANK YOU!!!

@Dave Reid, though Hass's comment was not appropriate in #21 with all due respect, it's been over two months since "The Great Nodewords Cleanup" was posted and the first time you have chimed in on this since August 10th.

I offered in #11 above to become a sponsor for work on 6.x to get that in shape but my offer went ignored. This comment also makes me wonder about things: http://twitter.com/davereid/status/25523659523

I get that we are all busy and have to earn a living and all that. I personally donate several hours of my free time a week to helping people out on drupal forums as well as blogging about Drupal -- I have a series of "how tos" that have been helpful to many.

It would be good to get some kind of update on the state of Nodewords. I personally think Drupal 6 is a bit more important than Drupal 7 as there are many Drupal 6 sites out there already that could stand to benefit from a good working version of this module.

Thanks, and cheers, Danny :)

Thanks for the info, I have sent Palantir.net a message with my intentions.

It was and is appropriate. My DB was cluttered. I was made to restore backups, have written the #613376: How to downgrade broken nodewords 1.1+ to 1.0 for a smooth upgrade to 1.3 and wasted my time doing many many upgrade tests and created many bugfixes to get a well working 1.3 out. I'm sure if I haven't written the patches it would still be broken as 1.1 and 1.2. And what happens again a very few version numbers later? Again the upgrade path was broken and the learning effect was NULL and today I have again a version 1.11 that cluttered my 160.000 node site and a few others, too. *Damn* I'm really angry. Sorry for speaking that clear - but it must have been said - after xmlsitemap and nodewords has been cluttered - today I was really so happy that a much more expierenced Developer took over the job and I may be able to install a version in future that may simply work without making me and thousands of others tons new headaches.

@hass,

I have to agree with you. I also spent a lot of time fixing problems and stopped upgrading for a while.

Right now, the -dev version is really good, a lot better than 1.11 except for one bug:

#835172: Robots not saved, keeps being noindex/nofollow

and that's not been applied to the -dev version as far as I know. Although someone tried with good feedback.

Outside of that, I had a couple of E_NOTICEs. No big deal.

Ah! And the upgrade went smoothly except on a couple of websites (out of 20+ not bad!) and that was because some entries were duplicated which was not supposed to happen. Anyway, I do not know whether that's Dave's work or the whole community, but the current -dev is great! The admin can edit nodes and only see the 2 or 3 boxes you select as it was a while back. That I appreciate very much! 8-)

Thank you.
Alexis

Please help us get ready for a solid next release:

• Test the v6.x-1.x-dev release.
• For any issues that are found:
  • Please check to see if the issue already exists,
  • If the issue exists and a patch has been supplied, please help test the patch,
  • If the issue does not exist, please add a new ticket and assign the v6.x-1.12 blocker tag.

Thank you.

FYI, due to the amount of effort required to do a rewrite it is debatable whether this rewrite will happen in Nodewords, or whether we'll instead just put the effort into building the D7 Metatags module and just providing an upgrade path. As such I am postponing this task.

@DamienMcKenna, I am not sure I understand, I am wondering if you can clarify -- comment #29 seems incongruous with #28. In #28 the implication is that things are being fixed and need testing but in #29 it's postponed. Thank you, Danny.

@highrockmedia: we're going to continue fixing Nodewords and gradually improving it, I just don't think a full rewrite / massive cleanup will be done any time soon, if ever.

As far as I can determine, the latest dev version does 90% of what it's supposed to do. I'm going to rename the version to 6.x-1.11.5 or something and be very happy. Since I just started using this module I didn't have any upgrade issues to deal with. The other 60K plus sites supposedly using some version of this can do whatever they need to do (and probably have) to make it work, including hiring a qualified developer, if need be.

That's just the way open-source works; no one is obligated to fix any specific issue for you or anyone else. Paraphrasing the Drupal mantra: Talk is cheap, Code is Golden.

Damien,

You may want to mark this issue as active and inform people that D7 is postponed or "moved" (like a new module not directly linked to this module). Then at some point someone will come up with an upgrade path from D6 to D7.

However, finishing D6 so we have a "dead stable" version would be a good idea... 8-)

It looks like many of the current issues are duplicates too. I would suggest you create a new alpha version with the few fixes that were already applied to 1.x-dev because many of the issues were rather bad and many people have a hard time with testing a -dev version...

Thank you.
Alexis

Great news. Thanks for all the hard work, Dave and Damien. (And of course all the others involved.)

Dave and Damien, thanks for all the hard work you have put in (and all others), it's much appreciated. - Danny

Subscribe

thanks for the awesome work!

Subscribing.

subscribe

I think a list of What works and what does not would be helpful to people. As someone that has posted questions about what version to use that just sat there for a year, it makes this really confusing and what to do and where do go as the current stable version once again is not saving data. Again, going back to move forward. I know everyone is excited about D7 but so many if not most sites that are not new seem to be on 6 so it seems important to get this stable as many people just cannot UP to 7 just because it's new and shiny due to modules getting up to speed. Almost every Drupal book and site speak about Nodewords.

@Dave Reid & @quicksketch: is there anything else to do on the code cleanup (#1146174: Start re-applying patches from the queue to the new 1.x branch) for now or can we just mark this one as being done?

We're close to a stable 6.x-1.x release after reverting the codebase to 6.x-1.11 and starting over, I think this can be closed.