Support » Plugins and Hacks » Jetpack by WordPress.com » [Resolved] Conflict with BNS Inline Asides in Single Views

[Resolved] Conflict with BNS Inline Asides in Single Views

  • Although I cannot guarantee this started with version 2.0.4, this was the first reported issue.

    I have narrowed down the conflict to Jetpack activated, connected to WordPress.com, and the content being displayed in a single view (read: via single.php, page.php, etc.) This happens with every theme I have tested (my own and the Twenty series).

    The crux of the issue appears to be the inline Javascript BNS Inline Asides uses being stripped out of the content and therefore the plugin’s primary functionality in single view is being removed with it. The plugin functions fine in multiple post views (i.e.: index.php, archive.php, etc.)

    A work-around will be committed to the WordPress repository shortly, although I would much prefer a better solution.

    BNS Inline Asides (WordPress): http://wordpress.org/extend/plugins/bns-inline-asides/

    BNS Inline Asides (GitHub): https://github.com/Cais/bns-inline-asides


Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Jeremy Herve


    Jetpack Mechanic

    Thanks for the report.

    To help us narrowing down the problem, could you let me know if you still experience the issue when deactivating the Sharing module and the Publicize module?

    You can find out how to deactivate Jetpack modules here:

    Thanks for the response!

    Deactivating both Publicize and Sharing modules appears to sort out the conflict; also to note, if only one of the two modules are deactivated the conflict will return.

    I currently use the following conditional:
    if ( ( is_single() || is_page() ) && Jetpack::is_active() ) { ... }

    … is there a more specific conditional I can use to test if both of these modules are active in its place?

    Plugin Author Jeremy Herve


    Jetpack Mechanic

    Thanks for the confirmation. We’ll have a look at your plugin and see if there is a better way to address the conflict!

    Plugin Author Jeremy Herve


    Jetpack Mechanic

    @jeremy – Thanks for the references. I can see how there may be similarities with these conflicts; and, I can tell from reviewing the page source the JavaScript in the plugin is being stripped out when the Publicize and/or the Sharing modules are activated, which appears to be the root of the conflict.

    Although I have not tested some of the suggestions from your references I also do not see reducing (or eliminating) functionality from one plugin to serve another as the best method to go forward long-term.

    I am willing to accept they may be an alternative to writing the dynamic JavaScript I am using, but since the plugin’s initial release I have not been able to successfully refactor the code to work any other way.

    Any other suggestions?

    Plugin Author Jeremy Herve


    Jetpack Mechanic

    As I mentioned earlier, I took note of the conflict with your plugin, and we will have a look at it and see if we can help.

    Of course, you shouldn’t have to reduce or eliminate functionality from your plugin; in the links I posted earlier, the plugin authors made a change to their plugin, solved the conflict, without removing any features.

    Thank you for the offer of assistance, and I would still appreciate more eyes on the plugin, but I also believe I have found a solution.

    It required I sort out a couple of points:

    1. How to use wp_localize_script to pass a dynamic variable to the script
    2. Putting the JavaScript into a separate file (best practice, but point 1 had to be sorted out first)
    3. Enqueue the script so it plays nice with everything else

    I will be making the commits shortly to Extend (it’s already on GitHub).

    Plugin Author Jeremy Herve


    Jetpack Mechanic

    I wanted to let you know that we found on a work-around tolsve all these plugin conflicts. Could you try to update to Jetpack 2.2?

    Thank you.

    Thanks for the update. The “fix” I added last month also appears to have had a beneficial impact.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Resolved] Conflict with BNS Inline Asides in Single Views’ is closed to new replies.
Skip to toolbar