duttoluca

I solved it by myself, updating All in One SEO plugin solved the issue, there was a bug with the interaction with the internal REST API.

Logs are empty, ’cause I can’t save the settings if there is no valid token…
I click on Save in Advanced Settings and it doesn’t save ’cause there is no token (and another error 500 in console)

Hi, sorry to bother you again… when do you foresee to release the new version with the fix, in broad terms?
Days, weeks?
Thank you very much
Luca

Glad to hear that, thank you for your support!

Hi @bornforphp

I tried what you suggest, the result is always the same: wildcard is ignored.

As an additional test, excluding /td0551 correctly excludes the page, while /td0551/* doesn’t work with the subpages.

All other exclusion methods (UserAgent, cookie) are working correctly.

• This reply was modified 3 years, 6 months ago by duttoluca.

Thank you very much, but this code doesn’t seem to work: the aioseo metabox is still visible even if I put the slugs of the post types to disable in $disabledPostTypes…

Yes, I can install that plugin.
Or, maybe better, I could run some code from my functions.php…
Thank you very much

Thank you @arnaudbroes
The metaboxes are the problem indeed. In the previous version I configured some content types to have their AIOSEO metabox hidden, now they’re visible again for every content type.
Your suggestion to use Content Types > Post Type > Advanced is what I’m searching for…
But: since I’m working in a multisite with a lot of subsites, is there a way (maybe updating something in wp_xx_options via SQL?) to hide the metabox for a given post type in every site?
I mean: I want to hide the AIOSEO metabox for content type ‘foobar’ in 100 subsites without having to do it manually in the backend…is there a clever way to do that?
Thanks

Thank you.
But they’re unchecked already in my sites…

Thanks for your help, here the full log.
AFAIK the SMTP server only accepts TLS1.0…
My server is Ubuntu 20.04, PHP 7.4 + WordPress 5.5, OpenSSL 1.1.1f

Versions:
WordPress: 5.5
WordPress MS: Yes
PHP: 7.4.3
WP Mail SMTP: 2.5.1

Params:
Mailer: smtp
Constants: No
ErrorInfo: SMTP Error: Could not connect to SMTP host.
Host: mail.postassl.it
Port: 587
SMTPSecure: tls
SMTPAutoTLS: bool(true)
SMTPAuth: bool(true)
SMTPOptions: {"ssl":{"verify_peer":false,"verify_peer_name":false,"allow_self_signed":true}}

Server:
OpenSSL: OpenSSL 1.1.1f 31 Mar 2020

Debug:
Mailer: Other SMTP
SMTP Error: Could not connect to SMTP host.

SMTP Debug:
2020-12-24 09:20:36 Connection: opening to mail.postassl.it:587, timeout=300, options=array ( 'ssl' => array ( 'verify_peer' => false, 'verify_peer_name' => false, 'allow_self_signed' => true, ),)

2020-12-24 09:20:36 Connection: opened

2020-12-24 09:20:36 SMTP INBOUND: "220 smtpcm1-pc.aruba.it bizsmtp ESMTP server ready"

2020-12-24 09:20:36 SERVER -> CLIENT: 220 smtpcm1-pc.aruba.it bizsmtp ESMTP server ready

2020-12-24 09:20:36 CLIENT -> SERVER: EHLO hosting.pa-online.it

2020-12-24 09:20:36 SMTP INBOUND: "250-smtpcm1-pc.aruba.it hello [34.91.190.87], pleased to meet you"

2020-12-24 09:20:36 SMTP INBOUND: "250-HELP"

2020-12-24 09:20:36 SMTP INBOUND: "250-AUTH LOGIN PLAIN"

2020-12-24 09:20:36 SMTP INBOUND: "250-SIZE 524288000"

2020-12-24 09:20:36 SMTP INBOUND: "250-ENHANCEDSTATUSCODES"

2020-12-24 09:20:36 SMTP INBOUND: "250-8BITMIME"

2020-12-24 09:20:36 SMTP INBOUND: "250-STARTTLS"

2020-12-24 09:20:36 SMTP INBOUND: "250 OK"

2020-12-24 09:20:36 SERVER -> CLIENT: 250-smtpcm1-pc.aruba.it hello [34.91.190.87], pleased to meet you250-HELP250-AUTH LOGIN PLAIN250-SIZE 524288000250-ENHANCEDSTATUSCODES250-8BITMIME250-STARTTLS250 OK

2020-12-24 09:20:36 CLIENT -> SERVER: STARTTLS

2020-12-24 09:20:36 SMTP INBOUND: "220 2.0.0 Ready to start TLS"

2020-12-24 09:20:36 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS

2020-12-24 09:20:36 Connection failed. Error #2: stream_socket_enable_crypto(): SSL operation failed with code 1. OpenSSL Error messages:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol [/var/www/webpa/wp-includes/PHPMailer/SMTP.php line 426]

SMTP Error: Could not connect to SMTP host.

2020-12-24 09:20:36 CLIENT -> SERVER: QUIT

My bad. Obviously it’s 1 star!

Hi, thank you for your support.

Analyzing the error log I found the problem, it’s not directly related to your plugin, I report it here in case this anomaly impacts on someone else…

When cloning a site, an email is sent to the administrator, but I see in the logs that in WP 5.5 some mailing functions have been deprecated: the email crashed, and so did the cloning process.
Upgrading my email smtp plugin (WP Mail SMTP) to the latest version solved the issue.

Same here, it looks like a temporary connection / routing problem.
From my office and servers I can’t reach the jsDelivr api url, from my home or my mobile phone no problems at all…

I’m using Disable Gutenberg in a multisite environment, and it works as expected.
Just network-activate it and you’re ready to go.

As you suggested, the ‘ure_cpt_editor_roles’ filter works as expected.

function filter_ure_custom_roles_add( $roles ) {
    $roles = array("administrator", "tutto");
    return $roles;
}
add_filter( 'ure_cpt_editor_roles', 'filter_ure_custom_roles_add' );

Thank you.

• This reply was modified 4 years, 10 months ago by duttoluca.