PHP Error

[geach]

I checked my php error log and found an error I can't make sense of on error that keeps showing up.

The error is

PHP Catchable fatal error: Argument 1 passed to Smarty_Resource::buildUniqueResourceName() must be an instance of Smarty, instance of Smarty_Internal_Template given, called in \lib\smarty\sysplugins\smarty_internal_templatebase.php on line 180 and defined in \lib\smarty\sysplugins\smarty_resource.php on line 102

I am not sure how to fix/prevent this error. Is there anything I can do to fix or prevent this error from happening?

We run cmsms on windows with IIS7. The system information is:

Cms Version: 1.11.6

Installed Modules:

CMSMailer: 5.2.1
FileManager: 1.4.3
MenuManager: 1.8.5
TinyMCE: 2.9.12
Archiver: 0.2.6
CodePress: 0.1.2
CGExtensions: 1.32.6
ModuleManager: 1.5.5
Album: 0.9.3
News: 2.12.12
Uploads: 1.14.4
XMLMadeSimple: 0.1.2
CMSPrinting: 1.0.4
MicroTiny: 1.2.5
Search: 1.7.8
ThemeManager: 1.1.8
CGFeedMaker: 1.0.17
HostedVideoAlbums: 2.4.3
AceEditor: 0.2.5
JQueryTools: 1.2.5


Config Information:

php_memory_limit:
process_whole_template:
output_compression: false
max_upload_size: 2000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale: en_US
default_encoding:
admin_encoding: utf-8
set_names: true


Php Information:

phpversion: 5.4.10
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
memory_limit: 128M
max_execution_time: 300
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 8M
upload_max_filesize: 2M
session_save_path: D:\PHP\session (0777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)


Server Information:

Server Api: cgi-fcgi
Server Db Type: MySQL (mysql)
Server Db Version: 5.0.51b
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable

[calguy1000]

I would suspect that one of the plugins, UDT's or modules you are using isn't behaving properly.

You will probably need to isolate it down to which one.

I recommend that you:
a: find out which page request is generating the warning
b: copy the page template to a new name
c: copy the page to a new name (maybe make it hidden).
d: change the new page created in (c) to use the page template created in (b)
e: start trimming things out of the page, and page template until the problem
no longer occurs.

This will allow you to find the badly behaving plugin, UDT, or module.... and we can help you further.