<input> tags in cornerstone HTML 'content box' not rendering?

Support
#1

Hi Support,

Due to the lack of support for Mailchimp form options in X-theme Pro we’ve had to embed our naked malichimp code manually in an HTML content box placed on our homepage.

Experiencing a strange bug however in that no tags embedded in the markup are rendering in Safari ???

Everything is working in Chrome/Firefox/IE as far as can tell but it’s simply not rendering the email or checkbox in Safari for Mac…

Have confirmed it’s not a safari bug by testing the same code on another website directly embedded in the html (not via cornerstone) and the same inputs appear fine in safari.

See the screenshots below for issue…

Chrome/Firefox

Safari

Obviously this is a big issue as many of our customers use Safari when viewing the site.

Site is www.tradingboundaries.com

Have tried removing all CSS for simple styles to no effect so seem to have narrowed this down to a cornerstone issue!

Any help here would be greatly appreciated

Many Thanks,

O

#2

Hi Team,

Have just confirmed there is nothing wrong with the code itself and also safari does not seem to be the issue as colleagues are having the same issues in Chrome & Safari now. I’m not in Chrome but maybe this has something to do with my account being logged in.

This is a problem with CORNERSTONE rendering input tags within a ‘content box’.

We would really appreciate help with this ASAP as the site is live and will have to remove our newsletter functionality until this can be resolved.

#3

Also to add to this have noticed that the inputs are showing but only to LOGGED IN USERS

#4

SOLVED: Issue seems to be something to do with cornerstone’s regular ‘content boxes’.
We moved code to a classic ‘raw content’ box and now everything is working fine.

Can’t believe this issue isn’t referenced in X-THEME SUPPORT in any way, what a waste of time.

Eventually found a post from back in October that raised a similiar issue and the user managed to solve it himself without any help from support.

#5

Hey There,

Thanks for letting us know that you have figured out a way to resolved the issue.

Please always keep in mind that when you are inserting a custom html code, it is always best to use raw content element or the content area element because any other content boxes will removed some characters for security purposes and will convert new lines and line breaks into <br> and <p> tags whicl will difinitely broke your custom code.

Best Regards.

#6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.