floydius

Are you asking why the little OpenID icon doesn’t show up? I haven’t ever been able to figure that out myself; I did muddle around in the comments.php portion of the theme files and edit in a (OpenID enabled) to the side of the Website box, but as far as why it doesn’t look like what is on the screenshot with the little check box, you’ve got me.

Well, it seems doing that only fixed the problem temporarily, and then it came back. I backed up my WP database, and then went into the wp_options table, and the sidebars_widgets field. I copied the existing text onto a text editor to save it just in case, then removed the data for the twitter widget. it was not pleased. then I restored the original text, and voila, back to a working RSS feed. my guess is this will crap out again, but not sure why. maybe a database guru can figure it out?

@themightymo, are you talking about your overall WP database? After backing mine up, I went in and found a wp_options table, but am not seeing a sidebar widgets field. help? ??

EDIT
Nevermind, found it. Just had to move forward in the fields list. woops.

Hey, I think the problem is not with twitter or this widget, but rather with wordpress itself. You can test this by just using the regular RSS widget with your twitter feed (or any public twitter feed) and seeing if it works.

It seems like the database is getting messed up somewhere. My solution was to deactivate all my plugins, remove all my widgets, and then re-install wordpress automatically. (Tools –> Upgrade). Just re-install the same version. Then I went ahead and reactivated my plugins and replaced the widgets, and so far I’m in good shape.

Good luck.

Confirmed that SREG values are imported improperly (not at all) starting in version 3.2.

At this point I am stumped. I suggest comparing version 3.1.4 and 3.2 to see where the offending change occurred.

Best of luck.

ok, I’ve done some regression testing and found that the sreg values are being imported properly at least as far back as version 3.1.4 for this plugin. Looking at the readme, the changelog for 3.2 was substantial. one of the listings was:

“- don’t return empty SREG values”

Therefore, I’m guessing something in that change caused this.

Unfortunately, there may be other issues with 3.1.4. For instance, in safari, it will go to the openid provider, but won’t come back to the blog to finalize the comment. it does seem to work in firefox. haven’t tested other browsers.

anyway, hope this helps. if you’re having this problem, you may either wish to wait until the next update, or regress 3.1.4 and try your luck.

scratch that, it’s not phpMyID… gave it another shot with a different openID login and experienced the same results.

ok, I have tested and confirmed that this only happens when the “Don’t require name and e-mail for comments left with verified OpenIDs” option is set. If that option is left unchecked (off), then wordpress will not allow a user to leave a comment with openID unless Name and e-mail are explicitly provided, in which case it will pull those values into the comment data.

It would appear that lines 354-377 of openid/comments.php is attempting to pull the data from sreg:

/**
* Retrieve user data from comment form.
*
* @param string $identity_url OpenID to get user data about
* @param reference $data reference to user data array
* @see get_user_data
*/
function openid_get_user_data_form($data, $identity_url) {
$comment = $_SESSION[‘openid_comment_post’];

if (!$comment) {
return $data;
}

if ($comment[’email’]) {
$data[‘user_email’] = $comment[’email’];
}

if ($comment[‘author’]) {
$data[‘nickname’] = $comment[‘author’];
$data[‘user_nicename’] = $comment[‘author’];
$data[‘display_name’] = $comment[‘author’];
}

return $data;
}

where it’s asking for nickname and user_e-mail, it should be importing the values from that array straight into the comments. for some reason, it is not. i’m not educated enough in wordpress or php to know why, though.

one possible issue, and I’ll still have to test this, is that we’re all using phpMyID to host our own openIDs? If so, it may be that phpMyID is still conforming to an older OpenID spec and that this is relying on 2.0.

Yeah, I would guess this only happens when we have the

Don’t require name and e-mail for comments left with verified OpenIDs

option set.

From what I can tell, the plugin is verifying the openID delegate, but afterwards it only duplicates the name of the URL listed as the “name”. It does not look in the sreg in OpenID in order to retrieve the nickname or e-mail values.

if you look at the plugin under the comments.php file, lines 111-118 appear to show an intent to obtain this data later on. Lines 295-304 look like some attempt to obtain user data, but I can’t tell if it’s trying to interface with sreg. Finally, down at lines 354-378, looks like this is where it is trying to record what it obtained back in lines 295-304, so maybe the problem is in 295-304?

Perhaps it needs some tweaking? I did find some info on interfacing with sreg here:

https://wiki.diso-project.org/wordpress-openid-api#ExtendingtheOpenIDnbspProviderSimplenbspRegistration

please feel free to let me know if i don’t know what i’m talking about. : )

I’m not sure how to either; i’ve had serious issues, and i can’t edit source code on a post (even in the little html dropdown box) without wordpress changing it back for me. ?? It seems like plugins might be the only way to go, though i have problems there too.