oeconomist

Thank you for your response.

Exactly because it isn’t a problem quickly solved, I was hoping that someone had already solved it. I wasn’t looking for someone to do a lot of new work on my behalf. And I was and am aware that my hope was and is likely to be dashed.

.

Thank you each! I missed that by virtue of searching for “font-size”.

I’m having essentially the same problem, continuing with WordPress 3.9.1. My hosting service insists that they are finding no Apache or PHP problems. A test shows that cURL is implemented.

What WordPress often does is to replace an HTML escape sequences with the corresponding character, when what it ought to do is always to replace various characters (should the user enter them in bare form) with escape sequences. For example, your string should become

offrir à nos clients satisfaction et pleines écoute

But, while MidPhase’s behaviour could be worse, it ought to be better. MidPhase encourages customers to believe that MidPhase supports WordPress, but MidPhase keep hitting hosted ‘blogs with mod_security attacks. (Yes “attack” is the proper word.) Whenever MidPhase has effected a change that could produce these attacks, MidPhase should be checking the logs to see what is triggering mod_security to act, and MidPhase should be effecting exceptions quickly. Likewise for any other hosting service that purports to support WordPress.

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.

Mostly it seems that questions to ‘Net help fora result in some combination of eerie silences and advice such as “did U try googling?” I’ll try to be more helpful than that.

mu-open-id was designed to be used with the multi-user version of WordPress. My guess is that you’re plugging it into reg’lar ol’ WordPress, that you’ve installed WordPress in a directory named “blog”, and that in a resulting confusion mu-open-id is treating the directory name as the username, and unable to substitute a nickname for that username.

I used phpMyID to create an OpenID server on my own site. One may find useful supplementary discussion on this at InterWingly.net.

This plug-in (WP-OpenID) doesn’t provide an Open-ID server; rather, it enables (or tries to enable) a WordPress installation to accept OpenID.

(I used phpMyID to set-up my own OpenID server. I don’t know much about mu-open-id, which you seem to be using.)

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).

As I noted in “[Plugin: WP-OpenID] fatal error”,

With PHP versions 4.3.2 to 5.2.0, memory_get_usage() is defined if PHP was compiled with “--enable-memory-limit”.

Starting with 5.2.1, that compilation option was no longer required.

Will does not seem to be working this problem. If, like most people, you don’t have control over your PHP installation, then my suggestion is that you try version 2.1.9, which doesn’t use memory_get_usage().

Upon activation, I now get an avalanche of diagnostics, including the following

Fatal error: Call to undefined function: memory_get_usage() in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/logic.php on line 142

which brings me back to [Plugin: WP-OpenID] fatal error, where I explained

With PHP versions 4.3.2 to 5.2.0, memory_get_usage() is defined if PHP was compiled with “--enable-memory-limit“.

Starting with 5.2.1, that compilation option was no longer required.

Anyway, with WP_DEBUG defined, I couldn’t log out, so I removed that, logged-out, and then re-insterted it, and attempted to log-in with my OpenID. Thence I got

Notice: Undefined index: page in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/optimize-db/optimize-db.php on line 38

Notice: Undefined index: pollresult in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/wp-polls/wp-polls.php on line 1274

Notice: Undefined index: pollbooth in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/wp-polls/wp-polls.php on line 1279

Notice: Use of undefined constant widget_aboutme_header – assumed ‘widget_aboutme_header’ in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/about-me-widget/aboutme.php on line 94

Notice: Undefined index: clean_nonce in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/Auth/OpenID/SQLStore.php on line 276

Notice: Undefined index: clean_nonce in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/Auth/OpenID/SQLStore.php on line 282

Notice: Undefined index: clean_assoc in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/Auth/OpenID/SQLStore.php on line 276

Notice: Undefined index: clean_assoc in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/Auth/OpenID/SQLStore.php on line 282

Notice: Only variables should be assigned by reference in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/logic.php on line 117

Notice: Only variables should be assigned by reference in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/logic.php on line 530

Notice: Undefined property: identity_url in /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/openid/logic.php on line 531

Warning: Cannot modify header information – headers already sent by (output started at /home/oeconomi/public_html/blogs/daniel/wp-content/plugins/optimize-db/optimize-db.php:38) in /home/oeconomi/public_html/blogs/daniel/wp-includes/pluggable.php on line 770

What version of PHP are you running?

With PHP versions 4.3.2 to 5.2.0, memory_get_usage() is defined if PHP was compiled with “--enable-memory-limit“.

Starting with 5.2.1, that compilation option was no longer required.

Also, there seem to have been some MS-Windows-specific problems, and perhaps still are.

Unless you’re so hard-core that you’re going to code from scratch, you probably want to install phpMyID (though I suppose that you could also pull this off by forwarding).

On the assumption that you installed phpMyID at shep.ca, you’ll want to replace the openid.server and openid.delegate links in the head of shep.ca/index.php with <link rel="openid.server" href="https://shep.ca/phpMyID/MyID.config.php" /> and <link rel="openid.delegate" href="https://shep.ca/phpMyID/MyID.config.php" />

Likewise. I have WordPress version 2.6, PHP 4.4.7, and MySQL 4.1.22-standard. Wp-OpenID 2.19 works; versions 2.20 and 2.21 have fatal errors on reactivation.

My ‘blog is not installed in the root directory of my domain. Meanwhile, my OpenID is associated with the domain, rather than with the ‘blog. How ’bout yours, Branch and jaxidian?

Matt, this plugin is supposed to get a WordPress ‘blog to accept, rather than to provide OpenIDs. Visit OpenID.net to learn how to get an OpenID, and look at InterWingly.net for instructions on how to roll-your-own if you have your own domain.