4 ms·
The main problem perpetuating Wordpress' design woes is its plugin ecosystem and how it depends on Wordpress' internals. A massive hook system, scopeless globa
by pytrin 14y ago
The main problem perpetuating Wordpress' design woes is its plugin ecosystem and how it depends on Wordpress' internals. A massive hook system, scopeless globals passed around like nobody's business and overall reliance on how "things work" right now - if you change any of that, you break most of the plugins (the code for which looks even worse than Wordpress itself).
An idea I always have in the back of my queue is to write an adapter over the hook system and various state variables plugins expect to have, and bridge it (the plug-in system) to something like the Zend Framework or Symphony. The amount of work involved prevents it from becoming more than a pipe dream.
EDIT: Added clarification for the adapter purpose
- johnny22 14y agothere's already a symfony2 bundle that has started that work i think. I don't recall the name though.
- pytrin 14y agoYou're probably talking about this - https://github.com/kayue/WordpressBundle https://github.com/kayue/WordpressBundle Not what I was talking about - this allows you to run wordpress on a symfony site and share user state (pretty trivial). I'm talking about an adapter that allows you to run Wordpress plug-ins - without Wordpress. Basically allowing you to write a normal blog system while leveraging the huge community and functionality of WP plugins.