westcoastjetfighters

6 days since support’s last post! Why bother posting at all?

I also tried and deactivated a few plugins to decrease the memory required but it did not change anything. I think these crashes must be caused by a bug in the plugin.

Gerroald,

My website is hosted on a shared server. The maximum PHP memory is 256M so it could not be increased further. My web host has increased max execution time to 50 sec.

I have also installed iThemes Security 4.4.13. The admin site still crashes with memory errors.

Hi Gerroald,

The PHP memory had previously been increased to 256M by my host. I have also tried changing PHP memory by modifying php.ini (512M and 1024M) but it did not solve the issue.

I will confirm with them what the max PHP memory is and ask them to increase max execution time and will get back to you.

Regards,

Chris

Actually no, I haven’t got it working again! Just realized the plugin had not been reactivated. I re-activated it and the admin side has crashed again. It’s giving me memory errors.

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 122880 bytes) in /xxx/xxx/xxx/wp-admin/menu.php on line 79

I’ve got it working again. I FTPed in and renamed the iThemes Security folder. I refreshed the admin page and everything worked. I then updated all the other plugins, renamed the iThemes Security folder back to its original name and refreshed the admin page. It’s all working fine now.

Yes, I have just updated iThemes Security to 4.4.11 and I cannot log in anymore. I get a blank page after I click the log in button. I have tried different browsers and hard refreshing without success.

Update: I had flushed all caches and hard refreshed the browser but, somehow, it must have using a cached version of the page. The script is now inserted before the closing body tag.

mrkred, Josh,

Thank you for your help. I did what you both suggested. I checked the Firebug console and found a 404 error for the external javascript file. I used get_stylesheet_directory_uri() instead of get_template_directory_uri() and that error disappeared. I then had an error for the javascript contained in the external file telling me <noscript> was incorrect. I did some more online research and changed the code of the external javascript file to this:


<!-- Quantcast Tag, part 2 -->
<!-- hide script from old browsers
_qevents.push({qacct: "XXXXXXXXXX"});
document.write("<noscript><div style=\"display: none;\"><img src=\"https://pixel.quantserve.com/pixel/p-test123.gif\" height=\"1\" width=\"1\" alt=\"Quantcast\"/></div></noscript>");
// end hiding script from old browsers -->


I thought this was going to fix it but the script is still not showing. The console is not showing any errors anymore.

Any other ideas?