[Plugin: WP-OpenID] How to enable logging/debugging?

Your subject refers to enabling debugging, but then the body of the message asks how to disable it. I’m going to infer that you want enable it, as debugging should be off by default, and if you enabled it then you should know that, to disable that, you’d just reverse your action.

Anyway, insert

define('WP_DEBUG', true);

into wp-config.php to enable bugging. You may find yourself unable to log-out with WP_DEBUG set to true, so the process of turning debugging on and off might require FTPing (or the equivalent).

Thx oeconomist!

In fact, I intended to ask how to enable the debugging. Sorry for the typo ??

I already figured out this option for wp-config.php.

After I turned this option to true, I saw a lot of debug-output from various plugins, but unfortunately no output from wpopenid (although it is enabled). Is there a way to distinguish openid-debug-messages from the messages of other plugins (e.g. a special prefix etc)?

I was hoping to find the cause why logging in with a Yahoo!-OpenID was not possible. Is the cause or detailed error-message for a failed login-attempt written to the debug-output?

I found out later -without debugging- that I had a lot of outdated certificates in my cURL-installation and my provider updated them for me. This fixed the problem.

You really want diagnostics that refer to

blogDirectory/wp-content/plugins/openid/

rather than to “wpopenid”. If you’re not seeing those, then either your PHP installation is mean-spirited, or the problem doesn’t lie in wp-openid.

previous versions of the plugin did some weird things in regards to logging. That has been greatly simplified in the latest release (v3.0), so that the plugin now uses the standard PHP error log. It also respects the WP_DEBUG option, such that it should log a little extra info when that is turned on.

That being said, the logging in v3.0 is rather anemic right now. The plugin has been greatly improved, so there should hopefully be less need for digging through log files in the first place… but we still need to add a lot more logging for those time when it’s necessary.

Try using the v3.0 release and see if that works for you. If not, let me know and I’ll see if I can help debug things a bit.