I didn’t get anywhere in the Technical Support forum so I thought I’d double post here in the Plugins forum…

I am using Template Global Variables such as {company_name} inside custom weblog fields but for some reason they are not working inside my {page_content} textarea field when I have the field format set to Textile. The output of that variable should be something like Acme Corp. but instead it’s just coming out as {company_name}.

I set the field format to None and the variable worked fine so it’s definitely an issue with Textile. I’ve never had this issue on past sites. Anyone else had this issue?

Here’s what I’ve tried so far…

- I uploaded a new pi.textile.php file just in case the old one was corrupted but that did NOT help.

- I was using Textile Editor Helper (as I have done on past projects) so I disabled that Extension and deleted the files from the server. That did NOT help.

- I created a new Textarea field to test in case the other field was borked - but that didn’t help either.

- I tried setting the format both via the control panel and right in the templates - but both produce the same result.

Here are the details:
- EE 1.6.4
- Textile Plugin v 1.1.1 (2.0.0 r2779)

Hello,
I have the same problem with the last release of the textile plugin, EE 1.6.4.
If I put a user global variable in the textile code, the global variable is not parsed :

Do you find a solution ?

No, I have not found a solution. I just quit using global variables inside the textile fields. Not sure why this all of sudden started happening with newer installs. It’s worked perfectly fine before.

Does anyone know if it has something to do with the latest version of the plugin?

- Mark

if i try with a previous version of plugin, no problem.

See this blog entry, this thread (which discusses the 1.1.1 update), and of course the plugin’s changelog which also describes these changes.

Sorry, I check again : I upload the last 1.1.1 update (clear the data in cache ...), and

don’t work.

Correct…

and ... any idea ?

Well, it’s doing what it’s supposed to be doing, what that security update was created for: preventing Textile output from being parsed as tags and variables by EE.