Can’t use `form update` command with big forms

  • Resolved jkca

    (@jkca)


    7 years, 6 months ago

    The form update command requires passing the form json on the command line. This doesn’t work if the form’s json is longer than the maximum accepted command line length.

    I feel it would be more useful if there were a create-update command that took a file and created the forms that were missing and updated the forms that were already in the system.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter jkca

    (@jkca)

    I’ve been digging into this issue further to see if I could work around this issue and I haven’t found a way to safely migrate and update forms across deployments.

    When I import from an export, a new ID is generated which means shortcodes for forms are invalidated. I tried to use the field update API and it didn’t allow me to update IDs.

    Is there a workflow for keeping deployments in sync that doesn’t involve copying the database?

    • This reply was modified 7 years, 6 months ago by jkca.
    Plugin Author Steve Henty

    (@stevehenty)

    Thanks for letting us know. We’ll look into it.

    • This reply was modified 7 years, 6 months ago by Steve Henty.
    Plugin Author Steve Henty

    (@stevehenty)

    Please check out the latest version. We’ve added the –file arg to the wp gf form update command to allow forms to be updated from an export file.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Can’t use `form update` command with big forms’ is closed to new replies.