WP installation removes custom DB tables/fields about wp-browser HOT 8 CLOSED

First idea that comes to mind and the path of less resistance is to use the bootstrapActions parameter in WPLoader config to run the action in charge of creating the tables and to hook the table creation method to a test action.
E.g.

add_action( 'init', [ $tables, 'maybe_create_tables' ] );

// probably not in production code but in a tests config file
add_action( 'test_init_alias', [ $tables, 'maybe_create_tables' ] );

and in WPLoader configuration file:

bootstrapActions:
    - test_init_alias

Running the installation in a separate process is not an impossible task though and I might explore it but I'd like to try easier solutions first.

from wp-browser.

An update on this: I've pushed a first draft code to the https://github.com/lucatume/wp-browser/tree/enhance/separated-process-install branch.
For the time being it does little but replicate what the core testing suite does but that's a start.
Will iterate on this.

from wp-browser.

Yes, this works (almost).

I had to make one change in isolated-install.php. After the defines loop (lines 10-12), I added:

$table_prefix = WP_TESTS_TABLE_PREFIX;

Otherwise all the tables are created with no prefix.

from wp-browser.

Thanks for pointing it out; I've pushed a commit to the branch to fix that.

I've left the code in a branch as I've not yet taken the time to verify all the functionalities; what's that "almost" about?

from wp-browser.

what's that "almost" about?

Just the table prefix comment.

Also, I note that a custom WP_CONTENT_DIR doesn't carry through to the install. That's probably fine, but it does mean that custom tables created by plugins aren't deleted when the core tables are deleted. That works well for my purposes, but I'm not sure if it's a feature or a bug.

from wp-browser.

Ok, thanks.

I will look into the WP_CONTENT_DIR issue as the expected behaviour is to carry over (I guess).

from wp-browser.

Refreshing the issue: how is this going?

from wp-browser.

Closing the issue due to lack of activity, should this not be resolved I will re-open.

from wp-browser.