Title: Plugin Display Problem after update?
Last modified: June 28, 2017

---

# Plugin Display Problem after update?

 *  Resolved [RafaelDeJongh](https://wordpress.org/support/users/rafaeldejongh/)
 * (@rafaeldejongh)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/)
 * I just updated to the latest version of BPS 2.0 and it seems there is a javascript
   error or so as can be seen on this screenshot: [https://ctrlv.cz/shots/2017/06/28/tpDY.png](https://ctrlv.cz/shots/2017/06/28/tpDY.png)
 * The whole menu’s aren’t working as I assume it has something to do with the Javascript
   file.
 * I already tried reinstalling but that didn’t work.
    Does anyone have an idea 
   how to get this fixed?
 * Thanks in advance!

Viewing 7 replies - 16 through 22 (of 22 total)

[←](https://wordpress.org/support/topic/plugin-display-problem-after-update/?output_format=md)
[1](https://wordpress.org/support/topic/plugin-display-problem-after-update/?output_format=md)
2

 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9270912)
 * My guess would be you have a “combo” problem. ie you have many plugins or themes
   that load “rogue” scripts everywhere and they are conficting/colliding, which
   creates a snowball effect the wreaks havoc everywhere. 😉 This particular WPML
   Translation Manager js script is not using WordPress jQuery no-conflict code 
   and is instead using the default method to load jQuery > /wpml-translation-management/
   res/js/scripts.js. I believe the snowball of problems is starting with that particular
   script and if you do some googling you will see that WPML Translation Manager
   has at least a 3 year time span where these particular js errors have been occurring.“
   If it looks like a duck and quacks like a duck…” 😉
    -  This reply was modified 8 years, 11 months ago by [AITpro](https://wordpress.org/support/users/aitpro/).
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9270940)
 * > I think because some scripts are dequeued on the BPS pages that the problem
   > on this page is happening. Because one of the variables was set in a dequeued
   > script file. Maybe it’s possible to also deque that script by default while
   > on BPS pages?
 * BPS does not do anything with or to any other plugin scripts on BPS plugin pages
   unless you turn SLF On. SLF Only affects BPS plugin pages. So since there should
   not be any other plugin scripts loading in BPS plugin pages then it does not 
   matter if another plugin’s script variable has a value or not. SLF only affects
   BPS plugin pages and nothing else anywhere else on your website. Nope we cannot
   dequeue any other plugin scripts by default. That choice needs to be a concious
   choice made by each website owner and by turning SLF On or Off. That is the correct
   WordPress “way”. 😉
    -  This reply was modified 8 years, 11 months ago by [AITpro](https://wordpress.org/support/users/aitpro/).
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9270954)
 * In a perfect world other plugins and themes would only load their scripts in 
   appropriate places (not other plugins pages, etc). So ideally the root problem
   should be fixed – WPML should fix their plugin code.
 *  Thread Starter [RafaelDeJongh](https://wordpress.org/support/users/rafaeldejongh/)
 * (@rafaeldejongh)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9271000)
 * Okay thank you for the in depth information.
 * On my test website, I’ve disabled all plugins except WPML/BPS and WooCommerce
   as these are the three components that are at least required for everything to
   work.
 * Even then the error appeared on the BPS page and these where the scripts that
   were dequeued:
 *     ```
       Script Dequeued: sitepress-scripts
       Script Dequeued: wcml-lang-notice
       Script Dequeued: wcml-pointer
       Script Dequeued: wcml-messages
       Script Dequeued: thickbox
       Script Dequeued: installer-admin
       Style Dequeued: wpml-select-2
       Style Dequeued: wcml_admin
       Style Dequeued: thickbox
       Style Dequeued: installer-admin
       ```
   
 * But yea I do think it’s more related to WPML’s code so I’ll contact them! Thanks
   a bunch for your vastly replies and support!
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9271023)
 * Yep, at this point you have tried everything that is possible to do in BPS to
   workaround the problem in WPML. So yeah the next logical step is to go to the
   source of the problem > WPML. 😉
 *  Thread Starter [RafaelDeJongh](https://wordpress.org/support/users/rafaeldejongh/)
 * (@rafaeldejongh)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9271882)
 * A hotfix for this would probably to add the following piece of code inside the
   script just above the line of the error:
 * `if(typeof iclSaveForm === undefined){var iclSaveForm;}`
 * Pretty much just checks if the variable is undefined and if it is “defines” it.
   
   Not exactly sure yet what kind of effect/influence this will have on the actual
   plugin, but with this it does “fix” the BPS layout problem.
 * I also noticed that my support license expired a couple months ago for WPML so
   sadly I can’t partake in actually asking the question myself yet (until I extend
   it for another year).
 * Either way thanks!
    -  This reply was modified 8 years, 11 months ago by [RafaelDeJongh](https://wordpress.org/support/users/rafaeldejongh/).
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9271892)
 * Cool. I bet the WPML folks would like to have your fix whether or not they get
   any more of your $$$. ha ha ha. 🙂

Viewing 7 replies - 16 through 22 (of 22 total)

[←](https://wordpress.org/support/topic/plugin-display-problem-after-update/?output_format=md)
[1](https://wordpress.org/support/topic/plugin-display-problem-after-update/?output_format=md)
2

The topic ‘Plugin Display Problem after update?’ is closed to new replies.

 * ![](https://ps.w.org/bulletproof-security/assets/icon-128x128.png?rev=1731938)
 * [BulletProof Security](https://wordpress.org/plugins/bulletproof-security/)
 * [Support Threads](https://wordpress.org/support/plugin/bulletproof-security/)
 * [Active Topics](https://wordpress.org/support/plugin/bulletproof-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bulletproof-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bulletproof-security/reviews/)

## Tags

 * [javascript](https://wordpress.org/support/topic-tag/javascript/)
 * [problem](https://wordpress.org/support/topic-tag/problem/)
 * [update](https://wordpress.org/support/topic-tag/update/)

 * 22 replies
 * 2 participants
 * Last reply from: [AITpro](https://wordpress.org/support/users/aitpro/)
 * Last activity: [8 years, 11 months ago](https://wordpress.org/support/topic/plugin-display-problem-after-update/page/2/#post-9271892)
 * Status: resolved