This Module will Load the 0.5.0 Modules Making the Apropiate Changes,
Should work with all modules made for Current SVN

This module can be Placed were you want

The 0.5.0 Modules Must be placed in /custom/050/ Folder

What this Module will do is:

• Change all $this -> bot -> core(...) calls to Correct 0.4 calls
• Remove the prefix as 0.5 module dont get the prefix inside the message

Change Log

• 23/06/08 [0.4] - Now Replaces core("time")
• 23/06/08 [0.4] - Now Supports the function get_timer from timer module
• 23/06/08 [0.4] - Return Function of Extended Modules Fixed
• 23/06/08 [0.4] - Register Modules Added
• 23/06/08 [0.4] - Error Class Added
• 24/06/08 [0.5] - Now Supports the function list_timed_events which was added to 0.4 just after 0.4.3 release
• 25/06/08 [0.6] - Added Support for New DB Functions
• 15/07/08 [0.7] - Fixed Issue with Stopping other normal Modules loading
• 25/09/08 [0.8] -
• 20/10/08 [0.9] - Fixed Register_event function

Updated to Support Latest SVN modules

i dont see how this module an cause that prob,
altho the old version did a Chat redirect

im asuming you got a 0.4 bot and useing 0.5 Seurity.php ?

if you read it says you need to put the 0.5 modules in a certain folder, since security.php is a core you can make sure it load with core files by putting this support module in a core folder

Another bug I thought I would mention is once the module is activated all other modules in the same file location are no longer loaded. I have tested this in both the ./modules folder and ./custom/modules folder.

Any other info I can provide to help this get resolved?

I think that I may have mislead you, all the version 5 modules load properly. It is the older custom 4 modules that are now refusing to load. For example I have the new twitter module loaded in the custom module folder yet when I have the 0.5.0 support module in the same folder it will not load.

c:\mybot\custom\modules\0.5.0_Support.php    <- Loads
c:\mybot\custom\modules\twitter.php     <- Does not load
c:\mybot\custom\modules\homer.php      <- Does not load
c:\mybot\custom\050\onlineorg.php        <- Loads

If I disable the module for 0.5.0 support the other modules in the same folder will load

c:\mybot\custom\modules\_0.5.0_Support.php    <- Disabled
c:\mybot\custom\modules\twitter.php     <- Loads
c:\mybot\custom\modules\homer.php      <- Loads
c:\mybot\custom\050\onlineorg.php        <- Does not load (for obvious reasons)

Now this is where it gets funky. If I move the twitter.php and homer.php plugin to the main module folder they will load

c:\mybot\custom\modules\0.5.0_Support.php    <- Loads
c:\mybot\modules\twitter.php     <- Loads
c:\mybot\modules\homer.php      <- Loads
c:\mybot\custom\050\onlineorg.php        <- Loads

To double back and test completely, I placed the 0.5.0 support module in the main module folder to see what happens.

c:\mybot\modules\0.5.0_Support.php      <- Loads
c:\mybot\custom\modules\twitter.php     <- Loads
c:\mybot\custom\modules\homer.php      <- Loads
c:\mybot\custom\050\onlineorg.php        <- Loads
c:\mybot\modules\About.php                 <- Does not load

So the module is loading all 0.5.0 modules properly it is the other 0.4.0 modules that are now not loading when the support module is in use.

Seems to still be doing the same thing. To bypass it I have moved all the other modules back to the main module folder and they load great as long as they dont share the same folder as the 050 support module.

Ok, with the latest updates I am still encountering a problem with the SWStimer.php module. The message below is the error that is last sent before the crash.

Fatal error: Call to undefined method Timer_Core::list_timed_events() in C:\<mybot>\custom\modules\0.5.0_Support.php(60) : eval()'d code on line 124

Let me know if you need any more logs.

I havent replace the security module, but I will see if that is the culprit. I did at one time try and use the AccessControlGUI from version 5 but that was deleted (I did have it in the 050 folder). Not sure if that would have modified anything.

The problem ended up being the OnlineDB.php file not being in the right spot.

omg many thx for that help