WordPress.org

Ready to get started?Download WordPress

Forums

Dave's WordPress Live Search
Broken with Domain Mapping WPMU? (4 posts)

  1. Carl
    Member
    Posted 3 years ago #

    I've been running this great plugin for a while on a WordPress Network install with subdomains and Domain Mapping.

    Recently however the live-search plugin broke. It doesn't manage to load jquery.dimensions and daves-wordpress-live-search.js properly.

    Let's say a WordPress-site might be:
    http://clientswebsite.wordpresshoster.com/my-wordpress-post/

    Which with domain mapping would appear as:
    http://clientswebsite.com/my-wordpress-post/

    However, the following is how the live-search plugin attempts to load js-files in <head>:
    http://clientswebsite.comhttp//clientswebsite.wordpresshost.com/wp-content/plugins/daves-wordpress-live-search/jquery.dimensions.pack.js?ver=3.1

    What's up?

  2. Aldo
    Member
    Posted 3 years ago #

    Similar issue here:

    The JS code gets loaded like this:

    <script type='text/javascript' src='http://www.domain.com?dwls_js=dimensions& #038;ver=3.1'></script>
    <script type='text/javascript' src='http://www.domain.com?dwls_js=livesearch& #038;ver=3.1'></script>

    Note: I had to put a space between "&" and "#", so it shows correct here, but the space is not present in the code!
    I use the latest DEV version from 14.03.2011

    Any idea?

  3. Dave Ross
    Member
    Plugin Author

    Posted 3 years ago #

    Here's what's going to happen: The next version of DWLS is going to use WordPress's own plugin_dir_url() function to load JS & CSS resources. This should clear up all compatibility issues with supported WordPress configurations, like WPMU. It will also break compatibility with WP Subdomains and other plugins that don't implement the "plugins_url" filter, but that's not my problem. I'm done dealing with it. I'm tired of making special exceptions. I spend too much time dealing with this crap instead of working on new features or any of my other projects.

  4. Carl
    Member
    Posted 3 years ago #

    I for one think it's wise to follow the current norms set by the core developers. Plugins failing to conform to current standards should simply be left behind unless the core itself manages to fix compatibility.

    It certainly shouldn't be a plugin developer's job to provide compatibility-fixes above the current standard, I think.

    In the case of WP Subdomains that plugin hasn't been updated since before 3.0 and seems abandoned.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic