geemco

The thing is that I wanted the post to be shared but only to one profile with its checkbox ticked but not to the one I’d manually unticked. What I can add is that a sort of a “saved” message appeared briefly after deselecting the personal profile. This made me thinking that everything should go well.

I guess the second issue needs to be handled in the way you described. But interestingly after the second modification and unexpected sharing the “don’t share” was automatically ticked afterwards (which I had experienced before in other cases when it was ok to share to both profiles).

The post itself has the “Don’t share this post” unchecked. So in general it’s ok that it would be shared on normal edits/updates. It seems that this is also relevant on quickedits.

As a workaround I’ve tried to set the global setting temporarily to “Don’t share” but older posts (i.e. already published) are still shared on quickedits.

What I haven’t tried yet is to temporarily deactivate the global sharing targets i.e. my personal LI profile and a company profile or sharing posts in general, either to avoid having to rush over to LinkedIn to delete the just shared posts prior to anybody noticing them.

I would prefer quickedits rather than normal ones due to the fact that I want to update tags of 600+ posts and so quickedits make quite a difference.

I’ve digged a bit deeper into that issue. Reason is that a snippet includes the definition of the mentioned function. Each use of the snippet causes a repetitive definition of the same function which is not allowed in PHP. I’ve encapsulated the function definition by a if (!function_exists(randomString)) { } which resolved the issue.

However, I’m still wondering why this hasn’t been a problem before as the resp. snippet is in use for quite some time (prior to WP 5.6).

By the way, when will PostSnippets be made fully compatible with WP 5.6, resp. confirmed to be compatible?

Thanks for checking, Vladimir.

It’s strange as it seems to happen only when I’m logged into the WP backend, Safari & Firefox both on macOS. Same with Edge on Window 10. Once logged out everything looks fine.

Any idea how to dig that down?

Regards,
Goetz

Brilliant! Many thanks!

Thanks!

Sure, I know. But I’m not the author of that plugin. And the code is generally valid and as such it should not be reported.

Thanks, Mike, for the clarification.

Thanks, David, for the clarification.

There are further warnings, raised by php compatibility checker:

/wp-content/plugins/wp-db-backup/wp-db-backup.php
73 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
400 | WARNING | INI directive ‘safe_mode’ is deprecated since PHP 5.3 and removed since PHP 5.4.
858 | WARNING | INI directive ‘safe_mode’ is deprecated since PHP 5.3 and removed since PHP 5.4.
924 | WARNING | INI directive ‘safe_mode’ is deprecated since PHP 5.3 and removed since PHP 5.4.
1239 | WARNING | INI directive ‘safe_mode’ is deprecated since PHP 5.3 and removed since PHP 5.4.

Would also be interested re. any progress.

Thanks, I was close to ask that question as well.

I absolutely second that. I was just about to raise the same topic.