Home>Support>Error upon adding the Bundle Widget Plugin

Error upon adding the Bundle Widget Plugin

“Fatal error: Class ‘SiteOrigin_Widget_Meta_Box_Manager’ not found in /homepages/2/d395080616/htdocs/domain.com/secure_Yx24xT/plugins/so-widgets-bundle/so-widgets-bundle.php on line 645”

Is this because I am using a custom path instead of: “wp-content?”

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 8 years, 29 days ago Andrew Misplon
    Hi, I Work Here

    Hi wireb

    Sorry, I’m not sure off hand. Were you able to find a resolution?

  2. 8 years, 29 days ago wireb

    Unfortunately, have not found a solution for this site while trying to add the Siteorigin Bundle.

  3. 8 years, 29 days ago Andrew Misplon
    Hi, I Work Here

    How is wp-content being changed? Is it with a plugin that hides WordPress? If this is the cause, unfortunately, I’m not sure how far we can look into the issue.

  4. 8 years, 29 days ago wireb

    I have manually changed the path for security reasons. However I suspect that the Bundle may be hard-coded for the default WP path: wp-content.

  5. 8 years, 29 days ago Andrew Misplon
    Hi, I Work Here

    Cool, we’ll take a look.

    Please, drop a quick reply so you’re the last poster. Thanks :) Chat tomorrow.

  6. 8 years, 29 days ago Alex S
    Hi, I Work Here

    Hi Wireb,

    We make use of plugin_dir_path() rather than hard coding wp-content so it’s unlikely it’s related. With that said, what did you do to tell WordPress that you’ve renamed the directory? What happens when you (temporarily) revert this wp-content change?

    Also, if possible could you please do a plugin conflict to rule that out?

    Please try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.

    If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.

    Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.

    If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.

  7. 8 years, 29 days ago wireb

    Thank you Alex for your assistance.

    My mistake, the Siteorigin’s old Button widget has a conflict with the Bundle. Removed it, all seems to work now.

    Ron

  8. 8 years, 29 days ago Andrew Misplon
    Hi, I Work Here

    Super, glad we could make progress here. Thanks Alex, thanks Ron.

  9. 8 years, 28 days ago wireb

    Thank you also Andrew for the “Super glad.”

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More