shinerweb

Out of interest, what memory limits do you have set in the WP ini file and on the server itself?

131Mb seems to be a weird figure to run out of memory at. (i.e. it’s not set to 128Mb, so I’m guessing you have it set to 256Mb which then begs the question, why is it throwing a memory error at 131Mb + 5167bytes.

What type of hosting is this on?
What version of PHP?
What version of SQL?

Hi Mark,

We have a site with a membership of just under 400 members.
What we intend to do is email those members with an update on the new GPDR rules (i.e the 4 basic rules) then provide them with a link to a simple form that records their acceptance.
It’s basically the same acceptance statement we show on all forms. (i.e ticking here allows us to hold your information in accordance with our privacy policy yada yada yada”

If they choose not to accept the policy change, we delete their details and they can’t be a member. (It’s a group of choir members).

We did toy with just emailing them and saying”by continuing as a member of the choir they consult to us holding their data” etc etc, but decided on getting their explicit answer rather than inferring it.
We don’t envisage anyone not agreeing given they are already members.

As a member of a number of email subscription lists, I’ve already received a number of emails with something similar.
I’ve also seen pop-ups on logging into a website which again asks the similar question. The only reason we chose to email the 400 members is that not all log into the website regularly.

We’ll email all 400 now, then any stragglers a week before the deadline, and again a day before. On deadline day we’ll delete any members who didn’t give us permission to hold their data.
They won’t be able to be a member since we can’t collect fees, have them listed for insurance or royalty rights management etc. PITA but we don’t expect any trouble from our lot as I said above.

YMMV but just to be safe, I’d recommend getting explicit permission from existing members in one way or another.

Chris

Ps. Apologies for typos in first reply. Using the phone first thing in the morning without glasses. Doh!

• This reply was modified 8 years, 3 months ago by shinerweb.

Under General settings in WordPress, untick the “anyone can register”.
Then check your website logs as that will tell you exactly how they are landing on your website.
Once the sciptbots work out that ‘a site’ is running WordPress, they’ll then automate setting up of accounts (mainly for comment and trackback spamming).
They’ll use XML-RPC (which you can switch off if nothing else uses it), and you can also use a plugin such as WP Hide Login which will change your wp-admin link to something else. (Normal users of the site will still be able to login as all internal links to wp-admin forward to your ‘secret’ login link. It just stops the scriptbots from automatically landing on wp-admin and then signing up creating new accounts.

It’s 99.99% not likely to be wp-members, unless you have your sign-up process so open that your form is allowing every Tom, Dick and Harry to sign up.
If you are seeing multiple random users sign-up via your WP Members/sign up form, you will probably need to enable Admin approval and/or a combination of Akismet/User verification service.

As to why it’s ever since installing the plugin, that may well be down to bad timing and only now have the scriptbots found a new WP site to play with.
However, the fact you say they are being assigned ‘no role’ suggest that it could be WP Members (unless you’ve played with the existing WP Role structure) when it might well be them coming in via your WP Members.
Don’t forget, even though you may not have your registration form on display, it only takes one ‘leak’ of a link to that registration page and it’s on the bad boys search list. That list then gets passed around and you’ll be targeted.
If it is down to that link suddenly being attacked, change the link to a new one and update internally. Use .htaccess to redirect those trying to access the old link.
If you run WordFence or similar, you can even block those IP’s trying to access the old link.

Your website logs are your friend… go through them and analyse exactly how, from where and what they are trying to do… Only then can you close the doors.

Without the actual field being selected, i.e. when you have the list of all your fields being shown, move your mouse over the gear icon of the field you want to delete.
This will bring up the ‘clone’ and ‘delete’ icons.

See this image

I’d echo the same sentiments too Yehuda.

It’s a thankless task doing what you do.
No one else stepped forward to rescue the plugin, you did.

I wonder if people realise there are some 1060 files involved with the POST SMTP plugin.
There is no such thing as 100% test coverage, that’s only something we aim for, but it can never be achieved. There are an infinite number of variances of platforms that it can run on, there are only 24 hours in a day, and you do actually have a life, and a job and you can’t do it all !!

So I will also add my thanks here… Keep up the great work! It is much appreciated…

Have you tried it with the Facebook comments plugin disabled.
You have a Javascript error which is causing admin-ajax.php to throw an error.

The error appears to be that you haven’t added the domain success.africa to your list of domains for your Facebook App.

Can’t load URL: The domain of this URL isn’t included in the app’s domains. To be able to load this URL, add all domains and sub-domains of your app to the App Domains field in your app settings.

But the fact you say you’ve tried it with the other plugins suggests there might be something else. But I can’t see anything until the Facebook error goes away.
Try disabling the Facebook App plugin and letting us know and I will take another look.

Regards

Chris

Any update on this?
I’m seeing this on multiple sites and hadn’t noticed it until today. Doesn’t appear to effect functionality. Not sure when it stopped working.