Sanjeev Kumar

Hi satishraj19.

We have released a fix in v 1.12. Please update to it and let me know if it fixes your problem

Hi Satishraj19

What do you mean by wrong heading. Can you explain it more??

The thing might be happening at your end that When any SEO plugin compatibility is on in schema we take title and content from SEO meta tag so it will be same title in google SERP because Structured data is also a part SEO.

So happening the same with you or else???

Hi amberllll,

We have checked your schema markup on given url and all the data are coming as per modification done by you.

What you are talking about the preview in Rich Result tool, We do not have control over there, Google shows it as its own way. We just follow google guidelines and add data in pages.

Just inspect browser console and see if there is any js error. It seems there is a conflict with other plugins.

Hi there!

There is currently no way to convert or migrate FAQS created using SASWP to Yoast. You can rollback to SASWP version 1.11 and continue using it.

Hi newtweeks.

Thanks for using our plugin. Please do not deactivate it, If you really faced the problem in the latest update than help us to identify the issue or you can rollback to previous version and continue using it till we find the cause.

Hi there!.

Yes it is exclusively with AMP and It works with and without AMP.

Hi there !

Extremely Sorry for it. We have just released the new v1.11.1 with fix.

Please update to it and let us know.

Hi there !

Extremely Sorry for it. We have just released the new v1.11.1 with fix.

Please update to it and let us know.

Hi there !

Extremely Sorry for it. We have just released the new v1.11.1 with fix.

Please update to it and let us know.

Hi there !

Extremely Sorry for it. We have just released the new v1.11.1 with fix.

Please update to it and let us know.

Could you write whole error here. The above shared text shows only line numbers not the exact error??

Hi danishsard,

Thanks for the details bug reports.

Point 1. Yes you are right. Some styles are being added without its usages on page. We will fix it in next update. ( Follow Ticket: https://github.com/wpquads/quick-adsense-reloaded/issues/715 ).

Point 2. Yes you are again right here. Its a valid bug. Quicktags not being saved. ( Follow Ticket: https://github.com/wpquads/quick-adsense-reloaded/issues/713 )

Point 3. Are you sure it causes by WP Quads. I do not see it is as a bug. The fact that browsers seems to interpret this to unicode for some reason, and the text relying on these attributes appear to work fine on frontend.

Hi andrew1977,

Thank you so much for using our plugin for long time and your appreciation.

Regarding the field saswp_modify_this_schema_(ID), It only appears when you modify any schema on a particular post/product using button ( Modify schema output ) and this field again disappears when you restore to auto fetch.

So to know whether schema is modified or autofetched we must have to maintain a flag in postmeta field. If You do not want this particular field to appear in custom box than keep all schema types in Restore to autofetched mode.

Regarding other fields in the given screenshots (https://paste.pics/22ef5656388424c3d7f78fa470865ce3 ). You are right, if these fields do not have value than it should not be there in custom fields.

We have create a ticket for it and will check again all empty fields and would remove them.

Ref: https://github.com/ahmedkaludi/schema-and-structured-data-for-wp/issues/1862

Thanks again.

We have just released a new version1.10.1 with the fix. Please update to it and it should fix your issue.