pacwebhosting

Hi We hadn't yet as we were waiting for the CORE to be announced. I had contacted WHMCS support back and they also suggested 7.8.3 I will give it a try in a dev instance thanks for letting me know you have not seen this issue since 7.8.3 🙂

Hi Any updates on this?

Hi @WHMCS John Excellent thank you!

Hi Brian, We are currently still on 7.7.1 due to Had a look at the link you posted but don't think it applies as 7.8.x and descriptions don't seem relevant. Although I would imagine the issue would still exist in 7.8.x but cannot say for sure. I have opened a ticket also. Thanks

Hi We have just discovered an issue with go cardless module. For reasons know only to GC they are sending mutliple notifications for the payment which is resulting in invoices being in credit and future invoices being paid by this credit! We are going to have to go through all of the payments now however I have found two already. The Transaction ID is the same for all the duplicate payments so why it has been allowed to go in twice by WHMCS is an issue because if I added a manual payment it would not let me add a duplicate ID! Thanks

Hi @WHMCS John Thanks for replying I am looking forward to getting us on to 7.8.x Unfortunately following those steps for all of our clients is something that will take simply too long as it affects all customers. Although the myworks module comes up I am not sure how that could be an issue as to how the upgrade script fails to allocate the existing method to a new multi payment method WHMCS system, unless you are saying the upgrade script interacts with the relevant payment method module to work? So at this point we are waiting for the CORE fix. Thanks

Hi Thought I would share this so others are aware: - After upgrading we saw many issues with customers payment methods and had to roll back: - 1, Says Direct Debit however it is sage pay with the remote key and no card number but it says direct debit! 2, Shows Visa ending for example 1234 but when clicking into it all the info is there but it says it is the myworks paypal billing module but it is not it is sagepay! 3, Another is a mastercard but when you click in it says it is gocardless! Just a few examples but it was messed up across the board so you may want to think twice or be very aware before upgrading to this latest release. WHMCS have been able to replicate this from their side from the ticket we opened and they have created CORE-13682 Thanks

as enom have just announced price increases for over 200 domains from donut I thought I would share how we automatically cope with price changes and more! we use this module from Nerdle https://marketplace.whmcs.com/product/3821 it handles price changes automatically even across existing domains and can even import domains you don’t have into whmcs automatically including pricing and you set your margins etc! truly a quality addon and saves any amount of time. hope it helps someone out! Paul

Yay! A mere 5 and a half years after I reported it to you guys in a support ticket! Top job! Thanks

Hi @Vox I agree it will be a struggle but hope not 🙂 Not sure there is anything ICANN can do to get around GDPR which is the reason the WHOIS details cannot be gained from Registry to Registry when a domain transfers now. The solution is for WHMCS to recode their ENOM module to send the details to be used post transfer, complete pain but it appears it is the only way. Maybe I will be surprised and this will be resolved soon!

It certainly is a serious issue! I am trying to gain some traction within the community to get this fixed ASAP WHMCS have stated they have a CORE open for it however have just said keep an eye on the releases/hotfixes etc but this should be jumped on and sorted quickly. Previously had another CORE open for a couple of years regarding a NOMINET module problem they could also recreate without reply and as far as I am aware resolution so just keep an eye out for releases doesn't give me confidence. As the vast majority will likely use ENOM with WHMCS it is indeed a problem that needs fixing with urgency. We are going through all the transfers in since May 25th and sorting with customers. The problem here is how WHMCS is still sending the API string to ENOM but it has changed to how they (ENOM) apply it due to GDPR and now UseContacts needs to be 0 and the details to be used passed which it looks like WHMCS have totally missed. Not sure how you would sort the domains@whmcs problem as we do not use the WHMCS provided ENOM account but agree thats an issue!

Hi, We recently noticed an issue where domain transfers in using ENOM for example for a .com once the domain transfers in the registrant, admin and tech contact are all changed to our ENOM Account details! We contacted ENOM about this and they have said: WHMCS have confirmed this behaviour from their software and are looking at it (#CORE-12722) but I wanted to make everyone else aware that uses the ENOM module that all their transfers in will have the domains registrant, tech and billing contacts changed to theirs which seriously annoys customers, and to hopefully get some traction behind getting this resolved as it has been 2 weeks now with just a keep an eye on the changelog for updates scenario. But in this time and since May 25th this year ALL transfers in using ENOM WHMCS module have behaved in this way so that will be a lot of transfers in! so this could do with greater attention. Thanks Paul

Hello "SlimPay is a Direct Debit payment gateway supporting both BACS Direct Debit for UK based customers and SEPA for EU based customers." http://docs.whmcs.com/SlimPay However after speaking with SlimPay it only works for SEPA payments so no UK BACS functionality. They expect it to be able to do this from August 17 Thanks

Hi Might also be worth running a repair on your database, take a backup of it before you do any work on it! Thanks Paul

Hi The new Nominet files release 22/07/2013 do not pass the Ltd company number to Nominet and errors with: V074 Company Number required for UK Limited and Public Limited Companies Despite the Ltd company number being present for the domain. I raised a ticket and was advised that you can replicate it but it will only be resolved in future releases. Due to it being broken by an update pushed out by WHMCS I respectfully request it be given a higher priority as it is a fundamental part of the module not a nicety that could wait for example changing IPS TAG change. Thanks Paul Nesbitt