Recommended release is NOT recommended! Which release is stable then? HELP!

I appreciate your frustration. I guess the situation goes to show that the standard advice 'back up your project before installing new modules' is really worth following. Not that that will stop many developers losing hours, even days trying to fix faulty installs, because they assumed 'recommended' would be OK and didn't make a backup. Having a warning on the project page would seem like a sensible and kind thing to do.

Also, given that many thousands of sites use Nodewords, it's a shame that important bug fixes and valuable feature updates (like open graph settings to work nicely with Facebook) are taking so long to sort out. The most active maintainer maintains dozens of other projects, plus D6 is now not the current Drupal version any more. Both of which is going to slow progress. It's a pity, because when it's working well Nodewords is a kickass module.

I guess it would only take someone who knows the code well maybe half a day to fix the critical bugs and implement the most in demand features (many of which have almost working patches already). Perhaps we should start a little fund to get the work done? I'd be willing to chip in $15 to help get a version with all key features working and with the open graph patch successfully integrated. A dozen more should do the trick no?

You're welcome.

Under 'additional notes' on the project page I see there is already a warning, but I guess it could be more emphatic, given the current state of the files.

Maybe it's time to add a new project maintainer? But then who'd want to take on a D6 project?

I suspect getting a fund together might be the most effective solution. So with you and me, that's $30 so far. Who else is in?

Maybe anyone who's willing to pay something could say how much and what exactly they'd need fixing - in the version released to the community - for the price. Let's see if we can get this done.

maybe the answer is for everyone who's willing to donate get some work done on Nodewords to email Dave Reid directly and say so.

Hi there!

I would donate 30,- Euro (about 43 Dollar) for a stable version with token and taxonomy support. At the moment I have 6.1.11 installed.

We're building towards having the next 6.x-1.x release being stable, though I'm not sure if it should be called 6.x-1.12 or 6.x-1.13. We're also going to have to write an upgrade script to downgrade anyone who'd used the 6.x-1.12 releases: #1200526: Verify upgrade path from v6.x-1.12-x

It's good to hear and see that work is still being done on the module. I think because several important issues and key feature requests had been (and some still are) outstanding for over 6 months it was looking like the module might be left to fade away. Hence the initiative to fund some in demand updates.

Seems like there's some contention in that thread on the need for a upgrade/downgrade script. As for users who are already using 2.0 alpha, it looks like none of the recent updates to the code were ported to a recommended or new alpha 2.0 release. I know at least a few people are using that branch, including me, in an attempt to get the much demanded open graph support to work.

I think the offers of funding still stand, and in any case, good luck!

Hi all,

I have a fairly fresh Drupal 6 installation. Which version would you recommend for me?

I am not looking to be on the cutting edge, just want to be able to add keywords and metadata and also have an easy upgrade path in future.

Any ideas??

Thanks!

@ratinakage: honestly, can you give us a week to get another 6.x-1.x rc out?

Definitely... ;)

I'll watch this thread.

Thanks!!

Subscribing.

subscribe

@DamienMcKenna very interested in the progress of this, I too want to install this for the first time.

Subscribing.

Subscribing

subscribing

It looks like there's no commits to 6.x-1.x-dev since June 20th. Should we make it another release?

subscribing

@DamienMcKenna - You mentioned a week. Its now been a couple. What is your recommendation?

Thanks!!

maybe this is the maintainers way of 'encouraging' people to switch to D7? ;) they don't seem to be interested in donations..

I've been trying to get to it have just been more busy over the past two weeks than I expected - I'm trying to get to it by the weekend :-\

If anyone has time to help, this issue could really use some work: #1200526: Verify upgrade path from v6.x-1.12-x

Hi Damien,

Cool. I think I would be motivated to sort that script out myself before the weekend, if I knew the open graph patches would be integrated into the next imminent release. Do you know if that will that be the case?

@joehudson: The patch would have to be re-rolled for 6.x-1.x, the current patch is for 6.x-2.x.

Please help identify any possible problems downgrading from the 6.x-1.12 or 6.x-2.x releases to the latest 6.x-1.x-dev codebase and note your findings here: #1200526: Verify upgrade path from v6.x-1.12-x Thank you.

Hi all,

I know I've asked this before. If I had to choose a version to install now, which would it be?

Thanks....

guystern: If you need to launch immediately but can get by without taxonomy support for a week, use v6.x-1.11. If you have time before the site has to go to production, 6.x-1.x-dev. As soon as I finish two other module releases (ok, one module but both D6 and D7 editions) I'm looping back to Nodewords to get the next stable release out.

Subscribing with anticipation. After reading some issues with Location latitude or longitude stuff getting messed up with updates, and with my site being heavily based on that data, I'll just wait, no time to correct thousands of bits of geo data. Thanks for your hard work Damien!

Still waiting eagerly...

@DamienMcKenna - I guess you should priorities this release over Menu Minipanels. They have less than 400 active users. This module has almost 89000 users!! ;)

..this is so frustrating... I tried the 6.x-1.11 release. Not working. No description tags etc. Same like it was two years ago. I really hope you will get this module fixed, dude. It could be so great! Keep up the work, we need it! Thank you!

Edit: Installed the .dev version and everything is working as supposed. Thumbs up!!

Here's a challenge for you guys:

• I want to get a stable release out of this module ASAP.
• I want the next release-candidate to be compatible for anyone still using the dodgy 6.x-1.12 releases.
• The single most important remaining task for the next release is #1200526: Verify upgrade path from v6.x-1.12-x.
• I need your help!!
• I need example database backups and/or access to a development install of sites that are:
  • Still using one of the 6.x-1.12 releases,
  • Have lots of Nodewords data,
  • Are not heavily using Tokens in the Metatags.
• If your site fits that description please get in contact with me so that I can put together an update script for #1200526: Verify upgrade path from v6.x-1.12-x.
• I'll sign any NDAs you would like so long as you can help with the above.

Please, please, please, please, please help!

My goal is to have a release candidate out next week with an update script to handle the 6.x-1.12 update, and then have the next stable release out by the end of the month.

Again, please help me so we can make this the best release of Nodewords in two years :-)

Although I unfortunately can't help you, I wish you good luck and I hope that people will contribute. This module really deserves it and I want to thank you again for all of your work!

I would kick in some cash to get this working too

With Google Panda this module is more important than ever. This module is also in every Drupal article and book about SEO so I am not sure how and why this has been left for so many months. How about trying to get a stable version that works with Taxonomy working, it seems silly to wait on an upgrade path if the other can be solved in tandem ie as two separate issues.

@venusrising: offers of financing are appreciated but unnecessary :) Also, if you are in desperate need to have something working right now, please try the current 6.x-1.x-dev release as a stop-gap until I can get the update path working correctly. Thank you for the response.

subscribing

@DamienMcKenna The issue is we are nervous on a production site to run a a dev version of nodewords due to the bugs.

@venusrising: I understand your position, could you at least try it on a localhost / development / staging version of the site and see if you run into any problems?

@DamienMcKenna, I think my website may be a good candidate for your request. How about if I do the following?

1) Do a database backup of my existing website (http://garzawebdesign.com) and
2) Create another (damien.garzawebdesign.com) using the database backup. Then,
3) Implement the Nodewords module update on that one
4) Do a database backup and send it to you.

Can you check out that website and verify that it is a good candidate for you? If so, I can do this by the end of the weekend (11-Sep-2011). Let me know if this will be helpful to you.

-Frederico Garza

@Frederico: that'd be awesome, thank you!

@DamienMcKenna, it's done. I've sent you an email with followup information. -Frederico Garza

I have nodewords 6.x-1.11 and acquia marina and they don't seem to work together. How can I fix it? It's messed up my site a bit (http://winthropite.com). Unsure if it's related, but I can't run cron manually, either. winthropite{AT}gmail•com

@winthropite: please do not hijack issues, please first do a quick search to see if you can find any other matching issues, and then open a separate issue. Thank you though :)

I have been using nodewords dev for a long time now, i am thrilled to hear work is on it's way to get a final version out! Thanks so much for all efforts.
Subscribing ;)

@DamienMcKenna didn't mean to hijack; I sincerely thought this thread covered my issue. I'll start a new one... thanks!

Hey DamienMcKenna I'll take a look I've got a large site using it, and will need to do this anyway.

Though could you, as maintainer, remove the 1.11 release or put up a big warning about the smallint issue which corrupts data over 65535 nodes in the meanwhile?

subscribe...

Can someone explain what "corrupts data over 65535 nodes" exactly means? Is there a patch for 6.x.1.11? We use it on a huge production site... Are there complications upgrading from 6x.1.11 to 6x.1-dev?

Edit: Or better - is there a patch for 6x.1.11 that solves the smallint issue?

FYI I'm planning a Nodewords code sprint for Drupalcamp NH on the 29th!

@DamienMcKenna we are still on 6 production site so this is important for alot of people still. Getting OG tags working for CCK field images would be awesome too.
Would be great to choose and image filed to use for the OG image Meta so it can be selected and not have to be manually done per node. Especially helpful for user generated sites.

Any update on a stable release for D6?

Thanks....

Quick follow on question regarding Patrick's question #49 - this is if there are over 65536 rows in node is it? What data corruption can occur?

Thanks

@musojon74 and @patrickroma - the 6x.1.11 release of nodewords setting for the nodeword table restricts NID to be lower than 65536. Anything over 65536 saved as 65536... so if you have node with the NID of 104837, nodewords would save it as 65536... if you have a node with the NID of 234857, nodewords would save it as 65536... etc...

Any data for nodes with an NID higher than 65536 is all assigned to the NID 65536.

This quick fix is to go into MySQL and change the nodewords table's nid field from smallint to just int.

OK, now that's weird - because I've encountered the data loss bug on a site that has nowhere near that number of nodes.

When I originally saw this post, I thought it meant that it happened on databases that had over 65,000 records in total, and in this case, the search_index table had become bloated enough to push the total over that number. So I truncated that table (and search_dataset for good measure), as well as upgrading to the dev version of the module as various people had recommended. And the nodewords data does seem to have stopped disappearing, at least for now... (Though now I'm encountering other problems, but I'll post about that elsewhere so as not to hijack this thread.)

But the actual number of nodes in that site? 70. So something is causing data loss even on sites with far fewer than 65,536 nodes.

^ this scares me

The search tables have nothing to do with the Nodewords module. The problem with 6.x-1.11 is that if you have more than 65,536 nodes or terms (or users..), it cannot save meta tags for any records with ID's past 65,536. This has been fixed in the current 6.x-1.x-dev codebase.

Thanks to everyone's help we now have a new stable release: v6.x-1.13

Can someone outline if this is really safe for a production site and what items work and do not. That would be important to know before making alterations.

@venusrising: Please test it on a development install of your site. It should be completely safe, the only issues seen are some additional steps necessary when upgrading from one of the 6.x-1.12-x releases (four of the submodules no longer exist so you have to delete all old files first, or use Drush to do it).

Seriously, if you're still using 6.x-1.11 today, with or without fixes that were pasted in other issues, you really should try 1.13, I believe you should be pretty happy with the results.

@DamienMcKenna Thanks one important question. is there any issue with mobile tools? I know that there was a few translation things going on but not sure if this too would be an issue. thank for your hard work, what a winding messy rd! Happy 2012

Please stop changing the status of this ticket.

@venusrising: I don't know about Mobile Tools, feel free to report a new issue if you find one.

Sorry, thought that needed to be done to make it seen.