Chazz Layne

Got it. I take it things were updated from 2.1.8 because 2.1.8 fails to check the mothership for updates? So if we pay to upgrade to 2.5.12 will it phone home and look for updates on it’s own, or would we still have to manually go find out if there are bug fixes? That would be a mandatory feature for us (and anyone who doesn’t want their time wasted).

Ah, I see @mayorchapstick, you’re stressed out keyboard cowboying makes perfect sense now. That must be absolute torture re-applying all the misguided modifications you made to core plugin coding on every single plugin you use every time an author releases an update. (You do know that’s how it works, right?)

Here’s another tip for you sport: start adopting best practices. You’ll find your life far less stressful, and your schedule will be free to run around trolling bad developers to your heart’s content.

LOL! Here’s a tip kiddo: trolling works better when you know the meaning of the words you’re using. Go look up the definitions of “hypocrite” and “script kiddie” then come back and give it another shot.

Since I’m here anyhow, if anyone’s looking for a quick band-aid because you’re busy and have bigger fish to fry, go check out Contact Form 7 – reCaptcha v2 by IQComputing (that’s how CF7 is still working on Layne Studio): https://www.ads-software.com/plugins/wpcf7-recaptcha/

Scratch that, the JS option is working now for us. We’re not cached with anything I can see in WordPress or on the server, but perhaps our host has something going on at the cloud level that caused a delay. After cloning the site over to a completely different host it was obvious.

@sidneyquitorio8 have you tried leaving it enabled with the JS option, and returning back to it after a couple hours?

Same troubles here, anxiously awaiting an answer as we have a launch date looming (and need this to be legal).

I’ve tried both plain and JS options, both with and without a redirect link, and using the Yes/No option answers of both “yes” and “no” are simply reloading the page. Of course, we’ve also tried clearing cache/cookies and using several different browsers/computers.

If it helps, hovering over either button reveals the link <our-url>/wp-admin/admin-post.php

Hi James, thanks for the quick response!

Unfortunately, your response (and reading of my post) were performed with the same sloppy, lazy, bug-ridden style we would expect from Woo circa 2015… ??

If you take a step back and actually read what I wrote in the OP, you’ll see that there are no issues with shortcode (which wasn’t even mentioned, nor present in the WP5 editor) and no problems at all with having all of the Wooness loaded up in a single block interface—quite the contrary in fact: the editor/block interface couldn’t be better and I’d hate to see that portion of the plugin change.

Quite literally the only thing wrong with the plugin that I could find was the incorrect CSS classes used and erroneous redundant DIV present in the output. I’ve corrected this myself to make the plugin actually usable, but of course my changes will be overwritten at the next update unless Woo gets this fixed first. Correct those two little items and you’d be golden.

…well that and enable the standard WP5 (Gutenberg) editor for products, it’s laughably absurd that you chose to disable it and have the audacity to claim Woo is “Gutenberg compatible”…but that’s a gripe for a separate plugin’s support forum.

Cheers!

Hey @fernashes it’s five months later, your customers are still losing THOUSANDS. Where the hell is our 3D Secure? It is completely irresponsible for you to be releasing and promoting such a flawed, dangerous product. I’m shocked Visa/MC haven’t shut you down and no one’s held you accountable yet. I sense a class action coming…

I didn’t run into any errors to fix.

The problem is actually caused by a bug in Scriptaculous, which has been fixed in a newer version. Head over to Script.aculo.us and download the latest version. Then, replace the relavent .js files included in Flickr Tag with the newer ones downloaded from Scriptaculous (which are: builder.js, effects.js, prototype.js and scriptaculous.js).

This should make your Flickr Tag fully functional again, including Lightbox support.