verkko

Thanks for the confirmation. It’s good to see plug-ins being updated with version compatibility confirmation.

Gary

We have this resolved now thanks to Ryan C.

.htaccess file was blocking access to xmlrpc.php – probably written in by a security plug-in.

I have also used the Facebook debug tool at https://developers.facebook.com/tools/debug/ but no issues with what Facebook sees.

This problem only occurred when we updated the Jetpack plug-in.

Thank you for the link. I have already looked into the information in that thread and can report that there are no errors in that respect.

I have posted to the plug-in thread for assistance thank you.

I am still monitoring the issues but what does seem to have worked for me is to turn off WP Better Security automatic back up option. This was using considerable server resource and causing memory issues.

Hi,

Continuing to see memory leak issues having monitored the site over the weekend. Now also getting:

PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 25690701 bytes) in /mysitename.com/plugins/better-wp-security/modules/free/backup/class-itsec-backup.php on line 148

Having to disable the plugin entirely as this is the only way to remove the white screen my users are experiencing.

Thanks,

Gary

I have disabled those features for now as requested and will monitor for the next few hours.

For your info, activating the iThemes plug in again to set the above immediately caused the white screen error. The error log recorded:

[10-Oct-2014 15:14:25 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /home/sites/thesitename.com/public_html/wp-includes/wp-db.php on line 1974

Exact issue here. Everything stabilises when I deactivate iThemes Security though.

Running WP 4.0 and Version 4.4.16 iThemes Security Plugin.

Check all your code. You have x4 opening html doc types specified and a load of other errors too in the page link you posted.

That code looks very strange to me!! You are calling a css file called #

If you load your page and view the source code you will see that the css stylesheet call is missing.

Try this

<link rel=”stylesheet” type=”text/css” media=”all” href=”<?php bloginfo( ‘stylesheet_url’ ); ?>” />

You have no url to your css style sheet in your source

<link rel=”stylesheet” type=”text/css” media=”all” href=”” />

Log in to you dashboard and go to Settings > Discussion

Un-tick Allow people to post comments on new articles

Un-tick Enable threaded (nested) comments

You can also control the comment on individual page / posts by un-ticking the comments box. If you can see the comments box on the individual post edit pages, you can reveal it by going to the top right hand corner of the screen and clicking on the screen options drop down. Tick the Comments and discussions checkboxes and you will be able to control what you show on a page by page basis too.

Has this just suddenly happened for no reason?

If so just check that your .htaccess file hasn’t been injected? There is a lot of it happening at present.

If you can look at you logs to see if and when the .htaccess file was last changed. Or ask your hosting provider.