jshare

After a little more testing, it seems that for the Permalink field in the Edit Plugin Filter page, this:

A) http://mydomain.net/

is NOT the same as this:

B) http://mydomain.net

3 tests:

1) When I use A) without checking off ‘Also affect children’, I expect that a plugin will be filtered (e.g. turned off only) for the homepage.

But in my test, it was filtered for the homepage and other pages, but not posts, as if I had checked off ‘Also affect children’, so I think there’s a bug.

2) Similarly- when I use B) without checking off ‘Also affect children’, I expect that a plugin will be filtered (e.g. turned off only) for the homepage.

But in my test, the plugin was NOT filtered anywhere, as far as I can tell- not the homepage, not other pages and not posts.

Although technically A != B, I don’t think it’s reasonable to expect users to remember a trailing /, so while perhaps not a bug, this should be changed IMHO.

3) If I use A) and check off ‘Also affect children’, I expect that a plugin will be filtered (e.g. turned off only) for the homepage and other pages, but not posts.

And in my test, that’s exactly what happened.

4) If I use B) and check off ‘Also affect children’, by this point I frankly don’t know what to expect, so I’ll guess and say ‘nothing’, just like in 2) above.

And my test shows that I guess right. No big surprise there, it’ll depend on how you handle 2).

So to sum up the answer to my question AFAIK, with v4.1.1 I don’t see how to enforce a filter on the homepage only.

Awesome. Looking forward to it.

I understand now that wp-cron is kicked off when someone visits the site so if no one visits the site at the time my post is scheduled, it won’t get published. Even though my site usually has people on it, especially at the time of day when posts are scheduled – which is a reason why I choose that timeframe – it is possible that every so often, no one happens to be active on the site at the scheduled publication time.

To not have to worry about this, I’ve now disabled wp-cron and replaced it with a real cron job that kicks off hourly, for now.

Solved.

This was happening because I hadn’t done this yet:

codex.wordpress.org/Changing_The_Site_URL

Thanks Simon

It’s strange because I just tested creating a comment on my site with an email address of mine but with a different name and an innocuous line of text, and yet it was flagged as “local db spam”.

I was. I’ve now uninstalled it though. This is the first time in 7 years of blogging that I needed to delete an entire category and its posts and although that wasn’t what I was trying to do when I saw this strange behaviour, it was ultimately what I was going to do so I’m ok with the results. But I always like making bug reports and helping out when I can, especially when the plugin was free.

sweet