Thread

This question may be related to a resolved thread.

First time working with EE, it’s a fresh install only a month or so ago, and has never been upgraded.

Maybe a week ago, this appeared in the CP and won’t go away:

Security Update Release

An ExpressionEngine version 2.1.1, build 20101018 has been released as a security release. The latest version is: 2.1.3, and the latest build is: 20101220.

How do I get rid of this???

Under the ExpressionEngine Info Tab in the lower left corner of the screen it says:

Version and Build

A newer version of ExpressionEngine is available!

    Latest: 2.1.3 Build 20101220
  Installed: .. Build 20101220

and at the very bottom of my screen in small type it says:

Script executed in 0.0987 seconds - 25 SQL queries used - Build:  20101220

My /system/expressionengine/cache/ee_version folder has 777 permissions

but I do not see an “app_version” entry anywhere in my config file when looking at:
Admin -> System Administration -> Config File Editor

Should I manually add this? and if so… what should I set it to? 213 ?

Or is there some other way to get rid of this daft reminder?

Huge Thanks for any and all help >> Thanks

Hi, Charlie -

What version are you actually running at this point?  If it’s anything short of 2.2.1, the way to fix this is to actually update. =)

Thanks for the response Lisa,

Well, in the ExpressionEngine Info Tab in the lower left corner of my screen, under the “Version and Build” heading it says:

Installed: .. Build 20101220

and at the very bottom of my screen in small type it says:

Script executed in 0.0987 seconds - 25 SQL queries used - Build:  20101220

and the ExpressionEngine file that I downloaded and installed from is labeled “ExpressionEngine2.1.3”

So I’m pretty certain I have 2.1.3 installed, with the 20101220 build.

The only place I don’t have a version listed is within my config file, when viewing it through the config editor (Admin -> System Administration -> Config File Editor)

I have found some posts that mention a config entry: config[‘app_version’] but I don’t even have that key present, and don’t know if that is even necessary with 2.1.3

Hi, Brent -

2.2.1 is the latest; we lag those checks behind a little bit, hence the discrepancy you’re seeing.  You should have that key, yes, so please do add it.

Does adding it help? If not ,the next thing to try is updating to 2.2.1.