>> Site Map >> Forums >> Modules 7x
Forum module - topics in forum:
Modules 7x - Discussions regarding PHP-Nuke Modules. 7x
Module goes inactive randomly, PHPNuke or the module?
I have recently installed a calendar module ( TotalCalendar which is very cool IMO) and am having the strangest issue. I don’t know if it’s the module or my Nuke, but it is frustrating.
I can go to my site and see the Calendar module to the left, click on it and everything is great. Then a day or so later, I go to the site and the module isn’t on the left. I go to admin and it is inactive. I reactivate it and it’s there……for a while. The module itself has it’s own tables but do NOT touch the PHPNuke tables.
My question is: Is there anyway PHPNuke can decide to inactivate a module? The author of the script (or somebody in support) told me that since their module has its own tables, there is no way the module could be doing it. How can I find out (some log perhaps in PHPNuke) why this is happening? Is there a way I can force a module active with some code somewhere? I have even renamed the module folder and reactivated it think there was something hanging around with the old module name.
Any thought would be greatly appreciated.
I knew i'd replied to a similar problem before, have a look at this topic and see if it works: http://phpnuke-uk.net/modules.php?name=Forums&file=viewtopic&t=5282
I just optomized the DB, I'll sit on it a while. If it happen again, I'll delete the modules table and recreate it from the original SQL code.
Thanks for the input, I'll keep you posted.
I don't know why I said to drop the table in that topic, but don't drop the modules table as you'll find you won't be able to use any addon modules you've installed.
Well, the module went inactive again after optimization. I am at a lose now. If I shouldn't recreate the module table, is there a way to make a table (preferably a record) read only? Could I make the record in the module table read only?
I am reaching now
What is I were to drop the module table and recreate it from the original SQL code. My only custom module is the calendar, shouldn't I be able to retain the folder in the file structure and just activate the modules again I need?
Thanks for the help thus far
Well, this is still happening, so perhaps I'll rephrase the questions:
1) Is the ONLY place a module is flagged active in the modules table?
2) If so, what can write to that table to inactivate modules? (I thought it was only the admin control panel). Could a module that is misbehaving get flagged inactive by some other code somewhere?
This is the strangest thing I've seen with PHPNuke so far
bump
Don't bump topics.....
if an answer was known to someone I'm sure they would have answered it.UPDATE:
I was still having no luck in determining a solution so I completely removed Totalcalendar (folders and tables within my Nuke DB). I did a complete reinstall and configured and I am STILL having the module go inactive.
The author of the script insists it has nothing to do with him, so I am thinking I have something weird in my PHPNuke install. Since this is a soccer site and the season just started, I am going to sit on it until after the season and then probably install E107 (I've always wanted to try something different).
If anything changes on this, I'll be sure and post here, I am sure that somebody out there may have modules deactivate them self.
