Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter msabramo

    (@msabramo)

    Sorry. It appears that when I upgraded to 2.0.2, some of the files didn’t get updated. Upon recopying the files, it started working for me, so presumably this was a bug in 2.0.0 or 2.0.1 that got fixed in 2.0.1 or 2.0.2. I searched the bug db and didn’t find anything that sounded like this problem, but perhaps I overlooked it.

    Why not name the .tar.gz on the main download page with the version number as well? For people who are really attached to latest.tar.gz, just make that a symlink to the latest version.

    I find latest.tar.gz to be annoying because whenever I download with wget I have to add something like “-O wordpress-1.5.2.tar.gz” to the command-line so that I can remember what the heck it is that I downloaded.

    Why not name the .tar.gz on the main download page with the version number as well? For people who are really attached to latest.tar.gz, just make that a symlink to the latest version.

    I find latest.tar.gz to be annoying because whenever I download with wget I have to add something like “-O wordpress-1.5.2.tar.gz” to the command-line so that I can remember what the heck it is that I downloaded.

    A few more ideas:

    * Check that you’re running the latest WordPress version so you’re not missing security and/or bug fixes.
    * Security checking – check file permissions, .htaccess, database password, etc. to make sure user is using secure settings. Recommend more secure passwords, enabling mod_security, etc…

Viewing 4 replies - 1 through 4 (of 4 total)