[Resolved] Updated changed something

[Author]

Posts

[cristianR-3]

I am trying to: Display Parent Categories

Link to a page where the issue can be seen: hidden link

I expected to see: The Subcategories displayed on the top of the page before the divider

Instead, I got: Nothing displays.

[cristianR-3]

I was helped a while back to get my shop to show subcategories. It was working great right up to the point where I had to update the Toolset plugins. Then the whole thing broke. The shop page did not display anything at first. I had to change things around to get that back up, but as you can see the shop grid no longer displays the subcategories on the top of the page.

[Shane]

Hi Cristian,

I see the issue. However I believe this is a bug.

Would you mind if I took a copy of the site to have a further look?

Also In order to resolve the issue you can add the view contend directly to the view loop rather than using a content template in the view.

Looking forward to hearing from you.

Thanks,
Shane

[cristianR-3]

Yes, please make a copy of the site for you to troubleshoot. I also believe it's a bug since it was working and now it is not.

[cristianR-3]

Which view are you talking about? I can definitely change that if it fixes the issue.

[Shane]

The issue is on this view here hidden link

Just move the contents out of the content template, directly to the view loop.

Replace each instance of

[wpv-post-body view_template="loop-item-in-product-subcategory-views"]

with

<div class="category-box">
   <h3>[wpv-taxonomy-link]</h3>
  <div class="product-thumb"><a href="[wpv-taxonomy-url]"><img src="[wpv-woo-productcategory-images]"></a></div>
</div>

This should be a suitable workaround while I investigate the issue further with out team.

Thanks,
Shane

[cristianR-3]

This indeed fixed the issue. So the bug is in the way views bring in the content template? I will leave this issue as unresolved, so you can provide me feedback. But Shane, thank you once again. I would have not attempted this.

[Shane]

Escalated

[Shane]

Hi Cristian,

I can confirm that this has been resolved since our views 3.3 release.

If you are still experiencing the issue you are more than welcomed to get in touch again.

Thanks,
Shane