You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fatal error: Type of SmartyCompilerException::$line must be int (as in class Exception) in F:\xampp\htdocs\xoops2511\class\libraries\vendor\smarty\smarty\libs\sysplugins\smartycompilerexception.php on line 8
#1329
Open
Neil-hsu-168 opened this issue
Apr 8, 2023
· 3 comments
I downloaded the latest Xoops 2.5.11 update version released on April 6 and encountered the following error when upgrading my local Xoops installation:
Fatal error: Type of SmartyCompilerException::$line must be int (as in class Exception) in F:\xampp\htdocs\xoops2511\class\libraries\vendor\smarty\smarty\libs\sysplugins\smartycompilerexception.php on line 8
My local environment is as follows:
XOOPS version: XOOPS 2.5.11
PHP version: 8.1.12
MySQL version: 10.4.27-MariaDB
Could you please advise on what might have caused this error? Thank you!
The text was updated successfully, but these errors were encountered:
Hi,
This is a compatibility problem with smarty 3. There are several possible causes:
Your theme is not up to date (not smarty3 compatible), in this case you have to modify your theme to make it compatible or use for example the xswatch theme.
One or more modules are not yet compatible with smarty3. In this case you have to deactivate the modules and activate them one by one to see which one is the problem.
I downloaded the latest Xoops 2.5.11 update version released on April 6 and encountered the following error when upgrading my local Xoops installation:
Fatal error: Type of SmartyCompilerException::$line must be int (as in class Exception) in F:\xampp\htdocs\xoops2511\class\libraries\vendor\smarty\smarty\libs\sysplugins\smartycompilerexception.php on line 8
My local environment is as follows:
XOOPS version: XOOPS 2.5.11
PHP version: 8.1.12
MySQL version: 10.4.27-MariaDB
Could you please advise on what might have caused this error? Thank you!
The text was updated successfully, but these errors were encountered: