• Resolved Andrew1977

    (@andrew1977)


    Firstly, I’d like to say that this is a fantastic plugin, with excellent support!

    Have noticed that when we edit any product page we can see the following in the top Custom Fields box at the bottom of the page:

    saswp_modify_this_schema_21112

    Wanted to know if this is required for the plugin to work properly?

    Only reason I ask, is because we had an issue a while back, with lots of custom fields being created by this plugin, which you kindly resolved in a plugin update, which then stopped any custom fields from being created.

    When you resolved this previous issue, the custom field boxes were then always empty, but have noticed today, the following appearing in the top custom fields box:

    saswp_modify_this_schema_21112

    If this isn’t required for the plugin to work, are you able to stop this from happening in a future plugin update?

    Always worried about the database filling up with stuff that isn’t always required, if that is the case?

    Below is a link to when you fixed this for us last:

    https://wordpress.org/support/topic/custom-fields-374/

    Kind Regards,

    Andrew

    • This topic was modified 1 year, 9 months ago by Andrew1977.
    • This topic was modified 1 year, 9 months ago by Andrew1977.
Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Author Magazine3

    (@magazine3)

    Thank you for reaching us. Can you please let me know are you taking about this one? : https://prnt.sc/4uI5toiAfdOa

    If yes please confirm, or please share the screenshot of the one which you are referring. So that we will assist you acordingly to resolve your issue.

    Thread Starter Andrew1977

    (@andrew1977)

    Thanks for the quick reply @magazine3

    Please see below a link showing a screenshot, of what we’re referring too.

    https://paste.pics/8838c5986d982f0d0623c302afb1ad90

    Kind Regards,

    Andrew

    Plugin Author Magazine3

    (@magazine3)

    Thank you for sharing the screengrab. You can remove the values by deleting them if you dont want, So that it will gone . Kindly check once by removing them and let us know back.

    Thread Starter Andrew1977

    (@andrew1977)

    Thanks @magazine3

    Unfortunately after deleting them, they repopulate, and appear again.

    Here’s an example of one that we deleted that recreated itself:

    https://paste.pics/130063d80d1d93a14630b3fb78c012ed

    They appear in the box below, when one is deleted.

    Are these custom fields important for schema to work for just our website products?

    Not sure if you have a filter snippet that could remove these?

    Kind Regards,

    Andrew

    Plugin Author Magazine3

    (@magazine3)

    Sorry for the inconvenience. We will analyze this scenario and get back to you with the solution once we’ve done it.

    Thread Starter Andrew1977

    (@andrew1977)

    Thanks @magazine3

    Much appreciated!

    Kind Regards,

    Andrew

    Plugin Author Magazine3

    (@magazine3)

    Actually, The field saswp_modify_this_schema_21112 is required to work schema properly. So we can not remove it. And can you please let me know, How much space this field takes in the database?

    Thread Starter Andrew1977

    (@andrew1977)

    Hi @magazine3

    Thank you for your reply.

    Haven’t been able to locate this in the database.

    However have just noticed that any of our products that haven’t been updated recently, this custom field isn’t present, but as soon as we do any kind of product update, e.g: a price increase, these custom fields then get added, to these products that haven’t been updated recently.

    Looking at these products which haven’t been updated or had any changes recently, before we have done any updates, the schema is working correctly, and we no that before, when these weren’t present, everything worked correctly.

    Is there a filter that we could use to stop these custom fields from getting added?

    Or, if you could let us know the code that was added to the plugin, which creates these custom fields, more than happy to remove this our end.

    Kind Regards,

    Andrew

    Thread Starter Andrew1977

    (@andrew1977)

    Also noticed on some other products there are more custom fields that have been created (example below):

    https://paste.pics/22ef5656388424c3d7f78fa470865ce3

    We know that before when this happened you kindly released an update, which stop these kind of custom fields being created, and your plugin worked smoothly and fine, without these custom fields.

    If your able to provide a solution for us, it would be greatly appreciated.

    More than happy to add a filter to our functions.php file, if you have a filter that we could use to stop these custom fields being created.

    Kind Regards,

    Andrew

    Thread Starter Andrew1977

    (@andrew1977)

    This was the fix last time:

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

    Kind Regards,

    Andrew

    Thread Starter Andrew1977

    (@andrew1977)

    Have found out that the last version, which doesn’t create any of these custom fields is version:

    1.9.100

    It would appear that the changes introduced in version:

    1.9.101

    started the creation of these custom fields.

    Kind Regards,

    Andrew

    • This reply was modified 1 year, 9 months ago by Andrew1977.
    Plugin Author Magazine3

    (@magazine3)

    Hi, Sorry for the delay in getting back. Can you please let us know, Are you facing any issue because of these custom fields? Kindly do let us know the inconvenience if possible, So that we will analyze the scenario and assist you to fix the issue.

    Thread Starter Andrew1977

    (@andrew1977)

    Hi @magazine3

    Thank you for your reply.

    The issue that we are facing is that every time we edit a product to make any changes, a new custom field is created, and again, the next time any changes are made, more are added. They are filling up the postmeta table in the database, and we have to keep manally finding and deleting them from the database.

    The schema works perfectly without these custom fields, and we would like to be able to stop them from being created, as we don’t need them, and don’t want our database getting clogged.

    Version 1.9.100 is the last version that works, without creating any custom fields.

    Version 1.9.101 is when the custom fields started getting added again.

    If you could let us know the changes that were made that started the custom fields being created, more than happy to comment them out our end, to stop the creation of these custom fields, or better still, if you have a function that we could add to our functions.php file, that would be good.

    Kind Regards,

    Andrew

    Plugin Support Sanjeev Kumar

    (@sanjeevsetu)

    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.

    Thread Starter Andrew1977

    (@andrew1977)

    Thanks @sanjeevsetu

    Kind Regards,

    Andrew

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Custom Fields’ is closed to new replies.