[solved] problem upgrading from 1.4 to 1.5.4
[solved] problem upgrading from 1.4 to 1.5.4
I'm upgrading from 1.4 to 1.5.4
The initial errors on the first page say:
> string(123) "Smarty error: [in upgradeheader.tpl line 25]: syntax error: unrecognized tag 'assign' (Smarty_Compiler.class.php, line 590)"
and
> string(117) "Smarty error: [in upgrade1.tpl line 19]: syntax error: unrecognized tag 'cycle' (Smarty_Compiler.class.php, line 590)"
checksum gives multiple warnings that all say:
> Warning: date_format() expects parameter 1 to be DateTime, integer given in /home/content/w/r/k/wrk/html/tmp/templates_c/%%0B^0B9^0B9E1D2A%%upgrade1.tpl.php on line 40
I'd appreciate any suggestions.
thanks,
Courtney
The initial errors on the first page say:
> string(123) "Smarty error: [in upgradeheader.tpl line 25]: syntax error: unrecognized tag 'assign' (Smarty_Compiler.class.php, line 590)"
and
> string(117) "Smarty error: [in upgrade1.tpl line 19]: syntax error: unrecognized tag 'cycle' (Smarty_Compiler.class.php, line 590)"
checksum gives multiple warnings that all say:
> Warning: date_format() expects parameter 1 to be DateTime, integer given in /home/content/w/r/k/wrk/html/tmp/templates_c/%%0B^0B9^0B9E1D2A%%upgrade1.tpl.php on line 40
I'd appreciate any suggestions.
thanks,
Courtney
Last edited by quartney on Mon Apr 20, 2009 5:15 pm, edited 1 time in total.
Re: problem upgrading from 1.4 to 1.5.4
I would try to upload your files again maybe delete all of the files out of the templates_c directory as well.
If all else fails, use a bigger hammer.
M@rtijn wrote: This is a community. This means that we work together and have the same goal (a beautiful CMS), not that we try to put people down and make their (voluntary) job as difficult as can be.
Re: problem upgrading from 1.4 to 1.5.4
I have uploaded all the files again, cleared the cache, deleted files from templates_c ... and I have the same errors. Here is a checksum screenshot:


Re: problem upgrading from 1.4 to 1.5.4
Try reading through this post to see if it helps out: http://forum.cmsmadesimple.org/index.ph ... .msg152891
If that doesn't work I would delete the entire TinyMCE directory, re-upload it and check the permissions again.
If that doesn't work I would delete the entire TinyMCE directory, re-upload it and check the permissions again.
If all else fails, use a bigger hammer.
M@rtijn wrote: This is a community. This means that we work together and have the same goal (a beautiful CMS), not that we try to put people down and make their (voluntary) job as difficult as can be.
Re: problem upgrading from 1.4 to 1.5.4
I did all that and did what Mark suggested here.
http://forum.cmsmadesimple.org/index.ph ... #msg136539
Nothing has changed.
http://forum.cmsmadesimple.org/index.ph ... #msg136539
Nothing has changed.
Re: problem upgrading from 1.4 to 1.5.4
Also, does this screenshot of the admin window give a clue as to what's happening?


Re: problem upgrading from 1.4 to 1.5.4
Have you check in Global Settings > System Information and System Verification?quartney wrote: Also, does this screenshot of the admin window give a clue as to what's happening?
IMHO: you have some problem with permissions of modules folder
Alby
Re: problem upgrading from 1.4 to 1.5.4
In a prior post, Mark said:
> Had to set modules and tiny folders to 755, and tmp to 777...
and I did that. Now, I just set every folder in modules to 755 and nothing changed. Then, I set modules folder to 777 and nothing changed. I cleared the cache along the way.
> Had to set modules and tiny folders to 755, and tmp to 777...
and I did that. Now, I just set every folder in modules to 755 and nothing changed. Then, I set modules folder to 777 and nothing changed. I cleared the cache along the way.
Re: problem upgrading from 1.4 to 1.5.4
System information says:alby wrote: Have you check in Global Settings > System Information and System Verification?
> string(55) "Smarty error: unable to read resource: "systeminfo.tpl""
System verification says:
> string(53) "Smarty error: unable to read resource: "checksum.tpl""
Re: problem upgrading from 1.4 to 1.5.4
In response to the same problem as above:
http://forum.cmsmadesimple.org/index.ph ... 527.0.html
Alby says:
re-upload cmsms and look your system logs
Now I just need to find out where my system logs are ...
http://forum.cmsmadesimple.org/index.ph ... 527.0.html
Alby says:
re-upload cmsms and look your system logs
Now I just need to find out where my system logs are ...

Re: problem upgrading from 1.4 to 1.5.4
I am still going to stick by the fact that you are having upload problems and/or permissions problems.
If all else fails, use a bigger hammer.
M@rtijn wrote: This is a community. This means that we work together and have the same goal (a beautiful CMS), not that we try to put people down and make their (voluntary) job as difficult as can be.
Re: problem upgrading from 1.4 to 1.5.4
You have some troubles .....quartney wrote:System information says:alby wrote: Have you check in Global Settings > System Information and System Verification?
> string(55) "Smarty error: unable to read resource: "systeminfo.tpl""
System verification says:
> string(53) "Smarty error: unable to read resource: "checksum.tpl""
Upload file that you find in install folder (install/cmschecksum.php) in root folder of your installation and calling via browser.
It's a standalone version of checksum test
Alby
Re: problem upgrading from 1.4 to 1.5.4
is there a better way to upload than ftp? I first uploaded via dreamweaver ftp and then via winscp.
this checksum shows a bunch of stuff missing.
this checksum shows a bunch of stuff missing.
Last edited by quartney on Fri Apr 17, 2009 3:51 pm, edited 1 time in total.
Re: problem upgrading from 1.4 to 1.5.4
depend of your provider.quartney wrote: is there a better way to upload than ftp? I first uploaded via dreamweaver ftp and then via winscp.
Many have a panel tools with file management, ssh access or other things
Alby
Re: problem upgrading from 1.4 to 1.5.4
If you have CPanel access use the filemanager there to upload the tar.gz file and then unpack that file directly from the filemanager. It will save you loads of time and reduce the chance for corrupted files dramatically.
If all else fails, use a bigger hammer.
M@rtijn wrote: This is a community. This means that we work together and have the same goal (a beautiful CMS), not that we try to put people down and make their (voluntary) job as difficult as can be.