+- GetSimple Support Forum (http://get-simple.info/forums)
+-- Forum: GetSimple (http://get-simple.info/forums/forumdisplay.php?fid=3)
+--- Forum: Developer Discussions (http://get-simple.info/forums/forumdisplay.php?fid=8)
+--- Thread: disabling default features best practices (/showthread.php?tid=5758)
disabling default features best practices - Bertrand - 2014-03-08
My plugin replace the standard menu editor in a similar way the i18n plugin does (I guessed, didn't look at the code yet maybe he does it in a much cleaner way, jsut looked at the generated page and the menu editor link is still there so I supose he does just the same), that is by javascript jquerying a disappereance of the default menu entry though its html id.
Is there a standard way to disable standard features other than javascript-hacking the dom properties ?
This is not mandatory for my plugin to work, so maybe it is considered bad practice too...
RE: disabling default features best practices - shawn_a - 2014-03-08
Nope, there is no way
I suppose you could do output buffering between
pages-main and
pages-sidebar
hooks that is
and output your own instead
of course yours will break anytime this is modifed in core probably