Jehy

Becomes disabled?!!
I am the author of WP No External Links, and I can’t even imagine, how it is possible O_O

Oh. By disabled – do you mean that it does not work, or it auto-deactivates?

Yeah, it’s as you mentioned, there’s even a comment

#site root is excluded

It’s to disable masking of internal links. However, scripts finds the root directory itself (for example, if you have blog, located on https://jehy.ru/articles, the root will be https://jehy.ru), and adds the root directory to exclusions. So you don’t really have to replace siteurl with home there. As you wish.

Thank you for concern. I’ll look through codex and test it on my blog, and, possibly, change siteurl to home in next version of plugin.

wordpress doesn’t know anything about site url, only about blog dir.
What you should do:

1) replace get_option(‘siteurl’) with the url of your site.
2) Put line

RewriteRule ^goto/(.*) https://$1 [R=301,L]

in your .htaccess

But be careful: plugin updates will erase your changes, and also wordpress can rewrite .htaccess file.

1) It means that either you didn’t check “Mask comments authors`s links” in plugin options, or you have non standard theme, which does not use link filters. Author link must must be shown with comment_author_link function.

2) I think that you understand that plugin won’t be able to work upper to the blog directory. If you really need it, download plugin version 0.71 and be ready to rewrite .htaccess file.
You still wanna do it? I tried to make plugin v 2.0 as simple as it can be.

Thank you.
I am really happy to see the feedback – 3000 downloads and only several comments make me sad.

Soon, I’ll optimize plugin a bit for faster performance ??

Oh, sorry seems like that once again, I wrote too much, and too little.

I agree that there isn’t a widely used trust layer on top of OpenID right now, but how is that any different than normal WordPress account registration which requires only a username and email address?

Right now, wordpress registrations are usually validated with activation e-mail, matcapcha, or any other capcha. Openid users aren’t validated.
I really don’t want to write it in public, but with openid I will have no problems, for example, spaming for thousands of different identities (even from one web site address. I am not speaking about some openid providers, who allow almost automated openid creation. You won’t be able even to block them with akismet).
After all, allowing user to register means that we trust them even a bit.
But we can’t guarantee that OPENID user is even a human.
That’s why Openid is really a superweak authentication method
.

The fact of the matter is, however, that many OpenID providers provide much stronger authentication than a standard WordPress username/password account. Go take a look at MyVidoop, MyOpenID, and Verisign PIP.

I know that technically, authentication is stronger. You won’t belive, how many times I used OPENID for different hacking purposes ^_^’

Finally, all I mean that – openid user is the same an unverified guest: his openid only means that he owns some kind of url.

So, it’s not good to make such guest a user.

Also, please consider that in many blogs, registered users gain more privileges, then guests – and it’s not correct to give them to a openid guest.

I’ll consider adding more options for enabling portions of the OpenID plugin, while leaving others disabled. In the meantime, you can certainly disable portions yourself, as you’ve already done.

Thank you, that’s all we really want ^_^
Good luck, your openid plugin implementation is still the best.

Oh. I was a bit incorrect.
Sorry.
Yeah, I believe that openid plugin respects option “anyone can register”.

But you see… The point is that sometimes creation of user profile sometimes needs certain circumstances – in my case, user needs a certain invite code to register and create profile.

Right now I have many users with openid in my blog – I always thaught that these profile were created when they commented posts. My wrong. I believe you that they all used login page. Anyway – not much difference.

The main point is that we can’t really trust those who log in with OPENID. Openid is really a superweak authentication method…

It would be wonderful if in future plugin versions you added two advanced settings:
1) Don’t create openid user profiles;
2) Disable openid consumer support (just don’t include comments.php file)

We would be entirely happy if you implemented this ^____^

Thanks, added.
Also wrote some comments on how to use plugin…

Oh. I try to avoid short tags, but this time I missed the point…
Thanks.

I just thaught it would not be polite (for wordpress developers) to write it so directly ^___^’
But I really don’t think that it’s polite to put almost unremovable link to developer site either…

Plugin only masks links on output.
It DOES NOT CHANGE anything in the database.
If you uninstalled plugin, IT CAN’T ADD ANYTHING.

WordPress natively sometimes adds nofollow to links, or possibly you have some other plugins, processing links.

Great, thanks for feedback =)

Oh. Thank you.
I’ll make it if I’ll have some free time ??

so, the real problem is not with the plugin, it’s with WordPress. is_front_page() relies on an option named ‘show_on_front’ that is not always set. I’ve updated the plugin to set this option if it is empty, so that is_front_page() will work as it should. This will be in the next release.

Still not working in open 3.2.1…

Yeah, thanks.
I have no pages on my blog, and it could be the reason function didn’t behave properly.