Kevin Pirnie

I do have this figured out, but ended up running into an issue with the test no longer showing the twirling icon… the test runs, just never would know it because nothing shows.

I should have an update soon though… I do have the password saving now

My apologies for not getting back to you sooner. For some reason, I have not gotten emails from this support forum.

I will look into this, and either get back to you here, or push an update to correct it.

@wirecreative that is certainly a possibility, however, I have Oulook365, and use this on my personal site with SMTP settings for it. While I can confirm it works so long as the From address is the same as the sending address, it could also very well be an MX record.

Thanks!
Kevin

My apologies for not getting back to you sooner. For some reason, I have not gotten emails from this support forum.

I will look into this, and either get back to you here, or push an update to correct it.

Thanks!
Kevin

Mmm… certainly food for thought. I can explain 1.9.18 ??
I had an issue where I forgot to update the version in the readme for 1.9.17, so it was still showing as 1.9.11

So… for example, 1.9.11, it would be worth repeating what headers are set by the plugin itself?

I appreciate the input mate… I’ll see what I can do for future versions.

Hey mate. At this point there is not. I will be putting out a couple of blog posts about this and my other plugins, I just have not had time to.

What more specifically would you be looking for in the change log?

Really not sure why this was marked as resolved…

I “fixed” the issue by re-uploading those files from an older version of the plugin… though, why they were removed in the update is beyond me…

Yeah. I’m going to be filing a complaint with PayPal whom I used to purchase the “shortcode” for this plugin for.

My apologies, but it does not appear that the issue is corrected. It appears now to only happen when publishing posts… when the post is set to private the issue does not happen. it also does not happen when updating existing posts.

It “feels” like a conflict somewhere, but by process of elimination, the issue does not occur when the Accessibility plugin is disabled

[Mon May 03 14:07:27.808500 2021] [php7:notice] [pid 18148] [client THE.CLIENTS.IP.ADDRESS:50852] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘))) AND quaws_posts.post_type = ‘post’ AND (quaws_posts.post_status = ‘publish” at line 3 for query SELECT SQL_CALC_FOUND_ROWS quaws_posts.ID FROM quaws_posts LEFT JOIN quaws_term_relationships ON (quaws_posts.ID = quaws_term_relationships.object_id) WHERE 1=1 AND ( \n quaws_term_relationships.term_taxonomy_id IN (2090)\n) AND ((())) AND quaws_posts.post_type = ‘post’ AND (quaws_posts.post_status = ‘publish’ OR quaws_posts.post_status = ‘acf-disabled’ OR quaws_posts.post_status = ‘future’ OR quaws_posts.post_status = ‘draft’ OR quaws_posts.post_status = ‘pending’ OR quaws_posts.post_status = ‘private’) GROUP BY quaws_posts.ID ORDER BY quaws_posts.menu_order ASC LIMIT 0, 20 /* From [www.THEDOMAIN.com/wp-admin/edit.php?s&post_status=all&post_type=post&action=-1&m=0&cat=2090&seo_filter&readability_filter&paged=1&post%5B0%5D=5927&post%5B1%5D=5841&post%5B2%5D=5813&post%5B3%5D=5759&post%5B4%5D=5678&post%5B5%5D=5655&post%5B6%5D=5635&post%5B7%5D=5570&post%5B8%5D=5396&post%5B9%5D=5338&post%5B10%5D=5290&post%5B11%5D=5275&post%5B12%5D=5262&post%5B13%5D=5205&post%5B14%5D=5195&post%5B15%5D=5177&post%5B16%5D=5126&post%5B17%5D=5101&post%5B18%5D=5094&post%5B19%5D=5089&action2=-1] in [N/A] */ made by WP_Posts_List_Table->prepare_items, wp_edit_posts_query, wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts, referer: https://www.THEDOMAIN.com/wp-admin/edit.php?category_name=certification-station
[Mon May 03 14:07:27.874619 2021] [php7:notice] [pid 18148] [client THE.CLIENTS.IP.ADDRESS:50852] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘))) AND quaws_posts.post_type = ‘post’ AND (quaws_posts.post_status = ‘publish” at line 5 for query SELECT SQL_CALC_FOUND_ROWS quaws_posts.ID FROM quaws_posts LEFT JOIN quaws_term_relationships ON (quaws_posts.ID = quaws_term_relationships.object_id) LEFT JOIN quaws_term_relationships AS tt1 ON (quaws_posts.ID = tt1.object_id) WHERE 1=1 AND ( \n quaws_term_relationships.term_taxonomy_id IN (2090) \n AND \n tt1.term_taxonomy_id IN (2090)\n) AND ((())) AND quaws_posts.post_type = ‘post’ AND (quaws_posts.post_status = ‘publish’ OR quaws_posts.post_status = ‘acf-disabled’ OR quaws_posts.post_status = ‘future’ OR quaws_posts.post_status = ‘draft’ OR quaws_posts.post_status = ‘pending’ OR quaws_posts.post_status = ‘private’) GROUP BY quaws_posts.ID ORDER BY quaws_posts.menu_order ASC LIMIT 0, 20 /* From [www.THEDOMAIN.com/wp-admin/edit.php?s&post_status=all&post_type=post&action=-1&m=0&cat=2090&seo_filter&readability_filter&paged=1&post%5B0%5D=5927&post%5B1%5D=5841&post%5B2%5D=5813&post%5B3%5D=5759&post%5B4%5D=5678&post%5B5%5D=5655&post%5B6%5D=5635&post%5B7%5D=5570&post%5B8%5D=5396&post%5B9%5D=5338&post%5B10%5D=5290&post%5B11%5D=5275&post%5B12%5D=5262&post%5B13%5D=5205&post%5B14%5D=5195&post%5B15%5D=5177&post%5B16%5D=5126&post%5B17%5D=5101&post%5B18%5D=5094&post%5B19%5D=5089&action2=-1] in [/nas/content/live/swainc/wp-content/plugins/wordpress-seo-premium/admin/links/class-link-columns.php:219] */ made by WP_List_Table->display, WP_List_Table->display_tablenav, WP_Posts_List_Table->extra_tablenav, do_action(‘manage_posts_extra_tablenav’), WP_Hook->do_action, WP_Hook->apply_filters, WPSEO_Link_Columns->count_objects, WPSEO_Link_Columns->set_count_objects, WP_Query->get_posts, referer: https://www.THEDOMAIN.com/wp-admin/edit.php?category_name=certification-station

Appreciate the quick reply!

This is a very serious issue with the plugin. Is there no support?

From SalesForce Support:

Good news! The root cause of this issue has been discovered and a fix ticket has been created for Engineering to address it — but there is also an easy workaround to bridge the gap for the time being.
Root cause: This was caused by a recent code change to the plugin that prevented calls from going to the correct API version. If the Pardot account uses version 3 of the Pardot API (any account that does not have the “Allowing Multiple Prospects with the Same Email Address” feature enabled is on V3), the plugin still defaults to version 4 which eventually causes timeouts when attempting to pull information.
I’ve created the following Known Issue so that you may track the fix from Pardot Engineering: https://trailblazer.salesforce.com/issues_view?Id=a1p4V0000003y4C. If you click “This Issue Affects me”, you’ll automatically be notified via email when this is resolved. That Known Issue also has workaround steps that should allow you to load up the settings for the time being.

From SalesForce Support:

Good news! The root cause of this issue has been discovered and a fix ticket has been created for Engineering to address it — but there is also an easy workaround to bridge the gap for the time being.
Root cause: This was caused by a recent code change to the plugin that prevented calls from going to the correct API version. If the Pardot account uses version 3 of the Pardot API (any account that does not have the “Allowing Multiple Prospects with the Same Email Address” feature enabled is on V3), the plugin still defaults to version 4 which eventually causes timeouts when attempting to pull information.
I’ve created the following Known Issue so that you may track the fix from Pardot Engineering: https://trailblazer.salesforce.com/issues_view?Id=a1p4V0000003y4C. If you click “This Issue Affects me”, you’ll automatically be notified via email when this is resolved. That Known Issue also has workaround steps that should allow you to load up the settings for the time being.

From SalesForce Support:

Good news! The root cause of this issue has been discovered and a fix ticket has been created for Engineering to address it — but there is also an easy workaround to bridge the gap for the time being.
Root cause: This was caused by a recent code change to the plugin that prevented calls from going to the correct API version. If the Pardot account uses version 3 of the Pardot API (any account that does not have the “Allowing Multiple Prospects with the Same Email Address” feature enabled is on V3), the plugin still defaults to version 4 which eventually causes timeouts when attempting to pull information.
I’ve created the following Known Issue so that you may track the fix from Pardot Engineering: https://trailblazer.salesforce.com/issues_view?Id=a1p4V0000003y4C. If you click “This Issue Affects me”, you’ll automatically be notified via email when this is resolved. That Known Issue also has workaround steps that should allow you to load up the settings for the time being.

same here. WP_DEBUG shows nothing about it as well

Same here