Thank you for the suggestion. I have completed the database table checks you requested. Here is what I found:
- bczap4sP_icl_translate — tid column has AUTO_INCREMENT enabled, no rows with id = 0 found
- bczap4sP_icl_translations — sequential IDs, data intact with 5,117 records
- bczap4sP_icl_translation_status — sequential IDs, no anomalies found
- bczap4sP_posts — ID column has AUTO_INCREMENT enabled, structure normal
All primary keys have AUTO_INCREMENT enabled and no duplicate or zero ID rows were found in any table. Database corruption does not appear to be present.
For additional context, during troubleshooting I discovered that the wp_icl_translations table (note: wrong prefix) did not exist, but this was because my site uses the bczap4sP_ table prefix, not wp_. The correct table bczap4sP_icl_translations is intact and healthy.
The core issue remains: when WPeMatico's cron fires to pull in a new post, WPML causes the admin area to become inaccessible. When I deactivate WPML via File Manager, the post appears and the admin area is restored. I then have to manually reactivate WPML.
I have already tried the following without resolving the conflict:
- Switched WPeMatico from WP-Cron to an external server cron job
- Created a mu-plugin to unhook WPML during post insertion using wpematico_post_insert_before and wpematico_post_insert_after hooks
- Increased PHP memory limits and max execution time
- Confirmed all translation settings are set to manual, not automatic
The mu-plugin approach did not resolve the issue, which suggests WPeMatico may not be firing those specific hooks in my version, or the conflict is occurring at a different point in the process.
Could you advise on what specific WPML hook or process is interfering with WPeMatico's post insertion, and whether there is a supported way to suspend WPML's post registration during automated imports?
I have done some research on the WPematico plugin and while I did not find any known compatibility initiative between them and our time, nor many users reporting it, I did locate one user that confirms similar experience and that the plugin had to be deactivated due to issues between it and WPML.
