Jump to content

Why smarty won't find my template file?


Go to solution Solved by davidolson,

Recommended Posts

Why smarty won't find my template file?

Fatal error: Uncaught --> Smarty: Unable to load template file 'test.tpl' <-- thrown in C:\xampp\htdocs\testing\includes\smarty\sysplugins\smarty_internal_templatebase.php on line 129

also did testinstall

$smarty->testInstall();
Smarty Installation test...
Testing template directory...
C:\xampp\htdocs\testing\templates\frontend\default\tpl is OK.
Testing compile directory...
C:\xampp\htdocs\testing\templates_c\frontend is OK.
Testing plugins directory...
C:\xampp\htdocs\testing\includes\smarty\plugins is OK.
Testing cache directory...
C:\xampp\htdocs\testing\cache is OK.
Testing configs directory...
C:\xampp\htdocs\testing\configs is OK.
Testing sysplugin files...
... OK
Testing plugin files...
... OK
Tests complete.

And get template dir

var_dump($smarty->getTemplateDir());

array(1) { [0]=> string(55) "C:/xampp/htdocs/testing/templates/frontend/default/tpl\" }

 

File schema

htdocs
    -- testing
        -- incluses
            -- smarty
                plugins
                sysplugins
                Smarty.class.php
                SmartyBC.class.php
            -- configs
                configs.php
            -- db
                connect.php
                db.php
        -- configs
        -- cache
        -- templates
            -- frontend
                -- default
                    -- css
                    -- mages
                    -- js
                    -- tpl
                        test.tpl
            -- backend
        -- templates_c
            -- frontend
        index.php

index.php

<?php

ini_set('display_errors', 1);
ini_set('log_errors', 1);
ini_set('display_startup_errors', TRUE);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');
error_reporting(E_ALL);

ob_start();
session_start();

require 'includes/smarty/Smarty.class.php';
require 'includes/db/db.php';
require 'includes/configs/configs.php';

$page = isset($_GET['do']) ? $_GET['do'] : '';

switch($page){
	
	case 'home';
	include 'pages/home.php';
	break;
	
	default:
	include 'pages/test.php';
	break;
	
}

ob_flush();

?>

configs.php

<?php

$smarty = new Smarty();
$smarty->compile_check = true;
$smarty->debugging = false;
$smarty->cache = 1;
$smarty->setTemplateDir('C:/xampp/htdocs/testing/templates/frontend/default/tpl');
$smarty->setCompileDir('C:/xampp/htdocs/testing/templates_c/frontend/default');
$smarty->setCacheDir('C:/xampp/htdocs/testing/cache');
$smarty->setConfigDir('C:/xampp/htdocs/testing/configs'); 

?>

test.php

<?php

//$success = 'Success Message';
//$error = 'Error Message';
$errors[] = 'Error one';
$errors[] = 'Error two';

$smarty = new Smarty;
//$smarty->assign('success', $success);
//$smarty->assign('error', $error);
$smarty->assign('errors', $errors);
$smarty->display('test.tpl');

?>

test.tpl

{if !empty($errors)}
<div id="errors">
{section name=i loop=$errors}
{$errors[i]}<br />
{/section}
</div>
{/if}
Link to comment
https://forums.phpfreaks.com/topic/293458-why-smarty-wont-find-my-template-file/
Share on other sites

In what file is this statement?

var_dump($smarty->getTemplateDir());

 

My guess: in test.php, there is a new instantiation of Smarty in $smarty, quite possibly overwriting the previously existing instantiation of Smarty in $smarty from config.php.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.