Same form looks very different on two of the same website

  • wakinggirl
    Asked on January 26, 2015 at 1:31 PM
    ee the Subscribe form in the footer on these pages:

    http://safeembrace3.weebly.com/

    http://safeembrace.org

    (these are the SAME snippets of code, but see how they are two very different looking forms)

  • KadeJM
    Replied on January 26, 2015 at 2:09 PM

    With this issue it's notable that you're having a problem getting your jotform to appear the same on two separate webpages of a similar style after using the same form and embed code for each.

    If your jotform was actually set up as transparent properly it would look like this - 

    Same form looks very different on two of the same website Image 1 Screenshot 30

    However, I noticed your form doesn't do the above so I think something in your css is overriding it probably from when you were trying to fix it in the form designer most likely.

    Same form looks very different on two of the same website Image 2 Screenshot 41

    What I would suggest to resolve the issue would be to either revert your form to a previous version or remove the injected css. Alternatively, you could clone your form and do this on the copy instead. Once you're done with that then you can go back into the Preferences >>> Form Styles >>> and change the Background to transparent again which should fix it.

    Your jotform is noticeable on one because your background is purple and the other is white so that's why they appear differently. 

    If you need more help with this though just let us know.

  • safeembrace
    Replied on January 26, 2015 at 5:25 PM

    hrm.

    well, it looks different on the two forms because on one the subscribe button is AFTER the email field, and on one it's BEFORE.

     

    i'm fully aware of the differing background colors, and that's not the difference i was referring to.

  • David JotForm Support Manager
    Replied on January 26, 2015 at 7:30 PM

    Can you please try embedding the iFrame code instead of the current embedded method? Let us know if that solves the issue.