One could also use the notifier/observer system to address overriding the code obtained from includes/templates/YOUR_TEMPLATE/common/main_template_vars.php assuming it has been updated with applicable changes from the template_default directory.
There are two notifiers, one when coming into the file where the $template_dir is provided and the $current_base could be obtained, then there is one at the end that passes the editable $body_code. There are a few different directions one could go with this.
Could temporarily substitute the $current_page_base with one that doesn't exist, but for which the associated tpl_ file does. Then change it back when leaving the code. (con to this is if any other observer is loaded and expects to properly use the variable, then load sequence would be a concern).
At the conclusion of execution could use the exit notifier to set/reset the $body_code to whatever desired file if the $current_page_base is 'specials' and the $template_dir is 'my_template'. Could go and load additional files without "undoing" other things if the $current_page_base is 'specials' and $template_dir is 'my_template' or just in general or when loading the specials page.
In this way an additional file check would not be needed for each page load like is suggested in the other thread, but instead one or more variable checks with whatever action to follow and no template directory override. Just saying that there are ways without digging into code that would have to be compared against for the next version, though the code would still need to be reviewed to be sure it was compatible or needed changes.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
