I have upgraded from 2.1.0 to 2.1.3 and I am getting a Security Update Release notice as well as the footer still reads v2.1.0 build 20101220
Any ideas?
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
January 12, 2011 1:00pm
Subscribe [4]#1 / Jan 12, 2011 1:00pm
I have upgraded from 2.1.0 to 2.1.3 and I am getting a Security Update Release notice as well as the footer still reads v2.1.0 build 20101220
Any ideas?
#2 / Jan 13, 2011 2:11am
28Bytes,
It sounds like you only did a build update and not an actual version update.
Can you confirm if this is the case?
#3 / Jan 13, 2011 9:13am
It was a version update it walked me through the installer and then I removed the installer when it was done upgrading, but still says 2.1.0
#4 / Jan 13, 2011 5:21pm
Have you checked your config.php permissions? Is it writable?
#5 / Jan 13, 2011 5:23pm
My config is 666
#6 / Jan 14, 2011 12:03pm
Let’s see where things went wrong- if you take a look at your exp_member_groups table, do you have a field called can_edit_html_buttons? And just to confirm- if you open the actual config file (system/ee/config/config.php, what’s showing for:
$config['app_version'] = "213";#7 / Jan 14, 2011 12:53pm
Yes I have a field called “can_edit_html_buttons”
My app_version = “210”
#8 / Jan 14, 2011 1:57pm
OK- 2.2.0 db changes completed- let’s see if we can spot why the config didn’t change. Open up the config.php file again- look at:
$config['doc_url'] = "http://ellislab.com/expressionengine/user-guide/";Now- in the control panel, go to Admin > General Config and change the ‘URL to Documentation Directory’- no go back to the config.php page- did it change it to match what you just entered in the cp? It should (depending on editor, may need to close/reopen). If it did… I am not sure why the installer didn’t properly update it. Your db is looking good from here- and just changing the app_version in config should make everything ok. However- we’ll still be unhappy about not knowing why it wasn’t properly changed during update.
If it DIDN’T change, it’s a permissions issue. And your db is still looking good.
#9 / Jan 14, 2011 2:42pm
It changed, so I just went ahead and changed the app version and the warning went away. I will let you know if anything else seems fishy…
Thanks for the help.
#10 / Jan 14, 2011 3:11pm
Definitely something to look out for in the future. The only database change in 2.1.3 had to do with publish layouts. Unfortunately, it is not something easy to tweak manually. If you have saved publish layouts and run into any issues? Let us know and reference the thread. I believe everything ran fine. But it’s hard to tell from looking at the database. If anything does come up, though? Just start a new thread and let us know.