API & Interface Inconsistency

[abdi]

Till, again today I hit a bump ..
Now my AWBS module is ready and can create clients, domains and email domains all as 1 client known by the billing module.

What I now need is a user to click a singe button on the billing interface like "Control Panel" then there he would be automatically logged into ISPConfig.

I have the logins stored with my billing APP so I can easily add them as hidden fields. I have also searched the forums with no success ..

If its not possible, then do you mind giving me the name of the logged in user SESSION and or what other sessions must be created on successfull user login I could create a script that validates directly with the db if the form redirect fails ..

[till]

Take a look at the file /usr/local/ispconfig/interface/login/index.php if you like to know how a valid ispconfig session is setup.

[abdi]

Till, I also did notice that when you rename the database through API, much as it gets renamed in the "web_database" the physical database it self is NOT renamed.

Is it a bug or is working as expected?

[till]

Take a look at the interface, as you see there, the database name is locked and can not be changed after you created it. So the same applies to the api.

[abdi]

Hello Till,

What is the difference between client_delete and client_delete_everything commands?

My understanding would be:

client_delete_everything deletes everything that belongs to that client, and that is sites, domains, email domains, email accounts, databases and ie EVERYTHING

While client_delete should only delete the client leaving the rest of the information in system ..

Unfortunatly client_delete_everything does not return anything and ONLY deletes the client leaving the rest of the information like sites in place ..

Am I missing something?

Thanks, Joseph

[abdi]

Any help over there Till ?

Also noticed that sites_web_domain_delete command does not return affected rows as indicated in the documentation, just returns nothing ..so you really can't tell if all went well by comparing the return variables.

[till]

I will check that until the relaese of the final version.

[abdi]

Am sorry for the double posting, but since this thread is about API inconsistencies, may I kindly request you to check this too:

While in the creation of a domain name via API, I do set the following:

[.....]
'stats_password' => 'my_password',
'stats_type' => 'awstats',
[.....]

Expecting that Stats will be enabled automatically. Unfortunately, they are NOT. I have again to login to control panel to enable them. Is this how it functions or something missing?

NB: The /var/www/clients/client30/web49/web/stats/.htpasswd_stats wouldn't be created through API not until enabled through ISPConfig Panel.

[till]

Please do not double post:

http://www.howtoforge.com/forums/sho...3&postcount=19