Disabling plug-ins in the backend
-
I have one question w.r.t disabling plug-ins in the back-end.
I have defined a filter with //www.mysite.org/wp-admin and checked children also.
My question is – most plug-ins have same name for both front-end and back-end (in-fact it is).
Then how do I differentiate, If I’m disabling, say, ADROTATE, plug-in
from back-end to front-end.
I did disable ADROTATE from filter and I still see ADROTATE menu in ADMIN menu.
a) Does it mean that PO disabling ONLY FRONT-END module of ADROTATE only?
b) Does all plug-ins have different menu/data/file structure such that it differentiates what to load on FRONT-END and what to load on BACK-END.
c) Can I safely DISABLE all front-end modules even though they have name for back-end also?
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
- The topic ‘Disabling plug-ins in the backend’ is closed to new replies.