Download
2015-07-27, 05:22:46
You could use components or my hook_components plugin and target specific pages with a simple $id check, or use different templates for those pages with php in the template.
using eval on a content field breaks in wysiwyg editors and open you up for any kind of imaginable php code injection.
This is still a terrible plugin, even if I fix it. And if i fix it, then anyone using it that uses the return might get unexpected results.
But it might be best to release a different version with safely wrapped code tags, limited php execution protection, and a way to support anyone that is using modifying content with a return closure instead of outputting.
using eval on a content field breaks in wysiwyg editors and open you up for any kind of imaginable php code injection.
This is still a terrible plugin, even if I fix it. And if i fix it, then anyone using it that uses the return might get unexpected results.
But it might be best to release a different version with safely wrapped code tags, limited php execution protection, and a way to support anyone that is using modifying content with a return closure instead of outputting.
