zeno001

Peter.

Thanks for that. Email sent.

Alan

Sorry, can you explain that further – I don’t understand what that means!

Ah.

I realised that Local was installed just for me rather than for all users – I’m not sure why I did that when I installed it. However, I reinstalled Local for all users and after adding Local.exe as an exclusion in Kaspersky, I copied the openssl.cnf file I found in WPVivid (I reckoned this might do as a starting point) and placed it in C:\Users\<user>\Local Sites and pointed the Quick Setup Wizard to that file, it all seems to work – I no longer get that error.

So far so good.

However, I still couldn’t add a site. I got:

“MainWP Child Plugin not detected! Please make sure that the MainWP Child plugin is installed and activated on the child site. For additional help, contact the MainWP Support.”

I wondered if this was being blocked by Wordfence on the child site so I temporarily deactivated it but that wasn’t the cause.

However, switching “Verify SSL certificate (optional)” off allowed the dashboard to connect so it’s finally all working, even if I don’t really understand what the issue was in the first place.

My apologies, @bogdanrapaic, I had missed your reply.

There are openssl.cnf files but they are all in the WPVivid backup plugin directories I have installed in some Local sites. There are none anywhere else.

The directory it’s in is \wp-content\plugins\wpvivid-backuprestore\vendor\phpseclib\phpseclib\phpseclib

So clearly, this is used with phpseclib: does there need to be something installed under MainWP to create that lib and an openssl.cnf file?

@mainwp: have you been able to try it?

• This reply was modified 3 years, 8 months ago by zeno001.

Ha! I read that about ten minutes ago ??

But I’m not clear where it is saying the default location is and what the Windows bug does. Is it C:\OpenSSL-Win32?

And is this all that’s required for an empty openssl.cnf file?

HOME = .
RANDFILE = $ENV::HOME/.rnd

[ v3_ca ]

A local install does seem like a good idea for MainWP so it would be good if you could try it and let me know.

Thanks for your help.

Thanks for the quick response!

I’d found that page but none of the options seems to apply: there is no xampp/wampp directory. If I look at the phpinfo page (linked to in Local), it tells me the location should be C:\usr\local\ssl/openssl.cnf but there is no such location – that’s a Linux path.

Just to see what happens, I did enter that as the location of the openssl.cnf file but when I click on Connect, I get:

MainWP Child Plugin not detected! Please make sure that the MainWP Child plugin is installed and activated on the child site. For additional help, contact the MainWP Support.

If I disable the ‘valid SSL’ option, I get the same (the site does have a valid SSL cert – and all the parameters are correct). If I continue anyway, I get the same error on the MainWP dashboard pages.

If I try to add a site without using a Unique security ID, I still get the same error and the same dashboard warning.

I think a fundamental question is whether I should be selecting Linux or Windows. I have also posted on the Local by Flywheet support forum as I don’t really know where the issue lies but not had a definitive answer yet, just someone on a mac with the same error.

If C:\usr\local\ssl/openssl.cnf is actually the path MainWP wants to use, can I create that directory and copy an openssl.cnf file into it? Is there a way of creating that file?

You know those times where you missed a setting that does exactly what you think was missing? There is a setting in the customizer to stop Nicepage adding its own og: tags – I had completely missed it! Mea culpa.

I Ah. It’s not Jetpack at all: I disabled the Jetpack plugin and I’m still getting duplicate og: tags. Must be a Nicepage issue.

Sorry to bother you and thanks for the help!

Thanks for that, fresatomica.

I’ve also posted on Nicepage’s support forum (as I suspect that’s what’s causing the issue) but I’ll debugging today and try that way of forcing Jetpack to disable the tags.

Thanks for the explanation, Tim.

Thanks for the quick reply, Ronald.

I’m not sure: I am using their free plan and I don’t know if or how I would do that. I’ll investigate but can you tell me what scripts SCE uses?

With 1.3 installed, I see:

Documentation & FAQ | Add-Ons | Opt In | Deactivate

The Freemius website (https://freemius.com/wordpress/usage-tracking/1538/restrict-user-access/) says it tracks:

? Your user’s first & last name
? Your user’s email address & IP

Is this only my data as the site admin, or the details of the other users of the site that Restrict User Access controls?

What’s the problem with freemius? What data is transferred?

I’m back here again…

Artisteer are telling me the error originates from the AIOSEO plugin. The error starts here:

An error of type E_ERROR was caused in line 252 of the file /var/www/vhosts/medico-legalsociety.org.uk/httpdocs/wp-content/themes/Draft0_15/functions.php.
Error message: Uncaught ArgumentCountError: Too few arguments to function theme_update_title(), 1 passed in /var/www/vhosts/medico-legalsociety.org.uk/httpdocs/wp-includes/class-wp-hook.php on line 288 and exactly 2 expected in /var/www/vhosts/medico-legalsociety.org.uk/httpdocs/wp-content/themes/Draft0_15/functions.php:252

This function definition in the theme functions.php:

function theme_update_title($title, $post)

…requires two parameters. The call comes from the core WordPress function in class-wp-hook.php and that is only passing one parameter.

However, although this is a core WordPress file, I understand it’s the plugin calling the WordPress hook with the wrong number of parameters – as the stack trace shows.

If I disable AIOSEO, I don’t get the error, so it all seems to point to the plugin.

Can you confirm this?

Thanks! I’ll chase it up with Artisteer.