update_6113: No rows written to nodewords_tmp and therefore all data lost

Is the upgrade progress NOT aware of the reason that D6 runs all update hooks - nevertheless a module is disabled?

It seems Drupal runs update functions also for disabled modules. It's not what I would expect, and I don't know if the update functions could check if the update is running with the module disabled.

ehmm.... i get this problem too... on my blog http://www.blog.ckcybers.com :(
it's still under development...

but i hope the new version that will not remove table will clear as soon as..

Solo una domanda a KiamLaLuno: "Scusa Kiam, volevo solo sapere se un utente come me, che è tornato ad utilizzare Nodewords 6.x-1.0 dopo i problemi avuti con l' aggiornamento descritti nell' articolo http://giovanninews.com/problema-nodewords-drupal , devo aspettare la v. 6.x-1.3". Ti scrivo in italiano perchè con l' inglese non so spiegarmi bene. Ciao e grazie se riesci a rispondermi. Giovanni

Ti consiglio di aspettare che esca la versione 6.x-1.3. La versione 6.x-1.x-dev è pensata (al momento) per chi vuole aiutare nello sviluppo del modulo e verificare che il passaggio da 6.x-1.0 alla prossima versione ufficiale avviene senza problemi; più persone aiuteranno nella verifica, più presto la prossima versione ufficiale verrà rilasciata.

English translation (for who doesn't know Italian):
If you are still using version 6.x-1.0 (or you returned to use it because of the problems you got using the latest official releases), it is better you wait the next version 6.x-1.3. The development snapshot is thought (at the moment) for who wants to help with the module development, and check if the update from 6.x-1.0 to the next official release is without problems; the more people will help with the test, the earlier the next official version will be released.

For KiamLaLuno: They are at the moment to Milan, therefore far away from my zones. As soon as I re-enter in Abruzzi I will try the 6.x-1.x-dev and I will make you to know if the passage from the 6.x-1.0 will be painless. Hello and thanks. Giovanni

Rather than keeping to change referring version, it would be better to make reference to the development version; so far, the development version, and the latest official release share the same code.

if the code doesn't work in version 6.x-1.3-beta1, then it doesn't work in the development snapshot as well.
To use the development version as referring version is better than keeping to change the referring version to the latest official release.
Changing the referring version to the latest official release could still confuse people; then, the development version is the version I set when the bug is fixed.

I changed the code of some update functions to use update_sql() (it is always a good idea to use that function in the update functions); this could help in understanding the reason why the update from 6.x-1.0 is failing.

I checked the latest development snapshot (which is the same of the official release 6.x-1.3-alpha2), and tested the update from version 6.x-1.0. I have verified that the update doesn't cause anymore any data lose.

I changed the code for nodewords_update_6113(), which now doesn't log the executed queries.

That is the only update function that could execute a lot of SQL queries.

If there's a fix on this page can someone point it out to me, please.

Hello,

Is it possible to use this module to automatically add a description to all former nodes that didn't have any ?

How to do ? I'm checking my old nodes now and they don't have any description.

Thank you.

Please help.

@drupalinthailand/make-online-shop: Please don't reply on four-year-old closed issues.

I've replied on the other issue (#1911704: Old nodes that didn't have DESCRIPTION or lost it after update bug, how to add a description (again)).