It's likely to be to do with browser differences in the users uploading files. One of the updates we had to make for 1.5 involved Internet Explorer returning a completely different MIME-type for JPEGs; it's possible that the same thing is happening for MP3s.
PHP 5.3 contains a new set of functions that will detect filetype from the saved bits (as opposed to what the uploading browser tells it), but they're too new to rely on yet.
For the record, and for the information, found a fix about the problem.
This problem could affect any plugin using file upload, and is related to php mime magic function.
Mime magic support is broken inside some debian/ubuntu versions, maybe on some other systems, you have to check your phpinfo().
You should have inside a
mime_magic support enabled
If you have it disabled, you have the 'bug'. To fix it, here's the sumup :
On Debian/Ubuntu system, You'll have to modify your php.ini (located /etc/php5/apachex) and add the following section in the end of it.
[mime_magic]
mime_magic.magicfile = "/usr/share/file/magic.mime"
Depending of your version too, the mime file may 'not be ok' too, so you'll have to turn on startup error logging in php config file, restart your web server and check the problems eventually appearing regarding mime magic (and fix the wrong lines).
Hope this will help!!
Yes, but you report that your widgets are broken in the page linked above. My point is that they could never have worked in the first place if you were running 1.2 without a private settings table.
So I guess I'm wondering if you are upgrading from 1.1 or 1.2. If what you have is a sort of combination of the code from both, then I'm not surprised that the upgrade script is getting confused.
Yes, but you report that your widgets are broken in the page linked above. My point is that they could never have worked in the first place if you were running 1.2 without a private settings table.
So I guess I'm wondering if you are upgrading from 1.1 or 1.2. If what you have is a sort of combination of the code from both, then I'm not surprised that the upgrade script is getting confused.
This worked for me - but I was adding a theme and it did not seem to work for Kyle.
http://community.elgg.org/mod/groups/topicposts.php?topic=32571&group_guid=11
@M.C. that's quit a list. Am I correct that all are Enabled? If so here is what works for me. First elgg will place the news plugins at the bottom by default, start by disabling each one at a time, dumping the simplecache and starting simple cache back up each time.
Now I can tell you you may have some plugins located wrong, example is to keep like minded plugin together like blog and place blogextended just below it. walltowall just under messageboard, I group all my profile related plugin together. Keep custom_index either very top or very bottom.
I understand a lot of plugin developers say to place the plugin at the bottom, but not every plugin can have this position.
Make sure garbagecollector and logrotate are set to weekly and force a cron clean up. www.xxxxxx.com/pg/cron/weekly.
Now my advice is do as I say not as I do because you have so many plugin I would conside which ones you realy need, your site will be much faster.
Hope this helps
Hi Goofbucket
Thank you for helping me. I tried the cron and minue i turn off the simple cache, all css goes off.
I disabled all plugins and its still the same.

Strange its happening with all plugins disabled.
The minute i click enable simple cache, site loads normally
Im debugging and making changes so i need to disable caching
What could be the issue
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.