Thread

My client is getting the following error message in the File Upload dialog box when she attempts to upload audio files to her site:

Fatal error: Allowed memory size of 79352670 bytes exhausted (tried to allocate 24487559 bytes) in [system]/codeigniter/system/core/Common.php on line 492.

I have no problem uploading the same files. The differences:
(1) I have Super Admin permissions; the client has limited permissions.
(2) The client is working in Internet Explorer (not sure which version) on a Windows PC; I am using Google Chrome on a Mac.

The site is running EE version 2.2.1 build 20110705.

Any help figuring out what the problem is would be greatly appreciated. Thanks!

Brian

Hi Brian,

Let’s try to narrow down some of the variables between you and your client. In the CP, go to her member page and click “Login as Member” under Member Administration on the left. Now try uploading the same audio files. Are there any differences in your experience? Do you receive the same error? If so, it’s likely a difference between your account permissions.

If everything still works, it may be a browser issue. See if you can get ahold of a Windows computer and use the same version IE she’s using to try the same thing, both with your account and with hers. Anything different?

We’re basically just trying to narrow things down so that we know where the problem lies first.

I’m getting the same problem with the non-super admin user:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to 
allocate 33790133 bytes) in 
/public_html/system/codeigniter/system/core/Common.php 
on line 492.

If I upload the file as super administrator I don’t have any problem.

I’m using EE 2.2.2.
Any ideas?

Does someone know how to fix this problem?

Hi, milogdm.

http://www.youtube.com/watch?v=LW_TBhQeSCI has information on how to remove XSS filtering. I suspect that the extra check is what is going over the PHP memory limit.

Does that help?

Thanks, Kevin and Sue.

I logged in with my client’s account on my computer and I got the same error message, so it did appear likely that it was an account settings issue.

I followed the advice in Sue’s video and that seems to have fixed the problem.

Brian

Hi Brian,

Glad that Sue’s video got you fixed on this.

If anything else crops up then please don’t hesitate to post again as needed.

Thanks,

Mark