Support » Plugin: Header and Footer Scripts » Beware a weird conflict with WPBeginner’s equivalent plugin

  • warnerta

    (@warnerta)


    If you have ever in the past used WPBeginner’s equivalent plugin, this plugin may cause problems. In my case, when I used this plugin to place some custom JS code in my header, this plugin also somehow found and an old, long-unused snippet of JS code that I had inserted into my header years ago using the WPB plugin, and also placed that in my header. I spent two hours very confusedly trying to debug the very unexpected behavior of my new code before I noticed the old code and figured out how it was getting into my header (it wasn’t visible in the text box where one enters code to be inserted into the code, only my new code was there).

    • This topic was modified 10 months ago by warnerta.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Anand Kumar

    (@anand_kumar)

    The plugin do not add any code whatsoever. You should debug the script again.

    Plugin Author Anand Kumar

    (@anand_kumar)

    Also, if you find any unrecognisable code please share with us. This is highly unlikely but we will dig further.

    warnerta

    (@warnerta)

    Hi Anand. I have figured out what happened. This plugin conflicts with WPBeginner’s plugin of the same type, which I had used in the past.

    When I installed your plugin and added my code, your plugin appended a piece of code that I had installed previously in my header with WPBeginner’s plugin, and then removed. I did not recognize the code because it wasn’t mine – it was third-party code that I put in years ago for some purpose I don’t even remember. It was not in any way security-related. As I said the code set a one-second timer and after that ran down scrolled the screen down 100 pixels.

    This code by the way did not appear in the box where I entered my new code in your plugin. But it appeared in my header. Your plugin must have pulled it out of my wP database or somewhere like that. My theory is that your plugin apparently works so similarly to WPBeginner’s equivalent plugin that your plugin mixes up its own entries with old, no longer used WPBeginner entries still hanging around in the WP database.

    I’m amending my review accordingly.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Beware a weird conflict with WPBeginner’s equivalent plugin’ is closed to new replies.