Is there a way to see what bugs were fixed in this version?
2.0.2 Is out (76 posts)
-
febwa1976
Posted 7 years ago #
-
weeklytips
Posted 7 years ago #
-
spencerp
Posted 7 years ago #
Just for clarification purposes, I had noticed in the wp-testers list that the database hasn't changed correct? And there is no need to run the upgrade.php correct? Here below is the email I'm referring to..
--------------------------------------------
Kirk Steffensen wrote:
> Sorry. False alarm. I was getting a "Call to a non-member function error"
> on a call to $wp_roles->add_cap(). After deactivating the plugin, clearing
> the plugin options, and reactivating it, WPG2 works.
>
> I didn't get a Database update message when I installed 2.0.2. I assume the
> DB didn't need updated and this is normal. That being the case, it's
> curious that WPG2 didn't come up right the first time. Can't recreate it,
> because it's up and running now.The database hasn't changed so there is no need to run the upgrade.
The only place we call $wp_roles->add_cap() is in WP_Role:add_cap() and
that function global $wp_roles properly. Plugins shouldn't be calling
$wp_roles->add_cap(). They shouldn't really be using $wp_roles directly
at all.Ryan
-----------------------------------------------Or is it ok to run the upgrade.php file anyways like normal while upgrading, and not have to worry about getting errors? Thanks in advanced.. =)
spencerp
I could have just done an upgrade on a Test Blog and found out myself..but just wanted to bring this question out to the "public".. =/
Because if you "technically" don't need to run the upgrade.php file, it might help other(s) by getting this pointed out to them..or whatever maybe..I dunno. =/
-
I just downloaded the new version and ran upgrade.php and everything works fine.
-
Posted 7 years ago #
Awesome, thanks brittanie for your quick reply and for clarifying this.. =) So we/I can do all the normal steps for the upgrade like before and have no worries..this is great. =)
Now time to upgrade ALL the dang blogs lol! Jesus, talk about along night/morning for me..sigh, but it is well worth it though. =)
spencerp
-
My upgrade went really quick. No worries!
-
Mine went well too, done in minutes :)
-
gMk
Posted 7 years ago #
Yip - mine too - ran upgrade to no problems !
-
strangnet
Posted 7 years ago #
I wonder why Atom 1.0 wasn't included this time either?
-
transmothra
Posted 7 years ago #
mine went well. but i noticed that my post times are gone now. i haven't the foggiest where to peek.
-
Posted 7 years ago #
...good thing it turned out to be my own fault. no problems, then!
-
ginoxy
Posted 7 years ago #
Upgraded to 2.0.2 , THANKS :)
-
YellowSwordfish
Posted 7 years ago #
Any chance of a changed file list anyone?
-
masquerade
Posted 7 years ago #
Index: wp-comments-post.php
Index: wp-includes/template-functions-general.php
Index: wp-includes/version.php
Index: wp-includes/js/tinymce/plugins/wordpress/langs/en.js
Index: wp-includes/js/tinymce/langs/en.js
Index: wp-includes/js/tinymce/tiny_mce_gzip.php
Index: wp-includes/classes.php
Index: wp-includes/template-functions-links.php
Index: wp-includes/comment-functions.php
Index: wp-includes/functions.php
Index: wp-register.php
Index: wp-settings.php
Index: wp-admin/menu-header.php
Index: wp-admin/list-manipulation.php
Index: wp-admin/admin-header.php
Index: wp-admin/post.php
Index: wp-admin/admin.php
Index: wp-admin/admin-functions.php
Index: wp-admin/user-edit.php
Index: wp-admin/edit-pages.php
Index: wp-admin/import/blogger.phpAnd for the inevitable "Can we have a patch?"
http://somethingunpredictable.com/tmp/201-202.diff -
towfigh
Posted 7 years ago #
Sorry to ask a newbie question...: but how do you apply the .diff file? That would be such a perfect thing to do :-). Thanks!
-
Posted 7 years ago #
Thanks masquerade - makes life so much easier! Grateful
-
i put it on my local machine this AM; all good.
-
stuartc1
Posted 7 years ago #
Is there a list of the actual security problem with earlier versions? I dont want to upgrade unless its actually needed!
-
Peter Westwood
Posted 7 years ago #
And for the inevitable "Can we have a patch?"
http://somethingunpredictable.com/tmp/201-202.diffAnd for some more detailed patching instructions:
http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/
-
thesi
Posted 7 years ago #
Upgrade went smoothly but now the page won't stop loading in Safari (same as this page), I get the following in Safari's activity window:
http://www.google-analytics.com/_...Fblog%2F%7Cutmcmd%3Dreferral%3%2B
and I'm wondering what this is.
Thank you.
-
clarke1866
Posted 7 years ago #
You've got a google analytics plugin problem.
-
shakemusic
Posted 7 years ago #
anyone have an idea why i would get this error:
Warning: main(/var/www/html/blog/wp-includes/wp-db.php): failed to open stream: No such file or directory in /var/www/html/blog/wp-settings.php on line 73
Fatal error: main(): Failed opening required '/var/www/html/blog/wp-includes/wp-db.php' (include_path='.:/php/includes:/usr/share/php') in /var/www/html/blog/wp-settings.php on line 73
-
Posted 7 years ago #
Make sure all the files are uploaded into the blog/wp-includes/ directory, especially this file: wp-db.php
And make sure they are all uploaded into the other directories and the root like "supposed" to be.. =)
That error you recieved is basically telling you what is not there and or where the file is supposed to be at. =)
Warning: main(/var/www/html/blog/wp-includes/wp-db.php): failed to open stream: No such file or directory in /var/www/html/blog/wp-settings.php on line 73
I hope this is right...it should be the reason for the error lol.. =)
spencerp
-
IronMac
Posted 7 years ago #
Due to another problem, I installed 2.0.1 and, then, decided to upgrade to 2.0.2. (In the end, it turned out that I did not need to install 2.0.1 but that's another story.)
I read the upgrade instructions:
http://codex.wordpress.org/Upgrading_WordPress
and noted that it said not to use upgrade.php. Ok, so I went further down the codex and found the following:
1. Delete /wp-admin/ folder.
2. Delete /wp-includes/ folder. Note: You must backup /wp-includes/languages/ directory if exists.
3. Delete all the wordpress files in the root directory where the root index.php file is found. DO NOT DELETE wp-config.php.
4. Download and extract the new version.
5. Upload it to the appropriate folders such as /wp-admin/ and /wp-includes/.
6. Upload all the files in the root directory.
7. If existed, restore /wp-includes/languages/ directoryIs it just me or are #5 and #6 a bit vague? In the end, I simply kept my wp-config.php file and replaced everything else in the directory with the new 2.0.2 files. It seems to have worked out fine.
-
Severa
Posted 7 years ago #
Ran the upgrade from 2.0.1 to 2.0.2 this morning, went smooth as silk!
Keep up the great work! -
TDHS
Posted 7 years ago #
I encountered the same problem as shakemusic. Since the initial installation of WP was more luck than knowledge (I have the wordpress files in both the root and my /weblog folder and deleting any single file completely screws everything up), that scared the **** out of me! :-0 So I put back the old files and I'll try again later.
-
Posted 7 years ago #
Is there a list of the actual security problem with earlier versions? I dont want to upgrade unless its actually needed!
There is no formal list, but let me say that the upgrade is absolutely necessary, the vulnerabilities are not crackhead zero-chance holes, they could easily be used to bring your blog to its knees.
-
a53classic
Posted 7 years ago #
I followed the intructions to the letter, yet at the bottom of my dashboard page I still see "2.0.1 — 0.10 seconds" and when I click view source I still see <link rel="stylesheet" href="http://www.focusedandfree.com/wordpress/wp-admin/wp-admin.css?version=2.0.1"
Does that mean the upgrade didn't take or ???
-
Posted 7 years ago #
I did the upgrade from 2.0.1 to 2.0.2 and I see a 2.0.2 - 4.95 seconds.
-
hpnotiq
Posted 7 years ago #
I have to say, for someone who isn't very technical at all when it comes to this stuff, the upgrade was very easy! See? I knew there was a reason why I dumped movabletype and got wordpress!
Topic Closed
This topic has been closed to new replies.
