[wp-hackers] User folders for themes, plug-ins
Brian at TheCodeCave.com
Thu Jan 18 17:37:11 GMT 2007
A less intrusive solution might be more compatible. Rename the wp-content
directory, in the distribution tarball, to wp-std-content. Then during the
install/upgrade process, the files in the wp-content-std directory are
iteratively copied into the wp-content directory. WordPress would make no
other references to wp-std-content.
Since this is a file by file process, the whole directory replacement
argument is moot. There does not need to be a massive rewrite of existing
plugins. No testing need be done on all the areas of the core code that
reference plugins or themes. It a has a limited scope of change and limited
testing requirements. It does not complicate the tarball. What are the
negatives? Are the functions required to perform the copy going to be
active in all php installs?
More information about the wp-hackers