Yes it is you 😉
The version comes from the file wp-includes/version.php so that file didn’t get uploaded. It should be 2.2.3.
Might want to reupload.
Nope… It’s not… pppffht…
Current Version:
# md5sum /some/directory/here/wp-includes/version.php
2b24bb612b03decdbd6ab9c69c29b9fd /some/directory/here/wp-includes/version.php
Update Version:
# md5sum wp-includes/version.php
2b24bb612b03decdbd6ab9c69c29b9fd wp-includes/version.php
And it shows:
# cat wp-includes/version.php
<?php
// This holds the version number in a separate file so we can bump it without cluttering the SVN
$wp_version = ‘2.2.1’;
$wp_db_version = 5183;
?>
Heh… Maybe I’ll just change that myself then…
That tells me all the files didn’t get uploaded.
Nope. The files are all on the server. The file in wp-includes/ was the result from untarring current.tar.gz that I got off of the download page this morning. Then the copy from the untar directory to the production director for the blog did infact succed.
… Or are you saying that the dev group didn’t upload into the current.tar.gz (?)
I just downloaded the tar file off the downloads page — the version.php was the last file modified and it reads correctly. Its also has a time stamp of 9/7/2007, three days ago. (for what its worth)
oh, and it also matches the md5 here..
http://ww.wp.xz.cn/wordpress-2.2.3.md5