bitpath

Yup. Exact same thing I’m sure. I network activated it, but didn’t test behavior on network admin. I only noticed this reviewing child sites for network activated plugins. It was still super helpful sorting through a conflict, and I tested disabling it and it brought child plugin searches right back.

Well, thank you for caring! If you think it might just be something quirky with my setup, please let me know as well.

I hate to throw a kink in it, but the changes don’t seem to affect my setup.
I have this network activated on a multisite and am configuring the new options in the site menus. I still need to set site config in a simple network activated plugin I think. I think this will still work for most people and don’t want to complicate things because of my setup, but wanted to let you know the image past did not seem to take with TMCE Advanced network activated and individually configured in the site admin menus, but my odd setup may be a poor test case.

Thank you for adding that!
I agree, too many options in your face is clutter, especially small use case ones.
I was thinking more of a single “fine, let it all through then” option at first, to let as much as possible come through to help troubleshoot various issues, like missing charts, pictures, empty paragraphs, styles, etc., and then switching to html to see what it was coming over as to see what was being blocked. That’s how I’d use it, but I don’t know how many people would make use of that or just be lazy leaving it all unfiltered and leaving a crazy mess of code in their wake.
Well, thank you again. Even without any more options your plugin is quite a help as-is. thank you also for explaining the implications of string encoding the clipboard images right next to the option!! I’m wondering if the “stop removing p and br tags…” option will help people reporting empty paragraphs and line breaks disappearing after the update. If that options was already there I hope people will take a second look at it too!

For anyone having this problem, the good folks at https://premium.wpmudev.org/ solved it for me. They advised to network activate buddypress, which was a no-go for me since I needed it on a certain site that was not root, then advised to use the following code in my wp-config.php file to define which blog I wanted buddypress on. So I was able to network activate buddypress and set it to the right multisite child blog I wanted and then network activate this privacy plugin fine.
define ( 'BP_ROOT_BLOG', $blog_id );
(replace $blog_id with the ID of the blog you want buddypress on. You can see which one this is by looking over your database and seeing which one has what number as part of the table names, or if you have a domain mapping plugin it may list the site IDs)
Here is the buddypress reference for the config options to point it to a specific site when it is network activated.
https://codex.buddypress.org/getting-started/customizing/changing-internal-configuration-settings/
Cheers and good luck!

Hi,
I have buddypress on a child site of my multisite. It is not on the main site.
Buddypress is active there, but this plugin does not show up anywhere but in the network admin plugins. I wonder why it does not even show up in the list of plugins to activate on child sites, especially the one buddypress is activated on.
I think my issue is the same, the only place this is visible to activate it from is the network admin, and network activating it triggers a fatal error because buddypress is activated on the dashboard of a different site this won’t show up on to activate it from. As far as I know the only reason a plugin should not show up on child multi sites to activate is if it’s network activated but this one is not and is still not showing up on the site I am trying to activate it on, it’s only listed in the network admin plugins where it can’t be activated.
please advise. thank you.

Do you have any other plugins that manage widgets? It may not be wp-client, it could be any plugin that is designed to manage widgets interfering with it.
The clue for me is I saw wp-client code in the area where I usually do my tinymce edits.
If you go to Appearance->Widgets, is there anything else showing up where you would normally edit, like a drop-down or control from a different, recently installed or recently updated plugin?

Ozz is already considering how to best implement something like this, and he’s the true TinyMCE guru here. I know just enough to fiddle. There are potential problems with my workaround, sometimes bringing over undesired styles or messy code, especially for end users not comfortable reviewing text mode or using the format eraser.
I look forward to however he sees best to give a few more filter options! This really isn’t the best default config for many, disabling all the cleanup by default, it’s just easier for my current workflow. Thank you so much and glad it helped!

That would be really cool!

I’d prefer a “paste all wysiwyg” button to selectively enable these elements and bypass default filtering only if needed, but with my limited skill-set, disabling the cleanup as much as I could think of solved my current need.

I totally get that it disables the cleanup.
I really dig your plugin by the way.
TinyMCE default cleanup was way too restrictive for me, preventing me from pasting screen print images, excel tables and other elements. I’d rather paste as text (cleaned up) when I want or use the little eraser.
I appreciate the warning about pasting bad code from IE and Firefox and feel mileage will vary on that one. For some just being able to copy and paste images from clipboard or certain elements from Word/Excel might be more important to workflow than the underlying code being pretty. I don’t mind it encoding images right in the HTML in a pinch to paste a quick screenshot, but realize it might make some cringe :). I use mostly Firefox and Safari and switch back and forth wysiwyg and text modes often and haven’t noticed a lot of extra markup in my normal usage, but will keep an eye out.
Thank you for a great plugin!

They just fixed it with 3.6.6!
I confirmed with their developers that the current update should fix it and they did.
What they did is recently add a box to widgets to select which “WP-Client” pages the widgets appear on. Initially there was bug in the code that gave errors and also interfered with editing content in widgets but it seems fixed now.
I asked them to consider making this feature optional since I don’t need it (since there’s widget logic and so many other options to manage where they show up) and I’m not sure about a hook into my widgets I can’t turn off since I’m not using or needing it, but maybe others could.. As long as the defaults are to leave them alone.. ??

This is related then. I will change my approach from trying to have certain sites silo’d, since all members must come back to the network root or main site to reset passwords.
Does this mean in a multisite, all users by nature have access to the main site? I assume yes, and I just noticed they are. If you restrict someone from the root domain site then of course this is counter to wordpress multisite if that’s where they reset passwords for example, right?
Thank you. I really was thinking of this differently so I’m straightening out my thinking and approach.

Point is the URL they are is a certain site and they are requesting a password from a certain site. I considered this a bug at first that everything else, even admin area can be configed to look like a specific site but the password reset and link crudely takes them back to the network root without further ado or explanation.
I was only thinking of certain members with access to just 1 of the sites.
It does seem better to educate though, since some people will use multiple sites, and I will look at adjusting the password reset page to make it clear they are changing it for multiple sites.
I can see a few different cases where people want everything for a certain site to reference that site. I managed to use domain mapping and such so that even the admin area can be transparent, but not being able to configure that one part, the password link stood out like a sore thumb. I was thinking of some limited cases and will change my approach. I did not want to give everyone access to my root site but not doing so would obviously cause confusion if the password reset always references it.
thanks!

Ah, so it’s a usability/design issue and intentional, in other words, not likely to be addressed or changed in core.
Got it.
I’m not going to argue semantics of what they’re changing. There is a point to multisite, and if a member only has permission on site A, and they click reset password from site A, they expect the email and link to pertain to site A. The network underneath should be transparent to them. Of course, I as the admin, know the network root and underpinnings, etc.
thanks