after upgrading version # stays 1.0.2
after upgrading version # stays 1.0.2
Hello,
After upgrading from 1.0.2 to 1.0.4 the version # stays 1.0.2 The upgrade went without any problems.
Anyone a suggstion what this might be?
Thanks,
G
After upgrading from 1.0.2 to 1.0.4 the version # stays 1.0.2 The upgrade went without any problems.
Anyone a suggstion what this might be?
Thanks,
G
Re: after upgrading version # stays 1.0.2
Which upgrade procedure have you followed ? (link?)Gregor wrote: ...The upgrade went without any problems.
Have you cleared your cache at the end ?
Pierre M.
Re: after upgrading version # stays 1.0.2
Thanks for your reply.
I did www.uisge-beatha.eu/install/upgrade.php
By now, the install-directory is now longer available for the outside world. I also cleared the cache and the /tmp directory.
G.
I did www.uisge-beatha.eu/install/upgrade.php
By now, the install-directory is now longer available for the outside world. I also cleared the cache and the /tmp directory.
G.
Last edited by Gregor on Wed Mar 07, 2007 1:46 pm, edited 1 time in total.
Re: after upgrading version # stays 1.0.2
Gregor,
I just passed by your site again and noticed the "Home page, shortcut key" message while hovering your header. This can be removed or changed, by changing the text on the options page of your homepage. The message there is being displayed. Or if empty, the name of your homepage.
How did you see that the version is 1.0.2. in your footer? Did you check wether the "GCB" "footer" or the "UDT" "custom_copyright" is filled. I'm not sure if {cms_version} is used or if 1.0.2 is coded in one of them.
Ronny
I just passed by your site again and noticed the "Home page, shortcut key" message while hovering your header. This can be removed or changed, by changing the text on the options page of your homepage. The message there is being displayed. Or if empty, the name of your homepage.
How did you see that the version is 1.0.2. in your footer? Did you check wether the "GCB" "footer" or the "UDT" "custom_copyright" is filled. I'm not sure if {cms_version} is used or if 1.0.2 is coded in one of them.
Ronny
Re: after upgrading version # stays 1.0.2
Thanks Ronny for the improvement 
The text of the footer is:
G
EDIT: I just ran
As result I got 25.
When upgrading, I copied the new versio files into the install-directory, having overwrite the original files. The result from the upgrade:

The text of the footer is:
It is not in the UDT's, or coded anywhere else. Allthough it is just a number, I'm more concerned if the upgrade went well.© Copyright 2006 - 2007 Gregor
This site is powered by CMS Made Simple version {cms_version} | {cms_selflink page='sitemap' text='Sitemap'}
G
EDIT: I just ran
SQL-query:
SELECT *
FROM `cms_version`
WHERE 1
LIMIT 0 , 30
As result I got 25.
When upgrading, I copied the new versio files into the install-directory, having overwrite the original files. The result from the upgrade:
Does this help?Welcome to the CMS Upgrade System!
In order to upgrade properly, upgrade needs to have write access to your config.php file. This is so any extra settings that have been introduced in this version can be set to their defaults.
Upgrading config.php...[done]
Cleaning cache dirs...[done]
Please review config.php, modify any new settings as necessary and then reset it's permissions back to a locked state. You should also check that all of your modules are up to date, by going to the Extensions -> Modules page and looking for any listed as 'Needs Upgrade'.
The CMS database is up to date using schema version 25. Please remove this file when possible. Click here to go to your CMS site.
Last edited by Gregor on Wed Mar 07, 2007 1:51 pm, edited 1 time in total.
Re: after upgrading version # stays 1.0.2
The link I asked for is a link to the manual/doc/upgrade procedure text explainations, to try to understand where you started from and what you have done so far.
If the version number is not hardcoded in a UDT or GCB but the output of {cms_version}, could it be that what defines {cms_version} was not well FTP uploaded ?
BTW you haven't confirmed that you have cleared the cache.
Pierre M.
If the version number is not hardcoded in a UDT or GCB but the output of {cms_version}, could it be that what defines {cms_version} was not well FTP uploaded ?
BTW you haven't confirmed that you have cleared the cache.
Pierre M.
Re: after upgrading version # stays 1.0.2
@Pierre:
- set the various directoy rights (including config.php)
- I copied the files from the diff-tar into the according directories
- started the upgrade procedure
- set the various rights
The version number is not hard coded, as far as I have seen.
I cleared the cache before upgrading.
Gregor
- set the various directoy rights (including config.php)
- I copied the files from the diff-tar into the according directories
- started the upgrade procedure
- set the various rights
The version number is not hard coded, as far as I have seen.
I cleared the cache before upgrading.
Gregor
Re: after upgrading version # stays 1.0.2
Hello Gregor,
I didn't know these diff-tar. Thank you for the discovery.
I can't think of anything wrong about what you have done. May be the diff-tar is wrong ?
Pierre M.
I didn't know these diff-tar. Thank you for the discovery.
I can't think of anything wrong about what you have done. May be the diff-tar is wrong ?
Pierre M.
Re: after upgrading version # stays 1.0.2
Check version.php in your CMSMS root.Gregor wrote: The version number is not hard coded, as far as I have seen.
Regards,
D
Re: after upgrading version # stays 1.0.2
I checked the 1.0.2-1.0.4 and 1.0.3-1.0.4 diff tarballs and both have a correct version.php included.
Maybe the file didn't get overwritten correctly?
Regards,
D
Maybe the file didn't get overwritten correctly?
Regards,
D
Re: after upgrading version # stays 1.0.2
You're right Dee, I guess the file did not get overwritten. I've set the first two variables according to version 1.0.4 Should I set
Thanks for your support!
G
to 27??$CMS_SCHEMA_VERSION = "25";
Thanks for your support!
G
Re: after upgrading version # stays 1.0.2
Gregor,
this post is also about versions remaining 25 after upgrading.
http://forum.cmsmadesimple.org/index.ph ... 379.0.html
Ronny
this post is also about versions remaining 25 after upgrading.
http://forum.cmsmadesimple.org/index.ph ... 379.0.html
Ronny
Re: after upgrading version # stays 1.0.2
Indeed, the schema version should be 27:
Upload the install directory from the 1.0.4 package and run /install/upgrade.php to complete the upgrade (to schema version 27).
Regards,
D
Code: Select all
$CMS_VERSION = "1.0.4";
$CMS_VERSION_NAME = "Lanai";
$CMS_SCHEMA_VERSION = "27";
Regards,
D
Re: after upgrading version # stays 1.0.2
Since you're using the diff package: you can also use the install directory from the 1.0.2-1.0.4 diff.Dee wrote: Upload the install directory from the 1.0.4 package
Re: after upgrading version # stays 1.0.2
Maybe it's a good idea to re-upload all (the other) files from the diff-tar (too), making sure they get overwritten/uploaded properly (and run upgrade.php).
Regards,
D
Regards,
D