|
Wednesday 17 October 2007 9:27:57 am
Thanks for your reply, Betsy. I will definitely give it a deeper look. Meanwhile, I think I have come up with a solution that maybe will not stand a universal one, but may fit into our hosting environment configuration. Just in theory for now: 1) I configure my HTTP server so that a given domain and any user-dynamically-created subdomains of any level direct the root of the installation. That will probably require a wildcard of some kind. Lets say, I've got a <b>domain.com</b> domain and I setup a <b>*.domain.com</b> rule, meaning * can be anything.
2) I create a mod_rewrite rule which reads the requested SERVER_NAME and extracts (and validates/secures) whatever the subdomain part name is (if there is anything in place of <b>*</b>), and redirects to something like this:
<i>/domain.com/index.php/default_siteaccess/content/view/subdomain/(name)/*</i>
where * is whatever the subdomain was.
For example:
<i>letstry.domain.com</i> <b>is rewritten to</b> <i>/domain.com/index.php/mysite/content/view/subdomain/(name)/letstry</i> 3) Now it's easy to create a template override for a given class and for the mode "subdomain" of the view view of content module. I can easily grab the value of "name" parameter, and it all gets down to is a fetch in the template (a "subdomain" attribute in the class would be useful). ---
I still have to make this empirical, but I have good feelings about it ;)
Will get back to this issue ;)
--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu
|