[wp-trac] [WordPress Trac] #14096: More protection against fatal errors from plugins
WordPress Trac
noreply at wordpress.org
Wed Aug 14 20:49:53 UTC 2013
#14096: More protection against fatal errors from plugins
-----------------------------+-----------------------------
Reporter: nacin | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: Future Release
Component: Plugins | Version:
Severity: major | Resolution:
Keywords: dev-feedback |
-----------------------------+-----------------------------
Comment (by WebTechGlobal):
"Check plugins before an auto-upgrade."
We created something like this by sending clients blog specs to us using
SOAP. We compare the specs to a profile we have for the plugins they have
purchased. We can use it to warn them of conflicts before they even
download the plugin.
I would much prefer the core to simply use specifics in the plugin. An
array of changes to both code and specifics which Wordpress loops through
prior to updating.
We pretty much have this in our plugins already, even in our free plugins.
But what we cannot do is prevent the existing plugin files being written
over. So already changes are made and THEN users find out that a new
version could cause problems. This is where a second plugin directory
would come in. There is a ticket for the ability to have nested plugin
directories. Possibly two birds one stone on that.
That second directory and reading the readme.txt plus main file would be a
good start. The files would be temporary obviously.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/14096#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list