allow instalation customisation - code included and tested

[thomask]

Current Wordpress can have own instalation using instal.php file in /wp-content folder. The problem is, that this file can ovewrite only wp_install a wp_install_default functions, which are run AFTER both whole setup-config.php and install.php files were run. So e.g. it is not possible to add own logo to the instalation script, own input for e.g. predefining blog description ...

I have made very small changes to the install.php file
a) add if ( !function_exists( ... ) ) before all (2) functions in this file
b) create 'check_blog_installed' function as enclosure for part with blog checking with !function_exist check again, so it can be also owerwritten
c) create step_0, step_1, step_2 functions, and adding content of code parts run when $step = 0 or 1 or 2, again with !function_exist, so every step can be simply ovewritten
d) create display_footer with !function_exist check and move footer to it, so even footer can be overwritten.

I have made no other functions to install.php (even i think it should be revised because of not so nice code as other wordpress) because i think it should be next step

the functions i have created should not be a problem, as they are only in scope of instal.php file

ups, wrong formating and typo. Should be:

...
I have made very small changes to the install.php file

1. add if ( !function_exists( ... ) ) before all (2) functions in this file
2. create 'check_blog_installed' function as enclosure for part with blog checking with !function_exist check again, so it can be also owerwritten
3. create step_0, step_1, step_2 functions, and adding content of code parts run when $step = 0 or 1 or 2, again with !function_exist, so every step can be simply ovewritten
4. create display_footer with !function_exist check and move footer to it, so even footer can be overwritten.

...I have made no other changes to install.php...

new install.php file - replacement for /wp-admin/install.php (previous one miss global $wpdb by mistake))

You should really use svn to generate a diff file.

See ​http://core.trac.wordpress.org/wiki#HowtoSubmitPatches

Replying to scribu:

You should really use svn to generate a diff file.

See ​http://core.trac.wordpress.org/wiki#HowtoSubmitPatches

I know, sorry, but I am probably dumb or old-mind, never been playing with Trac and diffs

I have created diff to actual 2.9.1 version. I have never done it, so please someone to review it.

Diff solving ticket #11093 from version 2.9.1 wp-admin/install.php

Tickets are closed upon code being commited to Trunk.

Setting milestone to 3.0 pending patch review & dev thoughts.

Could you perhaps upload a Unified Diff, for example, from the output of Svn Diff? It'll make the changes much easier to review.

​http://funcdoc.wordpress.com/2008/01/21/how-to-patch-the-wordpress-core/

Punting pending proper patch.

Here is a new patch

Given the lack of activity/requests here, closing as wontfix