How to prevent conflicts with another plugin?

[tangrufus]

Specifically when installed via composer, should we (as plugin authors):

• change namespace (via imposter / mozart)?

• change table names so other plugins won't try to drop my tables?

$this->jobs_table     = $this->database->prefix . 'queue_jobs' . '_my_plugin';
$this->failures_table = $this->database->prefix . 'queue_failures' . '_my_plugin';

• change filter and hook names?

apply_filters( 'my_plugin_wp_queue_cron_time_limit', 20 );
apply_filters( 'my_plugin_wp_queue_connections', $connections );
apply_filters( 'my_plugin_wp_queue_cron_memory_exceeded', $return );

[szepeviktor]

@tangrufus Seems like those are fixed.

[dingo-d]

Only partially if you are using imposter plugin #15.

[ianmjones]

Specifically when installed via composer, should we (as plugin authors):

• change namespace (via imposter / mozart)?

Yes, although we'd recommend PHP-Scoper these days.

• change table names so other plugins won't try to drop my tables?

Yes, you should definitely use unique custom table names.

• change filter and hook names?

Yes, in your subclasses override the functions that use apply_filters() and rename them to be unique to your plugin.

This last one in particular is a bit of a pain, we should probably make this easier with some sort of prefix property or similar, and maybe make it easier to install the two tables with the same prefix included in their names.

I've marked this issue as an enhancement that we should look into.