Guti

According to Bing, you should not ping the same URL more frenquently that 10 minutes. So let’s say that a post if modified 2 times, you will send two pings, even if no 10 minutes has been elapsed.

Most probable case. Asume a new post that gets a lot of comments. Each time a comment is posted the URL will be pinged, even if 10 minutes have not passed.

Hi again,

I like the approach of storing the key in the wp-config file in order to avoid extra database queries, and polluting the wp-options table. Also like that a new comment triggers the ping, something that Bing’s plugin does not have. But there are some features I am still missing:

1) Ability to ping other engines (Yandex for instance), something that mihdan’s implementation did.
2) Ability to limit pinging same URL in 10 minutes (that is the recommendation, to not request reindexing more frequently than that).

So far it is working nicely.

Great! Thanks.

Of course @zabatonni it would be great. I was trying mihdan-index-now and then tried bing’s one. No one was complete (IMHO).

Checked again the source code for autorskielegalnie.pl and I see Spam Fighter files properly loaded, but not anti-spam-4.1.js.

Maybe spam fighter is conflicting with anti-spam.

Checked again, and in the source code for autorskielegalnie.pl I see spam fighter JS loaded, but not Antispam.

Are you sure you have the plugin enabled?
I do not see its main JS file included in your HTML source (anti-spam-4.1.js)

Thank you.

Do not think enabling it by default would be a good idea. Specially without an options panel to easily disable it.

Most users will not read documentation, and left it enabled filling its web storage. Also, logging only makes sense to me for testing, and making sure it is working properly.

OK, just added that and setup in my blog in 30 min: https://www.javiergutierrezchamorro.com/_temp/anti-spam.php.zip

Maybe not elegant, because it is reusing the login for administrator email sendings, but working.

Let me know if any concerns.

It’s is not already implemented. Just looked at the source, and find it not to difficult to implement it, but was not sure if you would prefer to code it by yourself or not.

If it works with 3.5, let me know and I will take a look to 4.0.

Thanks for the confirmation MarkRH.
Nice to hear.

Thank you very much for the mention, and thanks for the release.

My WP automatically detected the 4.0 update, and upgraded the plugin without any issue.

It is now running with 4.0 stable without any issue.

And yes, it is very important to remove uneeded dependencies, that was the main reason of my countribution. Specially, being the need of jQuery so tiny.

Kind regards.

Changes in RC1 makes sense for me <b>webvitaly</b>.
setTimeout will not do any hurt, and as you say, may solve some incompatibilities with certain browsers.

Also like the small changes such as initializing current year inside the global section.

Nice.
Let me know if you notice any other problem.