Do not install the development snapshot
kiamlaluno - September 26, 2009 - 23:33
| Project: | Nodewords |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Do not install the development snapshot in a production site; the development snapshot code still needs to be changed to allow a smooth update without to lose any data / settings.
When the message in the project page will be removed, the development snapshot will be safe to be installed on a production site, and there will not be the risk to lose any data / settings.

#1
Hi KiamLaLuno:
Maybe you also need this message on release notes for the dev version (too late for me - I installed after mikeytown suggested the auto descriptions are in dev version now...)
Also, I'd suggest changing release notes for 1.2 - when I'm administering Drupal, see that an update is available for a module, I check release notes, won't look at issues queue. Could save a fair bit of grief, for people who are yet to "upgrade"
#2
@Kiam: PLEASE - stop committing more than one patch at once as already said! It's impossible to review your buggy commits! I'm pretty worried about the new code quality and demolition of the stable 1.x branch used on soooo many sites! Review and test your code and patches *more* carefully before committing them, please!
#3
basic_metatags_update_6103() is currently broken. It loads and load and loads and never finishes on my DEV box. I have only 40 rows in the nodewords table. I have ran update.php with basic_metatags disabled. And to note - CPU is at 100% all the time. I'm now waiting for over 10minutes and there is no time-out.
#4
Looking into the mysql logs shows something very strange - i have thousands of lines with the same SQL request:
#5
it would be nice if the main project page showed 1.0 as the recommended version. that was save people a lot of grief.
#6
This is currently not possible with the project module... :-(
#7
custom meta tags module is named "name = Extra meta tags"
#8
The problem with the update function is that the SQL query that grab the data from the database is different from the query that counts the number of rows to update (the last one should be
SELECT mtid, content FROM $table WHERE mtid > %d AND name = 'revisit-after' ORDER BY mtid ASC).#9
Now
nodewords_update_6113()seems to have an endless loop. I've tested the direct upgrade from 1.0 to latest DEV and update.php hangs at step 14.After aborting the upgrade I have a nodewords_tmp table and this table is empty, plus a nodewords.content with cluttered content.
#10
I cannot repro this if updating from 1.2 to latest DEV.
#11
I think that is now safe to use the development snapshot.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.