Dustin L.

I ended up switching to Safe SVG. It seems to work ok.

Thank you. Regarding the second part of my question, Google lists SVG as a supported image format. However, if I upload an SVG, your plugin sets the width and height to 1. I think there needs to be a way for the user to set the width and height of an SVG.

BTW, I installed a different plugin on our site to resolve this issue for now. Hopefully, Organization schema can be correctly implemented with Yoast in a future update.

Another way to have the Organization schema detected by the Rich Results Test is to add a contactPoint property.

"contactPoint": {
        "@type": "ContactPoint",
        "contactType": "customer support",
        "telephone": "",
        "url": "https://example.com/contact-us/"
      },

See test results here.

In this case, I added only the contactPoint property and not the foundingDate property.

Is it possible to set contactPoint in Yoast?

• This reply was modified 1 year, 3 months ago by Dustin L..

Here are some observations…

Regarding the Rich Results Test: I noticed on Yoast.com the Organization schema has several properties that aren’t on the schema on our site. I tested them to see if any are impacting this test. If I add a foundingDate property, which Yoast.com has, to the Organization schema, the Rich Results Test detects the Organization schema. I did this by manually editing the code and pasting it into the testing tool.

Here is a link to the results. You can see the foundingDate property added to the end of the code. That is the only change made to the code Yoast is outputting on our site.

As far as I can tell, there isn’t a way to set the foundingDate in the Yoast settings. Is that right? I guess I would need to use the schema api to correct this? If so, hopefully this could be changed in a future update.

Regarding the Schema Markup Validator results for Yoast.com: I inspected the Organization schema and clicked on the @type property. This revealed that on Yoast.com there is Organization schema is in a separate code block after the site’s footer. It’s not in the main Yoast code block in the head of the HTML. Here is the code I am referring to:

</footer>
<script type="application/ld+json">
	{
		"@context": "https://schema.org",
		"@type": "Organization",
		"name": "Yoast",
		"url": "https://yoast.com",
		"logo": "https://yoast.com/app/uploads/2020/09/Yoast_Icon_SocialMedia_500x500.png"
	}
</script>

This code block doesn’t exist on our site.

Is Yoast.com adding this with the schema api?

I noticed the schema is implemented differently on Yoast.com. The Rich Results Test detects the Organization schema. The Schema Markup Validator shows the Organization schema as a distinct type of schema, separate from the WebPage schema.

How can I implement schema like Yoast.com?

Just thought I would update this thread…

I could never get the NGINX configuration working with ShortPixel and WP Engine. Testing isn’t easy because I can’t quickly try different configurations. All changes must go through their support chat.

I did get a custom NGINX configuration working for webp on WP Engine with a different plugin:

https://www.ads-software.com/plugins/webp-converter-for-media/

https://mattplugins.com/docs/nginx-configuration

I would assume something similar could work for ShortPixel but I couldn’t figure it out.

I decided to abandon the NGINX configuration route because according to the author of that plugin, that method can’t be used with Cloudflare caching unless you have access to the Cloudflare Zone ID and API Token.

We use WP Engine’s Global Edge Security which is powered by Cloudflare but doesn’t give us access to the Zone ID & API Token. So as far as I can tell images would stop being cached if I was able to get the NGINX configuration working.

https://www.ads-software.com/support/topic/getting-worst-ps-scores-hence-im-sad-to-say-is-now-deactivated/

https://www.ads-software.com/support/topic/cache-control-private/

https://mattplugins.com/docs/configure-cloudflare-caching

For now, using the PICTURE tag seems to work ok for the most part and our images are still cached.

Disregard. I figured this out. The human-readable custom post type name wasn’t very obvious. I found it, and it is working now.

Thank you! This seems to work.

Thank you for your work on this!

It looks like 3.0.0 is the latest version available. I see the description has been updated to mention 3.0.1 having the hotfix. But 3.0.1 isn’t available for download.

Do I just need to be more patient?

By the way, thanks for the awesome plugin. It has saved us a ton of time by not having to support customers who are having difficulty changing their passwords.

Heads up. High Performance Order Storage was released today. It would be helpful if you flagged this plugin as compatible if it is in fact compatible.

https://developer.woocommerce.com/2023/10/10/woocommerce-8-2-0-released/

Thank you

By the way, after reading about the 10-minute grace period, it looks like you can modify the code to avoid having to wait 10 minutes during testing.

1. You don’t have to wait 10 minutes when testing, as you can temporarily modify this line of code and replace 10 * MINUTE_IN_SECONDS with 0 to simulate having waited 10 minutes. Or, if you don’t like to touch core code, you could setup the following snippet in a suitable place (such as wp-content/mu-plugins/test-39191.php) then remove after testing:

<?php add_filter( ‘woocommerce_order_email_verification_grace_period’, ‘__return_zero’ );

https://github.com/woocommerce/woocommerce/pull/39191

One thing that comes to mind, when you are attempting to reproduce, it is important that you name the product with the same keyword you are searching for – so the search will actually find it.

For example, name the product “Test” then use “/?s=test” to search the site for test…

I was previously using WooCommerce 8.0.1. I updated to 8.0.2 and the problem persists.

Clearing server-side cache does not resolve the issue.

Switching from Twenty Twenty-Three to Storefront does not resolve the issue.

I will leave the site on Storefront now.

I deleted the original test product and created three new test products:

• Simple Product Test
• Variable Product Test
• Downloadable Test

All three were set to Visibility = Hidden using the bulk editor on the All Products page.

If I do a Quick Edit on each individual product, I can see Visibility = Hidden.

All three are visible on the search results:

https://wcsearch1.wpengine.com/?s=test

I tested in Chrome, Firefox, and Edge and the results are the same.

There are no errors in WooCommerce → Status → Logs or in my server logs.

Thank you

Thank you for the reply.

The User Verification plugin has no impact in my case. This isn’t surprising because all of our customers are guests. None have user accounts.

I created a test environment to reproduce the problem.

I’m using the latest version of WordPress, Twenty Twenty-Three, WooCommerce, and WooCommerce Stripe Payment Gateway with test keys.

I created a test product and, as an admin, created a test order for this product. The status of the order is Pending payment.

Wait over 10 minutes before testing to rule out the 10-minute grace period.

I’ve identified three issues. This first two are change requests, the 3rd seems to be a bug.

#1:

In an incognito window, load the Customer payment page.

The email address used for verification must exactly match the billing email address. For example, if the customer checked out with [email protected], they must enter exactly [email protected] to verify their email. The following entries will fail validation:

• [email protected]
• [email protected]
• [email protected]

Ideally, the verification would be case-insensitive.

#2:

Correctly verify the customer email address to access the Pay for order page.

Enter a test credit card number that will force a decline (Stripe docs).

A “card was declined” notice appears on the screen and the customer is forced to verify their email address again.

Considering the customer has already been verified, forcing them to verify again is a poor user experience.

#3:

Implement the disable filter using the Code Snippets plugin or similar.

add_filter( 'woocommerce_order_email_verification_required', '__return_false' );

Close the old incognito window and open a new one. Load the customer payment page.

The Pay for order page loads. No email verification is required.

Enter a test credit card number that will force a decline (Stripe docs).

A “card was declined” notice appears on the screen and the customer is forced to verify their email address – even though this was disabled using the filter.

Thanks for your help.

Hi Roxy,

Sorry for the delay in getting back to you. I’m still able to reproduce this problem after following the steps you mentioned.

The product…

https://wcsearch1.wpengine.com/product/test-produt/

..is set to Hidden.

It is hidden on the shop page:

https://wcsearch1.wpengine.com/shop/

But visible in search results…

https://wcsearch1.wpengine.com/?s=test

Here is the system status:

` WordPress Environment

WordPress address (URL): https://wcsearch1.wpengine.com<br>Site address (URL): https://wcsearch1.wpengine.com<br>WC Version: 8.0.1<br>REST API Version: ? 8.0.1<br>WC Blocks Version: ? 10.6.5<br>Action Scheduler Version: ? 3.6.1<br>Log Directory Writable: ?<br>WP Version: 6.3<br>WP Multisite: –<br>WP Memory Limit: 512 MB<br>WP Debug Mode: –<br>WP Cron: ?<br>Language: en_US<br>External object cache: ? Server Environment

Server Info: nginx<br>PHP Version: 7.4.33.3<br>PHP Post Max Size: 100 MB<br>PHP Time Limit: 43300<br>PHP Max Input Vars: 10000<br>cURL Version: 7.81.0<br>OpenSSL/3.0.2

SUHOSIN Installed: –<br>MySQL Version: 5.7.42-46-log<br>Max Upload Size: 50 MB<br>Default Timezone is UTC: ?<br>fsockopen/cURL: ?<br>SoapClient: ?<br>DOMDocument: ?<br>GZip: ?<br>Multibyte String: ?<br>Remote Post: ?<br>Remote Get: ? Database

WC Database Version: 8.0.1<br>WC Database Prefix: wp_<br>Total Database Size: 2.86MB<br>Database Data Size: 1.19MB<br>Database Index Size: 1.67MB<br>wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_actions: Data: 0.02MB + Index: 0.11MB + Engine InnoDB<br>wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_logs: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_comments: Data: 0.02MB + Index: 0.09MB + Engine InnoDB<br>wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_options: Data: 0.11MB + Index: 0.03MB + Engine InnoDB<br>wp_postmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_posts: Data: 0.05MB + Index: 0.06MB + Engine InnoDB<br>wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_admin_note_actions: Data: 0.05MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB<br>wp_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_meta_lookup: Data: 0.02MB + Index: 0.09MB + Engine InnoDB<br>wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB Post Type Counts

attachment: 1<br>page: 7<br>post: 2<br>product: 1<br>wp_navigation: 1<br>wp_template: 2 Security

Secure connection (HTTPS): ?<br>Hide errors from visitors: ? Active Plugins (1)

WooCommerce: by Automattic – 8.0.1 Inactive Plugins (0) Dropin Plugins (2)

advanced-cache.php: advanced-cache.php<br>object-cache.php: Memcached Redux Must Use Plugins (5)

Force Strong Passwords - WPE Edition: by Jason Cosper – 1.8.0<br>WP Engine Cache Plugin: by WP Engine – 1.1.4<br>WP Engine Seamless Login Plugin: by WP Engine – 1.6.1<br>WP Engine Security Auditor: by wpengine – 1.0.11<br>WP Engine System: by WP Engine – 5.0.1 Settings

API Enabled: –<br>Force SSL: –<br>Currency: USD ($)<br>Currency Position: left<br>Thousand Separator: ,<br>Decimal Separator: .<br>Number of Decimals: 2<br>Taxonomies: Product Types: external (external)<br>grouped (grouped)<br>simple (simple)<br>variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)<br>exclude-from-search (exclude-from-search)<br>featured (featured)<br>outofstock (outofstock)<br>rated-1 (rated-1)<br>rated-2 (rated-2)<br>rated-3 (rated-3)<br>rated-4 (rated-4)<br>rated-5 (rated-5)

Connected to WooCommerce.com: –<br>Enforce Approved Product Download Directories: ?<br>HPOS feature screen enabled: –<br>HPOS feature enabled: –<br>Order datastore: WC_Order_Data_Store_CPT<br>HPOS data sync enabled: – WC Pages

Shop base: #7 - /shop/<br>Cart: #8 - /cart/<br>Checkout: #9 - /checkout/<br>My account: #10 - /my-account/<br>Terms and conditions: ? Page not set Theme

Name: Twenty Twenty-Three<br>Version: 1.2<br>Author URL: https://www.ads-software.com<br>Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme<br>WooCommerce Support: ? Templates

Overrides: – Admin

Enabled Features: activity-panels<br>analytics<br>product-block-editor<br>coupons<br>core-profiler<br>customer-effort-score-tracks<br>import-products-task<br>experimental-fashion-sample-products<br>shipping-smart-defaults<br>shipping-setting-tour<br>homescreen<br>marketing<br>mobile-app-banner<br>navigation<br>onboarding<br>onboarding-tasks<br>remote-inbox-notifications<br>remote-free-extensions<br>payment-gateway-suggestions<br>shipping-label-banner<br>subscriptions<br>store-alerts<br>transient-notices<br>woo-mobile-welcome<br>wc-pay-promotion<br>wc-pay-welcome-page

Disabled Features: minified-js<br>new-product-management-experience<br>product-variation-management<br>settings<br>async-product-editor-category-field

Daily Cron: ? Next scheduled: 2023-08-12 13:42:20 +00:00<br>Options: ?<br>Notes: 68<br>Onboarding: completed Action Scheduler

Complete: 5<br>Oldest: 2023-08-11 13:43:28 +0000<br>Newest: 2023-08-11 13:45:40 +0000

Failed: 1<br>Oldest: 2023-08-11 13:44:38 +0000<br>Newest: 2023-08-11 13:44:38 +0000

Pending: 1<br>Oldest: 2023-08-12 13:43:28 +0000<br>Newest: 2023-08-12 13:43:28 +0000 Status report information

Generated at: 2023-08-11 13:46:52 +00:00<br>`