gerrit787

Ah, OK!
Thanks for clarifying this.

I found some other threads on this – somehow they didn’t show up when I searched before – and after checking the “Allow Page Access” checkbox users now can login again. Strange…

Looks like the problem is gone.

Now, I’m not sure what did the trick. Maybe the changes I made but it can also have been a couple of updates, maybe WP (4.53) or the theme or plugins..

Anyway, no more time limit exceeded errors since the last ones I reported here (also not on the test site).

Thanks for your help.

A slow server is unlikely. This site runs all alone on a pretty powerful VPS.
It could be the page, yes.
Setting up a test site as we speak. ??

Back to the drawing board I’m afraid.
No more undefined offset notices but three maximum execution time fatal errors, two on line 76 and one on line 176.

OK, your last answer pointed me in the right direction I think. ??

In SimpleTable.php I commented out the section
// Get attributes on table tag
since I don’t use attributes and/or a class.

Next I added:
$class = “”;
$attributes = “”;
to avoid new notices.

It’s been running like this for a while without notices and/or errors.

So far, so good.

The syntax (same on every page) is the most simple form:

[table]
spec(1)|value(1);;
spec(2)|value(2);;
….
spec(n)|value(n);;
[/table]

Like I wrote, I checked all tables and found a couple of times a line like this within the table tags:
comment;;
which I changed into:
comment|;;
After that the error still shows up every now and then.
So I’m pretty sure the syntax is not the problem.

Now the undefined offset warning shows up 50 times or so in the log file and directly after that the max. execution error shows up. Looks like there is a relation IMO.

I haven’t found a way to find out from which page the osd plugin was called before the error occurs. That would make life a lot easier.
Do you have a suggestion how to do this?

I might setup a test site one of these days, it will come in handy for other stuff, too.

Thanks for your time and effort, I really appreciate it!

This is what’s happening (around 50 times or so) before the max. execution time error is thrown:
PHP Notice: Undefined offset: 1 in /home/*account*/public_html/wp-content/plugins/osd-simple-table/SimpleTable.php on line 82

Thanks for your answer.
It’s not “the table”, there are tables (to show specifications nicely laid out) on >300 pages and (temporary) deleting those is out of the question.
I went through all tables in phpMyAdmin and found a couple of syntax errors: on a couple of pages on one row one column was empty and the | was not present. I fixed that.
Ever since I got one error (on line 76) but unfortunately the error message doesn’t show on which page. I will try to get a more detailed error report so I can find out on which page.