executon time exceeds 30 seconds

gerrit787,

It is possible that this error is not caused by OSD Simple Table at all, but we will run with the assumption that it is for the moment. This issue could be caused by a number of things. The first thing I would suggest trying is removing the table from the page causing the issue and seeing if the issue is resolved or not. If the page works perfectly fine without the table, then we know there is something wrong with the use of OSD Simple Table.

Next, I would examine the use of the shortcode carefully. Having a syntax error in the table code could cause some problems. You can always try cutting the table code, pasting it into notepad (windows) or text edit (mac), then cutting it again from their. This will remove any weird formatting html placed in their by WordPress.

If none of those things work, you may reply with your whole table code here and I can personally test it to find out what’s wrong.

I hope this was helpful, sorry you are having problems with OSD ST.

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.

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

I was working under the assumption you were seeing this error on a particular page. My suggestion was just to temporarily remove the table on that page. I understand that removing 300 tables is out of the question.

The “undefined offset” error that you’re seeing is just a PHP notice. That happens any time a table does not provide attributes. This error is not a part of the problem. It is a separate code cleanliness problem that should be addressed.

This still seems like a table syntax issue. Line 76 is a simple string position and should not cause an error like this. It sounds to me like there is a never-ending loop, infinite recursion in “the_content” filter, too much work being done somewhere else, or a simple syntax issue.

If you have a development site, you can try disabling the plugin to see if the error happens somewhere else. Unfortunately, without being able to see the table syntax to test it out, I’m at somewhat of a loss. If you get anymore information, please let me know.

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!

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.

Interesting. That must have been causing another problem somewhere else later on. Good find, and thanks for the information. If that fix ends up not working, please let me know.

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.

That’s more what I expected. Another possible problem could be that the page is sending a huge amount of content through the plugin and it’s just taking a really long time to process.
To test if this is an infinite loop issue you could extend PHPs maximum execution time to 2 minutes or something crazy like that. It could just be that the server is extremely slow or WordPress is loaded up with too many plugins.

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. ??

gerrit787,

Any update on this issue?

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.

I’m glad everything is going well. Thanks for the update.