Forum Replies Created
-
AuthorPosts
-
hi again,
i hear you. so, what you’re telling me is that what i’m reporting is NOT a bug, but intentional?
then would you please remove the wording that the empty line element, when set to print email only is NOT “email only”?that’s the part that doesn’t make sense. why say it’s for email only when it’s not for email only?
if it was truly for email only, then it would make zero changes on the front-end.i appreciate your replies but i’m feeling like we aren’t understanding each other. if that’s my fault, i apologize, and don’t know what else to say.
hey,
i made an annotated screenshot – hopefully it will appear below & help explain what i mean better.looks like the “Empty Line” Element, when set to “Print Email Only” is adding a “first_form” class to any field that doesn’t already have it. and that class seems to be the reason that it breaks a row on the front-end.
so seems to me that the “Email Only” “Empty Line” needs to stay email only and not add that class to fields on the front-end.
hope that helps. i don’t mean to beat a dead horse, so you can close this topic if you want. doesn’t seem to me that there’s anything else to be done until/unless ya’ll change that (to me, bug) issue so when an element is set for email only, it doesn’t change anything on the front-end.
then why give an option to have a BR in email only if it’s also gonna add it to the front-end?
hi Ismael,
i added your
avf_form_mail_form_field_mod
function code, and it does indeed strip all the BR’s from the email.so then i went in & added the Empty Line Elements between each element.
this still breaks the front-end even tho all the Empty Line Elements are set to Print in email only.
i went ahead & tested the form and i guess that function code overrides the Empty Line elements, because the resulting email was without any line breaks.
so i guess i’m just gonna have to go back to the default email formatting.
i’m not understanding, tho, if the Empty Line Elements are set to Print in email only, why it adds BR’s in the front-end. that’s why i think this is a bug, because to me, if it says it’s only for the email, then it should only be in the email & not affect the front-end at all.
hi Ismael,
thank you for your time on this. i understand about it being out of scope.about the last part tho – maybe i didn’t explain very well. when i use the ‘Print in email only”, it DOES work in the email. the problem is it also puts it in the webpage front-end.
so in this scenario, i create a contact form in the builder.
i have 2 Elements to show side-by-side on the webpage front-end by changing their style width to 1/2.
then add the Empty Line Element in between those Elements,
set it to use only in the email so they have some separation in the email, not the webpage.but for some reason when i set it like this, it ALSO puts the break between the two 1/2’s in the webpage front-end.
does that make sense?hi Ismael,
i’ve been playing around with this a little as i can and have some followup thoughts/questions/info for you…
in your message above, you said “adding html may not work as expected“.
– would you elaborate on that please?
– how would it not work?
– is it really not worth trying to bold the element & colon, and add a space between each in the email?
– if it’s not likely to work across the board, then i don’t want to mess with it. but if making those 2 modifications can work in all email apps & browsers, then i’m game to try figuring it out. i need it to be rock-solid (as solid as anything else the theme does).“IF” your response to that is positive, then please continue.
“IF” your response to that is negative, then nevermind & thank you! (although, please do see the end about the bug i found).in your function code snippet above, i see your comment to “do something with the message here/“.
– but i have no idea what to put there.
– i found similar code @…
kriesi.at/support/topic/using-the-universal-wp-lead-tracking-plugin-with-enfold-contact-form
…but the only part that looks familiar is the “\n
” part.
– i found some other similar code @…
kriesi.at/support/topic/contact-form-html-field
…but again, not enough info/examples for me to craft something to fit my use-case.i then ran across some posts advising folks to edit the theme file…
/enfold/framework/php/class-form-generator.php
1) i do NOT want to mess with the theme files at all (for obvious reasons);
2) i did look thru it (again, not really knowing php), and see on line 1559, there’s html code, adding some<br/>
and<strong>
tags to the “Your Message:” part of the email. i wondered if there’s a way to customize all email elements using that “avf_form_message” filter.
– so no matter what “Form Element Type” is used, the “Form Element Label” with colon would be bolded, and an empty space (hard return,\n
) would be between all Elements in the email.lastly, i discovered the “Other Element: Empty Line” Form Element Type!
thinking this may at least solve the issue of getting some space between the form types in the emails, so i added it and set it for “Print in e-mail only”.
– testing it does in fact add the spacing i was hoping for in the emails,
…BUT, YOU SHOULD KNOW…
there’s a bug in that even tho it’s set for “Print in email only” it still also adds it to the front-end webpage.
…when testing, all my elements with 1/2 width styling gets broken into individual lines.
– so unfortunately, i can’t use this cool discovery until that gets fixed in the theme.note: additionally, the “Message” element already has an extra space above it, so putting that empty element above it produces 2 blank lines in the email. would be nice to either have the spacing consistent for all element types or add a note about that in the form settings.
thanks for the help.
hi Mike. i guess you can close this thread.
i thank you SO much for your time & effort. it is greatly appreciated!
one thing, for reference, it wasn’t working for me right-away. after digging in & comparing to your live example, i discovered your example has back-ticks around
translateX(-${shift}px)
(which seem to be striped away from this post) which the above code didn’t. after adding that, it worked as expected.✌🏼
WOW Mike! thank you for all that!!
i will give it a try mid-week & report back on how it goes :-) -
AuthorPosts