Pro Reports issues after MainWP 6 update

Hi MainWP Support,

I’m having a few problems with Pro Reports since updating the MainWP Dashboard to version 6.

The scheduled reports at the beginning of the month weren’t sent, and when I now select multiple sites and click Send Now, the first report generates and sends, but it doesn’t move on to the next site. The screen stays on a spinner and the remaining sites aren’t processed.

In the browser console I’m seeing a JavaScript error from fomantic-ui.js:

“Slider: The method you called is not defined. [‘value’]”

For context, during the initial v6 update I also ran into a database issue with the MainWP log tables, which I resolved by dropping them and allowing MainWP to recreate them. It may not be related, but I wanted to mention it as background.

I’ve cleared caches, disabled optimisation, switched to the default template, and fully reinstalled the Pro Reports extension, but still no luck.

Any thoughts would be appreciated.

Many thanks,
Will

And here’s my System report:

WordPress Check Required Detected

FileSystem Method = direct direct Pass
MultiSite Disabled =true true Pass
WordPress Memory Limit >=64M 64M Pass
WordPress Version >=6.2 6.9.1 Pass

PHP Required Detected

cURL Extension Enabled =true true Pass
cURL Timeout >=300 seconds 300 Pass
cURL Version >=7.29.0 7.88.1 Pass
Function `tmpfile` enabled N/A Enabled Pass
OpenSSL Version >=OpenSSL/1.1.0 OpenSSL/3.0.11 Pass
OpenSSL Working Status Yes Yes Pass
PCRE Backtracking Limit >=10000 1000000 Pass
PHP Allow URL fopen N/A YES
PHP Disabled Functions N/A No functions disabled.
PHP Exif Support N/A YES
PHP IPTC Support N/A YES
PHP Loaded Extensions N/A Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, bcmath, ctype, curl, date, dom, exif, fileinfo, filter, gd, hash, iconv, imagick, intl, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_sqlite, posix, random, session, sodium, sqlite3, standard, tokenizer, xml, xmlreader, xmlwriter, zip, zlib
PHP Max Execution Time >=30 seconds 600 Pass
PHP Max Input Time >=30 seconds -1 Pass
PHP Memory Limit >=256M 512M Pass
PHP Post Max Size >=2M 512M Pass
PHP Safe Mode Disabled =true true Pass
PHP Session enabled N/A Enabled Pass
PHP Upload Max Filesize >=2M 512M Pass
PHP Version >=7.4 8.2.18 Pass
PHP XML Support N/A YES
SSL Extension Enabled =true true Pass
SSL Warnings = empty Pass

MySQL Required Detected

MySQL Client Encoding N/A utf8
MySQL Mode N/A ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
MySQL Version >=5.0 11.3.2-MariaDB-1:11.3.2+maria~ubu2204 Pass

Server Configuration Detected Value

Accept Content text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Charset Content N/A
Architecture 64 bit
Gateway Interface CGI/1.1
HTTPS ON
Memory Usage 8.89 MB
Operating System Linux
Request Time 1772452069
Server Protocol HTTP/1.1
Server self connect Response Test O.K.
Server Software Apache/2.4.57 (Debian)
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:148.0) Gecko/20100101 Firefox/148.0

MainWP Dashboard Settings

Abandoned plugins/themes tolerance 365
Cache control enabled No
Enable Uptime Monitoring No
MainWP Dashboard Version Latest: 6.0.1 | Detected: 6.0.1 Pass
MainWP legacy backups enabled No
Maximum number of pages to return 50
Maximum number of posts to return 50
Maximum simultaneous install and update requests3
Maximum simultaneous requests 4
Maximum simultaneous requests per ip1
Maximum simultaneous sync requests 8
Maximum simultaneous uptime monitoring requests (Default: 10)10
Minimum delay between requests 200
Minimum delay between requests to the same ip1000
Number of connected sites 26
Optimize data loading Yes
Plugin advanced automatic updates enabledYes
Primary Backup System WPvivid Backup for MainWP
REST API enabled No
Site health monitoring enabled Yes
Theme advanced automatic updates enabledNo
Use WP Cron Yes
WP Core advanced automatic updates enabledNo

Extensions Version License

Dashboard Lock 5.0.3 Active Pass
MainWP Domain Monitor Extension 5.1.4 Active Pass
MainWP Fathom Extension 5.0.2 Active Pass
MainWP iThemes Security Extension 5.0.1 Active Pass
MainWP Lighthouse Extension 5.2 Active Pass
MainWP Pro Reports Extension 5.0.10 Active Pass
MainWP Time Tracker Extension 5.1.1 Active Pass
WPvivid Backup MainWP 0.9.40

Plugin Version

Admin and Site Enhancements (ASE) 8.4.2 Active
Health Check & Troubleshooting 1.7.1 Active
MainWP Dashboard 6.0.1 Active
Redis Object Cache 2.7.0 Active
WP Crontrol 1.21.0 Active
WPvivid Backup MainWP 0.9.40 Active
WPvivid Backup Plugin 0.9.124 Active
WPvivid Plugins Pro 2.2.41 Active

Hey @WIllB

On the Dashboard site only, please temporarily deactivate Admin and Site Enhancements (ASE) and Redis Object Cache, and flush the object cache. Then hard refresh your browser with Ctrl + F5 and try sending the reports again.

If that doesn’t change anything, please deactivate everything except MainWP Dashboard and MainWP Pro Reports, hard refresh again, and test “Send Now” on multiple sites.

Also, can you confirm how this report is configured? Is it assigned directly to individual sites, or is it assigned via Tags or Clients?

If it is assigned to Tags/Clients, try changing it by assigning it to a couple of individual sites and see if that helps.

Hi Bojan,
Thanks for the suggestions but sadly, no luck. All plugins, apart from the MainWP Dashboard and extensions, are deactivated. I also cleared the object cache before disabling Redis and have done a hard refresh. The error I’m still seeing is:

Slider: The method you called is not defined.
Array [ “value” ]
fomantic-ui.js:19690:38

Re the reports themselves, they are applied directly to the sites via the Report Settings > Select Sites checkbox list.

During testing, I also tried a different browser in incognito mode since I did wonder if it could have been a cached js file lurking but I don’t think that’s the case.

Thanks,
Will

Thanks for trying that.

Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further?

Please refer to this Community thread by its URL in the ticket.