Fretless

@amagsumov

However the decisions that were already set when the plugin was first enabled remain in place, yes?

I guess what I’m asking is that – as an example – when the plugin was in it’s trial period it was rejecting fake sign ups and comment spam to my WordPress installation. Once the trial period ends, will it still reject fake sign ups and comment spam?

@amagsumov

Decisions? As in blacklists/whitelists and various options etc.?

If everything still works without restrictions then I’m all good with that. Thank you for your time in explaining things to me. Much appreciated.

I should add that what I have seen of the plugin looks very good, and it seems to work well in helping to eliminate fake logins, fake signups, comment spam etc. The interface is also well thought out and manageable.

I will also mark this topic as “resolved” in a few hours or so – to give you an opportunity to respond, if you wish to.

Hello @amagsumov

Does the plugin cease working past the trial period? Or does it still work in the background, but no longer gives you any statistics or other information? If it continues to work in the background then I don’t really have a problem with it. After all, $8 a year (or whatever the subscription amount is) is a decent price for statistics and information reporting.

However, if the plugin no longer works at all then I believe it has no place on the WordPress plugin repository and I may convince others that it shouldn’t be here – because, what’s the point of it being here? The plugin repository is here for plugins that are free, under the GPLv2 license and work. If plugins don’t work past a trial period, then why have them here?

Pardon my ignorance – as I’ve not been on the Forums for quite a while, nor do I really keep up to date on what the WordPress sphere is doing nowadays – but I have no idea of what “environment compositions” are, so I cannot comment on that.

Yeah, not really a good enough answer there Serge i’m afraid. As someone who has been using WordPress since Year One this sounds like a bit of a loophole that – at the very least – needs to be looked at.

I have no issues with paid upgrades or anything of that nature, but a free version of a plugin offered through the repository should not be crippled after a certain time period, because it then makes that plugin completely unworkable unless you upgrade. And why would www.remarpro.com want to have plugins on the repository that just don’t work after a week and take up space? Seems superfluous to me.

I’m specifically talking about plugins on the WordPress repository here. If a free, yet time limited, plugin were on another site then, obviously, I would have no issue with that.

I was able to fix it. The old ‘plugin conflict’ issue.

Actually I believe I’ve worked this out. I don’t think it’s related to Jetpack at all – rather another plugin for MailChimp that was originally bought as a premium plugin but has since been reverted back to a free version. I think it would’ve been the premium version with the added bells and whistles such as the dashboard stats box.

I’ll check with my friends and see if this could be the answer. At any rate I’m marking this topic as resolved for now.

It’s pretty easy to enable tags in pages by just adding a bit of code to your theme’s function.php file. Having said that, I too would be interested if you can add page & custom post support to your most excellent plugin, Sudar. Looking forward to it.

I’ve network activated several of my multisite installs and it works just fine. The interface (settings etc.) is accessed from the main site dashboard though – not the Superuser dashboard.

Thanks Yorman and UseShots (Denis?). I wanted to wait a little while before posting to see how effective my anti-spam/hack efforts were.

I found a plugin on the repository (via a Sucuri link) for a plugin called Stop XML-RPC Attack, which rewrites your .htaccess file to block all usage of the xmlrpc.php file but still allows JetPack to function by whitelisting the known IPs used by it. That seems to have done the trick quite nicely, though it could probably be modified slightly to help lessen server load even more. Still, as a quick fix, this is a good way to go.

I notice there are several plugins on the repository that will shut down your xmlrpc.php file completely if you’re not worried about breaking feed-related plugins. There are also .htaccess code snippets that can be done if people don’t want to go down the plugin route. The Sucuri link above is a great starting point.

Hi Yorman. Nope, I’m on a dedicated server so things are fairly fast. Because I’ve set the plugin notifications to a few emails per hour the timestamps are pretty spot on – that is to say that if it happened 5 minutes ago then the timestamp on the notification is also 5 minutes ago. There’s not really any lag time.

The XML-RPC makes some sense. I’ll look into that more and see what I can find out. I’ll also see about grabbing a copy of my access logs so I can send it to you.

Soulstudio > That seems about right. It would be 4-5 days for me as well. Possibly 6.

Settings > General. Down the bottom.

That seems to have fixed it. Thanks for that. Much appreciated.

If the transition mode is “horizontal” then it disappears, but if set to “fade” or “vertical” then the white box is there.

Thanks Mikko. I’m still looking into it & trying a few things.

Same problem here as well