The logs aren’t shown

Have you moved your site recently or installed any new plugins or similar?

Could you go to Settings ? Simple History ? Debug and see if there is any note there about missing tables or similar. Also do you have any values under “Database size”?

Also try to clear any caches you have (redis/object etc.).

I run a cache plugin WP-Optimize.

https://ibb.co/h1pTBzB

I don’t see any missing tables…

It’s starts to bug out when I have a certain amount of rows. If I empty the rows, it starts working again. Until a certain moment when it just shows that error.

That sounds strange. How many rows do you have when it starts to bug out? It has never happened to me, but perhaps if you are on a lower end server it could run out of memory or similar. You don’t by any chance have access to PHP/server error logs? It would be interesting to see if they report anything.

Sorry for the late reply. But I sadly don’t have any access to the server. But if you know a way to let PHP error logs spawn on my WP website in the form of a text log … I’m all ears to help resolve this issue.

I have probably the same problem – The Simple History admin page is completely empty (same for metabox), only its header is shown. DB tables are OK (80 + 1100 rows).

The server error log contains this error:

WordPress database error The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay for query … # START SQL_STATEMENT_LOG_ROWS

Thanks @mklusak for the error message. I have not seen that message before.

Could you tell me something about your hosting setup? Are you for example on a shared hosting, a budget hosting, a big end hosting.. any clues here would be useful.

Yeah, it’s shared hosting, nothing fancy. MySQL version: 5.5.5-10.5.19-MariaDB-0+deb11u2-log.

If I tries to run that monsterous query with SET SQL_BIG_SELECTS=1, it works and return ONE row (maybe that’s correct). max_join_size variable is 268435456.

Ok thanks. I have to read up on that error message and I will install that version of MariaDB locally to test a bit more.

80 + 1100 rows really does not sound that large in my opinion… :/

Can you run the query with EXPLAIN first and see if anything suspicious shows up? Not really sure what that could be however…

EXPLAIN -> https://ibb.co/s2pGDNJ … not sure if it helps.

If I use SET max_join_size=18446744073709551615; before query, it works. So there is a problem in the local “268435456” value – too low.

Hello, in my problem, your access to database does not allow to alter table, and simple history need alter or update your table in first install, I’m log every function on register and get that problem.

for Mr. @eskapims I don’t this suggestion can’t you execution or no, if you can create table in first installation without edit/alter table. because maybe user wp doesn’t have access to adjust permission on the MySQL

• This reply was modified 9 months, 2 weeks ago by masif088.

@masif088 thanks for the report. I think the issue you have is another one than the one that this support thread is about. That said, I agree that the first install logic could be improved.

@mklusak @nekojonez I may have a fix for this issue in version 4.14.0 of the plugin. Please give it a try!

I’ll keep an eye on it. And if it breaks, I’ll let you know. Is it best to clean out the history so it’s “clean” and generated by the latest version?

Cleaning should not make any difference. Just let it continue working/collecting.

Sounds like it’s working fine. We are a week now and it didn’t have the behavior it had in the past ??