We got the following PHP error on UrbanMinistry.org when doing a node find replace:
Unknown column 'key1_name' in 'field list' query: INSERT INTO um_node_find_replace_history
Because of this error, the history is not being recorded.
If possible, I would like to have the option to turn the history off entirely. Since our database is backed up, we don't know the extra load of the lengthy history MySQL queries when we're doing a long series of Node Find Replace (changing URLs).
Thanks for this extremely useful module!
Comments
Comment #1
regx commentedThis was fixed in the latest dev release. Drupal has been asking developers not to push as many releases and to keep updates in development branches longer.
Anyway, this has been fixed and I have created a new official release which should be available shortly.
The db changes have been moved out of the updates and into the main install routine (updates were not running properly on initial install!)
So as soon as the new release DRUPAL-5--1-3 becomes available, upgrade the existing module.
Then, so the new tables are created uninstall it (de-activate the module and it will appear in the modules uninstall list. uninstall it and then re-activate it).
This will completely remove the old table and re-create it with the new schema.
The history is only there to undo/redo if something goes wrong. After running a find/replace, you can delete the history if everything goes as expected.
The mysql queries are not that lengthy and should not cause any problems. It is only used when doing a find replace and with the option to delete the history is there.
Still, if you prefer to use backups (always a good idea) and do not want the added overhead of the history I could make the history optional.
Comment #2
EvanDonovan commentedOk, after uninstalling & reinstalling, this issue is resolved.