fips

Thanks also from me for this little fix!

Thanks for the prompt update joedolson!

Looks to be a known issue according to this thread.

Thanks Mr Scott, I can confirm that this solution also did the trick for me. Sites had been complaining vaguely about OpenID errors, one gave the following more detailed info (edited):

The OpenID Provider issued an assertion for an Identifier whose discovery information did not match. Assertion endpoint info:
ClaimedIdentifier: https://www.mysite.com/author/me
ProviderLocalIdentifier: https://www.mysite.com/author/me/
ProviderEndpoint: https://www.mysite.com/index.php/openid/server
OpenID version: 2.0
Service Type URIs: Discovered endpoint info: []

Turning off the XRDS-Simple plugin gave me a functioning OpenID service again, at least it seems now to function.

Sorry for hijacking this thread, but I just had some trouble setting this plugin up myself. On a clean, test WordPress install I added the plugin and enabled it, then went over to the options page. The first thing I was greeted with was being told I’d deleted all of the settings and could safely remove the plugin (sorry I can’t remember the exact wording!). After clicking ‘Save’, the regular options were brought up, but the defaults under advanced settings were all blank/missing, and the plugin naturally failed to do anything:

<!– Begin Shadowbox JS –>
<script type=”text/javascript”>
var shadowbox_conf = {
adapter: “yui”,
language: “en”,
players: [“html”,”iframe”,”img”,”qt”,”swf”,”wmp”],
animate: true,
animateFade: true,
animSequence: “wh”,
autoDimensions: false,
modal: true,
showOverlay: true,
overlayColor: “”,
overlayOpacity: ,
flashBgColor: “”,
autoplayMovies: true,
showMovieControls: true,
slideshowDelay: ,
resizeDuration: ,
fadeDuration: ,
displayNav: true,
continuous: true,
displayCounter: true,
counterType: “default”,
counterLimit: ,
viewportPadding: ,
handleOversize: “none”,
handleUnsupported: “link”,
initialHeight: ,
initialWidth: ,
enableKeys: true,
skipSetup: false,
flashParams: {bgcolor:”#000000″, allowFullScreen:true},
flashVars: {},
flashVersion: “9.0.0”,
useSizzle: false
};
Shadowbox.init(shadowbox_conf);
</script>
<!– End Shadowbox JS –>

Once the defaults were back in place (either manually or clicking to restore defaults), everything worked fine again. I can only assume that’s an issue for first time users of the latest version.

Brilliant, thanks very much ernestortiz, exactly what I’ve been looking for! ??

Resolved in so far as the problem isn’t there any more. Can’t figure out what exactly caused the issue, nor what solved it, so apologies to anyone who reads this thread looking for answers!

Essentially you want visitors to yourdomain.fr to stay on yourdomain.fr and likewise for .be/.nl addresses? Or are you wanting to customize the content for different visitors as well?

For the former situation, there seem to be a few solutions you could try, including using a plugin such as this one, or following the advice listed here, though both were written for older versions of WordPress.

Don’t mention it, I’m not much of an expert myself, but an extra pair of eyes often helps. ??

I’m assuming you mean that new comments to your blog are emailed to you at the wrong address, in which case you could try changing the address listed on the general options page (yourdomain.com/wp-admin/options-general.php).

Pages can also be commented on, but this may depend on your theme. However, as you surmise it sounds like you would soon have problems committing these posts as pages. If you’re simply trying to hide posts from the front page, a decent solution might be to add a post category which you then exclude from displaying on the main page. That might sound a bit complicated, but if you can follow the guide here you should be able to replace the relevant line in your current theme to enable you to do that.

Under settings the WP address is set as: https://the-sacred-path.com/testingsub (since it is in a subdirectory off of public_html).

The blog address URL is set as https://testingsub.the-sacred-path.com/

Not quite sure I get why you’ve done it that way, if you’re running a separate install. Have you tried setting the WP address as the same address you’re using (i.e. the testingsub.the-sacred-path.com address)?

For that little extra security it’s probably worth keeping your .htpasswd file outside of the web accessible area. And like 4seoblogs, you shouldn’t need the reference to AuthGroupFile in your .htaccess file if you aren’t intending to use one, TimothyA.

What does your .htaccess file say?

Glad to have helped ??