Hi Steve,

the new files for whmcs integration seems to work fine with CC2 and CC3 exept one thing:

in CC2 the command change password in shoutcast get an error like

"Module Command Error
Account does not exist in Centova Cast"

Naturally the account exist and other commands like create, suspend, termminate, start, stop etc.  work fine.

Thanks

the new files for whmcs integration seems to work fine with CC2 and CC3 exept one thing:

in CC2 the command change password in shoutcast get an error like

The Centova Cast v3 module is for Centova Cast v3.  The Centova Cast v2 module is for Centova Cast v2.  They are not intended to be compatible with one-another.

Ok, understood.
But in whmcs I can put only 1 server/centovacast folder.
So I cannot use both panels with whmcs?

Ok, it's possible to use both file integrations but it needs to change name of the php file.
In whmcs server module integration the format of file must be:
/modules/servers/filename/filename.php

For centova cast v2 and v3 the centovacast.php file has the same name and so it's impossible to get working together.  I try to rename the file of CC3 in server/centovacast3/centovacast3.php. It is listed but doesn't work.

So we need (I think) a copy of the centova cast v3 file with a different name so to put it in a different folder with the same name of new file.

Is it possible?

I write again because there was no answer.

To give the possibility to use whmcs integration both for CC2 and CC3 we needs to have 2 differents folders and php files for whmcs.

We need for example for CC3 a file like
whmcssite..........server/centovacast3/centovacast3.php

So we can use centovacast/centovacast.php for cc2  and centovacast3/centovacast3.php for cc3.

the only rename of file and folder doesn't work... it need something different in the code inside the php file I suppose.

- removed - do not hijack threads -

The next build will include a WHMCS module named 'centovacast2' in extra/billing/whmcs/centovacast2/ which can be used alongside the latest module.

Good Steve... but you mean that the cc2 version of the module will be 'centovacast2' ? and for cc3 'centovacast' ?
This means that we have to change the module name in hundreds of cc2 products on whmcs now are working.
Isn't better to simply get the name 'centovacast3' for cc3 and leave the old name on cc2 ( 'centovacast' )?

Isn't better to simply get the name 'centovacast3' for cc3 and leave the old name on cc2 ( 'centovacast' )?

No, because 1) we can't expect the WHMCS folks to bundle another new module every time we release a new major revision of Centova Cast, and 2) I suspect most of our clients will be upgrading to v3 anyway, and will want to use their existing billing packages with v3.  Keeping the module name for v3 as 'centovacast' allows them to do that.

Also you should be able to update your existing packages to use 'centovacast2' by running a simple MySQL query against your WHMCS database.