Plugin Updater detects wrong "Latest Version installed"

Description

I'm using 2.7-beta2 and trying to use the new backend plugin installer functions, and discovered a bug: If I have an empty folder with the name of the plugin I want to install, I get the message "Latest Version Installed" instead of the install link.

I got to this point due to installation problems with the error "Could not create directory", so I though I could just create the directory on my own - but then, no install link =(.

Its reproducible and applies to all plugins.

(Second, didn't manage to install new plugins over the admin interface at all, although upgrading already installed plugins works flawless. Have tested it with file permissions 755 and 777)

Attachments (1)

Change History (11)

Yes, Checking to see if the plugin is currently installed isnt exactly easy, I think I might replace that check with another option thats available, And actually check to see if a plugin exists in the folder (as well as the folder existing)

Have tested it with file permissions 755 and 777)

Was it using the FTP method? (ie. it asked for ftp credentials) or direct (no questions asked, just straight install)?

The problem code will be the same for both actions (just in seperate functions). I'll take a closer look later and see if i can spot whats causing it, Probably forgotten to set permissions or something on a created folder..

Using 2.7-beta2-9705 I get a "Latest Version installed" message no matter which version of a plugin is installed. No messages about creating folders, just not receiving any notification of available upgrades. When I search for the plugin using the built-in plugin search, it tells me the latest version is installed even though the version numbers are obviously different.