squarecandy

Here is my heavy-handed temporary solution to match the heavy-handedness of ACF’s colspan=100. This is fine to apply to any taxonomy for which you don’t have any ACF usage on the taxonomy edit screen. My custom taxonomy is called series. You should replace your taxonomy ID as needed below.

function squarecandy_yikes_acf_taxonomy_sort_hotfix($post_id) {
	$screen = get_current_screen();
	if ( 'edit-series' == $screen->id && 'series' == $screen->taxonomy ) {
		wp_deregister_script('acf-input');
	}
}
add_action('current_screen', 'squarecandy_yikes_acf_taxonomy_sort_hotfix', 99);

This is still not really a good final resolution, but will allow you to use the YIKES reordering plugin and ACF successfully at the same time for now.

+100!!!

This is saving me from having to transition dozens of sites to a completely different plugin.

Leave a 3 star review and then ask for help… not the best way to do it, my friend.

@dukeo – don’t worry, you don’t need to update your own privacy policy to notify users. Google has placed a convenient and beautiful badge in the corner of all of your web pages now with a link to their terms!

@locascioa – Your article that you linked to is really comprehensive and awesome!

Thanks for the tip that we can just use
https://www.ads-software.com/plugins/advanced-nocaptcha-recaptcha/
and disable the CAPTCHA feature provided by CF7 if we want to keep v2.

I know you’re now advocating for people to switch to v3 with 5.1.1, but it’s good to have options.

But new v3 keys must be created on https://www.google.com/recaptcha/admin for every domain and then installed in the plugin settings, right? That’s a ton of work. Discontinuing support existing v2 keys instantly on upgrade to the version that uses v3 seems like a bad approach. A separate setting for v3 and support for both would be so much better, allowing users to keep the plugin updated but make the switch to v3 when they have time and inclination to do so.

“We agree that the badge is obstrusive, but that can be removed by adding some additional styling.”

It’s against Google’s TOS to hide the badge with CSS. You can do it, but it’s technically illegal. The badge that’s inline with the form is not the prettiest, but at least it is a relatively positioned element that only shows on the form pages.

“We can even trigger a SPAM block by using autofill on all the form fields.”

Lots of real users use autofill for their contact info.

@claitonlord – obviously always backup first, because you never know… but, no you shouldn’t loose any forms, but you’ll need to re-enter the v2 keys if you switched to v3 keys.

I used https://www.ads-software.com/plugins/wp-rollback/ to roll back the version, which worked great.

Yep, I’m back on 5.0.5 until further notice.

I totally agree with Dave’s points here.

– Need continued v2 support

– If users opt to use v3, make sure the banner only displays on pages with forms. Showing that giant badge on every page is unacceptable.

Cool – yes I just submitted a ticket that said pretty much that exact thing and points them to this thread.

Thanks so much for looking into this, Kevin.
Is the ticket w/ ACF on the public support forum? If so, could you link to it here?

I can also open a private support ticket with my ACF pro account which might get faster attention.

Hi Kevin –

Thanks for the reply.

Yes, I went ahead and tested it w/ the free version of ACF and I’m seeing the same result.

I ran a diff of the default post categories page with and without ACF turned on:
https://gist.github.com/squarecandy/5c06b4e574abfc637d67d04e01086c78

Looks like it’s probably a conflict with how jquery ui sortable is handled/loaded… but I’m not sure.

Let me know what you find out and if I can be helpful in any way.

Thanks,
Peter

WooCommerce > Settings > Products > Product Fees

Setting “Fee Tax Class” to “No Taxes for Fees” did not work for me.

Setting it to the “Zero Rate” tax class did work.

It might be worth posting an update at the top of the description. If you search for “Classic Editor” this comes up in the #2 spot and starts w/ the description about the things C.E. doesn’t do…

This technique still works great for me. With watching out for a few “gottchas” and a few code modifications I got it working even better.

First – make sure that you are using a recaptcha key specifically for invisible type – a key for a regular v2 “i’m not a robot” box will not work. Generate a new key at https://www.google.com/recaptcha/admin if you need to.

Second, I didn’t like that the code above did a full browser-level submit of the form. I prefer the nice AJAX that’s built in to WPCF7. Here’s the javascript code I ended up using:

// implement the invisible google recaptcha
var recaptchaSubmitCallback = function( token ) {
	document.querySelector( '.g-recaptcha-response' ).value = token;
	form = jQuery( '#thesubmit' ).closest('form');
	wpcf7.submit(form);
};

jQuery( '#thesubmit' ).closest('form').on('submit', function(e) {
	e.preventDefault();
	grecaptcha.execute(0);
} );

And lastly – I didn’t like the fixed position badge, so I put it inline with the form like this:

    .grecaptcha-badge {
      width: 100% !important;
      height: auto !important;
      position: relative !important;
      box-shadow: none !important;
      right: auto !important;
      bottom: auto !important;
    }
    div.grecaptcha-badge:hover {
      right: auto !important;
    }
    .grecaptcha-logo {
      display: block;
      overflow: hidden;
      width: 256px;
      height: 60px;
      margin: -22px auto 0;
      box-shadow: none;
      transform: scale(0.6);
      opacity: 0.6;
      transition: opacity 300ms;
    }
    .grecaptcha-logo:hover {
      opacity: 1;
    }

Also – Here’s the shortcode I’m using in the WPCF7 form settings:

[recaptcha size:invisible callback:recaptchaSubmitCallback] [submit id:thesubmit "SEND"]

Hope this helps someone!