Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#31 2015-02-05 23:45:46
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,319
Re: txp 4.4.1, too much code on page, save blanks template
jakob wrote #288056:
And you need to start the line with a space in front of the opening
<txp:….
I’ve not had space/notextile troubles with an output_form tag in an article, yet. Seems to save OK without.
Last edited by uli (2015-02-06 16:50:35)
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
Re: txp 4.4.1, too much code on page, save blanks template
Ah, I made them Article. Miscellaneous makes both visible.
Offline
Re: txp 4.4.1, too much code on page, save blanks template
jakob wrote #288056:
You say you’re putting them in articles.
Check the source code of the page as it is output in the browser to see if it is actually being parsed. Sometimes textile will convert it into a string and not parse it as a tag, especially if you’ve not left enough space around the tag. Usually if you need to include tags in the body field, you need to do it like this:
(a blank line)...And you need to start the line with a space in front of the opening
<txp:…. That should prevent textile from converting it into a well-formed paragraph.If you still have no luck, try starting the line with:
notextile. <txp:output_form form="your-form-name" />...And, of course, check your syntax in your article, your forms and the page template. 9 times out of 10 I find I’ve forgotten to close some tag, or I have closed a container tag where I shouldn’t have…
No blank line above the first one on each article. A blank line separates each form in an article.
I made them forms in the articles so the site navigation menu at the top of all articles wouldn’t become cumbersome. This way I connect places in one town together, or a nearby adventure together.
Offline