Pods Not Saving

  • Resolved Esteban

    (@santiagodigitaldesign1)


    1 year, 8 months ago

    Pods is not saving any changes after clicking Save.

    I have a pod with an image field, I update the image and click save. I refresh the page and see the original image.

    I made an edit to another pod, a text field. I clicked Save and refreshed the page. It reverts to the previous text.

    I found an older article and thought this was my issue but deactivating my cache and resaving the pod type field did not work for me: https://wordpress.org/support/topic/version-2-8-3-no-longer-saving-images-in-pods/

    I also deactivated all plugins except Pods, no luck.

    Running Pods Version 3.2.2

    • This topic was modified 1 year, 8 months ago by Esteban.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support pdclark

    (@pdclark)

    1 year, 8 months ago

    Do you by chance have a required field that is not filled out when running these tests? If using the Block Editor, there is not currently a way to provide feedback regarding the empty required field. An empty required field or an unchecked required checkbox will cause the content to not save.

    If not that, do things change if all other plugins are disabled?

    Thread Starter Esteban

    (@santiagodigitaldesign1)

    1 year, 8 months ago

    Hi, thanks for helping me.
    The pod is not a required field and disabling all plugins did not work. Generally, when I click Save I get a notification and the page jumps back to the top but I’m not getting anything and the page isn’t jumping to the top. I do see a spinning icon for a moment that appears to be saving but when I refresh no edits are actually saved.

    I have a staging site available I can share here or via the slack channel?

    Edit: I also empited Pods cache and checked for PHP errors but didn’t see anything.
    Here is a loom video showing the error with all plugins disabled: https://www.loom.com/share/6341c451b57c4a63b80f1208a3c78dc7?sid=739dbc28-a1f8-4a8f-a24b-72a7ccae45b7

    • This reply was modified 1 year, 8 months ago by Esteban.
    • This reply was modified 1 year, 8 months ago by Esteban.
    • This reply was modified 1 year, 8 months ago by Esteban.
    • This reply was modified 1 year, 8 months ago by Esteban.
    • This reply was modified 1 year, 8 months ago by Esteban.
    Plugin Support pdclark

    (@pdclark)

    1 year, 8 months ago

    Thanks for the details.

    In the web browser’s web inspector, try opening the Network tab before clicking the save button.

    If the data is being sent, a new HTTP request will appear on the left when the button is clicked. Selecting this new request will display details on the right, such as a Preview tab which shows what the server sent back, and a Headers tab saying whether it was successful or not (200 for success, 4XX for various authorization errors, 500 for a server error.)

    There might be an error in the Preview tab, it might say unauthorized or rejected, usually indicating security blocks such as Apache ModSecurity configured by the hosting company, or 500 indicating a general software error on the server-side.

    Setting define( 'WP_DEBUG', true ); in wp-config.php will make relevant errors more likely to be displayed when checking the result of the save attempt in the Network tab.

    Yes, we are also available in the plugin support chat channel if the above inspection does not yield results.

    Thread Starter Esteban

    (@santiagodigitaldesign1)

    1 year, 8 months ago

    I opened the Network tab before clicking the save button. I’m seeing 200 status for everything.
    Then I made an edit and click on Save, nothing immediately changes.

    After a moment, a new line item appears: admin-ajax.php with status of 200 but I think this is related to heartbeat.min.js

    I’ll move into Slack

    • This reply was modified 1 year, 8 months ago by Esteban.
    • This reply was modified 1 year, 8 months ago by Esteban.
    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    1 year, 8 months ago

    As per Slack, there was a required field that was not filled out. On the Pods side, we’re still working on the changes needed to handle prerequisite save checks for the Block Editor and other areas to prevent the save/submit on those forms in a cleaner way.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Pods Not Saving’ is closed to new replies.