xpcwebhosting

I would HIGHLY recommend writing a WordPress plugin that lets us place the order modules and such on our WordPress sites. This way we can pick whatever design we want easily. I'm not sure if I can even explain how badly I've been wanting something like this...

Yes, thanks.. it works now.

I see that the following fields are empty, and one of them mentions 3D: Processor ID (Cardinal 3D Secure Details) Merchant ID Transaction PW But this is PayPal Pro, all the information I have is just the API info. I should mention that the CC processing continues to work for everyone else, it's just this one customer who's having the problem.

I have one client complaining that our site wont accept her credit card. She's been with us for months now, and I think (still waiting for a response) that the CC used to work with us. She tried two different CC's and our logs show the following error each time: No 3D Auth ERRORDESC => Error Processing Lookup Request Message, Invalid Merchant Id or Processor Id, Error Validating Merchant Id Value, Invalid Transaction Password, Error Validating Processor Id Value ERRORNO => 1002, 2002, 4020, 2020, 4000 The only change I can think of is we updated to the latest version a few days before she had this problem, either that or it's a new credit card. Does anyone know what these errors translate to? Thanks.

I just found eNom's global edit tool. It helps quite a bit, but not entirely because some domains are registered elsewhere. Any idea of a tool that will tackle that? Or maybe finding a way to list what domains are not registered through us...

We had the previous owners name servers shut down without warning and some of the clients domains are still set to use them. Does anyone know of a way I can find a list of what name servers each domain is using. Maybe a report, or looking in a database, etc.? Our registrar is eNom, and I don't see a method of running that type of report on their end. I wonder if that data is actually stored in WHMCS... should I be asking eNom instead?

I'm getting this error on one of my servers, but not the other. They both run Plesk 9.2.3. Would applying the same change fix or break (since my version of plesk is far newer than others). It does create the client's account, but not the domain. There is also no IP assigned to the account, which I assume is what's causing the problem. On a side note, when this did work (and even on our 2nd server), it never has created a www. DNS record ever from what I can tell. I always have to manually add it in (but that's not the main issue).

Thanks for that, I think I tracked down why it was encoded (someone else did it)... I think I can solve it, if not I'll use that code

But mine is for some reason, I have no idea why, or if I have a non encoded version.

I currently have a support ticket open for this, but if anyone can get around to answering it faster/better then that would be great. I learned that simply adding my $api_access_key to the end of the config file won't work if it's been Ioncube encrypted. I was told: "You need to add the api key line to the original unencoded version and then re-encrypt if using ioncube." Has anyone ever done this before? I don't even think I have an original unencrypted config file. Any help would be appreciated. Thanks!

Excellent, thanks! I figured as much, but I was worried about testing my theory on a live site To clarify my 3rd question... There were some of our domains that got renewed on enom and need payment. They are in our system, but enom renewed them too early because they had the auto renew setting turned on. If the customer pays for the invoice that gets generated, will it renew the domains again (even though they were just renewed a few days ago) or would it just leave them alone? It sounds like it will renew again according to what's been said above, but in our initial setup we had enom auto renew on for all domains without realizing what was going on, and domains were never renewed a second time when the payment came along. (or were they? ) The next due date is set this month, whereas the next expiry date is over a year from now. Would it notice that ordering a 1 year renewal when there is more than a year left would be pointless and then not process it? If that is the case, how do I bill the customer without getting automatic extra renewals?

1.) If I set the automation settings so that invoices are generated early, does it affect the dates for the next renewal (regarding both domains and hosting products)? For example if the customer gets an invoice for a domain renewal 7 days prior to the date and then pays it that day, it won't change the next renewal date to the earlier day, will it? ------------------------------------------------------------------------------------------------------------------------------------------------ 2.) Also, would it renew the domain directly on payment, but then still renew on the same day next year? ------------------------------------------------------------------------------------------------------------------------------------------------ 3.) I have a few domains in my system that got auto renewed early by eNom. I'm wondering if i set the due date earlier than the actual expiry date that it will renew again (add +1 year to the domains).... any ideas? ------------------------------------------------------------------------------------------------------------------------------------------------ Sorry for all the questions... as you can see, I'm slightly confused on how to set invoicing settings properly

It's capturing stuff now, it seems like it was just that one day where it decided to create invoices but skip ever trying to process CC's. I did it manually.

I turned off the SSL fix and tried to re-run the CC capture and still no go. At least this time it says 1 failed, but it missed all the other unpaid ones that have CC numbers and are ready to go from the 1st of the month.

Cron Job: Completed It doesn't say anything about failing... I ran the cron again this morning and it captured one CC payment and one failed. There are still a bunch from the 1st of the month which aren't being handled though and I don't know why...