[wp-hackers] Block Specific Plugins
andrew.bartel at gmail.com
Wed Apr 29 21:15:55 UTC 2015
Really would recommend you start working with proper contracts if you have
those kind of concerns. The cost of a lawyer to write up and review
contracts is trivial compared to headaches it will prevent.
On that note: https://www.youtube.com/watch?v=jVkLVRt6c1U (good talk at
creative mornings, but contains nsfw language)
On Wed, Apr 29, 2015 at 2:09 PM, <chris at 314media.com> wrote:
> Thanks - the setup is above my pay grade but very informative though..
> I was thinking smaller -- use case is on dev server working as a 3rd
> party developer - I don't want client to install theme downloader or
> some csv exporting thing but they need admin access.. - and someone in
> their org is probably smart enough to figure out - hey let's not pay
> I'm lazy enough to disable the editors but thinking would be nice to
> have as a function I could drop in for a little more security...
> Editing user roles I guess... Back to work :)
> > On Apr 29, 2015, at 4:03 PM, Daniel <malkir at gmail.com> wrote:
> > You may be able to swing something with WPCLI and a cron to search for
> > specific plugins, or only allow specific plugins. That's how some major
> > WPaaS places do it.
> >> On Apr 29, 2015 2:01 PM, <chris at 314media.com> wrote:
> >> Any function to block a specific plugins based on its repository name?
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers