Page 1 of 2
[open] Template error after upgrade
Posted: Thu Aug 07, 2014 8:18 pm
by oliver341
I got the attached template error after upgrading a fully working site to 2.0. There were no reported errors during the upgrade process.
In Content Manager, all pages had "** ERROR **" in the template column.
Error messages pasted below (same as screenshot).
----------------------
ERROR: at line 127 in file /var/www/html/lib/smarty/sysplugins/smarty_internal_templatebase.php:
Unable to load template tpl_top '24'
#0 /var/www/html/lib/classes/internal/class.Smarty_CMS.php(306): Smarty_Internal_TemplateBase->fetch('tpl_top:24', 'p15', NULL, NULL, false, false, false)
#1 /var/www/html/index.php(169): Smarty_CMS->fetch('tpl_top:24')
#2 {main}
Re: Template error after upgrade
Posted: Thu Aug 07, 2014 8:22 pm
by calguy1000
Care to share the template?
Note: We are aware that not all sites will upgrade cleanly. But for simple sites, there should be few problems.
Re: Template error after upgrade
Posted: Thu Aug 07, 2014 9:02 pm
by oliver341
How do I share the template? Go into Edit Template and copy/paste everything in the Content box?
Re: Template error after upgrade
Posted: Tue Aug 19, 2014 3:58 pm
by paulbaker
Yes, inside [ code ] code forum tags [ /code ].
Re: Template error after upgrade
Posted: Tue Jan 13, 2015 12:31 pm
by Rolf
Could you please re-test this issue in the Beta 3 release?
Thanks, Rolf
Re: Template error after upgrade
Posted: Tue Jan 13, 2015 3:55 pm
by oliver341
Hi again.
I installed the beta3 upgrade using the phar. There were no reported issues by the installer during upgrade.
However, post-upgrade when I attempted to load the site, I got a blank white page.
Error log reported:
Code: Select all
[Tue Jan 13 15:55:10 2015] [error] [client 192.168.1.64] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 49152 bytes) in /var/www/modules/MenuManager/action.default.php on line 94
Re: Template error after upgrade
Posted: Tue Jan 13, 2015 5:03 pm
by oliver341
I just noticed there is a new CMSMS version, I am on 1.11.11. I'll upgrade and re-test.
Re: Template error after upgrade
Posted: Tue Jan 13, 2015 5:51 pm
by oliver341
Same error as before when upgrading from 1.11.12.
Code: Select all
[Tue Jan 13 17:50:42 2015] [error] [client 192.168.1.64] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 49152 bytes) in /var/www/modules/MenuManager/action.default.php on line 94
Re: Template error after upgrade
Posted: Tue Jan 13, 2015 6:54 pm
by jce76350
Re: Template error after upgrade
Posted: Tue Jan 13, 2015 7:16 pm
by oliver341
Maybe. Certainly it's MenuManager related, as the error would suggest. Uninstalling the MenuManager module breaks the {menu} tag.
Is there a solution for this?
Re: [open] Template error after upgrade
Posted: Tue Jan 13, 2015 7:59 pm
by jce76350
Uninstalling the MenuManager module breaks the {menu} tag.
so replace the tag {menu ... by {Navigator ...
Note : "
A new module for building navigations (Navigator)"
Re: [open] Template error after upgrade
Posted: Tue Jan 13, 2015 8:42 pm
by oliver341
Thanks, I have swapped out {menu} for {Navigator}.
New error though:
Code: Select all
[Tue Jan 13 20:39:24 2015] [error] [client 192.168.1.64] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 130968 bytes) in /var/www/lib/classes/class.cms_config.php on line 496
The second and subsequent refresh give this:
Code: Select all
[Tue Jan 13 20:40:41 2015] [error] [client 192.168.1.64] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16384 bytes) in /var/www/lib/smarty/sysplugins/smarty_internal_templatebase.php on line 174
Re: [open] Template error after upgrade
Posted: Tue Jan 13, 2015 9:10 pm
by oliver341
And now I'm getting this.
Code: Select all
[Tue Jan 13 21:09:19 2015] [error] [client 192.168.1.64] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 49152 bytes) in /var/www/modules/Navigator/action.default.php on line 168
Re: [open] Template error after upgrade
Posted: Wed Jan 14, 2015 5:29 pm
by jce76350
A problem of Allowed memory in PHP
Try to delete some modules if possible
Re: [open] Template error after upgrade
Posted: Wed Jan 14, 2015 6:07 pm
by oliver341
I don't think that's the reason. I have a modest selection of modules and no issues at all on 1.11.12. I even boosted the memory limit to 256 MB and got this.
Code: Select all
[Wed Jan 14 18:03:31 2015] [error] [client 192.168.1.64] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /var/www/lib/smarty/sysplugins/smarty_internal_templatebase.php on line 178
Module list.
Code: Select all
----------------------------------------------
Cms Version: 2.0-beta3
Installed Modules:
CMSMailer: 5.2.4
FileManager: 1.5
MenuManager: 1.50
ModuleManager: 2.0
News: 2.50
Search: 1.50
ThemeManager: 1.1.8
Captcha: 0.5.0
FormBuilder: 0.8
MicroTiny: 2.0
AdminSearch: 1.0
CGExtensions: 1.44.5
CGJobMgr: 1.3.4
NMS: 2.9.5
Banners: 2.6.1
CGSimpleSmarty: 1.7.4
CGFeedback: 1.6.8
ExtendedTools: 1.3.3
RSSSimplePie: 1.0
JQueryTools: 1.3.4
CGBlog: 1.12.9
CMSContentManager: 1.0
DesignManager: 1.0
Navigator: 1.0
Config Information:
php_memory_limit:
max_upload_size: 2000000
url_rewriting: none
page_extension:
query_var: page
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true
timezone: Europe/London
Php Information:
phpversion: 5.4.36-0+deb7u3
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference:
test_db_timedifference:
memory_limit: 256M
max_execution_time: 60
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 8M
upload_max_filesize: 2M
session_save_path: /var/lib/php5 (1733)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
Server Information:
Server Api: apache2handler
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.40
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No file system time difference found
----------------------------------------------