Michael

I can confirm this is a bug as well. Broke on my website, need a fix immediately. Not custom code, default WordPress functionality is not beign supported. Woo Commerce is breaking our websites because they are not following the standards. How do we turn off the WooCommerce Taxonomy display when assign Taxonomies to Products?

Woo Commerce HAS to follow standards, and HAS to support taxonimes associated.

Here is a giant list of people you are hurting:
https://www.ads-software.com/search/custom+taxonomies+intext%3A%22Plugin%3A+WooCommerce%22/

• This reply was modified 10 months, 2 weeks ago by Michael.
• This reply was modified 10 months, 2 weeks ago by Michael.
• This reply was modified 10 months, 2 weeks ago by Michael.

Check the backgrounds, there is an image feature. You can then change it to cover, or other.

I appreciate your response, and I’ve now tried that. It didn’t help. Is there a class or ID that needs to remain on focus, or active for it to stay on? Is there a class I can add to the menu while I remain on the datalist, then remove when I leave? Is there a javascript function I can call to open the menu again, or an event I can block then re-add?

I also added this element to the WordPress menu, because I wanted this functionality on mobile. The mobile menu works. I’m wondering if its a CSS display property problem with the Astra theme. I’ve tried playing with this, setting some to blocks, but I cant get the menu to stay open.

I’m a capable developer, I will share all my results so you can fix this for all your users.

• This reply was modified 11 months ago by Michael.
• This reply was modified 11 months ago by Michael.

Also technically, when we filter based on one taxonomy page, we are duplicating that taxonomy page. So on content type with multiple taxonomies, we start getting duplicate content. Your filtered content, and the actual taxonomy. It makes it very hard to use this product.

I suspect nofollow is going to help.

I’m also seeing this. Its shutting down my website, as the bot just crawls. Whats more, it is compounded by WP-rockets Critical CSS and Preloading. The number of counts on the taxonomy tables start increasing, and the queries start delaying. Then the memory goes to upto 8gb. And eventually we get 20 second page loads.

This is a massive problem. And I had to disable your plugin entirely, as this just causes a huge issue on my website.

It happened again, this time with this selector in the CSS. What does

body .spectra-image-gallery__control-lightbox–main .swiper-slide {
display: none;
}

On both of them, all of the containers have a z-index of blank.

I will remove this review if the author responds. I may need to fix this myself, as I need a plugin like this.

Not sure why this is resolved. No answer.

Not sure why we got that warning, I provided an email and never asked for credentials.

I think we just need to add a transaction to the action, I was going to submit a patch if I got it working.

Though a patch could mess up other features. It would be nice if the delete_user was covered all under a single transaction.

• This reply was modified 1 year, 6 months ago by Michael.

I agree with you, Vortex.

Also, just to be more specific. There are reasons why most companies do not do this. I’d add that formidable may want to discuss this situation with their lawyers better. I can imagine a half dozen situations where they may find themselves legally liable for losses due to these types of policies. I also do not know of any other plugins that disable themselves.

I’m a fan of formidable, but I do have a few problems with software. I share this one.

• This reply was modified 1 year, 6 months ago by Michael.

https://prismjs.com/plugins/normalize-whitespace/

When I disable SiteKit, the file vanishes.

BTW, its almost certainly an issue with GDPR cookie notice and anchor ads.

Yep, the issue is that. Turning off Anchor ads is the only solution offered. Please fix this, and tell people who are complaining that the website isn’t working this. This issue is over 5 months old and not resolved. Its the EXACT issue as is in that article.