Sean

I’m not sure about the character set, but I tried it both in Pantheon and in my local (fresh install).

But, I think you got me wrong. What you tested was uploading an image to a wysiwyg ACF field, what I mentioned was about broken HTML tags.

Can you please try to create a new page, add an ACF custom block that uses a wysiwyg field, then run the conversion?

The HTML tags there will be converted to HTML entity after the process.

Hi there! Is there any news on this?

Thank you!

Sorry, I think I listed down the wrong query there. But yes, that is one of the slowest one. About indexation, yes it has been done in the past.

This one is the main issue:

SELECT MAX(p.post_modified_gmt) AS last_modified, MIN(p.post_date_gmt) AS published_at
FROM wp_posts AS p
WHERE p.post_status IN (?)
AND p.post_password = ?
AND p.post_type = ?

Seems that it’s being run every time we lists posts in the admin.

in mysqli_query called at /code/wp-includes/class-wpdb.php (2431)
in wpdb::_do_query called at /code/wp-includes/class-wpdb.php (2320)
in wpdb::query called at /code/wp-includes/class-wpdb.php (3018)
in wpdb::get_row called at /code/wp-content/plugins/wordpress-seo/src/builders/indexable-home-page-builder.php (141)
in Yoast\WP\SEO\Builders\Indexable_Home_Page_Builder::get_object_timestamps called at /code/wp-content/plugins/wordpress-seo/src/builders/indexable-home-page-builder.php (115)
in Yoast\WP\SEO\Builders\Indexable_Home_Page_Builder::build called at /code/wp-content/plugins/wordpress-seo/src/builders/indexable-builder.php (413)
in Yoast\WP\SEO\Builders\Indexable_Builder::build called at /code/wp-content/plugins/wordpress-seo/src/repositories/indexable-repository.php (506)
in Yoast\WP\SEO\Repositories\Indexable_Repository::upgrade_indexable called at /code/wp-content/plugins/wordpress-seo/src/repositories/indexable-repository.php (240)
in Yoast\WP\SEO\Repositories\Indexable_Repository::find_for_home_page called at /code/wp-content/plugins/wordpress-seo/src/actions/indexing/indexable-general-indexation-action.php (125)
in Yoast\WP\SEO\Actions\Indexing\Indexable_General_Indexation_Action::query called at /code/wp-content/plugins/wordpress-seo/src/actions/indexing/indexable-general-indexation-action.php (45)
in Yoast\WP\SEO\Actions\Indexing\Indexable_General_Indexation_Action::get_total_unindexed called at /code/wp-content/plugins/wordpress-seo/src/helpers/indexing-helper.php (249)
in Yoast\WP\SEO\Helpers\Indexing_Helper::get_unindexed_count called at /code/wp-content/plugins/wordpress-seo/src/helpers/indexing-helper.php (297)
in Yoast\WP\SEO\Helpers\Indexing_Helper::get_filtered_unindexed_count called at /code/wp-content/plugins/wordpress-seo/src/integrations/admin/indexing-notification-integration.php (239)
in Yoast\WP\SEO\Integrations\Admin\Indexing_Notification_Integration::get_presenter called at /code/wp-content/plugins/wordpress-seo/src/integrations/admin/indexing-notification-integration.php (214)
in Yoast\WP\SEO\Integrations\Admin\Indexing_Notification_Integration::notification called at /code/wp-content/plugins/wordpress-seo/src/integrations/admin/indexing-notification-integration.php (164)
in Yoast\WP\SEO\Integrations\Admin\Indexing_Notification_Integration::maybe_create_notification called at /code/wp-includes/class-wp-hook.php (308)
in WP_Hook::apply_filters called at /code/wp-includes/class-wp-hook.php (332)
in WP_Hook::do_action called at /code/wp-includes/plugin.php (517)
in do_action called at /code/wp-admin/admin.php (175)
in require_once called at /code/wp-admin/edit.php (10)

I’m guessing Yoast is trying to tell us about how much unindexed posts there are, but this query is quite heavy to be run every time we list posts. Can you please let me know if there’s way to get around this?

Hi Chad!

Thanks for letting me know what’s that about. It’s still weird though.

As I said in the first post, I haven’t used this plugin before. I didn’t even know how to enable or add the setting for fixed period expiration.

I just installed the plugin, go to the settings, enable this checkbox “Enable Products”, add a new product, and the error is there.

You’ll need to remove the setting for fixed period expiration for this particular membership.

How do I do that? How to enable it in the first place? This error is also happening whenever I add a new Membership product.

Sorry for the late reply, was involved in another issue.

Yeah, that solved it. Manually going to database and clearing up entries in that table seems to solve the issue.

Would be nice if we can do it via wp-admin though. Since setting a mapping object with no WordPress triggers will definitely cause this issue.

Some of the entries in that table even have some kind of a string like WordPress ID (prefixed by tmp_). There’s no other way to fix this, other than going to the database table.

Btw, I’m curious if we can manually triggers an object import, something like a button in a post edit page, that will import SalesForce object when it’s clicked. Which one of the plugin class is doing it?

Nice! So what I’ll need to do, is just somehow delete that relation row?

Mapping Errors tab

Where do I find this though? There’s only 6 tabs in the plugin page.
Settings, Authorize, Fieldmaps, Scheduling, Import & Export, Log Settings.

You’re right about the logs. Something weird though, it logs both success and error.

56min Ago
Error: WordPress update for equality_guide ID 27232 was unsuccessful with these errors:

56min Ago
Success: Update WordPress equality_guide with ID of 27232

Those two posts in logs, are talking about the same post ID. I wonder why it’s triggering both success and error log?

• This reply was modified 5 years, 7 months ago by Sean.