Hi,
We also observed a similar issue on one of our users WP install (I work for a WordPress hosting company).
From our analysis the issue seems to be that the plugin code expects the shepherd_tec_tasks table to use the InnoDB engine, but on our server the default is MyISAM.
@k4media could this be the same cause for your issue too? Could you please check which DB engine is the default one on your DB and the one used for the table?
You should be able to do such checks via the following queries:
SHOW ENGINES; -- Check for the value "DEFAULT" in the "support" column
SHOW TABLE STATUS WHERE name = "wp_shepherd_tec_tasks";
Hi,
yes, it appears the issue is fixed in 5.3.2.
Thanks!