Conflict with WP Slimstat

  • paroflyer

    (@paroflyer)


    10 years ago

    This plugin is great and easy to use. However, there is a conflict with WP Slimstat reports. I have been using WP Slimstat for awhile now but when I installed Login Screen Manager my stats disappeared. As soon as I disabled LSM my stats reappeared. I would give this plugin a 5 star if the problem was resolved.

    I realize it would be impossible to predict every conflict. Keep up the good work and thanks for you time in creating this FREE plugin.

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

  • We are looking into this.

    Apparently the plugin enqueues some Scriptaculous files that override standard jQuery functionality. They also create a problem with WordPress’ built-in heartbeat function.

    <script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/prototype/1.7.1.0/prototype.js?ver=1.7.1'></script>
<script type='text/javascript' src='https://192.168.1.10/wp-content/plugins/login-screen-manager/inc/js/jscolor.js?ver=4.1'></script>
<script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/scriptaculous.js?ver=1.9.0'></script>
<script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/builder.js?ver=1.9.0'></script>
<script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/effects.js?ver=1.9.0'></script>
<script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/dragdrop.js?ver=1.9.0'></script>
<script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/slider.js?ver=1.9.0'></script>
<script type='text/javascript' src='//ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/controls.js?ver=1.9.0'></script>
    Thread Starter paroflyer

    (@paroflyer)

    Please put this in layman’s terms, I’m not a programmer. Thank you for your fast response.

    I’m writing on behalf of Slimstat’s dev team. We tested this plugin and we found out that Login Screen Manager adds some code to the page that conflicts with what Slimstat does. The developer should change the code to avoid appending their stuff to Slimstat’s report pages (and any pages not directly related to their plugin, for the matter).

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Conflict with WP Slimstat’ is closed to new replies.