Flags not showing in Multi-currency settings tab in admin area

Resolved kimu
(@kimu)

4 months, 4 weeks ago

Currency flags are supposed to be visible in this page “wp-admin/admin.php?page=wc-settings&tab=wcpay_multi_currency” but they are not because the URL pointing to the CDN where the images are stored is wrong.

Current WooPayments version is 8.5.1, but this issue has been present in previous versions as well.

The URL of the flag image is pointing to a CDN. The flags are not visible because the URL is missing a part, “/svg/” before the resource name specifically.
For instance, the EU flag URL currently used is
https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/1f1ea-1f1fa.svg
The right one is
https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/1f1ea-1f1fa.svg

After “/assets/” and before the name of the resource, there should be “/svg/” resulting in “/assets/svg/resourcefile.svg”

I am not sure whether this is affecting also the Currency Switcher Widget, but flags are not visible there either. They are replaced by the 2 letter country code (ISO 3166-1 alpha-2), like us for USA, eu for Europe, etc.

Viewing 13 replies - 1 through 13 (of 13 total)

Plugin Support

Zubair Zahid (woo-hc)

(@doublezed2)

4 months, 4 weeks ago

Hello kimu,

Thank you for contacting WooCommerce support.

I checked the flags in the Multi-currency and they appear fine.
This is my test site running on the default environment.

Could you share a screenshot of the Multi-currency settings tab?

Also, share your site’s System Status Report.
You can find it via WooCommerce > Status.
Select Get system report and then Copy for support.

Lastly, where did you get these URLs?
These are not working.
https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/1f1ea-1f1fa.svg
https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/1f1ea-1f1fa.svg

Looking forward to your response. 🙂

Thread Starter

kimu

(@kimu)

4 months, 3 weeks ago

Hello,

I have a created a post on Imgur with all the images

There are 4 images
1. A screenshot of what I see on the currency admin page
2. 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 404
4. A screenshot of the second url, with “/svg/” added, which works.

Multi Currency flags issue – WooPayments

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

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 4 months, 3 weeks ago by kimu. Reason: Additional information on the URLs added

Plugin Support

Feten L. a11n

(@fetenlakhal)

4 months, 3 weeks ago

Hi there!

Thanks for your answer.

I have a created a post on Imgur with all the images

Thanks for the screenshots. You are not supposed to see a link there. Here is what I see on my side.

I am not sure that I understand how can you say that the URLS don’t work. Have you clicked on them?

Yes, and we understand what you see now. Which browser do you use? Is it the latest version?

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.

We totally understand that! Let’s see if the issue is related to the browser before coming back to the SSR 🙂

Thread Starter

kimu

(@kimu)

4 months, 3 weeks ago

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.

Thread Starter

kimu

(@kimu)

4 months, 3 weeks ago

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.

Plugin Support

Zubair Zahid (woo-hc)

(@doublezed2)

4 months, 3 weeks ago

Hello kimu,

Thank you for your reply.

My screenshots in the last message were from Google Chrome running on Windows 10.
I suspect this issue has something to do with the server configuration.

Do you have access to another server or local host where you can set up a blank WP site with WooCommerce and check this issue?

To help you further, I’d like to review your site’s System Status Report.
You can find it via WooCommerce > Status.
Select Get system report and then Copy for support.

Looking forward to your response. 🙂

Thread Starter

kimu

(@kimu)

4 months, 3 weeks ago

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.

### WordPress Environment ###

WordPress address (URL): https://www.simonadauria.com

Site address (URL): https://www.simonadauria.com

WC Version: 9.4.2

Legacy REST API Package Version: ✔ 1.0.4

Action Scheduler Version: ✔ 3.8.2

Log Directory Writable: ✔

WP Version: 6.7.1

WP Multisite: –

WP Memory Limit: 896 MB

WP Debug Mode: –

WP Cron: ✔

Language: en_US

External object cache: ✔

### Server Environment ###

Server Info: Apache/2.4.62 (Debian)

PHP Version: 8.1.30

PHP Post Max Size: 50 MB

PHP Time Limit: 60

PHP Max Input Vars: 2500

cURL Version: 7.74.0

OpenSSL/1.1.1w

SUHOSIN Installed: –

MySQL Version: 10.5.27-MariaDB-deb11-log

Max Upload Size: 50 MB

Default Timezone is UTC: ✔

fsockopen/cURL: ✔

SoapClient: ✔

DOMDocument: ✔

GZip: ✔

Multibyte String: ✔

Remote Post: ✔

Remote Get: ✔

### Database ###

WC Database Version: 9.4.2

WC Database Prefix: wp_

Total Database Size: 120.79MB

Database Data Size: 96.58MB

Database Index Size: 24.21MB

wp_woocommerce_sessions: Data: 0.08MB + Index: 0.02MB + Engine InnoDB

wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB

wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB

wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_actionscheduler_actions: Data: 8.02MB + Index: 8.81MB + Engine InnoDB

wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_actionscheduler_logs: Data: 5.02MB + Index: 5.03MB + Engine InnoDB

wp_addonlibrary_addons: Data: 4.52MB + Index: 0.00MB + Engine InnoDB

wp_addonlibrary_categories: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_asenha_failed_logins: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_cmplz_cookiebanners: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_cmplz_cookies: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_cmplz_dnsmpd: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_cmplz_services: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_comments: Data: 0.02MB + Index: 0.09MB + Engine InnoDB

wp_e_events: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_e_notes: Data: 0.02MB + Index: 0.17MB + Engine InnoDB

wp_e_notes_users_relations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_e_submissions: Data: 0.02MB + Index: 0.27MB + Engine InnoDB

wp_e_submissions_actions_log: Data: 0.02MB + Index: 0.11MB + Engine InnoDB

wp_e_submissions_values: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_gla_attribute_mapping_rules: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_gla_budget_recommendations: Data: 0.19MB + Index: 0.14MB + Engine InnoDB

wp_gla_merchant_issues: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_gla_shipping_rates: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_gla_shipping_times: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_jetpack_sync_queue: Data: 0.02MB + Index: 0.06MB + Engine InnoDB

wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_automations: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_mailpoet_automation_runs: Data: 0.02MB + Index: 0.08MB + Engine InnoDB

wp_mailpoet_automation_run_logs: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_mailpoet_automation_run_subjects: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_mailpoet_automation_triggers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_mailpoet_automation_versions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_custom_fields: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_dynamic_segment_filters: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_feature_flags: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_forms: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_mailpoet_log: Data: 0.05MB + Index: 0.00MB + Engine InnoDB

wp_mailpoet_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_newsletters: Data: 0.05MB + Index: 0.05MB + Engine InnoDB

wp_mailpoet_newsletter_links: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_mailpoet_newsletter_option: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_newsletter_option_fields: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_newsletter_posts: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_newsletter_segment: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_newsletter_templates: Data: 2.47MB + Index: 0.00MB + Engine InnoDB

wp_mailpoet_scheduled_tasks: Data: 0.39MB + Index: 0.31MB + Engine InnoDB

wp_mailpoet_scheduled_task_subscribers: Data: 0.06MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_segments: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_mailpoet_sending_queues: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_mailpoet_settings: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_statistics_bounces: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_mailpoet_statistics_clicks: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_mailpoet_statistics_forms: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_statistics_newsletters: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_mailpoet_statistics_opens: Data: 0.02MB + Index: 0.08MB + Engine InnoDB

wp_mailpoet_statistics_unsubscribes: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_mailpoet_statistics_woocommerce_purchases: Data: 0.02MB + Index: 0.08MB + Engine InnoDB

wp_mailpoet_stats_notifications: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_mailpoet_subscribers: Data: 0.02MB + Index: 0.23MB + Engine InnoDB

wp_mailpoet_subscriber_custom_field: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_subscriber_ips: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_subscriber_segment: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_mailpoet_subscriber_tag: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_mailpoet_tags: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_user_agents: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_mailpoet_user_flags: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_options: Data: 8.05MB + Index: 0.13MB + Engine InnoDB

wp_postmeta: Data: 33.19MB + Index: 4.70MB + Engine InnoDB

wp_posts: Data: 31.39MB + Index: 0.70MB + Engine InnoDB

wp_rank_math_404_logs: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_rank_math_analytics_gsc: Data: 0.02MB + Index: 0.06MB + Engine InnoDB

wp_rank_math_analytics_inspections: Data: 0.11MB + Index: 0.11MB + Engine InnoDB

wp_rank_math_analytics_objects: Data: 0.09MB + Index: 0.05MB + Engine InnoDB

wp_rank_math_internal_links: Data: 0.05MB + Index: 0.03MB + Engine InnoDB

wp_rank_math_internal_meta: Data: 0.06MB + Index: 0.00MB + Engine InnoDB

wp_termmeta: Data: 0.08MB + Index: 0.08MB + Engine InnoDB

wp_terms: Data: 0.08MB + Index: 0.09MB + Engine InnoDB

wp_term_relationships: Data: 0.14MB + Index: 0.09MB + Engine InnoDB

wp_term_taxonomy: Data: 0.09MB + Index: 0.11MB + Engine InnoDB

wp_usermeta: Data: 0.23MB + Index: 0.03MB + Engine InnoDB

wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB

wp_wc_admin_note_actions: Data: 0.05MB + Index: 0.02MB + Engine InnoDB

wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB

wp_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB

wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB

wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB

wp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_wc_product_meta_lookup: Data: 0.22MB + Index: 0.47MB + Engine InnoDB

wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

wp_wpc_accesslocks: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

wp_wpc_login_fails: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

### Post Type Counts ###

acf-field: 14

acf-field-group: 4

acf-post-type: 3

attachment: 791

elementor_library: 40

mailpoet_page: 1

nav_menu_item: 16

oembed_cache: 3

page: 15

portfolio-collection: 5

portfolio-gallery: 13

portfolio-image: 272

post: 28

product: 112

product_variation: 758

revision: 1695

shop_order: 2

test: 1

wp_global_styles: 1

wp_navigation: 1

wp_template: 2

wpr_mega_menu: 1

### Security ###

Secure connection (HTTPS): ✔

Hide errors from visitors: ✔

### Active Plugins (31) ###

Addendum Elements for Elementor (Premium): by Patrick Polloni – 0.0.1

Admin and Site Enhancements (ASE): by wpase.com – 7.5.3

Advanced Custom Fields PRO: by WP Engine – 6.3.11

Advanced Elements: by Goose Studio – 1.12.4-beta.4

Advanced Google reCAPTCHA: by WebFactory Ltd – 1.25

Breeze: by Cloudways – 2.1.19

Complianz | GDPR/CCPA Cookie Consent: by Really Simple Plugins – 7.1.5

Dynamic Visibility for Elementor: by Dynamic.ooo – 5.0.14

DynamicConditions: by RTO GmbH – 1.7.4

Elementor Pro: by Elementor.com – 3.25.4

Elementor: by Elementor.com – 3.25.9

Gelato Integration for WooCommerce: by Gelato – 1.3.0

Google for WooCommerce: by WooCommerce – 2.8.7

HappyFiles Pro: by Codeer – 1.8.3

MailPoet: by MailPoet – 5.4.0

Object Cache Pro: by Rhubarb Group – 1.21.3

Pinterest for WooCommerce: by WooCommerce – 1.4.12

Rank Math SEO: by Rank Math SEO – 1.0.232

Speculative Loading: by WordPress Performance Team – 1.3.1

TikTok: by TikTok – 1.2.10

Unlimited Elements for Elementor (Premium): by Unlimited Elements – 1.5.129

Country Based Restrictions for WooCommerce: by zorem – 3.6.8

Additional Variation Images Gallery for WooCommerce: by Emran Ahmed – 1.3.25

Variation Swatches for WooCommerce: by Emran Ahmed – 2.1.2

WooCommerce Legacy REST API: by WooCommerce – 1.0.4

WooPayments: by WooCommerce – 8.5.1

WooCommerce Shipping & Tax: by WooCommerce – 2.8.3

WooCommerce: by Automattic – 9.4.2

WP 2FA - Two-factor authentication for WordPress: by Melapress – 2.8.0

WPS Hide Login: by WPServeur

NicolasKulka

wpformation – 1.9.17.1

WPS Limit Login: by WPServeur

NicolasKulka

wpformation – 1.5.9.1

### Inactive Plugins (1) ###

Jetpack Social: by Automattic - Jetpack Social team – 5.5.1

### Dropin Plugins () ###

advanced-cache.php: advanced-cache.php

object-cache.php: Object Cache Pro (Drop-in)

### Settings ###

Legacy API Enabled: ✔

Force SSL: –

Currency: EUR (€)

Currency Position: right_space

Thousand Separator:

Decimal Separator: ,

Number of Decimals: 2

Taxonomies: 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_CPT

HPOS data sync enabled: –

### Logging ###

Enabled: ✔

Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2

Retention period: 30 days

Level threshold: –

Log directory size: 15 MB

### WC Pages ###

Shop base: #8 - /shop/

Cart: #9 - /cart/ -  Contains the woocommerce/cart block

Checkout: #10 - /checkout/ -  Contains the woocommerce/checkout block

My account: #11 - /my-account/

Terms and conditions: #174 - /terms-conditions/

### Theme ###

Name: Simona Dauria

Version: 1.0.4

Author URL:

Child Theme: ✔

Parent Theme Name: Hello Elementor

Parent Theme Version: 3.1.1

Parent Theme Author URL: https://elementor.com/?utm_source=wp-themes&utm_campaign=author-uri&utm_medium=wp-dash

WooCommerce 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.1

Connected to WPCOM: Yes

WPCOM Blog ID: 234729704

Account ID: acct_1Q9r3dFgNgEhVvGj

Payment Gateway: Enabled

Test Mode: Disabled

Enabled APMs: card

WooPay: Not eligible

Apple Pay / Google Pay: Enabled (product,cart,checkout)

Fraud Protection Level: basic

Multi-currency: Enabled

Auth and Capture: Enabled

Documents: Enabled

Logging: Disabled

### MailPoet ###

Sending Method: MailPoet

Send all site's emails with: Current sending method

Task Scheduler method: Action Scheduler

Cron ping URL: https://www.simonadauria.com?mailpoet_router&endpoint=cron_daemon&action=ping

### Admin ###

Enabled Features: activity-panels

analytics

product-block-editor

coupons

core-profiler

customize-store

customer-effort-score-tracks

import-products-task

experimental-fashion-sample-products

shipping-smart-defaults

shipping-setting-tour

homescreen

marketing

mobile-app-banner

navigation

onboarding

onboarding-tasks

pattern-toolkit-full-composability

product-custom-fields

remote-inbox-notifications

remote-free-extensions

payment-gateway-suggestions

printful

shipping-label-banner

subscriptions

store-alerts

transient-notices

woo-mobile-welcome

wc-pay-promotion

wc-pay-welcome-page

launch-your-store

Disabled Features: product-data-views

experimental-blocks

minified-js

product-pre-publish-modal

settings

async-product-editor-category-field

product-editor-template-system

blueprint

reactify-classic-payments-settings

use-wp-horizon

Daily Cron: ✔ Next scheduled: 2024-11-29 16:03:09 +01:00

Options: ✔

Notes: 78

Onboarding: completed

### Action Scheduler ###

Complete: 19,004

Oldest: 2024-10-29 15:09:26 +0100

Newest: 2024-11-29 15:05:40 +0100

Failed: 667

Oldest: 2023-12-31 00:18:09 +0100

Newest: 2024-10-17 14:39:37 +0200

Pending: 7

Oldest: 2024-11-29 15:07:40 +0100

Newest: 2024-12-03 12:01:24 +0100

### Status report information ###

Generated at: 2024-11-29 15:05:58 +01:00

This reply was modified 4 months, 3 weeks ago by kimu. Reason: Status report not readable

Plugin Support

Zubair Zahid (woo-hc)

(@doublezed2)

4 months, 3 weeks ago

Hello kimu,

Thank you for your reply.

I suggest using WooPayments’ Sandbox Mode on a new blank site.
This mode does not require additional configuration with the payment provider and allows for safe testing.

To ensure accurate results, please disable caching and security plugins during troubleshooting.
You may remove the SSR from the last message.

Looking forward to your response. 🙂

Thread Starter

kimu

(@kimu)

4 months, 3 weeks ago

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/ [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.

Plugin Support

Zubair Zahid (woo-hc)

(@doublezed2)

4 months, 3 weeks ago

Hello kimu,

Thank you for your reply.

Please note that your site is adding a CDN URL for the flag icons.
By default, there should not be CDN URLs as WooCommerce or WooPayments do not have them.

EU flag on your site:
https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/1f1ea-1f1fa.svg
EU flag on my site:
https://s.w.org/images/core/emoji/15.0.3/svg/1f1ea-1f1fa.svg

Could you contact your host and check if there is any CDN service enabled on the server side?
For comparison, you may create a test site at https://tastewp.com and check how that works.

Looking forward to your response. 🙂

Thread Starter

kimu

(@kimu)

4 months, 3 weeks ago

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.
In particular, it looks like you are using this version https://github.com/SebastianAigner/twemoji-amazing which, by default, uses 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/ 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 CDN
base: ‘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/ 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: 72
size: ’72×72′,

// default class name, by default ’emoji’
className: ’emoji’,

The html element used for the flags is

<img draggable="false" role="img" class="emoji" alt="🇪🇺" src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/1f1ea-1f1fa.svg">

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/ 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.

Thread Starter

kimu

(@kimu)

4 months, 3 weeks ago

Issue can be closed.

FYI, emoji flags are not natively supported in Chromium on Windows machines Add support for country flag emojis [40766658] – Chromium

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/.
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 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 4 months, 3 weeks ago by kimu. Reason: Provided more info for closing the ticket

Plugin Support

Zubair Zahid (woo-hc)

(@doublezed2)

4 months, 2 weeks ago

Hello kimu,

Thank you for your reply.

I appreciate your detailed account of the issue and the investigation steps you have taken.

I have tested this on my local host and a live staging site without any proxy but cannot reproduce this issue. Which suggests this issue is related to some configuration.

Having said that, I will ask my colleagues to check and verify if this issue appears on any of their sites.
If you find any new information, please share it with me.

Have a great day!

Viewing 13 replies - 1 through 13 (of 13 total)

You must be logged in to reply to this topic.