Backslash in fields leads to problem w/conditionals- |
|||
|---|---|---|---|
| Date: | 05/05/2008 | Severity: | Minor |
| Status: | Resolved | Reporter: | Robin Sowell |
| Version: | EE 1.6.3 | Assigned To: | Not Assigned |
| Keywords: | Modules, Weblog | ||
Details
re: http://expressionengine.com/forums/viewthread/78375/
If you end a field with a backslash:
something\
Then use that field in a conditional:
It’s throwing a t string error. Replicated on my install.
Comment on Bug Report
| Posted by: NDM-CareerOne on 5 May 2008 5:49pm | |
|
I am not sure if this is the best way to “subscribe” to this issue. But I reported it in the forums, and would like to keep track. |
| Posted by: NDM-CareerOne on 18 May 2008 5:58pm | |
|
|
My boss has asked me to chase this one up. Is there any movement at all, even a starting point for our own investigation would be good, if not a complete solution or workaround. Thanks. |
| Posted by: Justin Hurlburt on 29 May 2008 4:22pm | |
|
This has been corrected for the next release. If you would like, you can email me for the updated file. |
| Posted by: Justin Hurlburt on 29 May 2008 6:32pm | |
|
|
When comparing fields with backslashes, use the entity for comparison. Example:
{if field == ‘ends with backslash\’}
|