Still confused about versions!!!

@Ela: It's hard to understand him but I think he's saying he's planning for beta 5 to be broken as well and serve no purpose other than as a pathway to beta 6. Personally, I wouldn't recommend installing nodewords until there's a working non beta release because this is such a mess.

Michelle

Will any of these versions work? Can you please just let us know on the module page as it looks like there is so much confusion, duplicate posts, patches etc.
Thanks

What does that mean?

The project page really does not say which version to use that will save the description field etc and there are so many versions going that it is difficult to figure out which one works without any problems as the current stable version does not. Is there a version that does not have bugs and will save the description field?

I reopened it as you see others have the same question and it is not answered so it cannot be fixed. If you could simply address which version will work AND save the description fields that would answer the question please. Thank you.

I think this is still a relevant question. I have had issues with recent versions (filed issues in the cue) but still cannot get any version to work 100%. Specifically custom tags / paths.

I also can't find a working version and nobody wants to answer my questions. This is a joke.

I think this is clear now: 6.x-1.x-dev - 2010-Jul-02 (several issues have been addressed and fixed, the big one being the missing file from the CVS version which is now there)

#14 --Use 6.x-1.9 Even after this security risk was posted in Sept 2009?

* Advisory ID: DRUPAL-SA-CONTRIB-2009-060
* Project: Meta tags / Nodewords (third-party module)
* Version: 6.x
* Date: 2009-September-23
* Security risk: Less critical
* Exploitable from: Remote
* Vulnerability: Access bypass

-------- DESCRIPTION ---------------------------------------------------------

The Meta tags (also known as Nodewords) module provides meta tags based on
node titles. In certain conditions, the node meta tags were not respecting
access permissions, potentially exposing content not available otherwise.
-------- VERSIONS AFFECTED ---------------------------------------------------

* Meta tags for Drupal 6.x before Meta tags 6.x-1.1

Drupal core is not affected. If you do not use the contributed Meta tags
module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------

Install the latest version:
* If you use Drupal 6.x upgrade to Meta tags 6.x-1.1 [1].

Also see the Meta tags [2] project page.
-------- REPORTED BY ---------------------------------------------------------

Barry Jaspan [3] and Ben Jeavons [4], both of the Drupal Security Team [5]
-------- FIXED BY ------------------------------------------------------------

Alberto Paderno [6], the module co-maintainer
-------- CONTACT -------------------------------------------------------------

The security contact for Drupal can be reached at security at drupal.org or
via the form at http://drupal.org/contact.

[1] http://drupal.org/node/585706
[2] http://drupal.org/project/nodewords
[3] http://drupal.org/user/46413
[4] http://drupal.org/user/91990
[5] http://drupal.org/security-team
[6] http://drupal.org/user/55077

6.x-1.x-dev does not work right. None of the visions work right.

@Kiam Glad you pointed that out, all those 1s got a bit confusing, especially as I was having problems with 6.x-1.11. Feel reassured that 6.x-1.9 (which is working) is not an issue security wise thanks.

6.x-1.9 does not work. I tried it, it doesn't save custom meta tag pages or show meta tag node descriptions.

This is the most confusing thing! Which version do you use??? Nobody can seem to agree. 6.x-1.11 is the recommended version, but several posts state that it does not work. Use 1.9!!!, 1.3!!!, beta3!!!, beta 9!!!, do not use beta versions!!!... I have never had so much trouble trying to figure out what version to use! Should we assume that the module as a whole and all versions do not work? It is funny that every thread that relates to "which version to use" is closed, yet I have not found a consistent answer to the question! If 6.x-1.11 is not working, why is it the recommended version?

Changing the status to needs review. Also, the module has a new maintainer, so hopefully things will get in order now. I totally agree the various incarnations of versions of this module has been extremely confusing.

I hate posting negative comments, as I know how much work everyone puts into the project. It's like yelling at someone for giving you the wrong flavor of free ice cream! But the versioning and releases of this greatly needed module go against Drupal standards and best practices. I definitely think some clarification on the project page would be helpful.

There was a new issue filed called "The Great Nodewords Cleanup" filed 3 weeks ago, may be of interest to some people: http://drupal.org/node/864440

In my experience 12beta9 works pretty good except for a couple things:

- robots (nofollow/noidex) stuff is funky, don't use it w/ this version. If you dont need it great
- there is not permissions settings anymore so anyone that can create content can add meta tags.

There may be more issues, these are just the 2 that I've run into so far. I think the great cleanup will be very very nice once it gets going.

The way I installed and understand this module installation is this way.

1) Start with nodewords-6.x-1.11.tar.gz -- which works fine

If you want to upgrade and have the ability to add tokens in your meta tags descriptions, keywords, ect. Plus, create a custom page meta tag information you need to do this.....

2) Start with version nodewords 6.x-1.12-beta5. After, you run an update and if you want some of the higher betas next you need to install 6.x-1.12-beta9 then run an update. Once you have the beta9 installed you can then install the beta9 + (10, 11....)

---
I am currently using 6.x-1.12-beta5 and seems to work great on my site. I have tried the higher betas and there was issues with them.
It say Branch 6.x-2 was just an experiment so don't use that version. Plus, I think Branch 6.x-3 is underdevelopment.

Thanks for developing this module.

@gdbwb05 -- the fact that you had to go through an incredibly detailed and convoluted explanation in #33 proves the point of the title of this issue and many others like it, the version confusion is still utterly confusing for most people and it should not be that way. :)

@higheocksmedia I totally agree! If it takes several paragraphs to explain what version to use, then you know you have a problem. You almost need a flowchart! I am eager to see the module get back on track with the new maintainers. Thanks for everyones help with the explanations.

I am extremely confused with point 2 in #33. Does that mean I can't install beta9 right away? Do I have to install beta5 first and then only upgrade to beta9? I couldn't get the meta tags to generate for me and I'm wondering if it's because I installed beta9 right away.

Please see the updated status message on the project homepage. Please help test updating from 1.11 to 1.x-dev (on a copy of the site rather than your production install, just in case) and report any issues with the "v6.x-1.12 blocker" tag.

For clarification: with the module under new maintainership, please do not use anything other than the v6.x-1.x releases as the current v6.x-2.x and v6.x-3.x branches are no longer supported in their current forms.

Sorry for this silly question, but can I just install 1.x-dev without first installing 1.11 and then upgrading to 1.x-dev?

@quarantine: yes, you can.

I think we've clarified on the project page now. Please open any issues you experience upgrading to 6.x-1.x-dev or 6.x-1.12-beta9.