Serendipity Forums

yellowled wrote:I remember asking that we had the ability to choose separate templates for both the front and back ends... are you saying we now have that?

yellowled wrote:Are you also saying that your new front end template does not also have a matching backend/admin template?

• set $serendipity['defaultTemplate'] = 2k11 in serendipity_config.inc
• have my own template = myTemplate choosen as the main template
• and disabled INCLUDE_ANY settings in plugins (which has nothing to do with the further... ). To check this, I disabled myTemplate/default_staticpage.tpl. Now the Fallback follows the concept and looks into the next, this is $serendipity['defaultTemplate'] == 2k11. This would not be a problem if 2k11 would not have this serendipity_smarty_html5time modifier.

            $serendipity['smarty']->template_dir  = array($template_dir);
+            $serendipity['smarty']->template_dir[] = $serendipity['serendipityPath'] . $serendipity['templatePath'] . $serendipity['defaultTemplate'];
            $p = explode(',', $serendipity['template_engine']);
            foreach($p AS $te) {
                $serendipity['smarty']->template_dir[] = $serendipity['serendipityPath'] . $serendipity['templatePath'] . $te;
            }
            $serendipity['smarty']->template_dir[] = $serendipity['serendipityPath'] . $serendipity['templatePath'] . 'default';
+            $serendipity['smarty']->template_dir   = array_merge(array(), array_unique($serendipity['smarty']->template_dir));
            $serendipity['smarty']->compile_dir   = $serendipity['serendipityPath'] . PATH_SMARTY_COMPILE;

Timbalu wrote:The only secure way to pass by the mentioned problem having 2k11 as defaultTemplate and using some other template as (main)template, with the case of (staticpage) tpl fallback to2k11, is to add it to cores functions_smarty.inc [...] and get rid of it in 2k11's config. (if it is a must have feature!)

* Use $smarty.const. to access constants instead of $CONST within
Smarty templates; this is replaced using a Smarty prefilter, so
that within templates you can still use the $CONST shortcut
(garvinhicking)

Timbalu wrote:As 2k11 is going to be the standard and standard copy template, we could start here to cut off some antiquated traditions!

{assign var="navtitle" value=$CONST.TWOK11_NAV_TITLE}
[...]
<h2 class="visuallyhidden">{$navtitle}</h2>

<h2 class="visuallyhidden">{$smarty.const.TWOK11_NAV_TITLE}</h2>

yellowled wrote:Let's see if I get this: Instead of using

Code: Select all

{assign var="navtitle" value=$CONST.TWOK11_NAV_TITLE}
[...]
<h2 class="visuallyhidden">{$navtitle}</h2>

I can use

Code: Select all

<h2 class="visuallyhidden">{$smarty.const.TWOK11_NAV_TITLE}</h2>

..?

garvinhicking wrote:Why would you use this assign syntax in first place?

Timbalu wrote:The only secure way to pass by the mentioned problem having 2k11 as defaultTemplate and using some other template as (main)template, with the case of (staticpage) tpl fallback to2k11, is to add it to cores functions_smarty.inc

Code: Select all

$serendipity['smarty']->register_modifier('html5time', 'serendipity_smarty_html5time');

and

Code: Select all

function serendipity_smarty_html5time($timestamp) {
   return date("c", $timestamp);
}

and get rid of it in 2k11's config.

require_once or include_once('addCode.php');

if (!function_exists('serendipity_smarty_html5time')) { 
    function serendipity_smarty_html5time($timestamp) { return date("c", $timestamp); }

    if( defined('Smarty::SMARTY_VERSION') ) {
        $serendipity['smarty']->registerPlugin('modifier', 'serendipity_html5time', 'serendipity_smarty_html5time');
    } else {
        // old Smarty 2 syntax
        $serendipity['smarty']->register_modifier('serendipity_html5time', 'serendipity_smarty_html5time');
    }
}