AzeDK

@Code Sensei I found it here:

@brian! Can you share your plugin file? edit: I found it, thanks again Brian!

Added vote on both as well, we often get this request from customers.

Is it possible to setup notification rule condition where "contains" can be more than just 1 value ? Etc. can only get it working if only 1 value is added. Would be nice to make several OR contains, instead of having to make 1 rule per keyword. Example case: is looking for a list of keywords in ticket subjects.

It has not been working since first release, and still not working now. Its very frustrating, and misleading to be able to set the state field optional in WHMCS > System Settings > General Settings > Other > Optional Client Profile Fields, but the clientarea details pages and order pages still enforce the field as required for most countries. The only solution we found was to hardcode edit the inclusion of StatesDropdown.js in the /templates/twenty-one/clientareadetails.tpl file to the following (I suggest making your own Child Theme, to keep changes after WHMCS updates): <script type="text/javascript" src="{$BASE_PATH_JS}/StatesDropdown2.js"></script> And then copy the /assets/js/StatesDropdown.js file to StatesDropdown2.js and add our own country code "states": states['DK'] = ["","Hovedstaden","Sjælland","Nordjylland","Midtjylland","Syddanmark","end"]; Leaving the first option empty, for clients not wishing to bloat their invoice details with this unwanted state field. Please give some love for this feature request Allow State/Region Overrides

It has not been working since first release, and still not working now. Its very frustrating, and misleading to be able to set the state field optional in WHMCS > System Settings > General Settings > Other > Optional Client Profile Fields, but the clientarea details pages and order pages still enforce the field as required for most countries. The only solution we found was to hardcode edit the inclusion of StatesDropdown.js in the /templates/twenty-one/clientareadetails.tpl file to the following (I suggest making your own Child Theme, to keep changes after WHMCS updates): <script type="text/javascript" src="{$BASE_PATH_JS}/StatesDropdown2.js"></script> And then copy the /assets/js/StatesDropdown.js file to StatesDropdown2.js and add our own country code "states": states['DK'] = ["","Hovedstaden","Sjælland","Nordjylland","Midtjylland","Syddanmark","end"]; Leaving the first option empty, for clients not wishing to bloat their invoice details with this unwanted state field. Please give some love for this feature request Allow State/Region Overrides

Not sure how many have noticed, but in the latest makeover of requests.whmcs.com date and time has been removed, so you cant see how old a feature request is. Please put back the creation date, so we have a better chance of knowing if its a fresh idea or old idea, and if its worth supporting.

Works like a charm thanks 🙂

Yah, its a sidebar item though, so only way i know of fixing it, is removing it, and bulding a new one up from the ground. Thanks anyway 🙂

Can I get the solution as well, if you can find it again 🙂

Thanks Brian! I am in happy tears, its been an issue for me past 8+ years.

haha (sad laugh) Its worth a try, but knowing WHMCS past 10 years, my hopes are not high for this one.

@snake @akust0m @web2008 Please drop a vote for the feature request here: https://requests.whmcs.com/topic/prorata-billing-for-addons-2nd-try

@DennisHermannsen Its still an issue with latest WHMCS 8.1.13 and Twenty-One theme. Its a bug, and should not be a feature request. @WHMCS John Is it on a bug track list ? Reproduce problem: - set "State/Region" optionally in General Settings > Other "Optional Client Profile Fields" and remove all checkmarks from "Locked Client/User Profile Fields". - Go into /clientarea.php?action=details and set Country to "Denmark" and leave "State/Region" empty, and try save changes.

@tomb Did you ever solve your own issue with this?

@brian! They dont get charged for upgrading existing products, and this is why its confusing to customers, and causes extra support questions. Setup fee should only be visible when ordering new products. But I think in an older thread another company wanted specifically charge for setup fees during upgrades, and so John WHMCS added it back in many years ago. Could a hook target "upgradepackage.pricing" ? Then it should not affect regular pricing for new product pricing.

This is still an issue with latest theme in 2021. Now with the child theme feature, its possible to make your own upgrade.tpl file with modified pricing: {if $upgradepackage.pricing.monthly}<option value="monthly">{$upgradepackage.pricing.monthly}</option>{/if} {if $upgradepackage.pricing.quarterly}<option value="quarterly">{$upgradepackage.pricing.quarterly}</option>{/if} {if $upgradepackage.pricing.semiannually}<option value="semiannually">{$upgradepackage.pricing.semiannually}</option>{/if} {if $upgradepackage.pricing.annually}<option value="annually">{$upgradepackage.pricing.annually}</option>{/if} {if $upgradepackage.pricing.biennially}<option value="biennially">{$upgradepackage.pricing.biennially}</option>{/if} {if $upgradepackage.pricing.triennially}<option value="triennially">{$upgradepackage.pricing.triennially}</option>{/if} My guess is to change "{$upgradepackage.pricing.annually}" to a version without the setup fee included.

We had 1 case of this happening today as well, so its not solved yet sadly. Our issue was only related to WHMCS Invoice PDF attached to emails sent to the customer. Norton Life Lock claims there is a script attached.

Still not working in WHMCS 8

Thank you @Kian its perfect 🙂

@Kian if you get time, can you update your script to take into count "Guest" tickets ? They show up without <a href=""> tags inside the <small> tags. Its non-clients that make tickets. It breaks the loop array for me 🙂

Thank you very much @DennisHermannsen ! This has been driving me crazy for years 🙂

@WHMCS John will this also be included in the main ticket view? Credits to @Kian for the temp fix

Thanks @Kian works great :)!

@Kian Can you update it, so it works on flagged/assigned tickets too 🙂 ? It works if you look for both table#sortabletbl1 and table#sortabletbl2