Im not sure about others on here but I would look at project variants
to sort this. You could have a PHP variant for your templates and have
it default to publish with the php extension, and then use publication
packages deliver the correct pages as php files to the web server (or
train the editors to publish certain pages as php).

On Jul 19, 5:08 pm, Daniel <[email protected]> wrote:
> @Rich: Thanks for this info. I already thought about the same, but the
> strange thing is, that I can echo (PHP) the name of the file, but if I
> want to use this string in a method, it behaves like this GUID string.
>
> @Aaron and Wayne: Maybe the listed RQL will help me, because I think
> checking the filename property of the page will do it for me. If it's
> blank, this will also tell me enough. But I think I will have to read
> some RQL manual generally, as at the moment I only know how to run RQL
> via a job or a plugin. Is there also a way to get this code into my
> template to be evaluated when the page is being published?
>
> But Wayne you are right, I will describe my idea, perhaps there are
> even more ways to do it. The intention of my question is the
> following:
> Generally we use html pages in our project. But there are also some
> templates that can be integrated into pages as modules, that use PHP
> code. So I can't set a default extension for the template, as the
> parent page might also be a standard html page. Now it happened in the
> past, that editors created new pages without setting the filename
> (which, I know, is already demanded a lot for non technical people)
> and so there were pages out which showed some PHP code in plain text
> on the page, which is not only ugly, but also bad for security.
> So my idea was, to have some Preexecute or Render tag in these
> templates that prevents the PHP part of the template to published, if
> the file extension is not PHP.
>
> Do you think this RQL is usable in this setup?

-- 
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/reddot-cms-users?hl=en.

Reply via email to