spellingerrer

Nevermind, figured this out, just have to have a blank first column in the CSV file.

I should also add: In Chrome on a Mac, I can’t even click the elements on the page, I have to resort to editing the database directly using phpMyAdmin. Not an ideal situation.

Is there an easy way to do the custom CSS you describe? Looking at the rows it seems that they all have a custom class name (e.g. “row-234”), and to get this working I’d have to add a CSS entry for every row above 100…which seems excessive.

It seems to me the best solution is to just have a tiny bit of javascript that loads before the table is loaded that will hide the extra rows, if the user doesn’t have javascript enabled this hiding will never occur.

Made a minor update to it to not show “failed” when the hashes match.

Hi, OK I’ve added this, here’s a patched version that adds a hash to not update if the table is unchanged:

https://www.dropbox.com/s/jt7bsd13ig2ukp3/hashed-auto-update.tar.gz?dl=1

For manual imports I think it should forcibly update the table even if it’s unchanged, so I think it really only needs to be done for the auto updates.

One could just add a column to the table database entry called “autohash” or something that’s blank by default, whenever an auto update is performed that value is filled with a hash of the imported text. If the auto update ever matches the previous hash, it exits early. This would add a tiny computational cost, one could use a very cheap hash for this since collisions should be rare.

Hi Tobias, that seems to be a reasonable work-around, it also has the advantage of always executing whereas the normal cron only executes on a page load. Thanks very much for your assistance, and sorry for making you solve a problem that seems to be WordPress-wide!

My guess would be that this has cropped up suddenly because “Let’s Encrypt” is finally in an open beta, so a lot of websites have started adding SSL certificates (such as mine).

So I installed Crontrol, and at the top of the list of cron events is the following:

“There was a problem spawning a call to the WP-Cron system on your site. This means WP-Cron events on your site may not work. The problem was:
SSL connect error”.

So it’s definitely related to SSL. I have no idea how to resolve it though, I have a valid SSL certificate. But It’s not TablePress specific I don’t think.

I’m pretty sure this is related to SSL, *all* of the tablepress plugin cron tasks do not run anymore (such as the update checkers for tablepress-responsive-tables, etc.). I’ve also noticed that all of the hooked functions are arrays for the tablepress plugins; whereas the other cron tasks, which are still working, use a function name instead.

One more thing: No matter what I set the auto-update recurrence time to be, the “due time” is always 1 hour in the future (even for the 15 minutes setting).

OK, with core control I manually ran the auto import cron, and it worked. However, the “due time” was not updated! So it seems like the due time is not properly being updated, that’s why it’s only running manually. Saving the configuration resets the due time.

So some more bits of info for you:

– Turned off caching entirely, problem still exists.
– Saving the configuration alone does not import the table, need the combo of saving + manually loading wp-cron.php.
– Nothing in the log files with WP_DEBUG enabled.

I suspect this might still have to do with SSL in some way (since that’s the only thing that’s changed, aside from moving to 1.7). But I am not sure what exactly is breaking.

I will tool around a bit with the cron plugins to see if I can learn more. Thanks for your hard work on this great platform!

The site is using caching. I should also add that manually running the cron does not work unless I save the configuration too!

I do have admin access to the server and can run my own cron jobs, but I’m not sure how I’d go about saving the configuration each time beforehand.

So by saving the configuration and then forcefully running the cron via wp-cron.php?doing_wp_cron I was able to get the auto import to fire, but it is definitely not firing on its own (12 hours now even though I set it to 15 minutes). Saving the configuration by itself is not enough, the auto import will not fire until I run the cron manually.

As for the SSL I’m using the “file on server” option, so it shouldn’t be using the web server at all to pull the data.

One other note: Today I was upgrading things and started using SSL on my server. This might be another reason why the plugin stopped working.