Mandalorian

Please report this as a bug to both whmcs and ispapi. @PapaKai @John

Check your cron job might be running twice instead of once.

Thank you. I did that but the issue persisted. It only resolved itself when I manually edited and saved all custom fields per my previous comments.

Well said. Wish it wasn't so hard for an automation tool to automate stuff.

Strangely, it has started to work when you disable and re-enable the custom fields and make small changes like remove spaces after commas.

Dear WHMCS users, I have set "Product/Service >> Custom Fields" dropdown option for customers to select when buying a product. For example, customed had to choose the "data center location" dropdown when placing the order. Since upgrading to WHMCS 8.5.1, customers are seeing the following "Custom Field" throw error even though they selected the required custom field option: "Please correct the following errors before continuing: Invalid Selection Option." Before upgrading to 8.5.1, the "Custom Field Options" worked fine. Due to this, my whmcs store is not working as no orders can be placed. Did anyone encounter/fix this, please?

Thank you, Kai !!!!!!!!!!!!!!!!!!!!!

Hi Guys, WHMCS says WHMCS does not work with any caching tools. Have you used "Zend Opcache" on cPanel to improve WHMCS performance? If yes, did it cause any problems with the operation of WHMCS?

That's right, Kai. It didn't get a mention in 8.4.0 beta 1 release. According to WHMCS, it was an oversight and that the actual issue has been fixed in this release. Here is their response: Looking forward to your findings 🙂

UPDATE: #CORE-14055 didn't get a mention in the 8.4 GA. Worried, I checked with WHMCS if this was fixed as promised. Their response was that, #CORE-14055 didn't get a mention due to an oversight. I take it that it did get fixed. Hopefully someone can verify and confirm here.

Guys, please also post tickets and follow up on them to increase the chance of this getting fixed in this life time.

Cheers, Kai 🙂 Thanks for always making a new track through the wild wild country that whmcs is. xx

Just got the confirmation that this problem is finally getting fixed in upcoming 8.4 release. I am glad we reported it over 2 years ago and followed up on it. Cheers 🍻

That's so true, my friend. We're using Hexonet. This issue was raised with WHMCS over TWO YEARS AGO. I don't think I'll be able to run a serious business with WHMCS in this lifetime. ☹️

It's been more than two years since we have been struggling with "premium domain transfers" and "pre-owned/afternic/sedo" domains on WHMCS. WHMCS has a bug when adding Premium Domain transfers into shopping cart as they just display the standard domain transfer price (and renewal price). As a result of pricing mismatch, the domain transfers don't work. In December 2019, WHMCS had created a #CORE-14055 bug case for this back as far as I know. Since then there hasn't been any resolution whatsoever. This also means we cannot also register 'premium domains'. I have already pulled my hair out over this and am wondering if anyone else has done the same.