☆ A M B ☆
☆ A M B ☆
$cacheFile= "assets/cache/docid_" . $id . ".pageCache.php";
$domains = array(
'en' => array('English','mysite.com','ltr'),
'fr' => array('Français','fr.mysite.com','ltr'),
);
# what's the URI of the current page?
$url = $_SERVER['REQUEST_URI'];
# what's the name of the server?
$server = $domains['en'][1]; // English by default
$language = 'en';
# check that the server name is in the predefined array before assigning it
# to prevent injection via headers
foreach ($domains as $key => $value) {
if ($value[1] == $_SERVER["HTTP_HOST"]) {
$server = $value[1];
$language = $key;
}
}
foreach ($domains as $key => $value) {
if ($key != $language) {
$pattern = '/\<lang_'.$key.'\>(.*)\<\/lang_'.$key.'\>/Usi';
$modx->documentOutput = preg_replace($pattern,'',$modx->documentOutput);
} else {
// remove the wrapping tags on remaining content
$patterns = array('<lang_'.$key.'>','</lang_'.$key.'>');
$modx->documentOutput = str_replace($patterns,'',$modx->documentOutput);
}
}
☆ A M B ☆
<screen><!--normal template--></screen><mobile><!--mobile template goes here---></mobile>
☆ A M B ☆
<!-- this is my template --> <mobile> <html><head><title>[*pagetitle*]</title></head><body><!-- super simple streamlined formatting --> </moble> <standard> <html><head><title>[*pagetitle*]</title></head><body><!-- standard, graphic intensive formatting --> </standard>
Yes.
So, in other words, I’d maintain one set of templates for a site, but but within each template, I would have a portion dedicated solely to mobile browsers and a portion dedicated solely to standard "desktop" browsers, e.g.
<!-- this is my template --> <mobile> <html><head><title>[*pagetitle*]</title></head><body><!-- super simple streamlined formatting --> </moble> <standard> <html><head><title>[*pagetitle*]</title></head><body><!-- standard, graphic intensive formatting --> </standard>
The overhead of a single regexp on each page load is minimal. The overhead comes with running the uncacheable content twice.
And then on the OnWebPagePrerender event, I’d find and replace one or the other parts of the template? The cache file would then contain all the full template file, including both the <mobile> and <standard> parts (and the page content). Caching would function normally on any page, yes? This is a fascinating approach... I just worry about the overhead of regexing each page request, but I imagine it’s much speedier to regex a cache file than it is to re-render everything from scratch.
Yes.
Using the OnWebPagePrerender poses some changes too... currently, I’m using the OnLoadWebDocument to override the standard template with a mobile template based on either a URL parameter, a cookie value, or a browser detection script. By shifting to the <mobile> vs. <standard> dual-purpose templates, I could still rely on the URL parameters/cookie values/browser-detection scripts, but the result would determine which portion of the template to erase. Am I understanding this correctly?
You could put your individual templates in chunks and do something like:
The only drawback I can see here is UI for the designers: templates would become 2 in 1 hybrids, possibly making them more confusing to work with.
<!-- this is my template -->
<mobile>{{mobile_tpl}}</moble>
<standard>{{standard_tpl}}</standard>
☆ A M B ☆
