Thank you for the support. Now I know that it’s not possible to parse EE code on the back-end, and allow_eecode is useless even though I didn’t get it to work.
What I try to achieve is quite simple, and I described last time clearly. The workflow of EE is: 1) input the entry through EE CP, 2) the templates decide what to show and how to show the entries “automatically”. Now the workflow I want is: 1) input the entry through EE CP, 2) the editor look at what is going to be shown on the website and decide what to show and how to show the entries, 3) the templates show the entries. For example, part of a webpage will show the top 5 entries’ title as a list, if using the EE way, we can write a template to do this quite simple, however, the logic is fixed once the template is done; if using my way, say we have 8 top stories one day, then the editor can look a list with 8 entries first (by certain tool or interface), and he can choose which 5 of them to show and may change the entries title if he want. Surely, we can use the existing EE CP function to edit those entries title or status one by one, however, this is back to editing-time work. It’s like programming, there are compile-time and run-time. Usually a program’s behavior is defined at compile-time. If we can change a program’s behavior at run-time, this is considered more dynamic. The same thing we wanted here for EE.
Anyway, we have developed a module to do this in EE, so never mind. Still missing the capability to parse EE code at back-end, If that is possible, it could save us time to develop our module.
Thanks!