Here’s the setup:

Template set to parse PHP on Output.

Field {extended} set to Textile on submit/update form in CP.

Code in page:

This will output “{extended}” (without the quotes of course.)

But set the formatting on the field to “none” and then change the code to the following and it works as it should:

This is a simplified version of what we are trying to do but it demonstrates the problem. I only tried field formatting of ‘none’ and ‘textile’  so far.

If you don’t use the surrounding PHP do you get the correct content from the “extended” field or do you still get the actual field name appearing?

Hi Chris,

With no PHP, the extended field content is returned however it’s marked-up to be returned at the field level. Just did some more tests and here is an interesting result. Here is the acutal code block I’m dealing with. The {cf_include_extended} is a custom pulldown field that contains values: No, Top, Bottom, Both. We are using the {cf_extended} field for additional notes, links to additional and related resources, and links to audio files. For very long articles, we give the client the ability to place the extended material at the top or bottom of the page, or both, based on the value they choose in the pulldown.

The following displays {cf_extended} if the cf_extended field is set to Textile or xhtml. It displays its content if set to none.

Here’s the interesting part. The following slight variation of the above works if the cf_extended field is set to Textile. The Textile plugin tags were added to the bottom conditional. But of course the content at the bottom is spaced wider apart due to the “doubling” of the Textile formatting (one on the field directly and the one in the template.)

The ability to individually format a given field is brilliant so we want to keep as much formatting and plugins out of the templates as possible.

Thanks for your help on this. Please LMK if there are any other details that could help.