Edit pod field not saving

  • Resolved diegogaona

    (@diegogaona)


    7 months, 3 weeks ago

    After upgrading to the last version (from 3.2.2 to 3.2.6) by default a “code syntax” field came without REST active and with Sanitize HTML active.

    Before I was using with my REST Active and Sanitization inactive for this field.

    I tried do edit several times, I save, everything without any error on the console (the api call works fine too), but after refresh the page, the config not change, they return to REST inactive and Sanitize HTML active.
    I tried to modify the fields in the DB, but it not works too, in the field, the config don’t match the DB.

    I downgraded the plugin and everything returned to normal.

    What could be the problem?

    Best regards, Diego.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Paul Clark

    (@pdclark)

    In a default WordPress 6.6.1 installation with Pods 3.2.6, testing a Code Syntax field kept settings for both Sanitize HTML unchecked and REST active. Here are some things that might help:

    • Under Edit Pod > REST API tab, is REST enabled for the pod as a whole? This is necessary for fields to use REST individually.
    • When saving the field settings under Code (Syntax Highlighting) Options and REST API tabs on the field, do the settings revert immediately after save, after page refresh, or at a later time? Is it all REST fields, or only Read, Read Access, or Write?
    • Do things change if all other plugins are disabled and a default theme is used?
    • Are there any plugins, code, or configuration files such as pods.json overriding settings for Pods or REST?
    • Have user capabilities or roles been modified? Is the editing user an administrator?
    • Does clearing Pods cache at the top of Pods Admin > Settings help?
    • On Pods Admin > Pods Tools, does running Repair Pod, Groups, and Fields on the specific pod or Repair Pod configurations help?
    • Does exporting the configuration using Pods > Components > Import/Export Packages, then importing into a fresh installation, or re-importing into the same install after backing up the database resolve the issue?
    Thread Starter diegogaona

    (@diegogaona)

    Hi Paul,

    It is working now, but I will explain bellow, maybe it would help other users or to make some change to on the plugin (if it is a Pods problem)

    After the downgrade, the new changes I did do not save too.

    What helped me is deactivating the plugin, and deactivating Litespeed plugin, activating Pods and activating Litespeed again. Even clearing the Litespeed didin’t work.

    But I think it was some thing related to Litespeed and Pods together, not the Pods version.

    After it, the changes are Okay and everything is working, but I tried (for test purpose) to make changes and the problem still happens, after deactivating like I said above, it worked.

    About your suggestions:

    • Under?Edit Pod > REST API?tab, is REST enabled for the pod as a whole? This is necessary for fields to use REST individually.
      Yes, it was
    • When saving the field settings under?Code (Syntax Highlighting) Options?and?REST API?tabs on the field, do the settings revert immediately after save, after page refresh, or at a later time? Is it all REST fields, or only?Read,?Read Access, or?Write?
      after page refresh
    • Do things change if all other plugins are disabled and a default theme is used?
      Explained above
    • Are there any plugins, code, or configuration files such as?pods.json?overriding settings for Pods or REST?
      May only Litespeed and cache. I’m using Disable REST API plugin too, but I’m using it for years with Pods and the problem is new.
    • Have user capabilities or roles been modified? Is the editing user an administrator?
      No, its is an administrator
    • Does clearing Pods cache at the top of?Pods Admin > Settings?help?
      No, I tried it.
    • On?Pods Admin > Pods Tools, does running?Repair Pod, Groups, and Fields?on the specific pod or?Repair Pod configurations?help?
      I didn’t tried this, and I’m afraid to do it now that is all working.
    • Does exporting the configuration using?Pods > Components > Import/Export Packages, then importing into a fresh installation, or re-importing into the same install after backing up the database resolve the issue?
      I haven’t tried it, but, I tried to modify the database (the meta fields, using the field ID) directly with PHP My Admin, but the plugin was not showing the changes too (very strange), maybe some cache.

    Thank you very much for your plugin and your help.

    Best regards, Diego.

    Plugin Support Paul Clark

    (@pdclark)

    Thanks for the thorough follow-up. Sounds like a cache may have gotten stuck.

    Plugins like LiteSpeed, in addition to a full page cache, can often enable object caching, which can at times cause more granular settings or portions of pages to be cached or delayed in updating between page views.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Edit pod field not saving’ is closed to new replies.