Wow I must seem like an ass posting negative feedback on here like this.
But... What I've notice the only thing THT is good for is creating cpanel accounts. Everything else THT just fails at. For example today someone tried to create an account, messed up, so i denied it, then he tired to re-signup. Although he kept getting the fucking error:
Quote://///////////////THT ERROR
Error: Couldn't retrieve client data!
Username:
/////////////////
Your username doesn't exist in the DB meaning the query failed or it exists more than once!
What happened next? Well this error allowed the account to be created without being suspended, thus bipassing admin approval.
You cannot edit any usernames, domains, etc in THT and when having to manually edit it in whm the info in THT becomes out of date.
You guys have a lot of work to do.
Umm I guess I wont be truly evil... Umm... the the ajax stuff is pretty nice. lol
Quote:You cannot edit any usernames, domains, etc in THT and when having to manually edit it in whm the info in THT becomes out of date.
NO Control Panel can do this. Not iPanel, not WHMCS, none.
Many of the things that aren't in THT is simply a WHM API limitation. Each account doesn't have an internal WHM ID that we can reference it by. Then sync it on the cronjob. There's just no way. At least, with the current API. If you were to change the username in WHM then we'd lose track of it.
I do understand your frustration with this. I would love to see how other people use the script in itself, I never find any of these my self.
Also, when you denied the account, tell him to clear his sessions, close his browser and open it. He logged into the account, you denied it and deleted it, then THT was like UH WHOS THIS? Sort of thing.
(11-24-2009 06:48 PM)Jonny Wrote: [ -> ]Also, when you denied the account, tell him to clear his sessions, close his browser and open it. He logged into the account, you denied it and deleted it, then THT was like UH WHOS THIS? Sort of thing.
There's no (easy and reliable) way to delete some else's session. So we might have to implement some kind of check on every page load to make sure the account still exists. But as far as performance goes, I'd hate to have to do that.
Can't you use Cookies and destroy their cookie on account deletion?
All the system is coded to work with sessions, it's a unlucky chance that he's had his account deleted and it says this. Just tell him to close the browser and open it again. Gets rid of sessions.
(11-25-2009 05:50 AM)Jonny Wrote: [ -> ]All the system is coded to work with sessions, it's a unlucky chance that he's had his account deleted and it says this. Just tell him to close the browser and open it again. Gets rid of sessions.
Well, sessions are actually stored on the server. As compared to cookies which are stored on the client. There's a good chance the session will die when you exit your browser but the best thing to do is just hit the logout button. Since it'll properly destroy your session. "/client/?page=logout"
(11-25-2009 10:31 AM)Kevin Wrote: [ -> ] (11-25-2009 05:50 AM)Jonny Wrote: [ -> ]All the system is coded to work with sessions, it's a unlucky chance that he's had his account deleted and it says this. Just tell him to close the browser and open it again. Gets rid of sessions.
Well, sessions are actually stored on the server. As compared to cookies which are stored on the client. There's a good chance the session will die when you exit your browser but the best thing to do is just hit the logout button. Since it'll properly destroy your session. "/client/?page=logout"
Sessions and Cookies are stored both server side and client side. Cookies can just have an expire time.
(11-25-2009 06:28 PM)Jonny Wrote: [ -> ] (11-25-2009 10:31 AM)Kevin Wrote: [ -> ] (11-25-2009 05:50 AM)Jonny Wrote: [ -> ]All the system is coded to work with sessions, it's a unlucky chance that he's had his account deleted and it says this. Just tell him to close the browser and open it again. Gets rid of sessions.
Well, sessions are actually stored on the server. As compared to cookies which are stored on the client. There's a good chance the session will die when you exit your browser but the best thing to do is just hit the logout button. Since it'll properly destroy your session. "/client/?page=logout"
Sessions and Cookies are stored both server side and client side. Cookies can just have an expire time.
The session data is stored on the sever. The data for a cookie is stored on the client.
