Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo

Argh! Help! Hack attack?

Go to End

5 Posts   2158 Views


Community Member, 105 Posts

9 September 2008 at 3:38pm

OK, when attempting to call (a Silverstripe site) we are getting the message:

Fatal error: Allowed memory size of 18874368 bytes exhausted (tried to allocate 4864 bytes) in /home/ttec/public_html/sapphire/forms/CurrencyField.php on line 65

OK, what is going on? Is this an attempted hack gone wrong? It was most definately working previously ?


Community Member, 105 Posts

9 September 2008 at 3:55pm

I have attempted to copy over the forms directory with a local copy I have extracted. That does not seem to have helped.

This is a rather major drama for us, so although I would prefer to function with a cool head, I am not certain that a cool head prevails.

Logically, I can recreate nearly everything that was on the site, however, it would be rather handy if it could just be magically solved. I have made some customisations to Silverstripe (extra page types), nothing that would have caused this however.

Should I re-install a newer SIlverstripe version on top?


Community Member, 105 Posts

9 September 2008 at 3:58pm

Edited: 09/09/2008 4:11pm

You know what? Having a look at that error, to me it looks as though the server guys have done something. I'm asking them!

Alright, apparently there was a midnight upgrade last night and it has caused all sorts of havoc.

Using the solution found here:

It didn't work.


Community Member, 58 Posts

9 September 2008 at 4:11pm

Edited: 09/09/2008 4:11pm

Memory limit set to ~18MB by the looks, should be 32MB for SS - details and solution here:


Forum Moderator, 628 Posts

10 September 2008 at 11:43pm

Yeah this is nothing to do with a hack. As the error message you pasted states, and as StuM rightfully points out, the script has run out of memory, thanks to an overly restrictive/low limit being set.