• Resolved King Ding

    (@dazzerr)


    Hello!

    Can I disable this plugin using ‘Plugin Organiser’? This will disable the plugin on the frontend on either all or selected pages. I’d like to think that this won’t effect the functionality of this plugin since it’s a backend plugin?

    Thanks,
    – D

    P.S – would love to see this plugin updated, and even perhaps see it grow into a premium version!

Viewing 12 replies - 1 through 12 (of 12 total)
  • hannah

    (@hannahritner)

    Hi D,
    I haven’t worked with Plugin Organiser, but I believe this would be a question for their support. Let us know if you need specific information from us!
    Thanks for the feedback! We definitely intend on keeping this plugin updated:) Let us know if there are specific features you’re wanting!

    Kindly,
    Hannah

    Thread Starter King Ding

    (@dazzerr)

    Hi Hannah – I don’t think this is a relevant question for their support? Regardless of whether it’s Plugin Organizer or my own function, my question for Kadence is: can I unload this plugin on the frontend of the site?

    Thanks,
    – D

    hannah

    (@hannahritner)

    Hey D,
    From my understanding, this plugin doesn’t load on the frontend. So it shouldn’t be slowing down your site. Are you experiencing something different? I would discourage disabling it in the organizer.

    Kindly,
    Hannah

    Thread Starter King Ding

    (@dazzerr)

    Interesting. In which case, why would you discourage me manually unloading it from the frontend? Considering you suggest that it’s already unloaded from the frontend?

    From my tests, there are indeed no assets from Kadence that are being loaded on the frontend. However for some reason, when I load the WordPress Customizer on a few pages I am greeted with this error: https://www.dropbox.com/s/p2x2q3po7vqaakt/Screenshot%202020-12-11%20at%2008.20.12.png?dl=0

    I discovered after unloading Kadence from these particular pages eliminates this error, and then I can use Kadence as expected.

    Ay clues to why this might be happening?

    hannah

    (@hannahritner)

    Thanks for posting that. I’ll forward this to the developer and have him provide some insight.
    Thanks for your patience!

    Kindly,
    Hannah

    Hey,
    You wrote:

    In which case, why would you discourage me manually unloading it from the frontend?

    Because in order to work in the customizer you have to have the plugin loading when your site is loading the front end. The customizer in WordPress is built using the front end. So while the email part of this plugin is going to happen on the backend of your site it still needs to load along with woocommerce for all the hooks to properly be added and for the email customizer to work.

    I strongly suggest you not try to unload this plugin. It uses hooks to prevent your site from slowing down and loads how it’s supposed to be loaded. If you are having an issue please let us know what the issue is and I would be happy to help you. You should not break the way the plugin was designed for no reason.

    All the best!

    Thread Starter King Ding

    (@dazzerr)

    Thank you both. Ben, I understand.

    If you are having an issue please let us know what the issue is and I would be happy to help you.

    I am having an issue – I already mentioned that, so please do advise if you have anything to add. As a workaround, I have unloaded the plugin on this specific page in question. There seem to be no side effects in this case, but you have answered my question in that I definitely shouldn’t unload the plugin site-wide.

    Thanks,
    – D

    Hey,

    Sorry, I don’t understand then, I thought your issue was because you were unloading the plugin.

    If you are getting an undefined function for wc_get_order_statuses then are you unhooking woocommerce?

    https://github.com/woocommerce/woocommerce/blob/master/includes/wc-order-functions.php#L93

    Help me understand your issue. How do I recreate it?

    Ben

    Thread Starter King Ding

    (@dazzerr)

    Ah yes, of course! I overlooked that. (Obviously) Kadence requires WooCommerce. But on this particular page (or group of pages) I’ve unloaded WooCommerce, hence the Kadence error! Thanks for pointing that out ??

    Regards,
    – D

    Hey,

    Well glad that is worked out.

    Because of session tracking (live carts on your site), I don’t suggest unhooking woocommerce. I’m not sure I understand what all you are going for with unhooking things. Perhaps unhooking rendering scripts would be good and you can do that in different optimization plugins but unhooking the entire plugin seems extreme. ??

    Best of luck!

    Ben

    Thread Starter King Ding

    (@dazzerr)

    I understand how session tracking works, but it doesn’t pose a threat to my site. In my instance, I’m using a buddypress site. Consequently, it’s not necessary for WooCommerce to be active on the social pages, such as: Activity, Groups, or Forums. I wanted to separate the shopping and social experiences because people don’t go to the activity feed to shop, but rather to be social.

    Thanks for the tips Ben! ??

    Multisite are really great for that kind of setup. Glad you got it working.

    Ben

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Can I disable on frontend?’ is closed to new replies.