@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
@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
Yes, this is because of a permission check in the sub table delete function which fails because the base entity has been removed.
Easy enough to fix.
I have just committed a fix in SVN.
Subtable delete methods have now been deprecated and their functionality consolidated into delete_entity().
This shouldn't cause any problems now, however there is a theoretical issue if a plugin author creates a subtype of a main entity with its own class AND actively removes the subtable handling code... but I suspect this is highly unlikely to happen and will probably cause issues on creation in any case.
@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
@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
Yes, this is because of a permission check in the sub table delete function which fails because the base entity has been removed.
Easy enough to fix.
I have just committed a fix in SVN.
Subtable delete methods have now been deprecated and their functionality consolidated into delete_entity().
This shouldn't cause any problems now, however there is a theoretical issue if a plugin author creates a subtype of a main entity with its own class AND actively removes the subtable handling code... but I suspect this is highly unlikely to happen and will probably cause issues on creation in any case.
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.