mainwp
Forum Replies Created
-
Thanks, we’ll get this updated in the next version
Thanks @xtel.cz we’ll get it updated in the next version.
I tried to duplicate this issue for you but using the latest version of both Yoast SEO and the MainWP Child plugin it is not something I was able to reproduce.
Can you verify you are using the latest version of both plugins?
I haven’t seen behavior like that reported before, can you open a ticket at MainWP.com so the support staff can help you more individually?
Apologies for the inconvenience, this will be fixed in our next release. The line causing this was left there unintentionally after debugging.
In the meantime you can either open a support ticket at MainWP.com for a beta version of the Child plugin or simply just remove line 522.
Thanks
The MainWP Dashboard has no specific setting for this.
Your Dashboard shows you the plugin information of your WordPress install (as if you would click “Plugins” -> “View Detail”).
When you have set your locale setting to “fr_FR” your WordPress install will search http://api.wordpress.org/plugins/info/1.0/ with this locale parameter submitted. You can find this code in wp-admin/includes/plugin-install.php, the method is called plugins_api.
So in short: yes WordPress.org uses your locale, so you see an outdated version until all wp.org servers are synced.
Marking as resolved since no follow-up in 3 weeks.
It’s not something on our road map but please feel free to add it to our feature request area
Are you still having the issue with Dashboard 3.1?
What is the language you are seeing the issue with so we can review it?
Your Dashboard enables the style_loader_src and script_loader_src filter on the Child site in order to strip version tags from javascript and stylesheets.
The code is located in the MainWP Child plugin and you can review it here https://github.com/mainwp/mainwp-child/blob/7019c798eaff5c6cc794d9f79bebf9d0778d4dd2/class/class-mainwp-security.php#L16
Here is a blog post on how those functions work.
Your MainWP Dashboard checks if the style_loader_src and script_loader_src filters currently added are sufficient to remove versions. If it is not guaranteed by these filters we mark this is insecure.
If the warning is still there then the Child site does not believe it is connected.
Can you verify that your Dashboard does show it as installed and try syncing that Child site to see if that forces the warning to turn off?
I believe you submitted a ticket to support for this but just in case anyone else needs the information:
Before the child plugin will connect it checks to see if the OpenSSL is available, if not it falls back to md5 encryption. Since your site is giving an an error for SSL the plugin does not know to fall back and instead refuses to allow the connection. This is not the same as using HTTPS in your domain name.
It would be best to start by contact your host to find out why your SSL is giving an error and have them correct it.
If you need anything else, please reply to your help desk ticket.
It will end your loop on the Quick Setup Guide but again, as per the installation instructions the MainWP Dashboard should not be installed on a multi-site setup