robaxxx

Thanks Aamir, very much appreciated.

Yes, my issue is the same as chris above. I also have a back in stock notifier from codewoogeek on the site and after the update of the variation swatches plugin, the notifier stopped working on products that had variations due to the swatches being unclickable as described by others.

It had worked all the way through until this update and I had not changed any settings since first setting it up a year or more ago.

But regardless I’ll check the setting you’re referencing… but note I downgraded to v1.0.10. The Disable out of Stock is grey (not orange) and everything works.

I can’t get on my server at the moment, but I’ll switch the new version in for a test when I get back on it.

I’m also having this issue.

When an item is out of stock, the swatches show as red X’s and don’t do anything when clicked.

When I revert back to the previous version. the swatches show the labels on them and then when clicked, the out of stock ones trigger Out of Stock to be displayed.

Not sure what else I can add to help find the issue.

Regards
Rob

Bloody hell… thanks for figuring this one out Pieter!
ROb

Great news, thanks Patrick
Rob

Thanks Patrick.

Yes, I can use CSS to hide labels, but I was looking for something more elegant, perhaps like is in a form I use for another CMS. In that one, each field has a selector to choose from the following:

• Auto
• Hidden
• Left
• Center
• Right

In that case, Auto means to use a default setting that applies to all fields. And Hidden of course means to hide it.

When I use CSS in Forminator (as I did last night) I have to deal with each label separately because the forminator-label selector removes them all, including on radio buttons and checkbox lists that don’t have placeholder text. I did it after I made the post, but as you can imagine it’s a bit of a job.

Anyhow, just a suggestion perhaps.

Thanks (I’ll close this)
Rob

Forget this one – I was seeing the default admin notification template, not the one I’d made.

Woops!

I was testing both your version and the Kadence one last night and this post was meant for that plugin. Yours does keep both addresses on the same column and I actually ended up using that.

I’ll mark this resolved and you can happily ignore it, thanks!
Rob

Ok yep cool.

I don’t mind setting up rules manually. Just so long as one is able to disable the cache in the plugin if needed and clear it on demand. From what you’re saying, I believe that will be the case.

Regards
Rob

Yes, everything is on offer. I’ll email you now as I understand some things can’t be done via the forum here.

Regards
ROb

Ok I’ve submitted that now via the paid support system there even though it happens just with the free Spectra.

The video shows exactly what I reported.

I’m really just reporting this issue. Not trying to get into a big support process with this one. I’m sure the devs will know what to do.

But does the plugin do that automatically like it does with the old rules system, or does it have to be done manually?

And if the plugin doesn’t manage those rules, then what happens when one disables and enables caching in the plugin.. does it turn all those rule off and back on again, or would one have to remove them all and add them again?

• This reply was modified 6 months, 1 week ago by robaxxx. Reason: spelling

Hi there

I’ve double-checked on mine here and I can record it happening as I described. Have you got a place or email where I can send you a link to a video of my screen?

Regards
Rob

Yes, wondering the same thing – Whether the replacement rules system is going to work with the plugin.

For isaumya to refer to, this is the relevant page about the change:

Page Rules migration guide · Cloudflare Rules docs

It looks like the new system should still work, but maybe the plugin can’t add them automatically.
Rob

Hey, thanks for looking at this.

I received screenshots of the DNS which is at Godaddy and sure enough, there were two sets of A records in it, one set pointing to that Cloudflare IP you mentioned and the other to my server.

So, the site was randomly hitting Cloudflare (and even being cached!) on different pages at different times.

I’ve told them to delete those records and leave only the correct ones.

The client has had 3 rebrands over the last decade and I suspect the Cloudflare records would have been imported from a previous domain and previous registrar.

Strange is that it worked when routed to the Cloudflare IP and was being cached. Maybe everyone can have free random caching just by pointing an A record there heh.

Thanks again for the comments here that helped.
Regards
ROb