SooBahkDo

Agreed

Hello,

I agree this is s a very useful plugin.

It would be great to get the bug fixed that is conflicting with customizer saving.
That issue necessitates deactivating the plugin. ?? ??

For whatever its worth customizer saving fails for us when Woocommerce is active. Deactivating Woocommerce restores customizer saving.

When Woocommerce is active and customizer saving fails, then deactivating this plugin resolves the issue.

Maybe someone who is a coder can figure out a fix. hint, hint. ??

• This reply was modified 3 years, 9 months ago by SooBahkDo.

Here is an example of another plugin that identifies the source of the post types:
Secondary Title previously did something similar. Without this additional information, the post type selection section is almost useless.

Media: attachment
Template: elementor_library
Page: page
Post: post
Product: product
Wishlist: wishlist
Custom Section: wpbf_hooks
Hide Price & Add to Cart Button: addify_whp
Font: elementor_font
Icon Set: elementor_icons
Feedback: feedback
Follow-Up Email: follow_up_email
Product Variation: product_variation
Coupon: shop_coupon
Order: shop_order
Recipe: uo-recipe
Global Label: wapl
Reusable Block: wp_block
Graphics Type: wpf_graphics
Wp feedback Type: wpfeedback
Badge: yith-wcbm-badge
Role Based Prices: yith_price_rule
Custom CSS: custom_css
Changeset: customize_changeset
Plan: jp_mem_plan
Order: jp_pay_order
Product: jp_pay_product
Navigation Menu Item: nav_menu_item
oEmbed Response: oembed_cache
Revision: revision
Refunds: shop_order_refund
To-Do: todo
Automator Action: uo-action
Automator Closure: uo-closure
Automator Trigger: uo-trigger
User Request: user_request
Gravity Forms Entry: wf_gf_entry
Gravity Forms Form: wf_gf_form
Plugin: wf_plugin
User: wf_user

• This reply was modified 3 years, 9 months ago by SooBahkDo.
• This reply was modified 3 years, 9 months ago by SooBahkDo.

We have the same issue on PHP 7.3.

Is there an update resolution for this?

Hello javmah,

I hope all is well.

This is a Genius plugin! I think it has great potential.

Unfortunately, I too, experienced some issues upon activation.

I have sent you reports and screenshots directly via your support channel.

I look forward to you squashing those bugs so we can enjoy using your plugin on many sites. ??

Best wishes for a very successful endeavor!

Hi John,

I am not sure about the answer to your inquiries, but here is what I observe and have concluded.

Other plugins that do not deal with users and which are activated network-wide only affect the network(s) they are activated on. Those plugins’ features only appear on the network(s) where the plugin is network activated.

I thought perhaps User Switching might be a different case since users are shared across all networks and all sites on a multi-network.

It seemed possible that because users are common to all sites and networks on the multi-network install, that perhaps only one instance of it might be needed on the main site and the features might be available on all. ??

When I attempt to activate User Swithing on a network where it is not displaying as activated the following error occurs.

Plugin could not be activated because it triggered a fatal error.

Fatal error: Cannot declare class user_switching, because the name is already in use in /home/soobahkdous/public_html/wp-content/plugins/user-switching/user-switching.php on line 36

Upon further inspection, the User Switching feature displays on the user list page which would seem to indicate the plugin is active elsewhere on the multi-network, but its features are available on all other networks and sites on the install.

Am I off the road and in the ditch? ??

• This reply was modified 4 years, 6 months ago by SooBahkDo.

A helpful article
https://premium.wpmudev.org/blog/wordpress-multi-network/

Thanks for the reply.

I understand and agree.

My experience with Multi Networks Plugin is that is isolates network active plugins to the specific network they are active on.

So each different network can have different plugins active.

That said, I concur with your assertion that activating Wordfence on the main network site would mean that it can scan the entire code base.

The only question I still have is whether or not that single activated instance would be able to detect aberrant code execution on the other networks?

My experience is that on a Multi-Network installation a plugin can totally crash a network and not affect any of the other networks. It seems that perhaps WP compartmentalizes the code execution somehow. That’s just a guess.

That being said, I doubt Wordfence would be able to detect aberrant code behavior on any network other than the one where it is activated. I say that because unless it is specifically designed to see across networks, it is likely to be limited to the network it is active on.

Now all that being said and absent specific Wordfence compatibility with Multi-Networks, I do believe that one instance active and scanning on the main site would provide installation level protection.

However, it seems that to have site-level code execution protection it may be necessary to activate Wordfence on the main site of each sub-network and disable scanning for all those activations. There would be no need to scan the code base multiple times, but there would be a benefit having Wordfence monitor every site for aberrant code execution.

What I plan to do is:

SCENARIO A
1) Configure a Multi-Network installation and activate and configure WordFence with scanning on only the main site.
2) Then on some sites on a different network on that same installation, I will execute some actions that always trigger a Wordfence warning and whitelist option. If that still happens then, Wordfence is able to see across networks. (I doubt it will be able to do so since it is not specifically coded for Multi-Networks and all other regular WP plugins seem to be restriced to the network they are activated on.)

SCENARIO B
1) Configure a Multi-Network installation and activate and configure WordFence with scanning on only the main site.
2) Activate Wordfence on several other networks on the installation and DISABLE SCANNING on all those supplemental activations. It seems that should leave Wordfence’s code behavior monitoring active and working on each site on each network where Wordfence is activated.
3) Then on each different network on that same installation, I will execute some actions that always trigger a Wordfence warning and whitelist option. If that still happens then, Wordfence is able is able to detect aberrant code behavior, but will not be scanning the code base per activation.

I realize there are a lot of if, buts, howevers and assumptions in here, but the logic seems reasonable and potentially workable until such time as Wordfence adds Multi-Network compatibility. I do not anticipate that to happen anytime soon – if ever- as I noted only 600 installations of the WP Multi-Network plugin, so I acknowledge this is a rare bird.

I will report back at a later date with the findings of the tests described above.

• This reply was modified 4 years, 9 months ago by SooBahkDo.

Just a shout out and thank you to cyrfer (@cyrfer)!

The code modifications in the files you identified eliminated the console warning in our use case.

Thank you for chiming in to help!

Given the move toward the block editor, it seems like we will need to locate or create a block with similar features.

We use Beaver Builder and Elementor and other page builders, so looks like I need to extend my search for a replacement for this great plugin into those realms.

Shoot!

Hello spark36,

My experience has been that WordPress sending emails directly tends to work ok for low volume. Delivery time can be long (deferred cron jobs waiting for site traffic) and overall deliverability to user inbox (rather than their spam folder) can be inconsistent under some mixtures of circumstances related to email volume, host parameters, sending speed, IP address being spam listed, etc.

We use SendGrid for all transactional emails on 100 plus sites and also for mass newletter emailing to 40k plus recipients. Transactional emails are received instantly (password rests, etc.) and we have very few reports of Newletter delivery hitting user spam folders.

Even though we run a dedicated server, before we began using SendGrid, we had many user reports of not receiving password reset emails, not receive newsletters, etc.

We no longer get such reports with SendGrid.

This article may be of use:
https://www.wpbeginner.com/opinion/why-you-should-never-use-wordpress-to-send-newsletter-emails/

Best of luck!

Hello spark36,

Link shortening is a great idea even if it may go beyond the scope of this plugin.

You can submit feature ideas for this plugin and vote on others’ ideas here: https://www.wpsimplegiveaways.com/ideas/

We use Pretty Links https://www.ads-software.com/plugins/pretty-link/ because it allows shortening of links while preserving our site domain in the url. So rather than all the shared links featuring the urls for link shortening services, they all still feature our site domain even though shortened.

No loss of SEO value, or linking value or brand recognition.
Highly recommended. We use the Pro Version.

Best of luck with your giveaways in the New year!

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

I too, would love to see this plugin refreshed. ??

Have been using it on multiple multisite networks, but recently it began introducing a huge delay in image related post editing activities and we had to disable it. Sure do miss it!

Thank you for your prompt reply.

Just to make sure I understand the broadcast canonical setting,

Is the following correct?

By default the Yoast plugin creates a canonical rel on each post which points to itself, so when the Broadcast plugin canonical setting is checked, then Broadcast replaces the default Yoast canonical rel on each child post with a canonical rel that points to the parent post.

Am I on track?

Thanks!

• This reply was modified 5 years, 6 months ago by SooBahkDo.

Hello laboy

What about just selecting only the custom post types you want it to display on in the configuration page. It lists all registered post types that the plugin recongnizes and you can deselect all that you do not want the starbox to display on.