Jack Richardson

Hello @Mark,

Ok, we are waiting for your feedback.

Kind regards, Jack Richardson
The 8theme’s team

Hello @lukabp,

Could you please check it now? The issue occurred because the search was configured to include the product variation post type, which caused a conflict due to duplicate entries. We have excluded the “product variation” post type from the search results, and the results are now displayed correctly in both the AJAX search and the search results page.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @lukabp,

The issue occurs because there are two tab elements on your single product page that conflict with each other, as they share the same IDs for the description, reviews, and other tabs.

As a workaround, we have found a solution to activate the first tab opened in your Tabs Accordion widget (https://gyazo.com/9a8a4b710c7fe129de5c5ff6c22a4261) so that the script for the tabs will trigger the first tab in the original (horizontal) tabs to open by default (https://gyazo.com/30d7778eef7c341f56fa3066e29f8dfd).

Alternatively, you can remove the accordion tabs and use only one set of tabs per single product page. Please remember to clear the cache before checking the results.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @Ronny,

We have reviewed your request and found that everything is functioning correctly on our side (https://gyazo.com/6e9716468fe35a238fd7c9d9a0e0c33b). It appears that the issue may be related to caching on your website, as you are using a CDN and caching plugins. We kindly suggest clearing all caches and checking again. You may also contact your hosting provider to request a server cache flush.

If the issue persists after performing these steps, please provide us with detailed instructions to reproduce it on our side, as it is currently working properly for us.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @GreenLion,

We are pleased to hear that most things are functioning normally now. Regarding the outdated files, please note that the WooCommerce plugin was updated only about 20 hours ago (https://wordpress.org/plugins/woocommerce/). We are already working on implementation the compatibility in our next theme update, which will be released within the next few days (1–2 days). More information: https://www.8theme.com/documentation/xstore/theme-installation/theme-update/

The outdated files do not affect your website’s functionality, as the changes in those files are minor and involve only slight modifications to certain strings or data attributes in some tags.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @Mark,

Please check whether you have assigned the correct page in “WooCommerce → Settings → Advanced” that you created to be used as your customized WooCommerce checkout page.

We have tested your website but were unable to reproduce the issue (https://gyazo.com/968ffcdea9e98f58f1d7e25cd6337aae). Therefore, please provide us with detailed steps, screenshots, or a video demonstrating how to recreate the problem on our side. You can upload the video to a file-sharing service such as https://fex.net/ and share the download link with us.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @Jimmy Yip,

As we understand, you would like to modify the colors of the tags and the tag titles. If so, you can use the following custom CSS by navigating to “Search Widget → Advanced → Custom CSS” (https://gyazo.com/900931d2f6f5feb4c7e6848b9183213c).

Custom CSS:

selector .etheme-search-tags-title {
    color: red;
    text-transform: none;
}

selector .etheme-search-tags a {
    background: aliceblue;
    color: green;
}

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @Martin,

Unfortunately, it is only possible to reorder the tabs using CSS. If you would like us to temporarily modify the original file with our modules to comment them such tabs on the code side, please provide us with temporary wp-admin and FTP access, so the Layout will be displayed as first section on all widgets.

Please note that these changes are temporary and will be lost after a theme or plugin update. However, this can serve as a temporary solution during your development stage.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @John,

Over the past few months, approximately 5–7 versions of the WooCommerce plugin have been released (https://developer.woocommerce.com/changelog/), along with updates to other plugins that could potentially cause this issue. Therefore, we kindly asked you to test the current setup using the default theme to ensure accurate test results.

Thank you for your understanding and for respecting our support time.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @John,

Thank you for the information you have provided. Could you please check whether the issue persists when testing the same procedure with a default theme such as Storefront? Our theme does not automatically clear any cookies or cache on such pages, so the same issue may occur when using the default Storefront theme, as all script verifications and other configurations are managed by the WooCommerce plugin.

If you have a staging website, please recreate the test there using the default theme. If the issue occurs only with our XStore theme, we will investigate it in detail.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @Ronny,

According to the official Stripe plugin support, there was a known issue in versions 10.5.0 and 10.5.1, which has been resolved in version 10.5.2. Therefore, version 10.5.3 and later should not exhibit this behavior (topic -> https://wordpress.org/support/topic/versionerror-unsupported-on-version-clover-can-not-provide-apiversion-to-str/).

We have updated the plugin on your website to version 10.7.0, which includes the necessary fix. After testing on your website, the card is now displayed correctly (a video is attached in the private content).

Please check from your side, and if you still experience any issues, kindly provide us with a step-by-step guide so that we can reproduce the problem on our end.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @Andrei Andrei,

Is there a planned fix to render the carousel heading as static HTML, independent of JS initialization?
– We have not planned this yet, but we have added this task to our to-do list for future review.

Is there a way to render the announcement bar server-side to prevent the CLS 0.16 caused by JS injection?
– We did not fully understand your request regarding the “announcement bar.” Could you please provide some screenshots so that we can assist you further with this issue?

Which specific XStore JS files can you recommend deferring safely without breaking theme functionality?
– Each website uses different types of widgets. Since you are already using the LiteSpeed Cache plugin, it automatically defers the necessary scripts during page load. Without access to your WordPress admin panel, it is not possible to analyze the list of scripts, as all loaded scripts are cached and have modified names.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @GreenLion,

We have conducted tests on our local website using the latest version of WordPress, and everything is functioning correctly. It appears that the issues you are experiencing may be related to compatibility between the active plugins on your website and the current WordPress version.

Please provide us with temporary wp-admin and FTP access for your staging web-site in the private content section so that we can review the logs and identify the source of the issues.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @Jimmy Yip,

Please remove the unnecessary commas at the end of your options (https://prnt.sc/zT2vTDGhdhK4) that do not separate any words (https://gyazo.com/1865739b6c1a960072021330fc17a1dc). You will then see only the correctly separated words. Use commas solely to separate words. We hope you can resolve this issue on your side. Otherwise, we kindly ask you to provide temporary wp-admin access so that we can check it on your website.

Best regards,
Jack Richardson
The 8Theme’s Team

Hello @dano111222,

The issue is caused by the WordPress “srcset” attributes for images, which are calculated individually for each image. We have found a solution to disable the “srcset” attribute for your specific images by adding a custom PHP snippet to your “child-theme/functions.php” file:

add_filter( 'wp_calculate_image_srcset', 'etheme_child_remove_srcset_for_specific_image', 10, 5 );
function etheme_child_remove_srcset_for_specific_image( $sources, $size_array, $image_src, $image_meta, $attachment_id ) {
    if ( in_array($attachment_id, array(5769, 11806), true) ) {
        return false;
    }
    return $sources;	
}

You can find the IDs of your images in “Dashboard → Media → Edit Image” (https://prnt.sc/JyJNFXHt4WUZ).

The issue appears only on the frontend and in the editor (if the image is not newly set), because the attributes are attached to the image during page load. If you reselect the image, WordPress does not trigger the hooks to set the attribute for that image.

The frontend is now displaying correctly.

Best regards,
Jack Richardson
The 8Theme’s Team