
In a recent Business Bloomer Club Slack discussion, a member encountered an issue while working with the WooCommerce-compatible Shoptimizer theme and its required Commerce Kit plugin. The site was hosted on a Plesk-managed VPS running an older MariaDB version, which unexpectedly impacted the functionality of the plugin’s Ajax search after an update.
The underlying issue was related to database indexing support, where the Commerce Kit plugin attempted to create tables using the FULLTEXT index, a feature not supported in the outdated MariaDB version. The problem arose when a recent plugin update, which lacked documented system requirements, inadvertently led to compatibility issues during deployment.
This post explores approaches to mitigate database compatibility issues when updating plugins and provides solutions for WooCommerce developers and site administrators facing similar challenges.
Identifying Compatibility Issues
The member initially noticed that the Ajax search functionality had ceased working, prompting further investigation. After checking the system logs, it was evident that the database update requirement was the root cause, which Commerce Kit’s recent update did not communicate clearly.
Key Troubleshooting Steps
- Database Compatibility: The issue stemmed from the plugin’s attempt to use FULLTEXT indexing, which wasn’t supported in the older MariaDB version. Updating the database resolved this incompatibility.
- Plugin Re-activation: After updating MariaDB, deactivating and reactivating Commerce Kit was necessary. However, this action alone didn’t create the required table, likely due to a cached database configuration. Adjusting the plugin’s database version number forced the plugin to reinitialize and create the missing table, resolving the issue.
Suggested Best Practices
- Ensure a Staging Environment: Always test updates on a staging site before migrating to production, especially when plugins or themes are critical to core site functions. This is particularly important when database updates may impact functionality.
- Monitor System Requirements for Updates: Keep track of updates and their requirements, as plugins and themes may increase their minimum supported versions for PHP, WordPress, or database engines without notice.
- Use Plesk Database Update Scripts: For Plesk/CentOS users, the Plesk control panel now includes a script for easier MariaDB upgrades, automating the process that previously required manual intervention.
This case highlights the importance of regularly updating server environments and thoroughly testing changes before live deployment, especially in high-impact WooCommerce environments.