• Resolved djwbrown24

    (@djwbrown24)


    Hello again, final question for the week.
    Currently AutomatorWP doesn’t seem to be able to detect the difference between a ninja form ‘Save’ button hit when a user saves their ninja form progress and a ‘Submit’ button hit from the form, the action triggers when either button is hit. Is there a way to differentiate between the two, would your ninja form add-on solve this issue? Thanks again

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Paco González Pérez

    (@pacogon)

    Hi @djwbrown24 !

    Which “Save” button do you mean?
    Could you send me a screenshot so I can check it?
    I just tested on my WordPress and I only get the “Submit” button.

    Is it possible that you are using an add-on to display the “save” button?
    If you are using an add-on that allows to display the “save” button then it is a conflict issue because AutomatorWP only runs the automation if the “submit” button is pressed.

    Hope it helps!

    Thread Starter djwbrown24

    (@djwbrown24)

    Yes it’s an add-on from ninja forms that allows a user to save a ninja form, allowing the user to complete the form at a later stage.
    AutomatorWP triggers when either the submit or the save buttons are triggered.
    Thanks

    Plugin Contributor Paco González Pérez

    (@pacogon)

    Hi @djwbrown24 !

    What is happening is that that plugin is sending the “form submitted” event when “save” is clicked.
    Then you have to tell them if there is a way to disable that event so that other plugins that wait when a form is submitted don’t detect the “saved” as “submitted”.

    But as a solution you can put a field at the end that only shows if the rest are filled in, and then you can use our trigger “User submits a form with a field value” to consider submission when all the fields are filled in.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Submit Save’ is closed to new replies.