forcing a module's .install file to run
Long story short: I did something daft with a module's db table (Forward module, if anyone's interested) I tried to manually recreate the tables but am obviously missing something as I'm getting sql errors all over the site when I try to utilize the module. So I just want to go back to scratch and start again. When I got into this difficulty, I deleted all the Forward module files AND deleted both db tables, forward_log and forward_statistics. And got ready to start from zero. Yet, when I uploaded the module again and activated it, the forward.install fine evidently didn't run and there were no new tables added to the db. Is there something, some flag, elsewhere on the db that tells the system the tables have already been created and there's no need to do it again?? If so, how do I switch it off/delete a value to allow forward.install to run again? Neil
On Thu, 28 Feb 2008 13:21:07 +0100 "Neil: esl-lounge.com" <neil@esl-lounge.com> wrote:
Yet, when I uploaded the module again and activated it, the forward.install fine evidently didn't run and there were no new tables added to the db. Is there something, some flag, elsewhere on the db that tells the system the tables have already been created and there's no need to do it again?? If so, how do I switch it off/delete a value to allow forward.install to run again?
{system}.status -- Ivan Sergio Borgonovo http://www.webthatworks.it
On Thursday 28 February 2008 4:21:07 am Neil: esl-lounge.com wrote:
Yet, when I uploaded the module again and activated it, the forward.install fine evidently didn't run and there were no new tables added to the db. Is there something, some flag, elsewhere on the db that tells the system the tables have already been created and there's no need to do it again?? If so, how do I switch it off/delete a value to allow forward.install to run again?
Neil
There is an entry in the system table for each module and theme that indicates its current status, including its database schema version. Find and delete the record for the module in question. You could also use the devel module [1], which has a forced reinstall feature. Just make sure you do it with the correct module. [1] http://drupal.org/project/devel -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 15; Cramer, 13; Travis, 11; Angela; Harry, 7; and William, 2) Linux User: http://www.kubuntu.org/ Drupal Fanatic: http://drupal.org/
participants (3)
-
Ivan Sergio Borgonovo -
Jason Flatt -
Neil: esl-lounge.com