Summy

If a client contacts us wishing to cancel via a support ticket, email or phone, we simply log in to their client area and submit the cancel request ourselfs using the appropriate mechanism. This then deals with not invoicing going forward, and wiping the account from the server, as said by chickdippers.

Simon, anymore thoughts or progress on this? We're looking at doing something similar, we want to do the following: - Offer a 30 day free trial package - Requires the customer to provide card details and an authorisation charge for £1 placed (which we refund/do not take, simply an authorisation), this would also do 3d secure etc on the card. - We use WorldPay FuturePay so this would also set up an agreement. At the end of the 30 days we want the customer to then be automatically switched/upgraded to one of our packages, unless they cancel beforehand. Payment will be automatically taken using the FuturePay agreement. Still wondering the best way to do it... all a bit ugly really and require work arounds.

Just a thought, but perhaps you could change the wording of your .uk domains, so it looks to worldpay (when they check) as if your charging say £10 for the first year, and the second year is free.

We also looked in to Ubersmith before we made the switch to WHMCS, about 6 months ago infact, started playing with it and spending quite a bit of time with it. One thing we'd LOVE to see borrowed from Ubersmith is the order queue system, gives you total control over setting things up to suit your business requirements. For all its wonders though, it does have a few major issues, and I've contacted them about this, gave a lovely big email but no reply. 1) it doesn't support multiple tax levels (so uk/europe businesses out of the question) and another big bummer: 2) it stores cvv2 codes in the database !!!

you guys have plenty of spare time on your hands obviously

also if you use a reseller account for each shared server... what kind of naming convention do you use... we'd like to use the hostname, but i'm not sure if thats possible.

Hi guys, Just wondering what the various people on this forum have set up in their "server module" section. Do you connect directly as "root" to your shared web servers for account functions, or do you create "master reseller" accounts on the servers, then use those details. We've got it set to use a reseller account on each server, rather than logging root details in the WHMCS database... What about other people, how do you have yours set up?

nevermind I see that I am missing the '$' character. Please delete this thread!

I've got an invoice template with {invoice_num} in the subject line, so that it helpfully displays the invoice number for the customer without them having to open it. On signing up/trying to send an invoice the following error appears in my php error_log file: [09-Mar-2009 15:12:41] PHP Fatal error: Smarty error: [in emailtpl:emailsubject line 1]: syntax error: unrecognized tag 'invoice_num' (Smar ty_Compiler.class.php, line 583) in /home/username/public_html/libs/Smarty.class.php on line 1095 So am I right in thinking that I can't have merge fields in the subject line? If not, can we put this in as a feature request please? Having 10 or so emails in a folder with the subject "Your new invoice", isn't very helpful.

Ok so here is the chaff that we've removed so far, and all seems to be working ok, although this is a test environment, we have yet to go live with whmcs. 1) Removed all ununsed admin, fraud, gateway, registrar and server modules. The only modules remaining on our set up are: enom, enomssl, maxmind, worldpayfuturepay (and the associated callback), and cpanel. 2) Placed .htaccess files with the following instructions: Order allow,deny Deny from all in these folders: ./includes ./lang ./libs ./modules ./pipe 3) So that the callback works, placed the following .htaccess file in the callback folder: # This needs improving to match the RBS WorldPay IP/Domains Order allow,deny Allow from all 4) Placed the following .htaccess file in the ./templates folder: <FilesMatch "\.(tpl|php|ini)$"> Order allow,deny Deny from all </FilesMatch> I'm not saying this is perfect, or that it won't break anything, as we're simply testing with it at this stage. Once we work out exactly what can be trimmed we'll put it all in the apache config, as having .htaccess files all over the place is going to be a tad messy, unless its something WHMCS can consider including in the releases. There is a lot of folders/files that don't really need to be in the web root, but this is further consideration for WHMCS. For now we have to just be happy with blocking http access to them. It may also be an idea to to add an htaccess block to the following file in the root folder: "dbconnect.php", probably others as well.

you could pay someone to code this for you, it wouldn't be much work. Or if Daniel posts his script then you are sorted

either remove the files (not sure if this will cause issues), or restrict http access to them in a .htaccess file: <FilesMatch "^(dontallow1|dontallow2|dontallow3)\.php$"> Order allow,deny Deny from all </FilesMatch> Very simple and crude but it would work. Replace dontallow# with your php filenames.

Thanks openmind, that's exactly the kind of thing we want to prevent. Chickendippers the reason is purely as a precautionary measure. I'm not saying it's a risk leaving unused modules laying around, but for the 5 minutes it takes to remove any unused scripts, or remove direct http access to them, it's time well spent. If anyone else can chirp in, perhaps from WHMCS or first hand experience, I guess it's going to be a 'suck it and see' test.

I'm not sure if whmcs supports this kind of feature, I suspect not (im sure someone will pip in if i'm wrong).... What you could do is create a very simple cron script that checks each account's age, if account age = 30 days, fire off the email template.

I'm just wondering if it is fairly safe to remove unused modules, i.e. payment gateways, server modules and the like from my WHMCS install. Also, is there any way in which I can find out what PHP files require HTTP access, other than those in the root folder and admin root folder? I plan to remove any unused modules, and secondly remove access (via .htaccess) to any PHP files that don't require direct access.