|
|
|
|
|
|
![]() |
#1 |
wtfwjd?
Join Date: May 2007
Posts: 2,103
|
Wordpress 2.5.1 out now
Maybe they fixed some of the little bugs...
|
![]() |
![]() |
![]() |
#2 |
...and since we know an end will come it makes our living so much fun
|
I think so.. I am still with 2.3.3.
![]() |
![]() |
![]() |
![]() |
#3 |
There's Xanax in my thurible!
|
I just did the update on one of my blogs yesterday or the day before. Haven't noticed any problems, but I also only posted a couple of entries.
|
![]() |
![]() |
![]() |
#4 |
old enough to be Grandma Scrotum
|
This is good news, hopefully it will fix the bugs I've encountered.
__________________
![]() |
![]() |
![]() |
![]() |
#5 |
That'll teach you to leave your sister unattended.....
|
I've updated 5 blogs to 2.5.1. with no problem so far. Another 25 or so to go.....
|
![]() |
![]() |
![]() |
#6 |
Oh no, I'm sweating like Roger Ebert
|
I swear to some mythical creature supposed to live in the heavens above, keeping upgraded to WPs latest and greatest has become almost a full time job.
|
![]() |
![]() |
![]() |
#7 |
You can now put whatever you want in this space :)
Join Date: Feb 2007
Location: Australia
Posts: 658
|
Does anyone use WPMU?
Would this make upgrading easier? |
![]() |
![]() |
![]() |
#8 |
That which does not kill us, will try, try again.
|
I mentioned this in the Wordpress Exploits thread that Walrus started, but I think it's worth adding here since many people I've talked with have skipped this step.
Up until now, upgrade instructions told you not to overwrite your wp-config.php file, which was good advice since that file has your database login information which the upgraded script needs. And that was fine since the wp-config.php file wasn't changed until 2.5 came along and added a new constant called SECRET_KEY which is used to introduce some 'permanent randomness' as another security measure. If you're used to doing upgrades the usual way, you may miss this step. But this time you should open the new 'wp-config-sample.php' file and enter the config info from your old file. Now enter a 'secret phrase' that WordPress will use to scramble some things in the background for you. Save the file as wp-config.php and upload that to your server, overwriting the old one which doesn't have this new code. HTH
__________________
"If you're happy and you know it, think again." -- Guru Pitka |
![]() |
![]() |
![]() |
#9 | |
That'll teach you to leave your sister unattended.....
|
Thanks Simon - I missed that - now I get to redo all my config files
![]() I guess it's better late than never. Quote:
|
|
![]() |
![]() |
![]() |
#10 |
Wheither you think you can or you think you can't, Your right.
|
I also just upgraded my first blog to 2.5.1. All went well. From what I can see all the plug-ins work fine, though many had upgrades, hope they are keeping up with the new wp versions.
I agree, it's like a full time job to keep up with the upgrades. Also, seems by now they would make it easier to upgrade, instead of uploading everything every time. Thanks Simon, I missed that one too. I've been meaning to upgrade and since my host sent out a notice about the recent exploits, thought it was past due. Host also mentioned to look out for hidden users in the admin pane users page. I like the new dashboard, take a little getting up to, but I like the looks. Course we'll see how it goes after I start posting and editing, ect. Gee, only like 10 more to go. |
![]() |
![]() |
![]() |
|
|