zem_contact_reborn 4.0.3.20

Karsten · 2011-04-24 19:50:40

Hey guys,

I found after installing IE9 today, that in IE9 ALL layout as specified in the CSS had gone. I just got an outline with randomly placed input fields and labels. Very nice. The form was simply posted as txp:zem_contact_text tags in an article body with all basic settings.

I found that when I changed the default “Use Textile” setting to “Leave Text untouched” the form did suddenly show correctly, albeit with messed up layout as of course textile didn’t do its job. So I went about adding some basic HTML tags such as <h2> </h2> and <br /> in order to get things in order.

Than, I found on another page I use, that the form placed there worked perfectly… how peculiar… I copy pasted the form to a new article to see if I had done something differently there… but after posting, again all layout had vanished in IE9….

After a while I found that the reason the form had initially worked was because above the form I had placed an image using basic textile: . However, as I wanted to center the image and couldn’t be bothered to find the correct way to do it I had added a <center> </center> html tag around the image only. The presence of both the opening and closing center tag however subsequently caused the form to display properly in IE9.

So, if I post a contact form now it looks messed up, but when the form is preceded by a basic html tag like <center> image </center> and than the form tags… than everything works perfectly….

Does anyone has any idea what is going on? Is it it just me being a newby with textpattern/zem_contact, or did MS mess things up again with IE as usual…?

> cool note with regards to the latter… IE9 does now apparently support CSS3 rounded corner tags which I used… however, my form also has a border in another color… this however is too complex for IE9 so the main fill displays a rounded corner, but the border around it follows the contours of a rectangle… very strange…

the page I’m playing around with is posted at http://www.scriptieprint.nl/test/contact/ it will be online for a short while…

ruud · 2011-04-24 20:31:43

^^ Carsten, this is probably not related to ZCR, but more a generic CSS problem. You may want to start a fresh topic to get support for this. Before doing so, make sure your CSS validates

Last edited by ruud (2011-04-24 20:33:34)

Karsten · 2011-04-24 21:17:27

Not sure that I agree. How can it be a CSS problem… if I post a regular article with just ZRC tags to make a form, none of the CSS gets implemented. If I change the settings for the same article to “Leave Text untouched” the CSS it does… even when in textile mode, the CSS gets implemented as long as the ZRC tags are preceded by some html tags such as a <center></center>…

The CSS elements that do not validate are mostly double codes used to get IE along, one for all browsers (transparent background colour), and one for IE <9 (non-transparent background colour)… technically double, but otherwise things don’t work… but more importantly, none of these have anything to do with the ZRC CSS.

All other elements on the site work fine by the way, it’s just the ZRC that’s messed up suddenly.

Any help is much appreciated

Karsten · 2011-04-24 21:59:07

Well, although not really understanding why things were getting messed up in IE9, I did find a solution. I used the .zemContactForm fieldset class to define a nice background for the form, nice colour, rounded corners, border, that sort of stuff.

I now completely stripped the .zemContactForm fieldset class to only include border: none; width: 520px; all the rest I just moved to a new div which I named #zemdiv. Now by just putting all the ZRC tags within this div the resulting form displays nicely as it should, and as it did in IE pre-9.

kevinpotts · 2011-05-02 12:30:01

Has anyone pulled in a category list as the value attribute to zem_contact_select? The tag parser keeps erroring out. Something like this:

<txp:zem_contact_select name="Categories" break="" list='<txp:category_list parent="whatever">,<txp:category title="1" /></txp:category_list>

johnstephens · 2011-05-02 12:49:49

It looks like you’re missing the end quote for the list attribute, and the end /> of the zem_contact_select tag:

<txp:zem_contact_select
	name="Categories"
	break=""
	list='<txp:category_list parent="whatever">,<txp:category title="1" /></txp:category_list>'
/>

kevinpotts · 2011-05-02 12:58:20

Yeah, sorry, I have that but just mistyped above. Basically the tag starts to parse, but then instead of closing out with the proper ' /> at the end, it renders ;” />.

ruud · 2011-05-02 13:03:33

What does this show in HTML source (when visiting the page), when used outside ZCR tags:

<txp:category_list parent="whatever">,<txp:category title="1" /></txp:category_list>

kevinpotts · 2011-05-02 20:15:10

Ruud — this produces the normal result.

I get the same character encoding thing when I embed the same code into a <txp:variable /> tag. It also produces the same result when I change category_list to self enclosed; doesn’t seem to make a difference. (Running 4.4.0 on a relatively virgin install.)

ruud · 2011-05-02 21:44:26

Can you provide an URL and put the website in debug mode?

Bloke · 2011-05-02 22:05:58

kevinpotts wrote:

I get the same character encoding thing when I embed the same code into a <txp:variable /> tag

Just out of curiosity (and not just ‘cos this is the 1000th post in this thread) are you putting the code directly in an article? I’ve had weird encoding stuff like this because of Textile getting involved when using tags-in-tags. If so, does it fix things if you turn off Textile or escape the zcr tag with ==?

kevinpotts · 2011-05-03 02:14:38

Here is the page in question: http://buzz.kevinpottsdesign.com/add-buzz

And this is the complete line of code in question:

 <li><txp:zem_contact_select break="" label="Area" list='<txp:category_list parent="locations">;<txp:category title="1" /></txp:category_list>' delimiter=";"  /></li>

When I remove the category list and dump in a hard-coded list of locations, it works perfectly. The only thing I can think of is that I have a rogue quote mark somewhere, but not sure where.

Gocom · 2011-05-03 03:18:53

kevinpotts wrote:

The only thing I can think of is that I have a rogue quote mark somewhere, but not sure where.

As the form is inside an article body, try what Stef suggested:

turn off Textile or escape the zcr ~~tag~~ block with == notextile..

It seems that Textile is doing some formatting and causing the problems.

Also, set category_list’s break attribute to unset (break=""). It defaults to br, which probably doesn’t belong there.

Last edited by Gocom (2011-05-03 03:24:11)

kevinpotts · 2011-05-03 11:30:48

Just out of curiosity (and not just ‘cos this is the 1000th post in this thread) are you putting the code directly in an article? I’ve had weird encoding stuff like this because of Textile getting involved when using tags-in-tags. If so, does it fix things if you turn off Textile or escape the zcr tag with ==?

Here’s an interesting experiment. When I typically write zem forms inside an article, I usually escape Textile by adding a single space before the line. 99% of the time, that works: Textile won’t create a <p> around my line and it does not encode any characters. However, in this case, that single-space tactic failed. Calling notextile. before the actual line worked, just as Stef and Jukka suggested, and the weird encoding things disappeared. Now, my code above works perfectly fine. I only make this pedantic observation as a reminder to self to not assume adding an empty space before a line is doing anything other than preventing the creation of <p> tags. Thanks all.

merz1 · 2011-05-03 12:50:53

Kevin, check the different output on the Textile 2.2 page. I think its self explaining and needs no translation:

Im Detail: Diverse ‘NoTextile’ Textteste für (z.B.) Textile 2.2 Testseite

Replace this text with your _textile_.

Leerzeichen vorweg 
 Replace this text with your _textile_.

notextile. Replace this text with your _textile_.

== Replace this text with your _textile_. ==

Leerzeichen vorweg
 == Replace this text with your _textile_. ==

Achte auf die Feinheiten bei ‘underlying HTML’ und wo und wie kein Textile verwendet wird.

Die letzten Beiden sind identisch mit:

==Replace this text with your _textile_.==
 ==Replace this text with your _textile_.==

Textpattern CMS

Textpattern CMS support forum

#991 2011-04-24 19:50:40

Re: zem_contact_reborn 4.0.3.20

#992 2011-04-24 20:31:43

Re: zem_contact_reborn 4.0.3.20

#993 2011-04-24 21:17:27

Re: zem_contact_reborn 4.0.3.20

#994 2011-04-24 21:59:07

Re: zem_contact_reborn 4.0.3.20

#995 2011-05-02 12:30:01

Re: zem_contact_reborn 4.0.3.20

#996 2011-05-02 12:49:49

Re: zem_contact_reborn 4.0.3.20

#997 2011-05-02 12:58:20

Re: zem_contact_reborn 4.0.3.20

#998 2011-05-02 13:03:33

Re: zem_contact_reborn 4.0.3.20

#999 2011-05-02 20:15:10

Re: zem_contact_reborn 4.0.3.20

#1000 2011-05-02 21:44:26

Re: zem_contact_reborn 4.0.3.20

#1001 2011-05-02 22:05:58

Re: zem_contact_reborn 4.0.3.20

#1002 2011-05-03 02:14:38

Re: zem_contact_reborn 4.0.3.20

#1003 2011-05-03 03:18:53

Re: zem_contact_reborn 4.0.3.20

#1004 2011-05-03 11:30:48

Re: zem_contact_reborn 4.0.3.20

#1005 2011-05-03 12:50:53

Re: zem_contact_reborn 4.0.3.20

Board footer