JetPack forms processing screws up backend processing

  • Unknown's avatar
    gymnasiegruppen · Member ·

    I have a form on a page that when submitted generates an email. When I receive the email in outlook I save it as a textfile and FTP (with a trigger) to a backend server. The backend parses the textfile, updates a database and does a bunch of processing.

    Now I have noticed a difference in the email format in that it mentioned “Jetpack forms”. Also the save-as textfile is totally corrupted as there is only one character per line. (Imagine a name field spread over twenty lines …)

    Is there a way to go back to the way things were??? That is using any other method than Jetpack???

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    staartmees · Member ·

    We can’t help with custom coding (that’s what your backend server does). The only solution is by adapting your custom coding.

  • Unknown's avatar
    gymnasiegruppen · Member ·

    This is not about custom coding in the backend. This is about the format of the email changing because of the Jetpack function.

    Can I go back to the way this worked before “JetPack” was introduced????

  • The topic ‘JetPack forms processing screws up backend processing’ is closed to new replies.