PluginUs.Net - Business Tools for WooCommerce and WordPress

[realize your idea - make your dreams come true]

Support Forum

You need to log-in to create request (topic) to the support

Custom price format showing double currency code with grouped products

The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page please
If you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
kentb(@kentb)
6 Posts
Customers
October 22, 2020, 00:07

Hi, I have some grouped products, but as the cost is showing a range, the Custom price format is displaying two currency codes on the page.

$308.00 – $473.00 (USD) (USD)

When I remove the custom price format, no currency code is displayed.  The switcher seems to work fine, but just this display issue.

Any thoughts on how to remove one of these and only show once?

#1
Pablo Borysenco(@pavlo_borysenco)
34,196 Posts
October 22, 2020, 10:13

Hello

Please  drop  me  exact  link to  the  issue

#2
kentb(@kentb)
6 PostsTopic Author
Customers
October 22, 2020, 17:39

Here is the page with the issue. thanks

https://netonomy.com.au/product/io_modules1/

#3
Pablo Borysenco(@pavlo_borysenco)
34,196 Posts
October 23, 2020, 15:34

Hello

Try  in  file -  wp-content\plugins\woocommerce-currency-switcher\classes\woocs_after_33.php - delete/comment  this  code - https://c2n.me/49yi5IA.png

#4
kentb(@kentb)
6 PostsTopic Author
Customers
October 23, 2020, 22:59

Well done. Worked like a charm...

Will this fix be broken each time there is a new version of the plugin?

#5
Pablo Borysenco(@pavlo_borysenco)
34,196 Posts
October 26, 2020, 11:17

Hello

No! We will fix this in the next version.

#6