5 ms·
Correct. It's definitely targeted towards developers and WP sites that are controlled by them rather than front-end users. It's usually not a great idea to let
by bretthopper 13y ago
Correct. It's definitely targeted towards developers and WP sites that are controlled by them rather than front-end users.
It's usually not a great idea to let normal users install plugins and update WordPress. For an analogy, you definitely wouldn't have users installing Gems in a Rails app.
- camus2 13y ago> It's usually not a great idea to let normal users install plugins and update WordPress. For an analogy, you definitely wouldn't have users installing Gems in a Rails app. that's not the same thing, Installing a gem wont magically add a feature to your rails app. Non developpers cant do it either(let alone deploying any ruby app on a server).Installing Plugins on wordpress dont require any developper knowledge.
- bretthopper 13y agoObviously it's not the exact same, but my argument is they should be treated the same (when possible). First, a lot of WP plugins do require some dev work to integrate. Second, non-developers have no idea what a plugin might change. It could easily break your entire site. Plugins should be installed on dev/staging and tested before just adding them in production. Plugins in WP are a double-edged sword.