Hi,
thanks for your post, and sorry for the trouble.
Unfortunately, the Extension is a bit hard to debug, as everything runs separately and not on the actual page load.
The good thing: Your are tables are importing with the manual import, which means that something in the automation (and not the import) is not working.
TablePress uses WordPress cron jobs for this, which require active site visitors (as these are triggering them in the background). This is also why the time span is so unpredictable. So, for example caching plugins can cause problems here.
One idea (if the server and the service plan with the web host company supports them) is to use a real server cronjob, which can be more stable. The setup is slightly different for each company, but here’s a fairly common set up guide:
https://www.siteground.com/tutorials/wordpress/setup-cron-job.htm
Also, you can try to use plugins like https://wordpress.org/plugins/core-control/ or https://wordpress.org/plugins/wp-cron-control/ to fix issues with the cron system.
Then, it’s important that there’s enough memory available for PHP on the server. It’s therefore good to use a modern version of PHP (like PHP 7.2 or 7.3), and to maybe increase the memory limit, e.g. to 1024M, via https://wordpress.org/support/article/editing-wp-config-php/#increasing-memory-allocated-to-php
Also, you should check the server error log files for any potential hints.
Regards,
Tobias
Thread Starter
claing
(@claing)
Thank you for the suggestions. I have not gotten an opportunity to fully dive into cron jobs, however after disabling the table auto update feature for all but the one I really need seems to be a solution at the moment. The one table is now auto updating at regular intervals as expected. It just appears I cannot have more than one table assigned to auto update at a time. Maybe this workaround will be helpful to somebody else as well.
Hi,
hhm, that’s not really too nice of a solution, but good to hear that it works as a workaround for now.
Regards,
Tobias