Hi Rose

It’s offline at the moment. I’ll get back to you on this in a day or two. It’s not a major problem, as I made the top header background colour the same as the main header’s background image colour, so it kind of fits already.

Robert

Thanks for checking Rose.

The development site was not working before but is now. The live site popup works sometimes. Not sure if there is a problem caused by Cloudflare or something else is going on with the theme, but it doesn’t;t always work.

I’ll try changing Cloudflare settings and investigate a bit more, but right now in Firefox the dev site works and the live doesn’t. They have the same settings for the Newsletter options.

Robert

OK, I have worked out that the problem in Firefox not allowing my Instagram images to be displayed was because of a Firefox extension called “Facebook Container”. As soon as I disabled this plugin, the Instagram images in Firefox were visible again.

Please kindly close this ticket.

Robert 🙂

Thanks Rose

Very strange… it started working on its own again. I did have someone visit the site from elsewhere, not sure if that triggered the thumbnails to be generated. But seems to be working now.

Please close ticket.

Robert

Sorry. I just checked one of my sites that uses the 8theme Instagram widget and builder elements. The images are not being displayed in either the Home Page or the 8theme – Instagram widget found in the sidebar on the blog page. Is there a current issue you know about? or maybe it’s just this site.

I reconnected the API and use the reinit feature. I also ran the Regenerate Thumbnails plugin tool. Not sure why the #images are not being displayed.

** Edit ** When I hover over the mouse where the image thumbnails should be, the background changes from white to grey and I see the like and chat icons that were not visible before.

Hi rose

OK, great!

Thanks for responding. Have a great day! 🙂

Robert

Hi Rose

When I look at the code for an ordinary page I see this:

.bc-type-left2 .breadcrumbs, .bc-type-left2 .woocommerce-breadcrumb, .bc-type-left2 .bbp-breadcrumb {
    display: inline-block;
    width: auto;
    margin-right: 0.285em;
}

When I look at the CSS code for Wishlist breadcrumbs, I see this:

.woocommerce-wishlist .page-heading .breadcrumbs, .woocommerce-account .page-heading .breadcrumbs, .woocommerce-wishlist .page-heading .back-history, .woocommerce-account .page-heading .back-history {
    display: none;
}

Should I change it to this maybe?

.woocommerce-wishlist .page-heading .breadcrumbs, .woocommerce-account .page-heading .breadcrumbs, .woocommerce-wishlist .page-heading .back-history, .woocommerce-account .page-heading .back-history {
    display: inline-block;
    width: auto;
    margin-right: 0.285em;
}

Robert

Thank you.

Hi again Rose

I am sorry, but I have done further investigation myself from the Google Chrome console.

Please see this screenshot: https://prnt.sc/r5zt4e

In the list of Javascript errors, when I hover over them, most of them relate to javascript from your core plugin, as the author of Epic News had told me.

https://theatrelife.co.uk/wpcontent/plugins/et-core-plugin/packages/kirki/controls/js/script.min.js

I strongly do not believe that the Epic News plugin is at fault here. The Javascript faults are directly connected to your Xstore Core plugin as was previously mentioned, and the URL of the Javascript indicates exactly where the errors are to be found.

Will you now pass this onto the developer to look at and provide a solution?

Robert

Hi Rose

Thanks.

I have passed on your message to the Epic News Theme author. However, he has already stated that it’s your Core plugin causing the JS errors and the customizer also works when Core is disabled. I will wait until Epic News author responds following your screenshots.

Robert

Along time ago, when I purchased XStore, I spoke with your colleagues in support and they said it was OK to change the folder name from xstore to what I wanted, by altering style.css. I use many different themes on behalf of clients, and it’s quite normal for web designers to use themes as base templates and change the theme folder name to hide the fact that a template has been used. It’s normal in the industry.
I have had no problem over the years I’ve used XStore up until recent updates. If the theme folder is the problem, then I can no longer buy XStore. I have over 8 licenses in my name and many others I had clients purchase. If I am forced to rename the folder name back to xstore for the site to function, then its the last one that I will be buying, and for this site, I will switch to another theme. It’s easy for me to replicate the look of the site with another theme.
I request that in a future update, you do not code your Core plugin that specifies the folder name as xstore. This problem is new due to updates you’ve made.

Please note, I have updated XStore to 6.2.11 and Core to 2.2.1, but still have a problem with customizer hanging.

Hello Hung The

Please see private area for credentials.

I have enabled the Under Construction plugin, so head straight to the login URL I included and copy and paste that. I suggest first seeing what happens when you open the customizer. It will hang with all plugins enabled. Disabling either the XStore Core or Epics News Elements plugin will allow the customiser to work. The JS errors come from the core though.

NB – Please do not post details of the site url in the public area. also post any screenshot links in private area too, thanks.

Robert

I’ve just updated the theme from I think 5.5.1 to 6.2.9, and updated core and ensured all required plugins are up to date. With my other sites, I did not have this big jump to 6.2.9 and was updating incrementally with those. With this site, I tried to enable header builder and it came up with errors in the header style section, something like 15 settings unknown.

I went back to the WP dashboard and tried to go back into theme options again, but it just hangs loading with the loading icon with no errors. Site broken.

Should I go back and update from 5.5.1 to 6.1 and then afterwards jump to 6.2.9? like the other sites I updated?

regards
Robert

Hi Olga

Thanks and understood. I’ll update custom css for now and remove the extra lines on the next theme update.

Many thanks 🙂
Robert