Getting error when trying to update a Page or Post

Hi Thomas,

Sorry to hear this.

Can you look around your web space for error_log both in the root of your website, and under wp-admin folder.

Can you look within (at the end of) those error_log files for something relating to wp-simple-firewall and post them here.

My guess is there’s a function or something being run that your hosting doesn’t like.

Once I find the error, I can work around it.

Thanks!
Paul.

I’m going to try and do some more debugging with a test site. That was sort of a live site, that I don’t want to really dig into at the moment. I’ll report back if I find anything.

No problem… keep me posted on what you find.

It’s throwing this error on my test site:

Fatal error: Out of memory (allocated 267386880) (tried to allocate 65484 bytes) in /path/to/wp-content/plugins/wp-simple-firewall/src/icwp-firewall-processor.php on line 326

But it didn’t throw a 500 Server Error this time.

Which is strange because I’m on a dedicated server with lots of memory to spare. This is also a test site with only one other plugin activated and a commercial theme activated.

It works fine if I check this:
Ignore Administrators
Ignore users logged in as Administrator

I’ll keep poking at it, to see what else comes up.

An out of memory error indicates just that that particular operation exceeded the available memory, but it’s not necessarily that operation that was excessive.

In this case, 65484 bytes is tiny, so somewhere else is hogging up the memory and it could possibly be somewhere in the plugin… or it’s the plugin is the straw that broke the camels back.

256MB is a huge amount of available memory, and I can’t see the plugin consuming all of this.

I would feel that I’d have heard more stories by now if the plugin was consuming 256MB+ as that would kill of most shared hosting sites.

Keep me posted!

Not sure what the deal was with the memory. As the other live site just gave a 500 Internal Server error. But I do believe now, I know what caused it. I’m using a commercial theme and I think, one of the theme’s settings along with a non-standard configuration setting in wp-config.php was causing it. I believe it was just a coincidence that your plugin was in the mix as you touched upon.

Going to resolve this for now. If I find anything else, I’ll let you know.

Cool, thanks for keeping me updated on this!

If ya wouldn’t mind, fancy popping in a review of the plugin? ??

Cheers,
Paul.