Thread

I’ve been using path variables for years with no problem, i.e. {path='template_group/template'}.  I am working with a channel with a channel field group that has two textarea fields.  In a single entry page, path variables typed into one field work fine.  In another they behave like plain text and don’t show the proper path.

So for instance the url for {path='template_group/template'} would result in:

<a href="http://www.example.com/site/info/{path=template_group/template/single_entry_123}">http://www.example.com/site/info/{path='template_group/template/single_entry_123'}</a>

as the exact URL in the HTML, rather than the EE tags getting parsed and resulting in:

<a href="http://www.example.com/template_group/template/single_entry_123">http://www.example.com/template_group/template/single_entry_123</a>

I’m befuddled!  What am I missing?

The only difference between the two textarea fields is the size of the text area and the fact that one is required, one isn’t, one is searchable, one isn’t, and the formatting buttons display or don’t.  They are both formatted as XHTML.

EE 2.5.3

Any ideas?  Grateful for insight…

Hi oliversitedesign,

I think you’ve run into a bug here. Try this fix and let me know if that takes care of it for you!

Well great.  I think that took care of it!  And I did notice later that it seemed to work for the first entry okay, but subsequent ones didn’t work.  So to clarify, I commented out line 498 in EE_Typography.php, as listed in bug report 18287:

$this->initialize();

rather than doing the other fix as suggested in report 18239.

Thank you!  I thought I was losing it!  😉

No problem! It’s certainly a strange bug, so I’m glad we could nail it that quickly for you. If you need help again, just let us know!