What is the easiest way to find out what Addons are in use so I can remove the others?

Permalink
http://www.azselfstorage.org . Bluehost is throttling our website and it had something to do with cron jobs. Mike Lay was the primary developer on the site and he did a stellar job. Yesterday, he found and fixed what appeared to be the offending process, installed APC, I initiated CloudFlare through Bluehost, and yet they are still throttling it saying that is has something to do with scripts. The only thing I can think of is that I have an excessive amount of addons that are not in use and could be removed. How do you safely deduce what is an is not in use so they can be removed. I am a designer and not a developer and have little MySQL experience but can follow instructions well. Obviously... it is hosted with Bluehost.

barkingtuna
 
mhawke replied on at Permalink Reply
mhawke
I would doubt that inactive add-ons would be a problem. They take up disk space but not processing time so there's no reason to throttle you unless you're over your space quota and that's the way they force you to delete some stuff.

I ran your site through

http://www.unshit.com

A rather indelicate name but a good service. It shows how much $#it they believe is on your page and makes suggestions as to how best to solve it. Their complaint about 'scripts' may refer to the fact that your main page calls 15 separate JavaScript files but still I don't believe they would throttle for that.

Can you get Bluehost to explain their concern in greater detail and post their words here.
JohntheFish replied on at Permalink Reply
JohntheFish
Beebs93 published a beta version of an addon that helps with this. If you know what blocks a package provides, you can lookup where they are used on the site.

Its not quite finished so has not been submitted to the prb, but overall works very well.

http://www.concrete5.org/community/forums/block_requests/a-few-beta...

There is also a github version that may be more up-to-date.

What it does not find is blocks used in stacks, so you will have to check through stacks manually.
mhawke replied on at Permalink Reply
mhawke
I think this add-on is a much needed addition but wasn't barkingtuna concerned with packages that were NOT in use?

UPDATE: I see... you gotta know what's in use in order to know what you can delete. duh!