• Resolved olofpinzke

    (@olofpinzke)


    I get an error message in the wordpress admin when editing products, posts or pages.

    Failed to load plugin url: /plugins/ooohboi-steroids-for-elementor/inc/exopite-simple-options/assets/plugin.code.min.js

    In the console

    /plugins/ooohboi-steroids-for-elementor/inc/exopite-simple-options/assets/plugin.code.min.js?wp-mce-49110-20201110

    OoohBoi Steroids for Elementor v 1.7.4
    Elementor v 3.2.3
    Elementor Pro v 3.2.1

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor Oooh Boi

    (@ooohboi)

    What’s the actual error?
    In case you’re the ACE editor user, the following might help: https://github.com/JoeSz/Exopite-Simple-Options-Framework/issues/24

    I am getting this error to.

    Failed to load plugin url: /www/wp-content/plugins/ooohboi-steroids-for-elementor/inc/exopite-simple-options/assets/plugin.code.min.js

    It shows up on the back end when I go to gravity forms, dflip, and other various plugins.

    Plugin Contributor Oooh Boi

    (@ooohboi)

    I don’t think I can do much here. Likewise, Gravity forms can’t (or won’t) do much about being “incompliant” with the Exopite framework.
    Personally, I have never seen nor experienced any kind of errors, and the people who do test “Steroids for Elementor” too.
    I’m sorry but you’ll either have to find a different WP forms builder plugin or forget about Steroids.
    I’ve been using WordPress since 2010, and I experienced situations identical to yours many times so I know it may be frustrating.

    I understand this, you can’t code for everything.

    Just so you know this is also an issue for custom post types. I don’t think it is actually form related…

    This happens for example when WordPress is not installed in the root, but in a subfolder. The get_url() function doesn’t account for this, rather makes some assumptions about how your files are structured. Something like this should be more appropriate:

    diff --git a/inc/exopite-simple-options/exopite-simple-options-framework-class.php b/inc/exopite-simple-options/exopite-simple-options-framework-class.php
    index 4fe4e83..d03c0af 100644
    --- a/inc/exopite-simple-options/exopite-simple-options-framework-class.php
    +++ b/inc/exopite-simple-options/exopite-simple-options-framework-class.php
    @@ -650,11 +650,7 @@ if ( ! class_exists( 'Exopite_Simple_Options_Framework' ) ) :
     		 */
     		public function get_url( $path = '' ) {
    
    -			$url = str_replace(
    -				wp_normalize_path( untrailingslashit( ABSPATH ) ),
    -				site_url(),
    -				$path
    -			);
    +            		$url = plugin_dir_url($path) . basename($path);
    
     			return $url;
     		}
    Plugin Contributor Oooh Boi

    (@ooohboi)

    @pietervanhove, OK, that’s a clue, thanks! I might change that part on behalf of the SFE plugin only, however, I guess the proper way would be to commit changes @ Exopite’s Github.
    …is there a way that you make the pull request on your own?
    I would really appreciate it if anyone is willing to lend a hand!
    Thanks!!!

    I have encountered this issue with one of the Jet plugins in the past from Crocoblock, and their fix for the 3rd party files was to use a URL replace, like this:

    
    add_filter( 'cherry_core_base_url', 'jet_fix_framework_url' );
    add_filter( 'cx_include_module_url', 'jet_fix_framework_url' );
    
    function jet_fix_framework_url( $url ) {
    	return str_replace( 'www/wp-content', 'wp-content', $url );
    }
    

    Rather than wait on them to fix it (who knows when that will be), you can address it this way in the short term and get this terribly annoying issue fixed in your plugin in the short term. Then, when they fix it, it will continue to work because the www/wp-content value won’t be returned any more and won’t be picked up by str_replace().

    What do you think about this solution?

    Plugin Contributor Oooh Boi

    (@ooohboi)

    OK, it’s already on my to-do list for the next update. Thanks!

    Plugin Contributor Oooh Boi

    (@ooohboi)

    In case anyone is willing to test the latest beta 1.7.7 against the “Failed to load plugin URL” error, please download here:

    https://cutt.ly/NnnY1Wv

    Any feedback is appreciated, thanks!

    Thank you @ooohboi for the quick turnaround! The beta 1.7.7 got rid of the annoying error message. I will continue to test to see if there are other issues and report it here.

    Can you also send me a private message when you have a moment to tell me about sponsorship?

    Plugin Contributor Oooh Boi

    (@ooohboi)

    OK, I guess it’ll be fine if I push the official update.
    @dean-loh you can send me an email to oooh(dot)boi29(at)gmail(dot)com if you like. Thanks!!!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘I get error message in backend’ is closed to new replies.