You mean this stuff?
s:16260:"a:239:{s:32:"4391e507c3c844f25aa9733904ec66c2";a:1:{s:10:"11-30-2018";b:0;}s:32:"fe14d2ecd3b792b7721ca271908ee95c";a:1:{s:10:"03-06-2019";b:0;}s:32:"78ade9f3978b8376bc403968b6c9679a";a:1:{s:10:"03-06-2019";b:0;}s:32:"d6a58ea589153e7c500807b09566f499";a:1:{s:10:"03-06-2019";b:0;}s:32:"4c2a6d9793eaf7a538a08e237b25e5d3";a:1:{s:10:"03-08-2019";b:0;}s:32:"1f55730e6d89487037163e3798830870";a:1:{s:10:"03-08-2019";b:0;}s:32:"bf957302601db435942b169e1b16a449";a:1:{s:10:"03-08-2019";b:0;}s:32:"3a4b551a84ce877dea5122a09bb11084";a:1:{s:10:"03-08-2019";b:0;}s:32:"242670b85c3d5f530c32158555c4e6b4";a:1:{s:10:"03-08-2019";b:0;}s:32:"8dab7632536d134c9cac371ec85a0f58";a:1:{s:10:"03-08-2019";b:0;}s:32:"6efe07b2942331de168c999393c8d7fe";a:1:{s:10:"03-08-2019";b:0;}s:32:"bc7c5cf2cd2890ac1b4c913bb7c41259";a:1:{s:10:"03-08-2019";b:0;}s:32:"9c7dd07eaa6bd4dfe76801034055a532";a:1:{s:10:"03-08-2019";b:0;}s:32:"ce6a7764e600be8ea92feecda9c20c0b";a:1:{s:10:"03-08-2019";b:0;}s:32:"a02605a96e0eb77df06fd2b52e12718f";a:1:{s:10:"03-08-2019";b:0;}s:32:"9e3b127f418bdaa459fe8fdb8833b8de";a:1:{s:10:"03-08-2019";b:0;}s:32:"2bfde6fd3584c6b56e7929ae03b1347f";a:1:{s:10:"03-08-2019";b:0;}s:32:"59660ee70128a0614596b1f1ba395e4c";a:1:{s:10:"03-08-2019";b:0;}s:32:"a02815e1f08d1c8107289d180d3dca76";a:1:{s:10:"03-08-2019";b:0;}s:32:"3d0b4e8e7b3768ebcea76d1c433a3084";a:1:{s:10:"03-08-
Hi,
Yes, that is what I’m seeing and causing the debug log to reach almost 1gb.
Screenshot 1
Screenshot 2
This shouldn’t be an issue anymore in the latest version.
That’s great but the latest version is bundled with other features that seem to conflict with my theme’s login, I had to revert back to the previous version of the plugin, is there a chance you can email us a modified version that addresses the debug logs storage issue (wpua_hash_gravatar) without the actual changes you applied in the latest version?
