leanda

Hi Alex

Thanks, this was resolved a few weeks ago with support. Our host server configuration didn’t allow TranslatePress to perform a direct database connection. Problem now solved.

Thanks again.

Hi

Our host has confirmed that it’s the TranslatePress plugin triggering the error with their server configuration. We do run Wordfence, but we still get the issue with WF disabled, we don’t run any caching plugins.

I have sent errors logs to you guys so hopefully you’ll be able to pinpoint exactly what part of your plugin is triggering the mod security rule and making our server see it as an attack.

Hi

Thanks for getting back to me:

WordPress version 4.9.12
PHP version 7.1.27
Server environment linux

All been working fine until the last update, it also didn’t seem to auto update.

Thanks
Leanda

@transmothra Thanks! If I switch back to the original parent theme after activating the child theme will the original settings still be retained?

Hi @voltronik

I did! So far so good, everything seems to be working.

Actually, I think I’ve just sussed it after hours of looking at this. I’m using a custom plugin tutorial from tuts that uses a deprecated argument in the wp_new_user_notification. I was thrown off the scent because it worked when disabling bnfw. Anyway thanks for your help, much appreciated.

Hi,

I rely on the Members plugin for some other bits, so disabling isn’t really an option for me. However, I did test disabling it and it actually made no difference anyway.

Hi,

Thanks for the quick reply.

I’m using Members By Justin Tadlock, could that be the problem?

Thanks

Hi @wfalaa

Thanks for the reply. I’ve just checked and on this site we are running W3 Total Cache and excluded wp-content/cache, enabled ‘Scan file contents for backdoors, trojans and suspicious code’ and it all worked again!

Thanks so much!

Disabled ‘Scan file contents for backdoors, trojans and suspicious code’ and the scan completes. Thanks @siteweb44 and @adriandw

Not ideal to leave that disabled though.

• This reply was modified 7 years, 3 months ago by leanda.

Thanks for the clarification.

Yup, I implemented the fix exactly as you describe in the steps above, replacing the full file and in the end rolled back to the old version of the file and just replaced line 1244, which solved the symbols issue and also the admin bar issue.

If I replace the PgCache_ContentGrabbber.php from the RAW version it introduces the admin bar issue for us.

Hi

We had this same problem and applied the fix by switching the PgCache_ContentGrabbber.php file with the new version. This then caused the admin bar to be visible at all all times to visitors of the site. I rolled the file back and changed just the suggested line 1244 with the fix and the admin bar problem went away.

Any idea why this might be happening?

Many thanks

Thanks for the tips. Turned out to be a plugin that uses a custom login and password retrieval form.

Sorry to be a bother, thanks for the fast support.

– Leanda

Ok, I seem to have solved it by setting the New User Default Role in the WordPress settings to use one of the custom roles instead of Subscriber and now they are firing.

Seem to have another issue though with notifications not overriding the defaults, I’ll start a new topic.