Title: kimu's Replies | WordPress.org --- # kimu [ ](https://wordpress.org/support/users/kimu/) * [Profile](https://wordpress.org/support/users/kimu/) * [Topics Started](https://wordpress.org/support/users/kimu/topics/) * [Replies Created](https://wordpress.org/support/users/kimu/replies/) * [Reviews Written](https://wordpress.org/support/users/kimu/reviews/) * [Topics Replied To](https://wordpress.org/support/users/kimu/replied-to/) * [Engagements](https://wordpress.org/support/users/kimu/engagements/) * [Favorites](https://wordpress.org/support/users/kimu/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 22 total) 1 [2](https://wordpress.org/support/users/kimu/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/kimu/replies/page/2/?output_format=md) * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[X-Currency - The Ultimate WooCommerce currency switcher for a smoother shopping experience] Does not work with products with variants and breaks conversion rounding](https://wordpress.org/support/topic/does-not-work-with-products-with-variants-and-breaks-conversion-rounding/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [10 months ago](https://wordpress.org/support/topic/does-not-work-with-products-with-variants-and-breaks-conversion-rounding/#post-18645285) * Hi, sorry, but I do not have time to follow up with this and for proper debugging I’d need to set up a staging environment which is not something I can do now. All I can say is that we use Elementor and WooPayments. The theme is a custom one, and we know for sure that the theme doesn’t do anything with prices or price conversions. * Further down the line, we discovered that the price rounding is broken in WooPayments. Honestly, not a surprise, WooPayments is full of issues, but this one in particular, we never noticed it until we installed your plugin. We cannot say if it was there before, but logically, after further investigation for that specific problem, everything seems to points to WooPayments and not your plugin for the price rounding issue. * Everything else, all the issuee with the variants, were caused by your plugin. We did tests with both WooPayments multi-currency activated and deactivated to be sure that the issue was not caused by a conflict between the two plugins and it wasn’t because it did not make any difference. As far as we know, nothing else (apart from WooCommerce itself), partecipate to the price definition/conversion. Removing from the equation what was caused by WooPayments, the main issues with your plugin were: 1. In case of a product with variants, if one of the variant had a discount, the price range in the lists were shown 3 times and apart from the original strikethrough price, the other prices ranges were all wrong. The middle one was hard to figure out and in the last one the price range did not include the price of the last variant. 2. Price ranges for variants did not include the price for the last variant. If the product had 5 variants, let’s say priced 1,2,3,4,5 USD respectively, the price range should have been 1-5 USD, but 1-4 USD was shown. 3. Once a variant was selected in the product page, regardless of the currency and the shipping address of the customer, the price shown was the price in the customer currency with the shop country taxes applied, instead of the customer shipping address taxes. The price range in the product page was correct, let’s say 10-20 USD, but the final price once the variant had been selected was 12.5 and 25 because of the shop location taxes applied (25% where we reside). * I hope it helps, we had high hopes for you plugin, because of one really annoying issue with WooPayments that prevent us from using the cache, Breeze is the one we use, but every other cache out there is affected in the same way. When we saw that your plugin was tested with Breeze, and we also verified that cookies were set based on the currency selection, we knew that we could finally enable the cache. WooPayments has not managed, in years, to do something as simple as setting up a cookie based on the currency selection. I know, it’s amazing, but that’s how it is. * That said, we are sorry to see that your plugin has other, more annoying issues which prevents us from using it. We hope you can manage to fix the issues with the variants, whatever you do it does not play nicely with the price handling for products with variants. One thing in particular stands out in this case, which is that despite the usage of Elementor, the “Add-To-Cart” widget used in the product page is provided by WooCommerce itself. There is nothing else in the mix. If that one shows a wrong price, it is quite evident that you do something that upset WooCommerce itself. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[MailPoet - Newsletters, Email Marketing, and Automation] Restrict autogenerated coupon to subscriber email](https://wordpress.org/support/topic/restrict-autogenerated-coupon-to-subscriber-email/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 4 months ago](https://wordpress.org/support/topic/restrict-autogenerated-coupon-to-subscriber-email/#post-18332206) * Thank you, nice addition! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WebP Express] Wrong srcset loaded](https://wordpress.org/support/topic/wrong-srcset-loaded/) * [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 6 months ago](https://wordpress.org/support/topic/wrong-srcset-loaded/#post-18220279) * Hi, I am not the developer of the plugin, but I thought to share my thoughts about your issue. * In the first two cases 603×900 and 201×300 it seems is is just an artifact of the image ratio. If the image is not square WP will generate the various sizes using only one of the sides as reference. In this case give than the ratio is the same your image looks like being 0.67×1, instead of 1×1.This is the expected result for images with ratio different than the expected one and this is also confirmed by the img sizes `width="201" height="300"`Webp-express only translate what it finds, meaning that those sizes are those generated by WP for the 900 ×900 and 300×300 image sizes. If you look in your upload folder you should see that those are the sizes as for the original jpeg/png image generated by WordPress. As for the srcset, my understanding is that all the available variations are added to srcset, regardless of the media and the browser will pick the most appropriate based on the viewport.Potentially, the optimisation to be made here is to ensure that on the mobile view the image with the right size is used in that context. I hope it helps. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce] Empty row added after each attribute in add_to_cart widget](https://wordpress.org/support/topic/empty-row-added-after-each-attribute-in-add_to_cart-widget/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 6 months ago](https://wordpress.org/support/topic/empty-row-added-after-each-attribute-in-add_to_cart-widget/#post-18206786) * Actually, I would argue whether if would make even more sense to give an option to remove it when `woocommerce_reset_variations_link` returns nothing, which gives users an option to remove the Clear button entirely. * In that case the code should be * ```wp-block-code ' . esc_html__( 'Clear', 'woocommerce' ) . '' ) ); if ( end( $attribute_keys ) === $attribute_name && ! empty($reset_variation_link)) : ?> ``` * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[MailPoet - Newsletters, Email Marketing, and Automation] Restrict autogenerated coupon to subscriber email](https://wordpress.org/support/topic/restrict-autogenerated-coupon-to-subscriber-email/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/restrict-autogenerated-coupon-to-subscriber-email/#post-18196713) * Hello, * We ended up doing exactly what you suggested, set the Usage Limit Per Coupon to 1. It’s a way to work around the issue, not ideal, but good enough for now. Let’s hope the developers would find it to be a nice addition then, thank you for forwarding it to them. Bye! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooPayments: Integrated WooCommerce Payments] Flags not showing in Multi-currency settings tab in admin area](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/#post-18177118) * Issue can be closed. FYI, emoji flags are not natively supported in Chromium on Windows machines [Add support for country flag emojis [40766658] – Chromium](https://issues.chromium.org/issues/40766658) Several solutions, like polyfills, custom font type etc exists. You provide one that works only for the backend, not the frontend. At the end I have found a plugin that was blocking your backend solution, the one pointing to [https://s.w.org/images/](https://s.w.org/images/). In the SSR I sent over to you there were 2 plugins listed over there that have an option to block that URL. For you interested, these are Breeze and ASE.Your plugin was falling back on the WordPress default CDN [`https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets`](https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets) which would just work if you just added `/svg/` before the name of the file.On the frontend, for the Currency Switcher Widget, if you provide any solution, it doesn’t seem to work. For that I had to install a polyfill which loads Twemoji as a font type and replace the unicode chars for the flag emoji in the switcher html select element. - This reply was modified 1 year, 7 months ago by [kimu](https://wordpress.org/support/users/kimu/). Reason: Provided more info for closing the ticket * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooPayments: Integrated WooCommerce Payments] Flags not showing in Multi-currency settings tab in admin area](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/#post-18176706) * Twemoji it’s the library you use for rendering these flags. If you are interested you can find more about it here [https://github.com/twitter/twemoji](https://github.com/twitter/twemoji). In particular, it looks like you are using this version [https://github.com/SebastianAigner/twemoji-amazing](https://github.com/SebastianAigner/twemoji-amazing) which, by default, uses [https://www.jsdelivr.com/](https://www.jsdelivr.com/) as CDN. Or maybe you are just using the core one with that CDN in your config, but it doesn’t matter. What is matters, is that the Twemoji library is included as part of WordPress core, you can find it here `wp-includes/js/twemoji.js`.If you read that file, you can see that this url [https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/](https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/) is set as base for the configuration used by WordPress. You can see this at line 26 and 27.// default assets url, by default will be jsDelivr CDNbase: ‘[https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/’](https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/’);, So, no, my host or my site, is not adding a CDN or replacing these urls in any shape or form. This all comes from WordPress and apparently WooPayments is using it. Instead, it looks like these URLs are replaced in your installation somehow. That is because apparently you are using a Proxy, which must have been set up by your organization by the look of it, to avoid hitting that CDN, probably some rate limiting issue, and that explains why you are seeing those flags. Your organisation, or the host you are using, has a mirror in place for the content served by that CDN.If you follow this URL [https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/ ](https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/) you can see that it takes you to a directory with two subfolders, 72×72 and svg. By default, Twemoji in WordPress is configured to use png 72×72 format, lines 29-37 of `wp-includes/js/twemoji.js`. * // default assets file extensions, by default ‘.png’ ext: ‘.png’, * // default assets/folder size, by default “72×72” // available via Twitter CDN: 72size: ’72×72′, * // default class name, by default ’emoji’ className: ’emoji’, * The html element used for the flags is * ```wp-block-code 🇪🇺 ``` * class emoji, that url used as base, all matches, but there is one problem. As mentioned before, there are two subfolders and you have decided to use the svg version. As such, you should prepend `/svg/` before the name of the svg image, otherwise the resulting URL is wrong. As I said before, I have no idea why the URL is correctly completed when browsing from a linux machine and why it is not when browsing from a Windows machine, but for that you need to look at your code, something in your logic is faulty and it is doing something wrong in that context. But you need to look at this from an installation where that Proxy [`https://s.w.org/images/`](https://s.w.org/images/) is not used. So you can see what the rest of us, your mere mortal customers, are seeing. In conclusion, I am not contiuing this conversation, unless someone steps in and start looking at this issue properly instead of keep trying to bounce the problem back and try to make it look as if it was a configuration issue on my end. I was just trying to help you guys, but I have better things to do in my life than spending all this time digging out information that you, as the support for this plugin, should know better than me. As show in this reply, that URL, that library it is all part of WordPress, and nothing of it comes from me, my host, my site or what else, but on the other hand you are trying to look at this issue from an installation which is obviously not standard, where things are different than the ones you provide to your customers. Because we are not all in the same place, it is quite obvious that this discussion will lead to nothing and I think I have spent already enough time looking at it. I am sure that I can live without those flags, so please, keep your bug as it is. With all that said, I wish you all the best. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooPayments: Integrated WooCommerce Payments] Flags not showing in Multi-currency settings tab in admin area](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/#post-18171802) * Hello, * Sandbox Mode can be enabled only on a website sitting on a publicly accessible server apparently. It does not look like I can do it on an installation in “localhost”. * This error is returned when I try to enable Sandbox Mode. —There was a problem connecting your store to WordPress.com: “The Jetpack server was unable to communicate with your site [https://wp-template-shop.ddev.site/](https://wp-template-shop.ddev.site/)[ IXR -32300: transport error: http_request_failed cURL error 7: Failed to connect to wp-template-shop.ddev.site port 443 after 7 ms: Could not connect to server]” * — If you were asking it to yourself, yes, I have an internal Certificate Authority and DNS resolver. * I have a staging installation for the website were this behaviour is observed on a public domain, but it is deployed in the same physical server were the production installation reside, so that won’t make any difference, as you think this is a server configuration issue. Personally, I do not think this is the case, because we can observe the same issue in production and in our “localhost” installations. If this was a configuration issue, it has to be at the application level, which means that somehow is either an issue with WooPayments itself, or another plugin is affecting WooPayments. What sounds weird to me is that some other plugin could affect the admin page of WooPayments. If this issue was only seen in the frontend with the currency switcher widget, it would more reasonable.Of all plugins we have installed I cannot think of anything that could mess up with the WooPayments admin page as nothing extends or manipulates that part. The only plugins I can think of are the various caching layers, but it’s unlikely and it would be temporary. * Regarding the SSR, I can not remove it. Apparently, the window of time to edit the message has expired. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooPayments: Integrated WooCommerce Payments] Flags not showing in Multi-currency settings tab in admin area](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/#post-18169408) * Hello, We already have a development installation in “localhost” and it behaves in the same way in that environment too. I cannot create a blank WP site with WooCommerce to check this issue, because multi currency can be enabled only when WooPayments is activated and configured through the payment providers. I am not going to create a new configuration with the payment provider for a test website. You can find here the status report, please confirm when you have read it as I would like to remove it from here. * ```wp-block-code ### WordPress Environment ###WordPress address (URL): https://www.simonadauria.comSite address (URL): https://www.simonadauria.comWC Version: 9.4.2Legacy REST API Package Version: ✔ 1.0.4Action Scheduler Version: ✔ 3.8.2Log Directory Writable: ✔WP Version: 6.7.1WP Multisite: –WP Memory Limit: 896 MBWP Debug Mode: –WP Cron: ✔Language: en_USExternal object cache: ✔### Server Environment ###Server Info: Apache/2.4.62 (Debian)PHP Version: 8.1.30PHP Post Max Size: 50 MBPHP Time Limit: 60PHP Max Input Vars: 2500cURL Version: 7.74.0OpenSSL/1.1.1wSUHOSIN Installed: –MySQL Version: 10.5.27-MariaDB-deb11-logMax Upload Size: 50 MBDefault Timezone is UTC: ✔fsockopen/cURL: ✔SoapClient: ✔DOMDocument: ✔GZip: ✔Multibyte String: ✔Remote Post: ✔Remote Get: ✔### Database ###WC Database Version: 9.4.2WC Database Prefix: wp_Total Database Size: 120.79MBDatabase Data Size: 96.58MBDatabase Index Size: 24.21MBwp_woocommerce_sessions: Data: 0.08MB + Index: 0.02MB + Engine InnoDBwp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDBwp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDBwp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_actionscheduler_actions: Data: 8.02MB + Index: 8.81MB + Engine InnoDBwp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_actionscheduler_logs: Data: 5.02MB + Index: 5.03MB + Engine InnoDBwp_addonlibrary_addons: Data: 4.52MB + Index: 0.00MB + Engine InnoDBwp_addonlibrary_categories: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_asenha_failed_logins: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_cmplz_cookiebanners: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_cmplz_cookies: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_cmplz_dnsmpd: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_cmplz_services: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_comments: Data: 0.02MB + Index: 0.09MB + Engine InnoDBwp_e_events: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_e_notes: Data: 0.02MB + Index: 0.17MB + Engine InnoDBwp_e_notes_users_relations: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_e_submissions: Data: 0.02MB + Index: 0.27MB + Engine InnoDBwp_e_submissions_actions_log: Data: 0.02MB + Index: 0.11MB + Engine InnoDBwp_e_submissions_values: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_gla_attribute_mapping_rules: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_gla_budget_recommendations: Data: 0.19MB + Index: 0.14MB + Engine InnoDBwp_gla_merchant_issues: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_gla_shipping_rates: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_gla_shipping_times: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_jetpack_sync_queue: Data: 0.02MB + Index: 0.06MB + Engine InnoDBwp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_automations: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_mailpoet_automation_runs: Data: 0.02MB + Index: 0.08MB + Engine InnoDBwp_mailpoet_automation_run_logs: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_mailpoet_automation_run_subjects: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_mailpoet_automation_triggers: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_mailpoet_automation_versions: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_custom_fields: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_dynamic_segment_filters: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_feature_flags: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_forms: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_mailpoet_log: Data: 0.05MB + Index: 0.00MB + Engine InnoDBwp_mailpoet_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_newsletters: Data: 0.05MB + Index: 0.05MB + Engine InnoDBwp_mailpoet_newsletter_links: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_mailpoet_newsletter_option: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_newsletter_option_fields: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_newsletter_posts: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_newsletter_segment: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_newsletter_templates: Data: 2.47MB + Index: 0.00MB + Engine InnoDBwp_mailpoet_scheduled_tasks: Data: 0.39MB + Index: 0.31MB + Engine InnoDBwp_mailpoet_scheduled_task_subscribers: Data: 0.06MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_segments: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_mailpoet_sending_queues: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_mailpoet_settings: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_statistics_bounces: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_mailpoet_statistics_clicks: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_mailpoet_statistics_forms: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_statistics_newsletters: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_mailpoet_statistics_opens: Data: 0.02MB + Index: 0.08MB + Engine InnoDBwp_mailpoet_statistics_unsubscribes: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_mailpoet_statistics_woocommerce_purchases: Data: 0.02MB + Index: 0.08MB + Engine InnoDBwp_mailpoet_stats_notifications: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_mailpoet_subscribers: Data: 0.02MB + Index: 0.23MB + Engine InnoDBwp_mailpoet_subscriber_custom_field: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_subscriber_ips: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_subscriber_segment: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_mailpoet_subscriber_tag: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_mailpoet_tags: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_user_agents: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_mailpoet_user_flags: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_options: Data: 8.05MB + Index: 0.13MB + Engine InnoDBwp_postmeta: Data: 33.19MB + Index: 4.70MB + Engine InnoDBwp_posts: Data: 31.39MB + Index: 0.70MB + Engine InnoDBwp_rank_math_404_logs: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_rank_math_analytics_gsc: Data: 0.02MB + Index: 0.06MB + Engine InnoDBwp_rank_math_analytics_inspections: Data: 0.11MB + Index: 0.11MB + Engine InnoDBwp_rank_math_analytics_objects: Data: 0.09MB + Index: 0.05MB + Engine InnoDBwp_rank_math_internal_links: Data: 0.05MB + Index: 0.03MB + Engine InnoDBwp_rank_math_internal_meta: Data: 0.06MB + Index: 0.00MB + Engine InnoDBwp_termmeta: Data: 0.08MB + Index: 0.08MB + Engine InnoDBwp_terms: Data: 0.08MB + Index: 0.09MB + Engine InnoDBwp_term_relationships: Data: 0.14MB + Index: 0.09MB + Engine InnoDBwp_term_taxonomy: Data: 0.09MB + Index: 0.11MB + Engine InnoDBwp_usermeta: Data: 0.23MB + Index: 0.03MB + Engine InnoDBwp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDBwp_wc_admin_note_actions: Data: 0.05MB + Index: 0.02MB + Engine InnoDBwp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDBwp_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDBwp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDBwp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDBwp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDBwp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_wc_product_meta_lookup: Data: 0.22MB + Index: 0.47MB + Engine InnoDBwp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDBwp_wpc_accesslocks: Data: 0.02MB + Index: 0.00MB + Engine InnoDBwp_wpc_login_fails: Data: 0.02MB + Index: 0.00MB + Engine InnoDB### Post Type Counts ###acf-field: 14acf-field-group: 4acf-post-type: 3attachment: 791elementor_library: 40mailpoet_page: 1nav_menu_item: 16oembed_cache: 3page: 15portfolio-collection: 5portfolio-gallery: 13portfolio-image: 272post: 28product: 112product_variation: 758revision: 1695shop_order: 2test: 1wp_global_styles: 1wp_navigation: 1wp_template: 2wpr_mega_menu: 1### Security ###Secure connection (HTTPS): ✔Hide errors from visitors: ✔### Active Plugins (31) ###Addendum Elements for Elementor (Premium): by Patrick Polloni – 0.0.1Admin and Site Enhancements (ASE): by wpase.com – 7.5.3Advanced Custom Fields PRO: by WP Engine – 6.3.11Advanced Elements: by Goose Studio – 1.12.4-beta.4Advanced Google reCAPTCHA: by WebFactory Ltd – 1.25Breeze: by Cloudways – 2.1.19Complianz | GDPR/CCPA Cookie Consent: by Really Simple Plugins – 7.1.5Dynamic Visibility for Elementor: by Dynamic.ooo – 5.0.14DynamicConditions: by RTO GmbH – 1.7.4Elementor Pro: by Elementor.com – 3.25.4Elementor: by Elementor.com – 3.25.9Gelato Integration for WooCommerce: by Gelato – 1.3.0Google for WooCommerce: by WooCommerce – 2.8.7HappyFiles Pro: by Codeer – 1.8.3MailPoet: by MailPoet – 5.4.0Object Cache Pro: by Rhubarb Group – 1.21.3Pinterest for WooCommerce: by WooCommerce – 1.4.12Rank Math SEO: by Rank Math SEO – 1.0.232Speculative Loading: by WordPress Performance Team – 1.3.1TikTok: by TikTok – 1.2.10Unlimited Elements for Elementor (Premium): by Unlimited Elements – 1.5.129Country Based Restrictions for WooCommerce: by zorem – 3.6.8Additional Variation Images Gallery for WooCommerce: by Emran Ahmed – 1.3.25Variation Swatches for WooCommerce: by Emran Ahmed – 2.1.2WooCommerce Legacy REST API: by WooCommerce – 1.0.4WooPayments: by WooCommerce – 8.5.1WooCommerce Shipping & Tax: by WooCommerce – 2.8.3WooCommerce: by Automattic – 9.4.2WP 2FA - Two-factor authentication for WordPress: by Melapress – 2.8.0WPS Hide Login: by WPServeurNicolasKulkawpformation – 1.9.17.1WPS Limit Login: by WPServeurNicolasKulkawpformation – 1.5.9.1### Inactive Plugins (1) ###Jetpack Social: by Automattic - Jetpack Social team – 5.5.1### Dropin Plugins () ###advanced-cache.php: advanced-cache.phpobject-cache.php: Object Cache Pro (Drop-in)### Settings ###Legacy API Enabled: ✔Force SSL: –Currency: EUR (€)Currency Position: right_spaceThousand Separator:Decimal Separator: ,Number of Decimals: 2Taxonomies: Product Types: external (external)grouped (grouped)simple (simple)variable (variable)Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)exclude-from-search (exclude-from-search)featured (featured)outofstock (outofstock)rated-1 (rated-1)rated-2 (rated-2)rated-3 (rated-3)rated-4 (rated-4)rated-5 (rated-5)Connected to WooCommerce.com: –Enforce Approved Product Download Directories: ✔HPOS feature enabled: –Order datastore: WC_Order_Data_Store_CPTHPOS data sync enabled: –### Logging ###Enabled: ✔Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2Retention period: 30 daysLevel threshold: –Log directory size: 15 MB### WC Pages ###Shop base: #8 - /shop/Cart: #9 - /cart/ -  Contains the woocommerce/cart blockCheckout: #10 - /checkout/ -  Contains the woocommerce/checkout blockMy account: #11 - /my-account/Terms and conditions: #174 - /terms-conditions/### Theme ###Name: Simona DauriaVersion: 1.0.4Author URL:Child Theme: ✔Parent Theme Name: Hello ElementorParent Theme Version: 3.1.1Parent Theme Author URL: https://elementor.com/?utm_source=wp-themes&utm_campaign=author-uri&utm_medium=wp-dashWooCommerce Support: ✔### Templates ###Overrides: /wp-content/plugins/woo-variation-gallery/templates/product-images.php/wp-content/plugins/woo-variation-gallery/templates/product-thumbnails.php### WooPayments ###Version: 8.5.1Connected to WPCOM: YesWPCOM Blog ID: 234729704Account ID: acct_1Q9r3dFgNgEhVvGjPayment Gateway: EnabledTest Mode: DisabledEnabled APMs: cardWooPay: Not eligibleApple Pay / Google Pay: Enabled (product,cart,checkout)Fraud Protection Level: basicMulti-currency: EnabledAuth and Capture: EnabledDocuments: EnabledLogging: Disabled### MailPoet ###Sending Method: MailPoetSend all site's emails with: Current sending methodTask Scheduler method: Action SchedulerCron ping URL: https://www.simonadauria.com?mailpoet_router&endpoint=cron_daemon&action=ping### Admin ###Enabled Features: activity-panelsanalyticsproduct-block-editorcouponscore-profilercustomize-storecustomer-effort-score-tracksimport-products-taskexperimental-fashion-sample-productsshipping-smart-defaultsshipping-setting-tourhomescreenmarketingmobile-app-bannernavigationonboardingonboarding-taskspattern-toolkit-full-composabilityproduct-custom-fieldsremote-inbox-notificationsremote-free-extensionspayment-gateway-suggestionsprintfulshipping-label-bannersubscriptionsstore-alertstransient-noticeswoo-mobile-welcomewc-pay-promotionwc-pay-welcome-pagelaunch-your-storeDisabled Features: product-data-viewsexperimental-blocksminified-jsproduct-pre-publish-modalsettingsasync-product-editor-category-fieldproduct-editor-template-systemblueprintreactify-classic-payments-settingsuse-wp-horizonDaily Cron: ✔ Next scheduled: 2024-11-29 16:03:09 +01:00Options: ✔Notes: 78Onboarding: completed### Action Scheduler ###Complete: 19,004Oldest: 2024-10-29 15:09:26 +0100Newest: 2024-11-29 15:05:40 +0100Failed: 667Oldest: 2023-12-31 00:18:09 +0100Newest: 2024-10-17 14:39:37 +0200Pending: 7Oldest: 2024-11-29 15:07:40 +0100Newest: 2024-12-03 12:01:24 +0100### Status report information ###Generated at: 2024-11-29 15:05:58 +01:00 ``` - This reply was modified 1 year, 7 months ago by [kimu](https://wordpress.org/support/users/kimu/). Reason: Status report not readable * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooPayments: Integrated WooCommerce Payments] Flags not showing in Multi-currency settings tab in admin area](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/#post-18167327) * Hello, I have installed an Ubuntu virtual machine to test it in a OS different than Windows and over there I can see what you can see. I cannot test it on a Apple device.For what I have been able to see so far, it seems to be affecting only Windows machines. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooPayments: Integrated WooCommerce Payments] Flags not showing in Multi-currency settings tab in admin area](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/#post-18167197) * Hello, I have opened that page in 4 browsers, and 2 different computers, both running Windows.The only browser where I see what you see is Firefox. Chrome, Edge and Opera, they all show what I see. That means that every Chromium based browser I have installed in my systems are affected by this issue.They are all at the latest version. I have tried to open the same page in a private instance of these browsers, with no extensions loaded and the issue remains. So, I would exclude that any browser extension could be the cause of this issue. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooPayments: Integrated WooCommerce Payments] Flags not showing in Multi-currency settings tab in admin area](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 7 months ago](https://wordpress.org/support/topic/flags-not-showing-in-multi-currency-settings-tab-in-admin-area/#post-18164670) * Hello, * I have a created a post on Imgur with all the images There are 4 images1. A screenshot of what I see on the currency admin page2. A screenshot of the code of the EUR currency in the table where you can see where that URL comes from.3. A screenshot of the first url pasted on a browser, which returns a 4044. A screenshot of the second url, with “/svg/” added, which works. * > [Multi Currency flags issue – WooPayments](https://imgur.com/a/r2JkUyo) * I am not sure that I understand how can you say that the URLS don’t work. Have you clicked on them? a) The URL have been taken from your own code. b) Both of them work, the first one, which is the one currently present in your code, will return a 404, the second one, which is the one I have corrected, takes you to the correct image, the EU flag in this case. You can see them in the 3rd and 4th screenshot respectively.I have noticed that in my first message the URL of the second link is still the same. Click on this one and you will see that it works [cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/1f1ea-1f1fa.svg](https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/1f1ea-1f1fa.svg) Also, the fact the original URL does not work, it the whole point of this ticket. That one, as shown in the screenshots, is taken directly from your code. Regarding the System Status Report.Before I share it with you here, is there a way to make this conversation private?I don’t think that is safe from a security standpoint to put so many details about my system here freely available to everyone, I am sure you can understand.In the report that are information that cannot become public. The only way for me to share it with you here is to redact it, but that could mean that I possibly remove information that might be useful for you.` - This reply was modified 1 year, 7 months ago by [kimu](https://wordpress.org/support/users/kimu/). Reason: Additional information on the URLs added * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Admin and Site Enhancements (ASE)] Email Address Obfuscator not working on Firefox](https://wordpress.org/support/topic/email-address-obfuscator-not-working-on-firefox/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 9 months ago](https://wordpress.org/support/topic/email-address-obfuscator-not-working-on-firefox/#post-18079675) * I have just found a page using Gutenberg instead of Elementor and the same issue was shown there as well, so that excludes Elementor from the list. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Admin and Site Enhancements (ASE)] Email Address Obfuscator not working on Firefox](https://wordpress.org/support/topic/email-address-obfuscator-not-working-on-firefox/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 9 months ago](https://wordpress.org/support/topic/email-address-obfuscator-not-working-on-firefox/#post-18079658) * I have spoken too early. After a few other changes to the website, plugin updates and other maintenance activities, the issue is back again. * I don’t know what it is, it could be Elementor itself, which has been very temperamental today on our website, maybe some of the cache layers or, maybe something else. Nothing makes sense though, because if it was one of the cache layers, every browser would be affected.I am not aware of any user-agent checks done by Elementor, although it is possible. The fact that only Firefox is affected, makes it really hard to pinpoint it to a global behaviour/feature. What makes your plugin seeing a session in Firefox being a bot it’s bit of a mystery, but I wouldn’t be surprised if that was due to some of the security layers altering the request headers somehow. They look “regular” from the browser. Anyway, I cannot spend more time on this issue, otherwise I will try to understand if something changes in the server logs trying to find what is messing around with this 🙂For as much as this is a neat feature, it’s a nice-to-have more than a must, so for now I am going to disable it and put all the emails in clear on the website. Luckily enough they are exposed just in a few spots. If I find anything else, I will let you know. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Admin and Site Enhancements (ASE)] Email Address Obfuscator not working on Firefox](https://wordpress.org/support/topic/email-address-obfuscator-not-working-on-firefox/) * Thread Starter [kimu](https://wordpress.org/support/users/kimu/) * (@kimu) * [1 year, 9 months ago](https://wordpress.org/support/topic/email-address-obfuscator-not-working-on-firefox/#post-18079578) * I am not 100% sure yet, but I had a suspect about the WP Captcha plugin (aka Advanced Google reCAPTCHA) On top of dealing with Captcha it also has a Firewall feature which among other things offers to block bad bots.I already have something similar offered by my web provider, so it was no issue to disable it and that worked, but I had different responses on the development and production environments. Not surprisingly maybe, but still weird. * On the development environment, as soon as I deactivate the plugin the issue went away. In production that didn’t work. But disabling the Block Bad Bots option in the Firewall section did it. In Production, there are many layers of caches, so that might explain why it didn’t change it immediately, but again not 100% sure.When that feature is enabled, it adds a bunch of Rewrite conditions/ rules to the .htaccess file. I didn’t see anything related to Firefox or Mozilla in those rules, but somehow, it was, apparently, doing something that affected the Email Address Obfuscator.I will continue messing around with a few things, but for now it seems to be solved with this change I made to the setting of WP Captcha. Viewing 15 replies - 1 through 15 (of 22 total) 1 [2](https://wordpress.org/support/users/kimu/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/kimu/replies/page/2/?output_format=md)