zanix wrote:An option for handling addons is to edit addon.php
addon.php already uses ob_start() to capture output of addons
You could write a preg_match on all <a href="" and<form action="" links in the addons
This would make most addons easily portable, some would require more changes
The problem actually lies in the porting for the roster config variables...to use them with vBulletin (ie to have a vBulletin administration compatible admining of the system) the port needs to use vb's native configuration system, so instead of calling $roster_conf['whatever_setting'] it needs to call $vbulletin->options['whatever_setting']. The same for the language, instead of $wordings['whatever'], vb calls $vbphrase['whatever']. There in lies my issue atm.
For the moment I'm going to do hardcode on the ports of addons I'm including with the system, but later on I hope to have the system convert the variables to the vbulletin variables for the configuration and phrasing and then it should be a no brainer...