Hello, I've noticed that version 5.5 generates a new ordered list tag — <ol class="cf-ol"/> — before the (single) fieldset of my form, and I'm posting about it here because it impinges on my css styling. Is this really meant to be there? It seems a bit strange to me as it doesn't seem to serve any purpose? To make it a little clearer, the form's xhtml looks like this in firebug:
Note: I'm a new user & first time upgrading (from 5.4 to 5.5) and I'm not sure whether this is a new feature or perhaps something wnet wrong with my upgrade? I upgraded like this: 1) backup my form to text file. 2) Manually backup my css style and graphics in /images folder. 3) Deactivate plugin. 4) remove cforms folder from plugin dir and replace with new copy. 5) Move css and graphics back into place. 6) Activate plugin.
Sorry Oliver, I'm just testing things locally before going live :( the html looks very much the same, as far as I can tell, there's an ordered list tag without content just before the fieldset, whereas previously ordered list tags would show up inside the fieldsets only. The problem with my css stems from the fact that I am using background graphics just like the "dark-rounded" style example, and the ordered list tags are getting styled with the repeat bg graphic, and a bit of that shows up just before the actual form now. I can fix this of course but in case the ordered list tag is actually meant to be there, it would be great if its class attribute would be different from that of the ol's inside the fieldsets. I can email the html output to you if you want, the forum likes to eat my markup..
(looking at the code) I think I see what the issue is…or the cause for the superfluous, empty <ol> tag. While it doens't hurt the HTML layout per se, it shouldn't be there and seems to be the result of a different fix I applied…the fix will go into v5.6 which will be a bugfix release.
If you'd like to patch it yourself:
change this line in (cforms.php):
if ( !$fieldsetopen && !$ol ) {
to this:
if ( !$fieldsetopen && !$ol && $field_type<>'fieldsetstart') {