Bojan Katusic

Just to provide an update on this –

The issue was caused by the HTTP Basic Auth on the Dashboard site.

Hey @mastafu

Thanks for the additional information. Nothing in the system report stands out as an obvious issue.

Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further? https://mainwp.com/my-account/get-support/)

Hi @mastafu

I assume you’re describing installing plugins via ZIP upload as covered in this knowledge base article? https://kb.mainwp.com/docs/install-by-upload-plugins/

If so, are you able to fully complete the installation procedure on the MainWP Dashboard which results with green checkmarks (as seen in the video embedded at the top of the article)?

Are you using the latest versions of MainWP Dashboard (v4.6.0.1) and MainWP Child plugins on the child sites (v4.6)?

Just to provide an update on this –

@tfrank77 has confirmed that the fix we provided in the Help Desk ticket is good.

It will be included in the next version of the MainWP Child plugin.

>As I said, the main drawback for me and for many users (as seen in other forums) is the lack of possibility to adjust the timing of the scheduled auto updates for Trusted items on a per child site basis. Correct me if I am wrong: this issue/idea has been raised a couple of years ago and it still isn’t in your roadmap (https://feedback.mainwp.com/plugins/roadmap).?

Correct – right now, only the frequency of the automatic updates can be set (from once per day to twelve times per day) but not the actual time.

Please feel free to make a suggestion about this on our feedback site. That way, others can vote for it, letting us know which features our users want the most. https://feedback.mainwp.com

>Asking to use WPCron or similar plugins to handle this expectation is clearly not a correct answer. I want to use MainWP from its Dashboard, full stop. Not experiment things with extra Cron plugins or so.?

WP Cron is a core WordPress functionality used for all scheduled actions, so leaning into it for the scheduled MainWP emails makes sense. After all, all other plugins do exactly that.

The suggestion for additional plugins in your case was related to localhost environment. Unfortunately, the specific limitations of WP Cron in a localhost environment is something that WordPress would have to address.

For us, as a self-hosted WordPress solution, it would be unwise to invest into development of alternative methods.

Hey @tfrank77

I couldn’t reproduce these PHP warning messages with PHP 8.1 and 8.2.

Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further?
https://mainwp.com/my-account/get-support/

Hi @tucpakic

As @linux4me2 pointed out, self-hosting in this context means that the MainWP Dashboard is installed and runs on your own website and hosting environment, which grants you full control of MainWP and the related data.

Email deliverability, in general, can be problematic in local host environments, and so can WP Cron.
It’s important to also mention that while MainWP scheduled emails rely on these systems, they are not MainWP-specific.

Typically, local servers are not configured to send emails by default.
Have you tried manually sending test emails from your localhost site?

WP-Cron relies on website traffic to trigger scheduled tasks. In a local environment where there is no external traffic, WP-Cron might not run as expected.
There are plugins available that allow you to view and manage the Cron jobs that are scheduled within your WordPress site. These can be helpful for testing and debugging.

Setting up MainWP in a web-hosted environment is just as easy.
WordPress site where the Dashboard will be installed can be set up on a subdomain, so you wouldn’t need to have any additional expenses in that regard.

Thanks for the additional information and for making a screen recording for us.

I’ve managed to reproduce the issue and I’ve passed it along to our development team.

The fix for this will be included in the next release of MainWP.

Hey @tucpakic

I couldn’t reproduce this issue. The Time Format set on the MainWP Dashboard -> Settings -> General Settings page was applied to how the time is formatted on the MainWP Dashboard -> Info -> Cron Schedules page.

Are you using the latest version of MainWP Dashboard v4.6.0.1?
Are you using any plugins that may interfere with Date and Time formats?

And if possible, please attach screenshots of your Dashboard where this issue can be seen.

Hi @malakyto

It’s been some time since we heard back from you. I’ll assume that the issue has been fixed and mark the thread as resolved.

If you have any further questions, please start a new thread.

Thanks.

Hi @malakyto

There’s a possibility that the debugging was enabled externally.

Some hosting environments or plugins might enable debugging through methods other than the wp-config.php file. They might alter server configurations or use other mechanisms to initiate logging. In such cases, the wp-config.php file might not have these lines, but debugging could still be active.

Can you reach out to your hosting support and see if they’ve enabled debugging in some way?

Hi?@jwpfleurieu

It’s been some time since we heard back from you. I’ll assume that the issue has been fixed and mark the thread as resolved.

If you have any further questions, please start a new thread.

Hi @jwpfleurieu

We’re glad to hear you’re trying out MainWP.

Locally hosted sites shouldn’t have a problem connecting to a locally hosted MainWP Dashboard, and web-hosted child sites shouldn’t either (although there are some limitations in that scenario).

Would you mind opening a private Help Desk ticket so we can collect some information about your setup & investigate further? https://mainwp.com/my-account/get-support/

You are most welcome for the information, and you are still more than welcome to open a private help desk ticket if you have any logs related to this issue for us to take a look.

If you have any new questions, please start a new thread.

Hi?@surferking

It’s been some time since we heard back from you. I’ll assume that the issue has been fixed and mark the thread as resolved.

If you have any further questions, please start a new thread.