dryline

Matt got in there this afternoon and fixed it!

Well, armed with that knowledge, I guess I won't respond any more. Not like it does any good anyway, the only responses I get is basically, we're looking in to it, which I have gut feeling the "looking in to it part" stopped when they hit the reply button. I really, REALLY don't want to have to go looking for, and switch to a new system again, but if they aren't going to support this one, I can't go on forever with a broken system. I even tried a fresh upload (not overwrite) of the 5.2.2 files, just using the old configuration file, and the issue is still there. Just wanted to make sure a file didn't get borked up during the upload of the upgrade.

14 days now, and after 3 inquiries from my on the ticket, I still haven't had any further response whatsoever in 6 days.

Now on 6 days since my last support ticket response, event though I've replied a few times asking for an update. For me, support seems to be non-existent at the time.

I'm at 13 days and counting on a support ticket for a non-functional support ticket system. I rarely open a support ticket, and they have all been quickly resolved in the past. This time around the best response so far was "we are investigating the issue". And it takes me several inquiry replies to even get a response.

Anyone else having this issue? Upgraded to 5.2.1. on 03/12 and this problem showed up, so I opened a support ticket with WHMCS: ***** First support ticket response the next day was to download the new patch files (which at the time were only for the previous versions) for a fix. After I pointed that out, it took until 3/15 until they said 5.2.2 was available that would fix the issue, but it didn't. It took me responding to the ticket several times until they finally logged in and looked at it on 3/19 and said: and then the next day on 3/20: Now 6 days later, and a couple more inquiries from me on where they are at on this and no further response, and still no functioning support ticket system, 13 days now and counting...

I opened a support ticket and they provided a couple of update files that fixed it right up.

I'm having the same issue now. Customer gets created, but nothing about the domain registration passes to NEO. Also, existing customers doing transfers/renewals are not passing from WHMCS to NEO. This just started the last couple days or so.

Hello everyone! I've been using BluePay/Online Data Corp for years now and I'm finally fed up with the ever increasing fees and random charges and decided to switch to CDGCommerce and the Quantum Vault. Reading through the WHMCS docs I see there is a vault migration script that will transfer all of the client card details from the Quantum Gateway to Quantum Vault and remove them from the database. I was just wondering if it will work since I've been using the Bluepay module? I'd like to especially hear from anyone who has done it and anything in particular I need to be wary of in the process. Thanks!

I got a couple of the update emails tonight, and it was back to the more generic pages like it used to be, with out eNom account name on them. Thanks for getting on that Matt.

I've been very happy with the WHMCS software, but this is completely unacceptable and unworkable. I'm seriously hoping this is unintentional.

Why is this happening? I have a eNom reseller account under WHMCS, and here in the last few days, they have been sending out the required ICANN notices to my registered domain name owners as they have in the past, except now instead of going to a generic page that says to contact us if they need to update, it's now going to a WHMCS sales page with all sorts of competing products including hosting, domain name registration and domain protection, enticing our customers to get it through WHMCS. This is not acceptable.

We use suphp 777 permissions are not allowed

I just had this issue as well. I found this thread, and had been using FF so I switched over to IE and gave it another shot. This time I got to the step 1 of 5, please wait 120 seconds and nothing has happened since and email log shows nothing went out. I am on v. 4.1.2

Exactly what was in quotes in your post #7 in this thread. I had the default line, I made it look exactly like you had it there, and got the error. I quadruple checked it and can't seem to get it to work.