Hello Brian,
The error shows on the homepage. Please see the sensitive data.
Maybe it’s empty cuz there aren’t reviews for products? What else can we do to remove the CollectionPage schema? Or change the value of primaryimageofPage to og:image?
Thank you.
Hello,
Thank you for getting back to us.
We can only remove the collectionPage schema using the code I gave to you. In the meantime, we want to check how you have set up your schema on the homepage.
We might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress & FTP logins in the designated Sensitive Data section.
Please do take a complete backup of your website before sharing the information with us.
It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:
https://wordpress.org/plugins/temporary-login-without-password/
You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):
https://wordpress.org/plugins/wp-security-audit-log/
We really look forward to helping you.
Hello,
I have updated the sensitive data as requested. Can you please check further?
Thank you.
Hello Brian,
I have added user data in sensitive data without expiration. I hope you’d find the problem.
Please let me know when you are done.
Thank you a lot!!
Hello,
Thank you for getting back to us.
The warning here is expected because we have unset the webpage schema and the data is still available. All these schema entities are usually interconnected and we do not usually recommend removing any one entity from the Schema.
You can hide these warnings since it does not affect the operation of the site via the wp-config file.
If you do wish to proceed please set the 'WP_DEBUG_DISPLAY', true to false. In case you do not know how to achieve this you can simply include your FTP credentials at the sensitive data.
Hope this helps.
We are looking forward to helping you.
Hello Brian,
It was done.
define( ‘WP_DEBUG’, false );
But the error still shows ahead.
I haven’t FTP credentials 😐
Thank you.
Hello,
Thank you for getting back to us.
Depending on the Host Provider you are using you may request them to create FTP credentials for you. Here are some sample steps: https://www.bluehost.com/help/article/how-to-create-an-ftp-account
Additionally, if you are able to access the file manager of your website from your host Cpanel, you may share the credentials of the panel instead.
Hope this helps.
We are looking forward to helping you more.
Hello Brian,
I wrote to the host support and no answer has been seen yet.
But I have activated the File Manager plugin and works properly.
Please check it.
Thank you a lot.
Please let me know if there would be any problem. Thnx.
Hello,
You seem to have deactivated the credentials you had provided in the sensitive data section. However, I did not mean the file manager plugin, we needed the file manager from your server section. If the plugin works well and good we can check it out after you have updated the credentials. If not we may have to wait for your host’s response.
We are looking forward to helping you.
Thank you.
Hello Brian,
Sorry, the password was created and provided to you mistakenly.
Now it’s correct.
Thank you, very appropriate. 🙏
Hello,
Thank you for getting back to us.
Just managed to hide the warning from your homepage. Please counter-check this from your end as well.
Hope this helps.
Hello Brian,
Yes, I discovered that you added define(‘WP_DEBUG_DISPLAY’, false ); and the warning disappeared.
But the ImageObject schema still exists. Please check the new URL in sensitive data, for reference.
Thank you.
Hello Brian,
I have removed Woocommerce default schema and the problem solved.
Used this filter:
/* Remove the default WooCommerce 3 JSON/LD structured data */
function remove_output_structured_data() {
remove_action( 'wp_footer', array( WC()->structured_data, 'output_structured_data' ), 10 ); // This removes structured data from all frontend pages
remove_action( 'woocommerce_email_order_details', array( WC()->structured_data, 'output_email_structured_data' ), 30 ); // This removes structured data from all Emails sent by WooCommerce
}
add_action( 'init', 'remove_output_structured_data' );
Thank you!
Wish you all the best!!!
Hello,
Thank you for the update.
We are glad that this issue is already resolved.
If you have any other concerns, please don’t hesitate to contact us anytime by creating a new ticket to assist you further with anything else.
Thank you.
