davidacq
Forum Replies Created
-
@eskapism Issue seems to be fixed when updating to 5.18.0
Thank you very much.Update…
Every time i log in to wordpress dashboard and/or go /wp-admin/index.php, monday until today the error still shows at least once a day, triggers two lines of the same error at once it seems.
Monday:[20-Oct-2025 23:33:38 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
[20-Oct-2025 23:33:38 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
Tuesday:[21-Oct-2025 19:01:49 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
[21-Oct-2025 19:01:49 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
Wednesday:[22-Oct-2025 23:02:43 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
[22-Oct-2025 23:02:43 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
Today:[23-Oct-2025 16:16:07 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
[23-Oct-2025 16:16:07 UTC] PHP Warning: Trying to access array offset on value of type null in /home/public_html/wp-content/plugins/simple-history/loggers/class-theme-logger.php on line 535
Using wordpress versión 6.8.3-es_MX (up to date)
Plugins (all up to date):
Accessibility by UserWay version 2.6.5
Advanced Custom Fields version 6.6.1
Classic Editor version 1.6.7
Classic Widgets version 0.3
Contact Form 7 version 6.1.2
Redirection version 5.5.2
Simple History version 5.17.0
Theme (not viable to switch to default theme in production due to work restrictions):
Custom made theme. Classic style, no gutenberg bloat.
Currently not using anything related to blocks, gutenberg is disabled- This reply was modified 5 months ago by davidacq.
So the last friday when i posted the issue i purged the cloudflare cache, logged out of wordpress, logged back in and the php errors rarely appeared again but still sometimes showed.
Also regarding the history btn issue I noticed that while navigating in the /wp-admin/index.php, it did populate the drop down menu data history results succesfully.
But as soon as i navigate to a normal page, the top admin bar History btn would fail to load the data. and throw the react error in the browser console.
Today I did further tests opening an Incognito tab in chrome and logging in to the wordpress site and there wasnt any issue at all anymore.
Also in firefox didnt have this issues neither.
So i proceeded to open a normal chrome tab, went to the chrome settings -> privacy and security -> site data and permisions -> deleted the individual site data.
Althought i havent seen any php errors today, the issue with the History btn was still there.
Then weirdly enough i disabled the default extension Google Docs Offline that comes with chrome installation. (I recently did a fresh install of chrome this week)
And History btn started to work just fine in normal pages now, enabled Google Docs Offline extension back on.
And History btn still working fine.
Currenly not having any php errors today and after the tests done today i also dont have any history btn issues neither.
Perhaps it was a chrome caching, or extension behavior. I’ll keep monitoring if errors come back.
Thank you for your soon reply.Same here having PHP warning after updating to 5.0.3.
PHP Warning: Undefined array key "_user_id" in /public_html/mysite/wp-content/plugins/simple-history/inc/class-wp-rest-events-controller.php on line 743- This reply was modified 1 year, 5 months ago by davidacq.