Plugin Compatibility - ProjectNami/projectnami GitHub Wiki
We make no attempts to maintain an exhaustive list of WordPress plugins which do or do not work with Project Nami. There are simply too many plugins available. But we can offer some guidance on evaluating the plugins you want to use.
Plugins fall into four basic categories...
- Plugins which use the WordPress APIs. These plugins should always work. If something is broken, then it is most likely a bug in Project Nami that has not been seen before and needs to be corrected.
- Plugins which query the database directly. These plugins may work. Many times the SQL statement will execute successfully. If it produces an error, we attempt to translate the query and resubmit it to the database. Translation efforts are not guaranteed to work, and they may introduce slight performance reductions as the query will have to be resubmitted with every failed execution attempt. We welcome pull requests which help to improve and expand the translation support. The translation functions are found in /wp-includes/translations.php
- Plugins which create their own database tables. These plugins are very likely to fail. While translation functions exist for table creation, there are so many different ways to structure those statements in MySQL that we simply cannot support all of them. It may be possible to work around some of them through the addition of plugin-specific translation updates as above, and we welcome such submissions.
- Plugins which call the MySQL objects directly. These plugins are guaranteed to fail. Obviously the point of Project Nami is to use SQL Server, so the MySQL objects are not configured and in some installations may not even exist. An example of this type of plugin is WooCommerce.