Settings not preserved when cloning forms

  • drjform1
    Asked on December 31, 2018 at 6:46 AM

    When cloning forms, some settings are not being preserved and I have to redo them every time. One is custom form warnings, the other is, that in my form the background image (which is set to "fixed") always resets to "repeat" when cloning the form. The third is that the form logo gets removed.

  • jherwin
    Replied on December 31, 2018 at 8:03 AM

    When you clone a form, the settings and design should be the same as the original form.

    Try cloning your form using this: How to Clone an Existing Form from a URL. If the issue still persists, please let us know the name of the form and send us a screenshot of the fields or settings that are not the same on the original form.

    Guide: How to Post Screenshots to Our Support Forum.

  • drjform1
    Replied on December 31, 2018 at 8:18 AM

     Works, thank you. However, I wonder why the other way doesn't work as well...

  • Ashwin JotForm Support
    Replied on December 31, 2018 at 9:54 AM

    Is the issue happening when you clone existing form (not through URL)?Please let us know which form you are trying to clone and we will test this issue.

    We will wait for your response.

  • drjform1
    Replied on December 31, 2018 at 8:46 PM

    I was cloning this form through the "clone form" option in the "more" dropdown menu on the "my forms" page.

  • jherwin
    Replied on December 31, 2018 at 11:00 PM

    I cloned the form you sent us and then clone it using the clone form options in drop-down menu. However, I was not able to replicate the issue. The settings, designs, logo are in the cloned form and the original form.

    First Cloned form: https://form.jotform.com/83648821125964

    Cloned form (using clone form in drop-down options): https://form.jotform.com/83649035625967.

    I cleared your form caches in an attempt to fix the issue. Please try to clone your form again and let us know if the issue still persists.

  • drjform1
    Replied on January 1, 2019 at 10:51 AM

    Seems fixed. Thanks.