I did that but still have the same problem unfortunately. Perhaps for those fields that I know will always use textile I’ll just use the tag instead… At least that will (hopefully) solve the issue.
Thanks for your time Derek - I really appreciate it. Especially as I know you’re probably incredibly busy with EE 2.0 (which I really can’t wait to use).
Cheers
Jim
Jim, I notice you are using some PHP includes in your files, and that you have a very very old Textile class file in your includes folder. What’s interesting is that the URI you and I were looking at works fine if the ee.php file is explicitly used in the URI, ‘ee.php/en/derek-test/’ vs. ‘en/derek-test/’, then the rendering is correct. I think via your URL rewrites and PHP modifications to the index/path/config files, you might be causing an old version of the Textile class to be used, either in that include file, or via a second system folder lingering somewhere with the old plugin still installed?
You’re exactly right Derek - thanks so much for helping me find the cause of the problem. I’m very happy that (of course) it’s not an issue with EE, but my own sloppiness, lol!
Updating the other textile file that I’m using fixed the issue. I just hadn’t realised that it was being used because I’m dealing with a pure EE page here.
Cheers again.
Jim
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.