justinmaurerdotdev

To be clear, I don’t actually want to be using Post Type podcasting in this setup. It just is the only way I can get the metabox to appear.

In any case, I’ll submit a ticket, as you suggest. Thanks!

Awesome. Great work all around! ??

@gameryo, no problem.

I’ve just submitted a pull request that fixes the issue. If anyone is in an emergency situation, I’ve forked the plugin and you can use my fork here. I’ve set the main branch to version 1.0.6.1. If a 1.0.7 is published, it should automatically overwrite mine. I will plan to remove my fork as soon as the main plugin is updated.

The relevant code that actually fixes the issue change can be found here, in my PR. The entirety of the code is pulled from ACF’s own advanced-custom-fields-pro/includes/fields/class-acf-field-select.php file, in the ajax_query() method.

• This reply was modified 8 months, 2 weeks ago by justinmaurerdotdev.

Dang, I was hoping it wasn’t this plugin that was the issue. I’m having the same problem. I believe it’s related to the 6.3.2 ACF update. They have refactored A LOT about how AJAX fields work in ACF, and I’m pretty sure this plugin just hasn’t been updated to support the changes.

I may end up needing to fork this, and will try to reply here if I find a workaround.

Actually, looking at this more, this thread seems like the place to start. It’s likely an issue with the character encoding in the database being mismatched from what WP is sending. The solution will be to either A) convert the database to the expected encoding, or B) tell WordPress to expect a different encoding, and shim the post content with the above code.

https://github.com/WordPress/gutenberg/issues/19552#issuecomment-1758798993

I don’t have an environment to test this in, but this looks like a possible solution, from here: https://stackoverflow.com/a/75888275/2694371

Adding this code in functions.php fixed it for me:

add_filter( 'wp_insert_post_data', function( $data, $postarr ) {
if ( ! empty( $data['post_content'] ) ) {
    $data['post_content'] = wp_encode_emoji( $data['post_content'] );
}
return $data;
}, 99, 2 );

What was the result of your test when re-adding plugins? Were things working well after removing them?

The most likely cause I can think of, specific to this page, would be: If a plugin was programmed to check for plugin updates every time that page was loaded, and the URL that the plugin is looking for doesn’t exist, or is delayed, maybe the update check is timing out the whole page.

Do you have any plugins that might be looking for non-existent update sources, or ones that require authentication of some kind?

Also, 504s should produce some kind of error in the server (Nginx or Apache) or PHP logs. Do you have access?

• This reply was modified 9 months, 4 weeks ago by justinmaurerdotdev.
• This reply was modified 9 months, 4 weeks ago by justinmaurerdotdev.

I have this same issue. Query Monitor prevents WP Rocket from being able to handle the Clear Cache function. Are there any workarounds, besides disabling QM?

Saw the fix is in the new update. Thanks for the swift action!

I’d be happy to submit a pull request for the fix, but I haven’t been able to find a public repo for the plugin.

OMG thank you!!! I got so excited when I saw that changelog item, and realized that I hadn’t checked back here for updates. This is a huge win for our update process. ??

SELECT name, val, autoload
FROM wp_wfconfig
WHERE name = 'detectProxyRecommendation'	

SELECT *
FROM wp_yoast_indexable
WHERE object_id = '8192513'
AND object_type = 'post'
LIMIT 1

SELECT *
FROM wp_gf_form
WHERE id=20

SELECT *
FROM wp_gf_addon_feed
WHERE addon_slug='gravityformsauthorizenet'
AND form_id=20
ORDER BY feed_order, id ASC

SELECT *
FROM wp_gf_addon_feed
WHERE addon_slug='gravityformsppcp'
AND form_id=20
ORDER BY feed_order, id ASC

SELECT *
FROM wp_gf_form
WHERE id=19

SELECT *
FROM wp_gf_addon_feed
WHERE addon_slug='gravityformsauthorizenet'
AND form_id=19
ORDER BY feed_order, id ASC

SELECT *
FROM wp_gf_addon_feed
WHERE addon_slug='gravityformsppcp'
AND form_id=19
ORDER BY feed_order, id ASC

Sure, here are the queries. It seems like it’s Wordfence, Yoast, and Gravity Forms. The Gravity Forms add-ons appear to be the worst offenders.

We were getting this too, but it went away after I upgraded WordPress SEO Premium from 19.0.1 to 19.1. If that doesn’t fix it, it’s likely from some other Yoast add-on that’s attempting to call this deprecated method.

Is this plugin abandoned? It’s entirely unclear how it’s supposed to work. There’s almost 0 feedback in the admin screens about what is supposed to be happening or whether the plugin is properly connected. The Development Mode appears to be publishing directly to our page under the new Creator Studio setup.

It would be really nice to hear from a maintainer or support person here. Pretty frustrating to have complete radio silence on a plugin built by Facebook and Automattic here.

Thanks, Robert. Very helpful. This should definitely be linked in the changelog tab, or directly included as a standard changelog file. But at least it exists…