Got to rethinking applying rod's suggestion in a "straight forward" manner by trying to use php code in the content of an ez page. (Ie, not having an internal or external redirect and not an image.)
So I populated the end of the description with code like:
Code:
<?php echo "Hello"; ?>
Saved it and then viewed it as a customer... The text Hello was not presented onscreen, but it was present in the source code in it's entirety. This only further validated my first recollection, that the content of the ez page is simply that, content. It is not preprocessed to be handled as php. This leads me back to if the page remains content based (not a redirect to elsewhere) then the applicable page template file(s) would probably be the "best" place to incorporate the above suggested code.
Mind you, the need for a single language doesn't mean other methods of presentation can't be used or that multiple languages have to be used on the other page(s), and the fact that the product is to remain pretty consistent, it all could be instead placed in a define page (which does get parsed for php content) or an individual page can be created similar to index.php?main_page=new_page_made
Also there is a plugin that offers multi-language ez pages, the thing in my opinion depends on what all is being displayed, ease of changing (remembering), how it is to be used, likelihood of impact on upgrade, how soon it's needed, impact on sales if not immediately implemented, etc...
Anyways, was just some more ideas and discussion. Application can be made any number of ways... I'm not at a computer to easily chase down the file(s) in which the above echo statement(s) would best be suited and not as famliar with that fileset to provide specifics.
Bookmarks