upgrade from 1.11.9 to 1.11.10

[staartmees]

Did you clear the website cache after the upgrade?

[chandra]

Upload the lib folder once again. Check your ftp program to use binary mode (NOT ASCII mode).

[Rolf]

How did you upgrade?

[wibby]

I too am getting exactly the same error

Warning: file(/home/host/public_html/lib/smarty/libs/sysplugins/smarty_internal_templatebase.php(151) : eval()'d code) [function.file]: failed to open stream: No such file or directory in /home/host/public_html/lib/misc.functions.php on line 2275

Fatal error: Maximum execution time of 90 seconds exceeded in /home/host/public_html/lib/misc.functions.php on line 2281

Cleaned the cache after the upgrade, made sure it was a binary mode FTP ... even did a fresh install of 1.11.10 Same error

Any help would be greatly appreciated

[Rolf]

System information?

[staartmees]

if you use an UDT in a template, problem could be in an UDT.

[wibby]

Template details:
http://www.cmstemplatebuddy.com/template-for-cmsms/1/

----------------------------------------------
Cms Version: 1.11.10
Installed Modules:
CMSMailer: 5.2.2
CMSPrinting: 1.0.5
FileManager: 1.4.4
MenuManager: 1.8.6
MicroTiny: 1.2.6
ModuleManager: 1.5.5
News: 2.14.2
Search: 1.7.11
ThemeManager: 1.1.8
Gallery: 1.6.1
FormBuilder: 0.7.3

Config Information:
php_memory_limit:
process_whole_template:
max_upload_size: 64000000
url_rewriting: none
page_extension:
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true

Php Information:
phpversion: 5.2.17
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
memory_limit: 256M
max_execution_time: 90
output_buffering: On
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 64M
upload_max_filesize: 64M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)

Server Information:
Server Api: cgi
Server Db Type: MySQL (mysql)
Server Db Version: 5.1.72
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No filesystem time difference found

----------------------------------------------

[tomaszgaluszka]

I installed clear version of 1.11.10 “Pinzon”cms on my server and for the first time page is viewed i got this error message in my browser:
(PHP 5.2.17)

Code: Select all

Warning: file(/home/tomasz/ftp/xxx.tomasz.pl/lib/smarty/libs/sysplugins/smarty_internal_templatebase.php(151) : eval()'d code) [function.file]: failed to open stream: Nie ma takiego pliku ani katalogu in /home/tomasz/ftp/xxx.tomasz.pl/lib/misc.functions.php on line 2275

Fatal error: Maximum execution time of 30 seconds exceeded in /home/tomasz/ftp/xxx.tomasz.pl/lib/misc.functions.php on line 2281

Fatal error: Maximum execution time of 30 seconds exceeded in /home/tomasz/ftp/xxx.tomasz.pl/lib/classes/class.CmsApp.php on line 429

Once again i installed the same clean version direct form cmsms website on my second machine with php 5.3.10 and works fine...

Help me

[staartmees]

It seems you need PHP 5.3.x

[tomaszgaluszka]

So minimum requirement to use yours cms is php > 5.3 ... ?

[staartmees]

Cmsms can run on php 5.2.x but CG-modules need php 5.3.x

[Jo Morg]

So minimum requirement to use yours cms is php > 5.3 ... ?

Well no, not for the core of CMSMS 1.11.x series. But this is a controversial issue: PHP 5.3 has been announced as having ended it's life-cycle:

[...]the PHP 5.3 series will enter an end of life cycle and receive only critical fixes as of March 2013.

Meaning that most of the hosts have already found mechanisms to allow users to switch versions. Persisting in using such an outdated PHP version (let alone 5.2.x) is, not only not advisable feature wise, but it is also a security liability.
That's why a number of module developers are choosing to only support PHP 5.3.x as a minimum. This won't be an issue with CMSMS 2.0: I believe it is only going to support PHP 5.4.x as a minimum.

A few of the errors mentioned above can be caused by a corrupt ftp transference of files, or other similar cause.
A good way to find such problems is to use the checksum file during installation, or later on the admin menu.

[wibby]

Well I'm migrating my servers up to php 5.3.x this evening so I will let you know how the sites go on.

It will be kind of sad if I have to tell my customers that I can't apply any security patches to their sites because of this. Quite a few of them have already expressed a "jumping of ship" to WP... I however really like CMSMS and have built many sites with it for years.. So I will keep trying to bring more customers onboard.

[Jo Morg]

It will be kind of sad if I have to tell my customers that I can't apply any security patches to their sites because of this. Quite a few of them have already expressed a "jumping of ship" to WP...

Actually in shared servers environments usually WP is the weakest link security wise for what I've seen.
It just doesn't make sense to hang to outdated technology, with very very few exceptions, now does it?
Well... just MnsHO...

[Rolf]

It will be kind of sad if I have to tell my customers that I can't apply any security patches to their sites because of this. Quite a few of them have already expressed a "jumping of ship" to WP...

Jumping of ship to another CMS, because of an outdated PHP version? pfff It is actually funny
A very outdated webserver isn't a CMSMS (or even a WP) issue...
The first security patch you have to do is upgrade PHP! You can't upgrade the CMS, because the customers don't want to upgrade the PHP... It is their decision and they are responsible for the consequences.

It is similar like users want the latest HTML5 features but still use IE7 or so. And yes, MS Office 2013 doesn't work on Windows XP, etc. etc. etc.
You can't expect from software/CMS/module developers they support all platforms forever!!

Engineers tend to solve the problem themselves because it seems like the "easiest" way, but they really have to convince customers that only they can solve the real problem!!
To convince someone is another skill than do some coding. IMnsHO the developer need to do the first thing some more, not the second one...