TobiasBg on "[Plugin: TablePress] Row delete does not work properly"

Hi,

I had a table with 38 rows from which I deleted 3 rows at the end. But afterwards I had only 22 rows left. So I have to enter 13 rows again. Or is there another way I can get those 13 rows?

Thanks in advance for your help.

Albert

https://wordpress.org/plugins/tablepress/

Hi,

thanks for your post, and sorry for the trouble.

I can then only assume that you inadvertently or accidentally had selected more rows (via the checkboxes on the left) in your table :-(
If you have already saved the table after deleting them, then there's likely no way to get them back, unless you have a backup of the table somewhere, or if it's maybe still cached in the Google Cache or the Inteet Archive's Wayback Machine.

And just to be sure: The rows are gone on the "Edit" screen as well and not just in the frontend, when viewing the table?

Regards,
Tobias

Thanks Tobias!

I'm sure I have ONLY checked those 3 rows for deletion - and saved the table after deletion. Anyway I enter those 13 rows again, make a table export and save it. So I could get it if there are problems.

Albert

Now, after entering again those missing rows and hitting the save button I got an error message, something with AJAX and I should use the SHIFT-key to save it. I did it, got the error message that the table could not be saved. Then I saved it again and now it got really saved.

So, probably with my very first saving I got also this error message, but I did not see it, and the table was not saved.

Albert

Hi Albert,

yes, that AJAX error could indeed be related then. Do you recall the exact and full error message? That might help us find out what exactly on the server caused this. It's usually a server issue, like a firewall that is too strict or a memory limit that is being reached.

Regards,
Tobias

Unfortunately I can't remember the error message. It's a 1and1 server.

Albert

Hi Albert,

ok, then I suggest that we take a closer look if this happens again. Right now, there's nothing really that we can do here :-(
Sorry again that this happened!

Regards,
Tobias