schemaappnick
Forum Replies Created
-
Forum: Plugins
In reply to: [Schema App Structured Data] Warning and Deprecated Message ErrorsHi @rajeshverma69
The fix for the deprecated messages has been published in version 2.2.8.
If you still require assistance for the other warning message as described, reach out to our support email [email protected], and our team may be able to help troubleshoot the problem in your environment to identify any specific problem you’re encountering.Hi @damnatus15,
Thank you so much for reporting this. We applied a fix for this in version 2.2.8.
The change in version 2.2.7 was intended to resolve a PHP deprecation warning, to declare class properties that were previously being set dynamically. However the visibility was set to be too strict.
In version 2.2.8 this has been updated to match the pattern used by the other post and page types, and you should be able to change the content of posts and pages as intended.Regards,
Nick
Forum: Plugins
In reply to: [Schema App Structured Data] Warning and Deprecated Message ErrorsFor the deprecated message, this is not critical, but I have submitted it for repair. I cannot estimate a timeline on resolution for this.
For the warning message, we would need to identify the specific problem. As stated above, in order to help troubleshoot this in your environment, please reach out to [email protected] and we will be able to provide assistance.Forum: Plugins
In reply to: [Schema App Structured Data] Character problemHi burhi,
This looks like an issue with correctly rendering these UTF-8 encoded characters. I will submit this for review and repair, thank you for flagging this.
Thanks,
NickForum: Plugins
In reply to: [Schema App Structured Data] Warning and Deprecated Message ErrorsHi rajeshverma69,
Thanks for reaching out. The deprecated messages are for some dynamic properties on some classes that need them declared. This has no effect on PHP 8.2, but will eventually throw errors in PHP 9. This is a straightforward fix and I will submit this for repair.
For the warning message around DOMDocument::loadHTML, it would be useful to get more information about your content in order to determine what is causing this – please reach out to [email protected] referencing this support topic, and our team will be able to help troubleshoot this further.
Thanks,
NickForum: Plugins
In reply to: [Schema App Structured Data] Plugin Conflict?Thank you all for reporting this issue.
We’ve released an update (version 2.2.2) to the plugin, in which we fixed a bug around this nonce check. The check now applies only to the relevant post types in which we render our meta box, the ‘post’ and ‘page’ types.Forum: Plugins
In reply to: [Schema App Structured Data] Plugin Conflict?@mrmiller23 I’m sorry to hear it. Our team is investigating possible causes for this error when updating pages or posts.
In the meantime, to answer your question about reverting to a previous version – the Advanced View on the plugin’s page has Previous Versions available to download under the Advanced Options section.
You can download the .zip for a previous version (such as 2.2.0) and install this in your WordPress admin. WordPress provides some instructions for installing a .zip here: https://wordpress.com/support/plugins/install-a-plugin/#install-a-plugin-with-a-zip-fileForum: Plugins
In reply to: [Schema App Structured Data] Plugin Conflict?Hello,
The recent plugin update resolved a security vulnerability related to a missing nonce check in the editor meta box (the “Schema App Structured Data” meta box that allows you to view or modify the post or page’s markup).
If you have any caching plugins or caching with your hosting provider, you may try clearing these caches and trying again.If the issue persists after clearing the cache(s), we can investigate this further if you would be willing to provide us with temporary access to the site in question. Please reach out to [email protected], referencing this support topic, and we’ll get back to you as soon as possible.
Forum: Plugins
In reply to: [Schema App Structured Data] datePublished and dateModified still have issuesThanks @billferris. I see that this is still unresolved, and I am bringing this to the attention of our team in order to repair this formatting issue.
In the meantime, these fields are considered optional, so these warnings should not impact rich result eligibility.Forum: Plugins
In reply to: [Schema App Structured Data] New vulnerability! Missing AuthorizationThank you @sanquo , our team is investigating this.
Forum: Plugins
In reply to: [Schema App Structured Data] datePublished and dateModified problemsThank you for letting us know, bakimeral. While the warnings displayed in Rich Results Test tool are for optional fields and are therefore non-critical, I have submitted this issue for repair.
Forum: Plugins
In reply to: [Schema App Structured Data] Pulling Description wrongHi @sarina1 ,
Please reach out to [email protected] referencing this support topic, and our team will be able to address your questions as soon as they can.
Thank you,
NickForum: Plugins
In reply to: [Schema App Structured Data] WooCommerce add-on increases frontend load timeThanks @nickcoupland.
I’ve attempted to replicate this issue locally but was unable to identify any signficant delay in a test environment.
We’d be happy to investigate this further if you would be willing to provide us with temporary access to the site in question. Please reach out to [email protected], referencing this support topic, and we’ll get back to you as soon as possible.
Thank you,
NickForum: Plugins
In reply to: [Schema App Structured Data] WooCommerce add-on increases frontend load timeHi Nick,
Thank you for bringing this issue to our attention!
To assist in troubleshooting this, could you clarify the following information?
– version of WordPress you have installed
– version of WooCommerce you have installed
– version of any other Schema App plugins you may have installed (the base Schema App Structured Data plugin or the Schema App Advanced WordPress plugin), if applicable.This will help us narrow down a possible issue with the plugin.
Thank you,
Nick