macconnect

Yeah, about 45 seconds of searching solved this problem for us. ;-) You can't insert merge variables in template subject lines by clicking them, but you can type/paste them in and they work just fine. Thought this might help someone down the road.

Greetings all, Our billing folks are complaining because threaded email clients (like Gmail) combine messages based on subject. So, when WHMCS sends out past due notices or payment failed notices, responses from multiple customers wind up in a single email thread. Very hard to sort that way. Looks like you can't use merge variables in the subject line of the email templates unless I'm missing something. Has anyone else found a way around this?

HI We have Ticket Piping set up and its working fine. We have several administrators working on tickets. We want to set it up so that if one admin replies to the ticket, all administrators receive a email reply. The way it works now is that only the customer who open the ticket gets the reply, so none of the admins know the ticket has been answered without logging into whm. How can we make this happen? Thanks!

HI With version WHM version 5.2.6 and Bulk Updater version 2.0 the bulk updater is not working. It cannot find any domains when searching? I have tried several combinations of search criteria and nothing works. are there any known issues?

We moved our WHMCS to a new server yesterday. No issues but one kinda annoying one. We did not install any cron job for domain sync, yet last night it just kicked in. Ran through all our domains and issued a bunch of emails confirming them as in sync. Not sure how without a cron job installed for it, but whatever. This morning we awoke to find the domain sync job running out of control, looping endlessly through all our domains. Un-checking the domain sync box in the domains tab of general settings stopped it immediately. After cleaning out the mountain of emails our operators received, we're left wondering what's going on? 1. How does the feature work if we never installed the cron job? 2. What makes it run out of control like that? We were running 5.2.5 on the old server too. The only change was moving it onto a shiny new VM.

Curious issue. We have IP restrictions on the admin area of our WHMCS installs using .htaccess. Works as expected for any web browser, but using the IOS app we can log in from anywhere. Not what we would have expected.

[bumped to enable email subscription to the thread]

Just upgraded to 4.5.2 since our older version didn't have the billing method choice in the client profile tab. There it is now, but when we select "mail in payment" as the default and click "save", nothing happens. No error upon saving, but profile tab still says "select to change default". Here's a screen shot: http://dl.dropbox.com/u/16356010/default-billing-method.png How do we know that the default payment method for the client has been changed? Also, this client has never paid by credit card, so the idea that invoicing for billable items is based on the client's previous invoice doesn't appear to ring true. Of course, we were running 4.2.1 up until this morning, so that might have something to do with it.

Small issue. When adding billable items (i.e. additional consulting work) for a client that normally pays by mailing in checks, those items are invoiced as "credit card payment" if they get invoiced independently (i.e. on next cron run). There should be a way to set those items to "mail in payment" to match the overall customer account. If the items are lumped into the customer's next usual monthly invoice, there's no issue. The invoice correctly reflects "mail in payment". Any ideas or feedback on this one?

I think we have this figured out. You still have to manually generate the CSR to paste into the WHMCS certificate "configuration" interface, and it appears that ENom will just email the cert to the customer, so it also has to be manually installed.

I'm a bit unclear about what WHMCS means when it wants to "setup" an SSL cert. Once a customer places and order and makes payment, I understand that they'll get an email link that they should follow to set up the cert. I assume this means just generating the CSR and submitting the order to Enom, yes? Will the cert, once issued, still need to be manually installed on the web server? This would be preferred in many instances since we're dealing with a ton of customers on non-managed (i.e. no integrated control panel) shared and colocated servers.

Looks like it was a simple fix. We had to re-enter our OpenSRS username and private key. For whatever reason, dropping the PEAR and Crypt folders in munged the info.

After upgrading WHMCS to the latest version, we were experiencing the partially loaded domains pages issue. We dropped the Crypt and PEAR folders into the opensrs modules folder. That fixed the problem, but now we're getting this on every OpenSRS domain page: "Registrar Error Could not get credentials for reseller ½Ò¶ãñÄ=çàĆjµƒ¼âšC<ŽdøÖ‘õrÛ." Any ideas?

In the last month we've suddenly seen the following: 1. Customer's domain is due for renewal 2. WHMCS auto-generates renewal order as expected 3. WHMCS auto-charges customers credit card as expected 4. WHMCS updates the "Next Due Date" to reflect the renewal 5. Order sits as a "pending order" and never gets submitted to the registar (OpenSRS) 6. Manually submitting the order to the registrar results in failure with "domain already renewed" In this case our only recourse is to manually renew the domain from inside the OpenSRS management interface. We then manually accept the order inside WHMCS while unchecking the "submit to registrar" box. Our WHMCS system has been running without issue for almost two full years now. Any ideas what could be causing this? Orders for new domains seems to be working perfectly.

Sounds like that would definitely do it. I'll try 600 seconds. That should be enough time. We'll see in the morning. Thanks!

March 1 was the first larger automated billing we've done through WHMCS. It appears that the nightly cron job is only processing between 35 - 45 credit card payments per night for some reason. Its not a disaster, but that means its taking a few days to run all the invoices that were due on March 1 and for the last two nights WHMCS has been sending out "overdue" notices to customers even though it has not attempted to charge them yet. Any ideas? We're using the BluePay gateway which seems to have been working flawlessly until now. Also, I noticed that the last email report of the nightly cron job was from Feb 29. My guess is that something is failing before WHMCS gets to the end of its job, hence no email report and not all cards being processed.

I think what we're wrestling with is the actual WHMCS logic behind domain renewals. By default, it appears that WHMCS wants to auto-generate a renewal invoice for a domain on the "next due" date. it will then attempt to charge the customer during the next cron run and if successful will renew the domain with the registrar. Fine, but our customers have been manually renewing domains for 7 years now. If a customer manually places a renew order, WHMCS still generates that auto-renewal invoice based on the due date. The manually generated invoice gets paid, but the auto-generated invoice still exists and also gets paid in the next cron run. The renewal fails since the domain was already renewed, but now we've charged the customer twice for the same renewal. Does WHMCS generate renewal reminders based on the expiry date, or the due date of a domain? Can we stop the auto-invoicing/renewals in some way? I have no problem with the logic behind asking the customer to opt-out of auto-renew in some way, but when you're migrating an old customer base that never agreed to that policy in the first place, you wind up with lots of billing disputes to handle.

This should have said "the domain is already RENEWED" (not removed). Sorry for the typo.

The client never logged in. We manually put the domain into WHMCS as a transfer with no invoice and no confirming email to the client. We then manually accept the order without sending to the registrar. We then edit the domain info to reflect the actual expiration and renewal dates (the same, right?). We then log in as the client and go through the renewal process, paying the invoice immediately when it is created. The invoice gets paid and the domain is immediately renewed. How, then, does the second invoice get created, and how did the higher sequence number invoice get created before the lower sequence number invoice (at least according to the time stamps on them)? It appears that even after the client completes the renewal, payment is made and the domain is already removed, the admin area still shows a pending order with the options to send to registar and send confirmation email. Both were already done when the client paid. Could that be the issue? So far WHMCS has been great for us. This is just a little mystery that we're scratching our heads over.

Duh. I guess its time to take a break. Thanks!

You're right. Somehow two invoices were created for the renewal. Invoice 10190 was generated 01/24/2008 03:15 Invoice 10191 was generated 01/23/2008 16:04 I did the order myself and while I'm certainly not above making a dumb mistake, I'm pretty sure I did it only once. Plus, how did the invoice with the higher sequence number get timestamped before the lower sequence number? The invoice created on the 23rd at 16:04 is the one I did. Nobody was working at 03:15 on the 24th and the client herself has never logged in.

If a customer registers a domain without purchasing hosting, is there a way for us to attach that domain to a hosting plan that the customer orders at some point in the future? Not critical, but it would make management a bit prettier, especially when customers have more than one hosting package.

A customer logs in and orders a domain renewal. No problems there. If they choose "Pay Now" on the invoice and pay immediately, WHMCS submits the renewal immediately to OpenSRS. Great, but then it seems to try again during the cron run in the middle of the night. It happened yesterday again when a five year renewal was ordered, paid for, and submitted successfully to OpenSRS at 3 PM. We then found that WHMCS tried to submit another 5 year renewal at 2 AM during the nightly cron. Is this a possible bug or are we missing something?

How are others dealing with domain renewals when the client and domain do not already exist in WHMCS? As of now, we manually create the client account (migrating from an older billing system), then manually create a domain transfer order without invoice or confirming email. We accept and complete the transfer order (without actually doing the transfer at the registrar) then manually update the domain expiration date and do a domain renewal order. Isn't there an easier way? It would be much nicer if we could simply allow existing domain clients to order domain renewal as a first transaction.

We had our first .org registrations via WHMCS last night. Everything went fine except that OpenSRS rejected the registrations due to formatting errors with the customer's telephone number. Isn't there a simple way for us to go in and manually fix the phone number format so that we can re-submit the domains to the registrar? We can change the phone number format in the customer's profile, but will that change be reflected in the registration re-submission?