Jump to content

Hal9000

Level 2 Member
  • Content count

    71
  • Joined

  • Last visited

  • Days Won

    1

Hal9000 last won the day on January 30

Hal9000 had the most liked content!

Community Reputation

12 Good

About Hal9000

  • Rank
    Level 2 Member
  1. I just so happened to pay an invoice on whmcs.com via PayPal and I actually got that awaiting notification message. However the URL shows &paymentsuccess=true and nothing else, so there must be some other criteria that makes that message appear. Since when adding that variable to viewinvoice.php when the invoice was paid showed the standard paid message, I assume that maybe some variable gets set inside the module_link function if $_GET['paymentsuccess'] is true or something. But which one? Damn...
  2. I know, and this is what I want to show. I coded my own gateway module and need to pass the return url to the gateway, but I need to know which parameter to attach to the URL in order to have the message show.
  3. The viewinvoice.tpl file shows the $LANG.invoicePaymentSuccessAwaitingNotify string if $paymentSuccessAwaitingNotification is true. Similarly it does for paymentsuccess, pendingreview etc. I know the other ones can be triggered by setting a URL parameter. But what is the parameter that sets $paymentSuccessAwaitingNotification to true? I found it nowhere in the documentation.
  4. Sorry, I forgot to follow up. The problem was that the domain had already the SpamExperts MX configured in it. When activating SpamExperts, they need to know to which mail server to relay the mail to, and they take this information from the MX record. However, if you already have SpamExperts as MX, they will not know where to send it to and refuse to configure. So I had to edit the DNS zone and wait over a day to be able to configure properly. I would have preferred a way where it would just configure without a relay and that I could configure it manually, but at least now I know what to do if this happens again.
  5. Same problem here... @davet did you mange to solve it?
  6. Ok I solved it. Looks like the patch set was missing the install folder, so I copied it over from the full install archive. The installer wrongly stated that it detected version 7.3.0 (I had 7.4.0), but still the upgrade to 7.4.1 worked...
  7. I uploaded the patch set for 7.4.0 to 7.4.1 and now I am greeted with a "Down for maintenance" message. Anyone else?
  8. Seems to be working again since upgrading to WHMCS 7.2.2
  9. This seems to have been fixed with WHMCS 7.2.2+hotfixes
  10. Thanks for your hint, the same thing happened to me in the past. But not this time, Maxmind says "Available Funds $24.89" which should be enough for plenty of fraud checks.
  11. Somehow centralnic is reeeally slow in replying, often resulting in timeout errors in WHMCS. I can do a whois in the server shell, it takes over 20 seconds until a reply comes in... So I guess I will contact CentralNic support anyway, maybe they throttle my IP or something...
  12. Thanks. Found out that whois.nic.store also works. [ { "extensions": ".shop", "uri": "socket://whois.nic.shop", "available": "queried object does not exist" }, { "extensions": ".store", "uri": "socket://whois.nic.store", "available": "DOMAIN NOT FOUND" } ]
  13. Duh, now I found where to configure the path and noticed it was indeed gone for some reason. Fixed
  14. Hi there, I noticed in my activity log that there are messages like this: While .design is contained in the dist.whois.json, I added .store myself in whois.json [ { "extensions": ".shop", "uri": "socket://whois.nic.shop", "available": "DOMAIN NOT FOUND" }, { "extensions": ".store", "uri": "socket://whois.centralnic.com", "available": "DOMAIN NOT FOUND" } ] Which looks correct to me. Either way, the "error detail unknown" is not very helpful... what could be wrong?
×

Important Information

By using this site, you agree to our Terms of Use & Guidelines