| Post |
|
Guest
| Len Wilson 11:10 pm January 22, 2009
| |
|
|
I've got the same form that is parsing differently when it is called on two different pages. Obviously there is some CSS on one of them that is affecting it. Specifically what is happening on page #2 is that the fields are displaying below the labels instead of to the right.
What is stumping me is that I cannot find what css is causing it to do this, as the page #2 container only has a width, and a font-size, and also I cannot seem to find any, or create any, class or id that will grab ahold of the cform on only page #2 and affect it so I can cause it to display correctly.
Make sense? Doesn't to me either!
|
|
|
Guest
| Len Wilson 6:11 am January 23, 2009
| |
|
|
Aha. After much angst I have realized that the reason I can't fix it through CSS because it's a coding issue…
Maybe a moderator can help me. On page #1, the label is followed directly by the field, but on page #2, the label is followed by a <br>:
<li id="li--2"><label for="cf_field_2"><span>Name:</span></label><br />
<input type="text" name="cf_field_2" id="cf_field_2" class="single fldrequired" value="Your Name" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt"></span></li>
Why is it creating a <br>?
|
|
|
Admin
| Oliver Munich, Germany posts 6237 7:17 am January 23, 2009
| |
|
|
|
|
Guest
| Len Wilson 2:49 pm January 23, 2009
| |
|
|
It's on my dev server here:
http://75.125.201.194/about/
The one that works right, same form, is here:
http://75.125.201.194/about/contact-us/
|
|
|
Admin
| Oliver Munich, Germany posts 6237 2:00 pm January 24, 2009
| |
|
|
It looks like some other plugin is adding the <br/> since cforms certainly doesn't, unless core code has been changed.
|
|
|
|
|
Guest
| Springthistle 5:33 pm October 18, 2011
| |
|
|
Oliver, the same thing is happening to me – BR tags being added after the </label>.
The BR tags are only added when a particular other plugin is actived. It's a plugin I wrote! Since there is no code in my plugin that adds BR tags to anything, I am thinking that maybe my plugin creates a setting that cforms reads, and that's where the BR tags are coming from?
If so, then I can fix my plugin so it no longer conflicts with cforms. Any ideas?
|
|
|
Guest
| Tim 6:36 pm December 16, 2011
| |
|
|
Experiencing same issue here. One thing I've noticed in my troubleshooting is that it only inserts the <BR> for me if I've inserted the form into a page via the WP editor. If I hard-coded it into the page template via PHP, there are no <BR> tags inserted after the labels. I suspect for me that this is something in the template functions.php file that is causing the problem.
|
|
|
Guest
| Julian 2:41 am January 25, 2012
| |
|
|
Same problem here. It just suddenly appeared and I haven't had proper time to debug it fully (ie. it's a very busy live site). A very fast hack is to add a CSS rule:
.cform br {
display: none;
}
|
|