[SOLVED] Upgrading from 1.6.3
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
[SOLVED] Upgrading from 1.6.3
Hi all.
Helping a friend upgrade.
Currently on 1.6.3.
Looking at the upgrade page, it seems to only have the option for upgrading 1.6.7. Is there an upgrade package for 1.6.3?
And how much is it for assistance on this project ?
-Steven
Helping a friend upgrade.
Currently on 1.6.3.
Looking at the upgrade page, it seems to only have the option for upgrading 1.6.7. Is there an upgrade package for 1.6.3?
And how much is it for assistance on this project ?
-Steven
Last edited by stevenryals on Tue Oct 20, 2015 8:56 pm, edited 3 times in total.
Re: Upgrading from 1.6.3
The mentioned versions are the latest of those 'major' versions. So latest of 1.6.x, latest of 1.7.x etc
Make sure you have a backup of files and database before upgrading!
You can first upgrade to 1.6.7 using the diff packages (no need to do database updates):
cmsmadesimple-base-diff-1.6.3-1.6.5.tar.gz or cmsmadesimple-full-diff-1.6.3-1.6.5.tar.gz
then
cmsmadesimple-base-diff-1.6.5-1.6.6.tar.gz or cmsmadesimple-full-diff-1.6.5-1.6.6.tar.gz
then
cmsmadesimple-base-diff-1.6.6-1.6.7.tar.gz or cmsmadesimple-full-diff-1.6.6-1.6.7.tar.gz
Full has a lot of extra language file
Base is English only
BTW: I would expect that using
cmsmadesimple-1.6.7-base.tar.gz or cmsmadesimple-1.6.7-full.tar.gz
to overwrite your installation would have the same effect (remove 'install' folder afterwards)
Of course you need to check system requirements and 3rd party module dependencies too.
Make sure you have a backup of files and database before upgrading!
You can first upgrade to 1.6.7 using the diff packages (no need to do database updates):
cmsmadesimple-base-diff-1.6.3-1.6.5.tar.gz or cmsmadesimple-full-diff-1.6.3-1.6.5.tar.gz
then
cmsmadesimple-base-diff-1.6.5-1.6.6.tar.gz or cmsmadesimple-full-diff-1.6.5-1.6.6.tar.gz
then
cmsmadesimple-base-diff-1.6.6-1.6.7.tar.gz or cmsmadesimple-full-diff-1.6.6-1.6.7.tar.gz
Full has a lot of extra language file
Base is English only
BTW: I would expect that using
cmsmadesimple-1.6.7-base.tar.gz or cmsmadesimple-1.6.7-full.tar.gz
to overwrite your installation would have the same effect (remove 'install' folder afterwards)
Of course you need to check system requirements and 3rd party module dependencies too.
Re: Upgrading from 1.6.3
You can go directly to 1.6.7
http://docs.cmsmadesimple.org/upgrading ... ions#1.5.4
http://docs.cmsmadesimple.org/upgrading ... ions#1.5.4
- + - + - + - + - + - + -
LATEST TUTORIAL AT CMS CAN BE SIMPLE:
Migrating Company Directory module to LISE
Migrating Company Directory module to LISE
- + - + - + - + - + - + -
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
Re: Upgrading from 1.6.3
Thanks guys, that's exactly the help I needed.
Too bad I can't skip all the subsequent versions and go straight to the latest.. looks like 5 or 6 upgrades to get where they need to be :0
Too bad I can't skip all the subsequent versions and go straight to the latest.. looks like 5 or 6 upgrades to get where they need to be :0
Re: Upgrading from 1.6.3
It depends on the third party modules you use on the website...
- + - + - + - + - + - + -
LATEST TUTORIAL AT CMS CAN BE SIMPLE:
Migrating Company Directory module to LISE
Migrating Company Directory module to LISE
- + - + - + - + - + - + -
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
Re: Upgrading from 1.6.3
I'll be patient and go one by one.
I just loaded the 1.6.7 files and my site says:
Site down for maintenance.
Also: many of the admin functions are broken:
system verification > "Smarty error: unable to read resource: "checksum.tpl""
they all say "smarty error... unable to read xxxxxxx.tpl"
Any clues here?
I just loaded the 1.6.7 files and my site says:
Site down for maintenance.
Also: many of the admin functions are broken:
system verification > "Smarty error: unable to read resource: "checksum.tpl""
they all say "smarty error... unable to read xxxxxxx.tpl"
Any clues here?
Re: Upgrading from 1.6.3
And how did you do that? FTP?stevenryals wrote: just loaded the 1.6.7 files (...)
"There are 10 types of people in this world, those who understand binary... and those who don't."
* by the way: English is NOT my native language (sorry for any mistakes...).
Code of Condut | CMSMS Docs | Help Support CMSMS
My developer Page on the Forge
GeekMoot 2015 in Ghent, Belgium: I was there!
GeekMoot 2016 in Leicester, UK: I was there!
DevMoot 2023 in Cynwyd, Wales: I was there!
* by the way: English is NOT my native language (sorry for any mistakes...).
Code of Condut | CMSMS Docs | Help Support CMSMS
My developer Page on the Forge
GeekMoot 2015 in Ghent, Belgium: I was there!
GeekMoot 2016 in Leicester, UK: I was there!
DevMoot 2023 in Cynwyd, Wales: I was there!
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
Re: Upgrading from 1.6.3
I'm sorry, yes, FTP. I extracted the files from the 1.6.7 Base tar to my local machine and pushed them to my FTP client.
I'm currently scouring the site to find the details of how to run the checksum test, but not having much luck. I'm assuming, from what I've been reading, that this should be my next step.
(FYI Admin > System Information give me:
string(55) "Smarty error: unable to read resource: "systeminfo.tpl"" )
I'm currently scouring the site to find the details of how to run the checksum test, but not having much luck. I'm assuming, from what I've been reading, that this should be my next step.
(FYI Admin > System Information give me:
string(55) "Smarty error: unable to read resource: "systeminfo.tpl"" )
Re: Upgrading from 1.6.3
FTP:
Not doing so can result in many corrupt files.
Just find the binary mode option of your FTP client and upload agina (make sure to overwrite all files)
source: http://docs.cmsmadesimple.org/installation/upload-filesNote: Be sure to upload the installer file in "binary" mode. Do not chose "auto" or ASCII.
Not doing so can result in many corrupt files.
Just find the binary mode option of your FTP client and upload agina (make sure to overwrite all files)
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
Re: Upgrading from 1.6.3
Cool.. I wouldn't have found that.
Reverted to 1.6.3. Still some errors, but able to get on admin without those *.tpl access issues..
Uploaded 1.6.7 files via binary ftp (filezilla)
ran 1.6.7 checksup : All checksums match those in the uploaded file
Template is destroyed lol
site is saying "site down for maintenenace", however, Site Admin > Global Settings: shows that enable system down messgae is not selected.. hmmmmm.....
Reverted to 1.6.3. Still some errors, but able to get on admin without those *.tpl access issues..
Uploaded 1.6.7 files via binary ftp (filezilla)
ran 1.6.7 checksup : All checksums match those in the uploaded file
Template is destroyed lol
site is saying "site down for maintenenace", however, Site Admin > Global Settings: shows that enable system down messgae is not selected.. hmmmmm.....
Re: Upgrading from 1.6.3
- Clear CMSMS cache
- check for existence of \tmp\cache\SITEDOWN (file) and remove it
- check for existence of \tmp\cache\SITEDOWN (file) and remove it
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
Re: Upgrading from 1.6.3
OK, i'm up to 1.12.1 now. I guess that's the most up to date I can get until the upgrade package is release, correct?
The site now says:
Oops!
Sorry, it looks like something went wrong and an error has occurred.
Don’t worry, it can happen to any of us.
Error: at line 28 in file /home/ucruise/public_html/lib/smarty/libs/sysplugins/smarty_internal_templatecompilerbase.php:
Syntax error in template "tpl_body:25" on line 28 "
" unknown tag "site_selflink"
Where are all of the tags located? I have a feeling I know what it is.. the previous host prefixed with cms_ the new host prefixes with site_
ETA: Yes, that's it. under Extensions > Tags, it still has the prefix 'cms_' while the error indicates a different prefix..
is it better to correct the tag, or the files containing the other tag?
p.s. it is also the prefix to my database... so that is likely when the error occurred and a grep replace... so i think this is something i can fix with an sql comand, just need to know where all of those tags are located (or the smarty files that call them)
The site now says:
Oops!
Sorry, it looks like something went wrong and an error has occurred.
Don’t worry, it can happen to any of us.
Error: at line 28 in file /home/ucruise/public_html/lib/smarty/libs/sysplugins/smarty_internal_templatecompilerbase.php:
Syntax error in template "tpl_body:25" on line 28 "
" unknown tag "site_selflink"
Where are all of the tags located? I have a feeling I know what it is.. the previous host prefixed with cms_ the new host prefixes with site_
ETA: Yes, that's it. under Extensions > Tags, it still has the prefix 'cms_' while the error indicates a different prefix..
is it better to correct the tag, or the files containing the other tag?
p.s. it is also the prefix to my database... so that is likely when the error occurred and a grep replace... so i think this is something i can fix with an sql comand, just need to know where all of those tags are located (or the smarty files that call them)
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
Re: Upgrading from 1.6.3
OK, so I went through and dropped the entire db..
rebuilt old db.. replacing the prefixes where needed..
I'm so close I think.. lol
It seems there is a custom tag somewhere..
Syntax error in template "tpl_body:29" on line 1126 "{news category='Vacation Blog' pagelimit='4' detailpage='vacation-blog'}" unknown tag "news"
the 'news' tag does not exist under Extensions > Tags or User Defined Tags. When i try to add the 'news' tag to UDTs, it says "Tag Already Esists"
Any idea how I can solve this error?
ETA: News tag is from the 'news' module.. so it should be working. it's upgraded and current and active.. any thoughts?
eta: found some css in the global content block.. it wasn't malformed.. but cms certainly didnt like it.. move it.. and it worked.
---------------------------
rebuilt old db.. replacing the prefixes where needed..
I'm so close I think.. lol
It seems there is a custom tag somewhere..
Syntax error in template "tpl_body:29" on line 1126 "{news category='Vacation Blog' pagelimit='4' detailpage='vacation-blog'}" unknown tag "news"
the 'news' tag does not exist under Extensions > Tags or User Defined Tags. When i try to add the 'news' tag to UDTs, it says "Tag Already Esists"
Any idea how I can solve this error?
ETA: News tag is from the 'news' module.. so it should be working. it's upgraded and current and active.. any thoughts?
eta: found some css in the global content block.. it wasn't malformed.. but cms certainly didnt like it.. move it.. and it worked.

---------------------------
-
- Forum Members
- Posts: 26
- Joined: Wed Apr 17, 2013 6:59 pm
Re: Upgrading from 1.6.3
Final issue.... i think..
I have changed to the new oneEleven template for latest functionality.
I have a few issue:
when i go to Content > Pages > Edit Page, i am directed to: 'editcontent.php?_sx_=76deaee6&content_id=15'
However, i get a 404 error at that page.
(on the old grey template, I get the page, but there is no edit wysiwig box there...)
I get the same 404 error page when i try to Add New Content (addcontent.php?_sx_=76deaee6)
Any thoughts on how to relieve this final issue (hopefully it's the last problem until the upgrade to 2.x.x is available.
I have changed to the new oneEleven template for latest functionality.
I have a few issue:
when i go to Content > Pages > Edit Page, i am directed to: 'editcontent.php?_sx_=76deaee6&content_id=15'
However, i get a 404 error at that page.
(on the old grey template, I get the page, but there is no edit wysiwig box there...)
I get the same 404 error page when i try to Add New Content (addcontent.php?_sx_=76deaee6)
Any thoughts on how to relieve this final issue (hopefully it's the last problem until the upgrade to 2.x.x is available.

Re: Upgrading from 1.6.3
Make sure any template used on pages have the old {stylesheet} tag changed to the new {cms_stylesheet} tag...