Changeset 158697

Timestamp:

09/28/2009 07:38:42 PM (16 years ago)

Author:

wnorris

Message:

more changes from google code

Location:

openid/trunk

Files:

• Auth/Yadis/Email.php (deleted)
• readme.txt (modified) (3 diffs)

openid/trunk/readme.txt

@@ -2 +2 @@
 Contributors: wnorris, factoryjoe
 Tags: openid, authentication, login, comments
-Requires at least: 2.3
-Tested up to: 2.7
+Requires at least: 2.8
+Tested up to: 2.8.4
 Stable tag: 3.2.3
 
@@ -53 +53 @@
 [libcurl]: http://lists.openidenabled.com/pipermail/dev/2007-August/000784.html
 
-= How do I add an OpenID field to my comment form? =
-
-The easiest way to display the fact that your blog accepts OpenIDs is to enable
-the "Comment Form" option for the plugin.  This will allow the normal website
-field to be used for OpenIDs as well.  If this doesn't display properly for
-your particular theme or you simply prefer to have a separate OpenID field, you
-can modify your comments.php template to include an "openid\_identifier" text field as
-part of your comment form.  For the default theme, this might look like:
-
-    <p><input type="text" name="openid_identifier" id="openid_identifier" />
-    <label for="openid_identifier"><small>OpenID URL</small></label></p>
-
-The input element MUST have the name "openid\_identifier".  Additionally, using
-"openid\_identifier" for the id causes the field to be styled with an OpenID logo.  To
-remove this, you can override the stylesheet or simply change the element id.
-
-= What version of WordPress does the OpenID plugin require? =
-
-While it should technically work with WordPress version 2.3 and up, the
-experience with the OpenID server is much better from 2.6 and up.  The OpenID
-plugin will always be optimized for the latest stable release of WordPress, so
-you should try and keep your blog up to date.  Future releases of the OpenID
-plugin can, and likely will, drop support for older versions of WordPress as
-necessary.
+= Why do I get the error "Invalid openid.mode '<No mode set>'"? =
+
+There are actually a couple of reasons that can cause this, but it seems one of
+the more common causes is a conflict with certain mod_security rules.  See 
+[this blog post][ioni2] for instructions on how to resolve this issue.
+
+[ioni2]: http://ioni2.com/2009/wordpress-openid-login-failed-invalid-openid-mode-no-mode-set-solved-for-both-wordpress-and-drupal/
+
 
 = How do I use SSL for OpenID transactions? =
@@ -110 +94 @@
 1. Commentors can use their OpenID when leaving a comment
 2. Users can login with their OpenID in place of a traditional username and password
-3. OpenID Consumer Options
-4. OpenID Provider Options
-5. Users authorized to use the OpenID Provider can delegate to a different provider
-6. Users can add additional OpenIDs which they can use to login to WordPress
-7. Users authorized to use the OpenID Provider can monitor which sites they've logged in to
+3. Users authorized to use the OpenID Provider can delegate to a different provider
+4. Users can add additional OpenIDs which they can use to login to WordPress
+5. Users authorized to use the OpenID Provider can monitor which sites they've logged in to
 
 
 == Changelog ==
+
+= version 3.3 (TBD) =
+ - minimum required version has been bumped to WordPress 2.8
+ - fix support for WordPress MU
+ - new, less obtrusive UI for comment form.  Should also work with all themes in some form (with or without js).
+ - many administrative options have been moved to their respective locations on core WordPress Settings pages
+ - drop support for experimental EAUT and IDIB protocols
+ - drop support for installing the plugin in mu-plugins folder
+ - always include 'index.php' on OpenID endpoint URLs.  Without that, some deployments were having problems.
+ - fix bug relating to trackbacks and pingbacks
+ - fix bug (#121) relating to unregistered options (props: tom.tdw for the patch)
 
 = version 3.2.3 (Jul 20, 2009) =