Home>Support>500 error loading resources for Page Builder and Widgets Bundle

500 error loading resources for Page Builder and Widgets Bundle

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

I am getting 500 errors when I edit a page/post using Page Builder:
This causes some of the features such as the “SiteOrigin Image” to not allow you to click on the: “Choose Media” / “Image Search” / “Remove” buttons.

http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//css/icon-field.css?ver=1.7.1
http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//css/media-field.css?ver=1.7.1
http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//js/icon-field.min.js?ver=1.7.1
http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//js/media-field.min.js?ver=1.7.1
http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//js/icon-field.min.js?ver=1.7.1
http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//js/media-field.min.js?ver=1.7.1
http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//css/icon-field.css?ver=1.7.1
http://dnr.at.utah.gov/wp-content/plugins/so-widgets-bundle/base/inc/fields//css/media-field.css?ver=1.7.1

We are also getting 500 errors on the settings page:
This causes the tabs to not display. And you can’t save your settings.
wp-admin: Settings: Page Builder:
http://dnr.at.utah.gov/wp-content/plugins/siteorigin-panels/settings//admin-settings.css?ver=2.4.17
http://dnr.at.utah.gov/wp-content/plugins/siteorigin-panels/settings//admin-settings.min.js?ver=2.4.17
http://dnr.at.utah.gov/wp-content/plugins/siteorigin-panels/settings//admin-settings.min.js?ver=2.4.17

Notice they all have a double slash in the middle of the URL: This is what is causing the webserver to throw a 500 error. I dont know if it is our particular apache config. I have not noticed these 500 errors on local XAMPP versions… But the extra slash is not correct in any case.

NOTE:
plugin_dir_url() documentation states that this function returns a trailing slash. Removing the extra slash in the code on the following lines fixes these 500 errors.

I have found the following in the plugin code:

FILE:
/wp-content/plugins/so-widgets-bundle/base/inc/fields/media.class.php
Line: 156, 157

wp_enqueue_script( ‘so-media-field’, plugin_dir_url( __FILE__ ) . ‘/js/media-field’ . SOW_BUNDLE_JS_SUFFIX . ‘.js’, array( ‘jquery’ ), SOW_BUNDLE_VERSION );
wp_enqueue_style( ‘so-media-field’, plugin_dir_url( __FILE__ ) . ‘/css/media-field.css’, array( ), SOW_BUNDLE_VERSION );

FILE:
/wp-content/plugins/so-widgets-bundle/base/inc/fields/icon.class.php
Line: 81, 82

wp_enqueue_script( ‘so-icon-field’, plugin_dir_url( __FILE__ ) . ‘/js/icon-field’ . SOW_BUNDLE_JS_SUFFIX . ‘.js’, array( ‘jquery’ ), SOW_BUNDLE_VERSION );
wp_enqueue_style( ‘so-icon-field’, plugin_dir_url( __FILE__ ) . ‘/css/icon-field.css’, array( ), SOW_BUNDLE_VERSION );

FILE:
/wp-content/plugins/siteorigin-panels/settings/settings.php
Line: 166, 167

wp_enqueue_style( ‘siteorigin-panels-settings’, plugin_dir_url(__FILE__) . ‘/admin-settings.css’, array(), SITEORIGIN_PANELS_VERSION );
wp_enqueue_script( ‘siteorigin-panels-settings’, plugin_dir_url(__FILE__) . ‘/admin-settings’ . SITEORIGIN_PANELS_JS_SUFFIX . ‘.js’, array(), SITEORIGIN_PANELS_VERSION );

Please fix!

I have had to edit these files directly which means I will have to keep making this fix until you place the fix in a future release. Is there another way I can apply a temporary fix?

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, 8 months ago Alex S
    Hi, I Work Here

    Hi Joseph,

    Thanks for reporting this. This was set to be fixed in the next version already but we somehow missed the icon form field occurrence – I’ve corrected this now. Very sorry about this typo!

    To clarify, this is only an issue on certain setups. I’m unsure of the exact setting that causes this issue to become apparent, sorry mate. :(

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