wp-unattended feature

[technosailor]

As mentioned earlier on the hackers mailing list, I think this can be a useful feature for the small minority that deploy large numbers of blogs - specifically blg network folks. This feature has a low footprint (3 line diff for install.php and any and all options in the ini are optional.

Included:
wp-admin/install.php (diff file)
wp-admin/automated-install.php
./wp-unattended.ini-sample

Optional:
Associated plugin to export settings from a Common Operating Environment blog to wp-unattended.ini
wp-content/plugins/wp-unattended-export.php

[davidhouse]

Recommend we add a hook to install.php then technosailer can distribute this as a plugin.

[technosailor]

Not sure that a plugin could be loaded in install.php as WordPress is not installed yet and thus a plugin not activated.

[davidhouse]

Sorry. I knew there was a reason I didn't suggest this earlier.

Anyway, I don't really feel that this is core material but I'm sure it'll be useful nonetheless. Any other opinions?

[davidhouse]

Recommend we add a hook to install.php then technosailer can distribute this as a plugin.

[davidhouse]

Argh. Sorry. Didn't mean that last comment.

[westi]

This sounds like a good idea.

Not keen on how hardcoded it is to just setting options though.

Something like the flexible install process discussed in ​this hackers thread from novemeber might prove more suitable and keep the I18N foke happy too.

[technosailor]

I'm not sure if I understand what was being proposed there but I'm willing to work with the devs and the i18n folks. Call this a proof of concept, if you will

[technosailor]

Seems like this feature would perfectly parallel Alex's about:config idea

​http://www.alexking.org/blog/2005/11/23/aboutconfig-for-wordpress/

In other words, I wrote this for install.php but that doesn't mean it can't be called using the init hook, no? Plugins could then load options from an ini file. This idea would have to be vetted out hard as I'm delusional at 2am, but I see the potential for more uses for this.

[ryan]

We can move the code that creates the default category, post, page, user, etc. into a wp_install_defaults() function that is pluggable. From install.php, we can look for wp-content/install.php and load it if it exists.

[Nazgul]

Added a small patch which looks for wp-content/install.php and loads if it exists.
The rest of the required functionality has already been build and committed for ticket #2616.

Based on a suggestion by Ryan in this ticket.

[ryan]

We require wp-content/install.php in upgrade-functions.php. Do we need to do it in wp-admin/install.php?

[Nazgul]

I missed it in upgrade-functions when I looked. Guess I need glasses.

But to me install.php seems like a more logical place, because you'll only use this during installation, not during upgrades.

If not, than this ticket can be closed as a duplicate of #2616.

[matt]

I think this already addressed by the pluggable functions.