anyone with the same problem?
Can you please post the community system report from your MainWP Dashboard for review? The report is located in your Dashboard under Status → Server, on the top right of the page.
Be sure to use the button like the one below; this button hides all your private information:
Pressing the button auto-copies the report to your clipboard then just paste it in a reply here.
### Server Info Required Detected Status ### MainWP Dashboard MainWP Dashboard Version 4.1.6 4.1.6 Pass MainWP Upload Directory Writable Writable Pass MainWP Extensions Advanced Uptime Monitor Extension 5.1.1 API License Active Pass MainWP Clean and Lock Extension 126.96.36.199 API License Active Pass MainWP Client Reports Extension 4.0.8 API License Active Pass MainWP Google Analytics Extension 188.8.131.52 API License Active Pass MainWP Rocket Extension 4.0.2 API License Active Pass MainWP UpdraftPlus Extension 4.0.4 API License Active Pass MainWP Wordfence Extension 4.0.3 API License Active Pass WordPress WordPress Version >=3.6 5.7.2 Pass WordPress Memory Limit >=64M 512M Pass MultiSite Disabled =true true Pass FileSystem Method = direct direct Pass PHP PHP Version >=5.6 7.3.28-1+0~20210503.84+debian9~1.gbp6819da Pass PHP Safe Mode Disabled =true true Pass PHP Max Execution Time >=30 seconds 480 Pass PHP Max Input Time >=30 seconds 480 Pass PHP Memory Limit >=128M 512M Pass PCRE Backtracking Limit >=10000 1000000 Pass PHP Upload Max Filesize >=2M 64M Pass PHP Post Max Size >=2M 64M Pass SSL Extension Enabled =true true Pass SSL Warnings = empty Pass cURL Extension Enabled =true true Pass cURL Timeout >=300 seconds 300 Pass cURL Version >=7.18.1 7.52.1 Pass cURL SSL Version >=OpenSSL/0.9.8l OpenSSL/1.0.2u Pass PHP Allow URL fopen YES PHP Exif Support YES ( V7.3.) PHP IPTC Support YES PHP XML Support YES PHP Disabled Functions , pcntl_alarm, pcntl_async_signals, pcntl_exec, pcntl_fork, pcntl_get_last_error, pcntl_getpriority, pcntl_setpriority, pcntl_signal, pcntl_signal_dispatch, pcntl_signal_get_handler, pcntl_sigprocmask, pcntl_sigtimedwait, pcntl_sigwaitinfo, pcntl_strerror, pcntl_wait, pcntl_waitpid, pcntl_wexitstatus, pcntl_wifcontinued, pcntl_wifexited, pcntl_wifsignaled, pcntl_wifstopped, pcntl_wstopsig, pcntl_wtermsig, PHP Loaded Extensions Core, PDO, PDO_Firebird, PDO_ODBC, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apc, apcu, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dba, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imagick, imap, interbase, intl, ionCube Loader, json, libxml, mbstring, memcached, mongodb, msgpack, mysqli, mysqlnd, odbc, openssl, pcre, pdo_dblib, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, readline, recode, redis, session, shmop, soap, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib MySQL MySQL Version >=5.0 10.1.48-MariaDB-1~stretch Pass MySQL Mode NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION MySQL Client Encoding utf8 Server Info Server Software Apache/2.4.25 (Debian) Operating System Linux Architecture 64 bit Server Protocol HTTP/1.0 HTTPS ON Server self connect Not expected HTTP response body: User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36 Gateway Interface CGI/1.1 Memory Usage 11.07 MB Request Time 1622654861 Accept Content text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9 Accept-Charset Content N/A MainWP Settings Number Of Child Sites 11 Use WP-Cron Yes Optimize for Shared Hosting or Big NetworksNo Automatic Daily Update Install trusted updates Abandoned Plugins/Themes Tolerance 180 Maximum number of posts to return Maximum number of pages to return Primary Backup System MainWP UpdraftPlus Extension Maximum simultaneous requests 4 Minimum delay between requests 200 Maximum simultaneous requests per ip1 Minimum delay between requests to the same ip1000 Maximum simultaneous sync requests Minimum simultaneous install/update requests Active Plugins MainWP Dashboard 4.1.6 Active Redis Object Cache 2.0.18 Active Wordfence Security 7.5.3 Active WP Mail SMTP 2.8.0 Active
The report seems fine.
Can you tell me do you get this problem only on one child site or all?
Does it help if you resync?
I can reproduce this issue. The wrong data is loaded. This is visible when you view the Wordfence widget on a single child site page.
I’ve found the solution in line 342-344 of the file mainwp-wordfence-extension/class/mainwp-wordfence.class.php, but If I try to post it here, I get a 403 error…
On 342 $localBlockToday is used and the following 2 lines need to become similar, but with $localBlockWeek and $localBlockMonth
@bogdan Can you please make sure this will be fixed in the next update? Thanks!
On all my child sites the same issue.
Thank you for your help Jos
I just checked with the dev team and they were able to duplicate and fix the issue. We will release this fix within next 24 hours. If you want to check the pre-release version, please PM me and I will send you the update.
Thank you for providing a quick fix (coming soon now…?)
MainWP Wordfence Extension 4.0.4 has just been released
Thanks for the update, but it still doesn’t show up on my dashboard’s updates. I’ve clicked “Check for updates” in the plugin screen multiple times and also on the WP Dashboard - Updates page. Is that still the bug with the broken updates checker, that comes back too often? Or hasn’t it been released to the users yet? The changelog hasn’t been updatet either. MainWP Wordfence Extension Changelog - MainWP WordPress Management
Hi Jos, the extension has been released to users. The changelog is updated now too.
If your dashboard doesn’t catch that update by tomorrow, please try to deactivate/reactivate the extension, activate API and check for updates again.
P.S. We are planning to upgrade the update system very soon. So I hope that these small glitches will go away.
I know the workaround, but as it’s not a one time bug, but a problem for already 9 months. Would it be useful to move this topic to a separate post to debug it or do you already know the cause and isn’t it something that can’t be fixed?
Please clear the cache, so the updated changelog will be visible.
I just cleared the cache.
Regarding the update problem, we are working on it.
We’re still facing this issue and can’t get the update to appear. I’ve tried clearing the cache, verifying credentials and unauthorising and re-authorising the extension but it’s still not showing.
@bogdan - Do you have any suggestions?
Can you please try to simply reinstall the extension?
Thanks Bogdan, that appears to have worked.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.