What makes a module out dated so they dont work?

when XOOPS changes versions, what makes the modules nolonger work?

where would one look in a module to make it active again?

Good question Northern...

You might be on to something there!

I believe that the big problem with XOOPS vs module vers is major changes in the db structure.

I guess the best way to diagnose and "tune up" (pun intended) a module would be to install it and see what db errors you get.

I would imagine that 9/10 times the problem will result from a modification to a vital table that may have once existed but no longer does. Or perhaps even as simple as a change in the name of the function.

A module is really nothing more than a script that utilizes and shares the same tables as your XOOPS install. If these change the module will obviously crash.

Just a guess.

I suppose you could also consider changes with your host on php versions and database versions, although a module may run doesn't mean that it will be secure from hacking attempts.

We're no on some version 5 of php no, and most older modules only work with ver4 or where developed for that, without breaking and creating security risks, if they are not already present.

Just a few more things to consider when trying to make older modules compliant.