My working version of this plugin

  • I have put a copy of this plugin on GitHub because it appears that the author is no longer maintaining this.

    I have no real interest in maintaining this plugin myself. I just need it work and I’ve implemented some hacks to do that.

    My version has some hacks and fixes to issues reported here on this forum. Specifically:

    • the email error when creating a new user
    • the issue with compatibility with sitemaps in the Yoast SEO plugin
    • being able to blacklist scripts so that they are enqueued properly

    Anyway, until the author returns, if the author returns, you can find it here: https://github.com/Hube2/root-relative-urls

    https://www.ads-software.com/plugins/root-relative-urls/

Viewing 4 replies - 1 through 4 (of 4 total)

  • I wish you had a donate button on there too, you saved my night, just the solution I was looking for with this problematic plugin! Thank you very much for posting this.

    Thread Starter John Huebner

    (@hube2)

    Thanks, I’m just happy that it helped someone besides myself ?? Seriously, I’m hoping that Marcus returns at some point.

    @hube2, How would I blacklist a script using your new, improved version?

    I replaced the original code in sb_root_relative_urls.php with your code from github. Then in the blacklist section in General Settings I put:
    /wp-admin/admin.php?page=revslider
    /wp-admin/admin.php?page=revslider&view=slider&id=3
    /wp-content/plugins/revslider/
    /wp-content/plugins/revslider/js
    (I also tried as absolute links, rather than relative for those lines)

    Which is basically the admin pages and the plugin folder of the 3rd party plugin that I am having trouble with. Do I need to include these in the actual sb_root_relative_urls.php file? Not sure what I am missing. Thanks for any tips you have.

    Thread Starter John Huebner

    (@hube2)

    My altered script only changed the ability to blacklist scripts loaded using wp_enqueue_script(). You must put the full url in rather than the relative path.

    for example: https://www.google.com/whatever.js

    This was the way it was built to begin with and I did not alter that part so I’m guessing you need to have the absolute path (including protocol and domain) for any script you want to blacklist.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘My working version of this plugin’ is closed to new replies.