Our official stance on integration into a CMS (content management software) is as follows...
WoWRoster is designed as a standalone application and is not ment for integration into a CMS.
There are some briliant people who do work on porting WoWRoster to certain CMS's such as WoWRosterDF (for Dragonfly CMS) and WoWRoster for phpNuke, and they do a wonderful job sqeezing WoWRoster into a module for these CMS's.
In some cases, the devs of WoWRoster are willing to help with porting (I myself wrote the installation for WoWRosterDF) but this is only when they have the time and the want to do this.
Since version 1.6.0 we have tried to make WoWRoster easier to port to a CMS module (better css, pathing, html validity, and so on).
Our stance is that WoWRoster is enough to deal with on it's own, without having to worry about integration problems.
Also, addons made for WoWRoster are generally designed to run in the standalone version of WoWRoster. If they do not work in a ported version of WoWRoster, then they too must be ported. Some addon authors are willing to help with this process (and who better to help than the author
).
