That would be pretty cool. I don't think it would not have to be too
complicated - even if there was the ability to flag and protect certain
folders from being overwritten by the FTP transfer that would probably
be enough for most plugin developers.
We're coming up with ideas for hooks all the time. Actually. Just to
give you an idea of some of the things we've worked on recently that
need hooks:
A plugin to let you edit the Blogtitle & Tagline inline via your
homepage (using an edit button)
-- to our knowledge there are no hooks that let us do this
A plugin that lets us change the page title for better / customized SEO
results
-- again to our knowledge there are no hooks that lets us change the
page <h1> title. We did find one to change the page meta <title> which
was nice though.
Ciao,
Dan
Jacob Santos wrote:
Might be time to revive the upgrade script idea (or am I thinking of
plugin data discussion). Might be useful to have a file called
upgrade.php (or whatever) which is called within the context of a
class which gives it access to control the flow of the upgrade.
Dan Milward wrote:
Hi Dion,
Thanks for the email.
If you could come up with a few hooks then that would be awesome. I'm
asking because we create plugins and I think it would be useful - the
problem we are having right now is that people can add additional php
files to our plugin to extend the core features.
So when the update the plugin from WordPress extend they loose their
work. If we were making a new plugin from scratch then this wouldn't
be a problem and we would do it differently but because we already
have lots of users I'm not sure we can do it.
As an interim what we're going to try and do is just disable auto
updates from happening but allow people to manually download updates
and do it themselves. For powerful plugins I think this would be
extremely cool.
Ciao,
Dan
DD32 wrote:
It is not currently possible to hook in to make changes to what
is/isnt deleted.
The plugin directory the files are stored in are often not the same
as the plugin's slug, In order to keep simpler code, all plugins are
stored into a folder based on their slug and the old plugin removed.
If you have made changes to the core plugin, Consider submitting
them as patches back to the author, or forking the plugn(at least
for yourself = modify the plugin name and url)
If the plugin stores files into its plugin folder, Consider asking
the plugin maintainer to store the data outside of the plugins
folder, Or in the database if its small enough. This has the benefit
of also keeping the plugins folder manageable.
It may be possible in 2.6 to filter what is/isnt
deleted/removed/modified/etc, There have been 1 or 2 requests for it
so far since 2.5 release :). I'm working on some changes which'll
affect the upgraders code, so i may well try and write a few hooks
or something in, But as it is, there is no list of files which you
cna filter, it just says "Delete that folder and any files in it, i
dont care what the files are, just get rid of them"
Cheers,
Dion
On Wed, 04 Jun 2008 10:52:24 +1000, Dan Milward <[EMAIL PROTECTED]>
wrote:
Hi Guys,
How do we add custom code to the plugin updating system to preserve
files that people may have added to the plugin directory.
Because by default it looks like it deletes the plugin directory and
replaces the all the files with the updated version - in the process
deleting any changes.
Ciao,
Dan
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
