Having installed V2.2.20 on a site originally built in 2.2.0 or thereabouts, it does not seem to be compatible with earlier template types or page types
I have found the following:
1) Site will not load if the previous site had a default Error Page (Content Type = Error Page). Error seen:
Parse error: syntax error, unexpected 'var' (T_VAR) in /home/customer/www/harwilassociates.co.uk/public_html/lib/classes/contenttypes/ErrorPage.inc.php on line 36
2) Site will load if I remove error Page before upgrade but then starts throwing PHP/Smarty errors as follows:
Deprecated: Using unregistered function "implode" in a template is deprecated and will be removed in a future release. Use Smarty::registerPlugin to explicitly register a custom modifier. in /home/customer/www/harwilassociates.co.uk/public_html/lib/smarty/sysplugins/smarty_internal_templatecompilerbase.php on line 651
Deprecated: Using unregistered function "count" in a template is deprecated and will be removed in a future release. Use Smarty::registerPlugin to explicitly register a custom modifier. in /home/customer/www/harwilassociates.co.uk/public_html/lib/smarty/sysplugins/smarty_internal_templatecompilerbase.php on line 651
This has happened on both the sites I have tried to upgrade. They have both been successfully upgraded over the years all the way from 2.2.0 to 2.2.19 with no problems of this kind. Current PHP version is 7.4.33
2.2.20 not compatible with earlier templates or content types
-
- New Member
- Posts: 5
- Joined: Fri Dec 08, 2023 11:16 am
Re: 2.2.20 not compatible with earlier templates or content types
I haven't heard of the error page issue, if you can produce this reliably on a clean site (e.g. nothing special on the error page itself) then please file a bug report with steps to reproduce.
For the Deprecated warnings, please see the release announcement for 2.2.20 (viewtopic.php?t=84035). The short-term solution is to not have deprecated warnings logged on production sites.
For the Deprecated warnings, please see the release announcement for 2.2.20 (viewtopic.php?t=84035). The short-term solution is to not have deprecated warnings logged on production sites.
Not getting the answer you need? CMSMS support options
Re: 2.2.20 not compatible with earlier templates or content types
[edited by admin as core code changes should not be posted on the forum - use the bug tracker instead]
http://dev.cmsmadesimple.org/bug/view/12712
http://dev.cmsmadesimple.org/bug/view/12712
-
- New Member
- Posts: 5
- Joined: Fri Dec 08, 2023 11:16 am
Re: 2.2.20 not compatible with earlier templates or content types
Editing ErrorPage.inc.php as suggested by creopard
[edited by admin as core code changes should not be posted on the forum - use the bug tracker instead]
http://dev.cmsmadesimple.org/bug/view/12712
Resolves the issue of sites not loading where Content Type Error page is used.
[edited by admin as core code changes should not be posted on the forum - use the bug tracker instead]
http://dev.cmsmadesimple.org/bug/view/12712
Resolves the issue of sites not loading where Content Type Error page is used.