Woocommerce archive (shop) error since Theme Pro update to 6.0.1

[tristup]

Hi @nblund,

I have seen that the mentioned layout is under the Single. I am not sure whether it has been created with WooCommerce Archive or just the Single type of layout in the previous version, or it is showing under the single in the updated version even though has been created as WooCommerce Archive. I have created a WooCommerce Archive and tested it by assigning it to the Shop and it worked perfectly fine. If that does not help, please elaborate on the matter a bit to understand the problem.

Thanks

[nblund]

I know it sounds weird, but before the upgrade there was a woocommerce archive layout named: Deamo layout product archive (shop). After the upgrade, there is still a layout named Deamo layout product archive (shop), but now that is a singles layout and the content of the layout has changed. Is there anyway I can recover the layout prior to upgrade?

[ruenel]

Hey @nblund,

There is a known issue in Pro 6.0.1 version. We recommend that you update the theme to Pro 6.0.2 version which is available now.

Kindly let us know how it goes.

[nblund]

Hi @ruenel,

So I updated to 6.0.2 but apparently nothing has changed. I have now checked multiple layouts and it seems to be a bigger problem with multiple layouts. (If you observe the layout name you would know how it was set up before the upgrade, and you would see how things have really been messed up). It would require quite some work to redo the layouts, so my question is: If I would chose a backup with the CS v5, then upgrade again but this time to 6.0.2, would the upgrade work well this time?

[christian]

Hey @nblund,

@nblund

If I would chose a backup with the CS v5, then upgrade again but this time to 6.0.2, would the upgrade work well this time?

We can’t guarantee it, but you can try it out.

Upon checking your Property Shop page, it’s using a WooCommerce Archive layout assigned to your Shop.

The Singe Layout cs5 one is empty so you can delete it.

If you need us to investigate further, revert your site to a working state and copy your live site to a staging environment. That way, we can see how your site looks before the issue you described happened. Please provide us the staging site URL once you’ve finished this.

If you don’t want to copy your live site to staging, please note that troubleshooting on your live site will disturb your website visitors.

Thanks.

[nblund]

Okay I think you should know that the upgrade brought with it numerous major errors. More than the ones above such as normal pages that now have a certain post layout. I will go ahead and use an old backup and go from there, so we can close this ticket.

Thanks.

[ruenel]

Hi @nblund,

Our developers are already looking into the issue. We are also glad that you reverted back to the previous stable version which is the Pro 5.1.5. What we can suggest is that you will need to create a staging site. The staging site is useful because you can always do the updates in the staging first. If it has issues and conflicts, we can do the troubleshooting in the staging area without disrupting the live site. Once everything is perfect, we can then proceed to update the live site. If you haven’t tried cloning a site for a staging area, this article would seem to help you much:

• How to Easily Create a Staging Site for WordPress (Step by Step) (wpbeginner.com)

And by the way, I checked your “Deamo layout Shop” WC Archive layout and I noticed that you have added a Looper Provider. Be advised that a WC Archive has already a WooCommerce loop and this loop will dynamically generate the product items. All you need to have is a Looper Consumer to display those returned product items. Having a Looper Provider in that layout will result to a conflict and will not display any products or display incorrect product items. In addition, the Pagination will not work on that page if you have added a Looper Provider.

Best Regards.

[nblund]

Thanks @ruenel, for mentioning the looper issue. My problem is that

1
I don’t know how to set up the terms (just below the page title) correctly without the looper. Can you explain that for me or point me to the right documentation, please?

2
In another website using Pro (see login credentials in secure note) I have successfully set up looper and consumer for terms and consumer only for products in the shop - which seems to work seamlessly with pagination - all within the same section. I have read the relevant Theme.co documentation multiple times, yet I can’t explain why it would work in that case but not in the case you have mentioned in the above? Can you?

Thanks.

[christian]

Hey @nblund,

Setting up or nesting a Looper Provder and Looper Consumer INSIDE a Looper Consumer works in Pro 5.1.5 but it’s confirmed that it doesn’t in Pro 6.0.2. Please downgrade your sites to Pro 5.1.5 for now.

Check out the screenshots below for the setup.

• The Looper Provider should be Current Post Terms > Product categories

• The Looper Consumer should contain Term Dynamic Content.
  

Hope that helps.

[Regnalf]

I can confirm this issue too, my problem is that the single site layout that should be the woocommerce archiv is empty!!

How did you revert the pro version to 5.1.5 without breaking the site?

And i can confirm that the issue is not only woocommerce related. I have a similar issue on another page where the blog archive layout is gone and appeared as a blank single layout.

[Regnalf]

I’ve investigate the issue further and found something!

The woocommerce archive layout is still there but the json code was invalid!!

I had a line that has custom css code inside and looks like this:

"text_content":"<h4 style="text-align: center">Contact</h4>",

The issue was that the " signs where not escaped with a backslash \ like \"
So the correct code should look like this:

"text_content":"<h4 style=\"text-align: center\">Contact</h4>",

After changing the false " signs the archive page come back!!!

And the same issue is in other layout archives. I hope this helps to find the right place in your pro code.

[nblund]

Well done @Regnalf. And agree, it is not just woocommerce related.

[Regnalf]

Thanks, I think this happened during the upgrade process. I’ve repaired the json code with this online editor https://jsoneditoronline.org
It tells you the line where the json is wrong.

I’m not checked this with new generated json in the cornerstone editor. But as far I can see there seems to be no issues yet.

I hope theme.co will find the related code lines to this.

[charlie]

Thanks for bringing this data to our attention. Was this an upgrade issue or when you edit text content? What was the element in question?

[nblund]

@charlie

In my case it was an upgrade issue. The issues named in the above were non-existent before upgrade to 6.0.1 and appeared immediately after the upgrade: Change of conditions, change of layout type (from archive to single for example), the 404 page issue, and maybe other issues. On one site I have downgraded to version 5 and awaiting issues to be solved.

Thanks for paying attention to this.

[Regnalf]

Yes it was an upgrade issue from 5 to 6. And it’s not only related to woocommerce. It happens to other layout as well. I think all that contain such custom changes like inline css styles that contains "

The Woocommerce shop looks good at the moment, and it seems that the issue is not present if you save the layout in the layout builder.

[christian]

Thank you for your feedback guys, we’ll try to replicate this issue and investigate furtther.

[nblund]

Thanks @Christian, let know if I can be of any help

[christian]

Thanks, @nblund, We’ll do.