Version 2.2.4 causing error

  • I upgraded to version 2.2.4, only to discover that the slider wouldn’t show up correctly (none of the template styles seem to have been applied). Went into the admin panel, tried to update and it presented me with a plain error message. Reverting back to version 2.2.3 solved the issue and now I can only recall the error message partly:

    call_user_func_array() expects parameter 1 to be a valid callback, cannot access private method Cyclone_Slider [[… in /wp-includes/plugin.php on line 173]]

    https://www.ads-software.com/extend/plugins/cyclone-slider-2/

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

  • I also get that error. Need help.

    Plugin Author kosinix

    (@kosinix)

    Hello guys, first sorry for the hassle. Im troubleshooting the problem too but could not reproduce the said error reported by 10010110. Can you please provide me with screenshots or at least a link to your website having this problem

    thanks,
    kosinix

    Hello kosinix,
    In my case the problem is solved by the new update. Thank you very much!!

    I’m having this problem with images from the template not working. Viewing the source, as well as looking in the cyclone-slider-2/css/templates.css file shows what looks like development urls (which may be why you are unable to reproduce the error).

    https://localhost/wp1/wp-content/plugins/cyclone-slider-2/templates/black/images/sprite-nav.png

    I am using 2.2.5

    Plugin Author kosinix

    (@kosinix)

    @brendanmcoffey thanks for the heads up. Im guessing those local paths came from the template.css and template.js that were bundled with 2.2.5, that were generated from my dev machine.

    Try resaving your slideshows, that should update the template.css and template.js with paths to your server.

    The previous versions does not use these files but few users are having problems with css and js not loaded. So i have to resort to compiling the css/js into template.css and template.js.

    Hope this helps!

    Thanks a lot! I re-saved it and we are working great again.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Version 2.2.4 causing error’ is closed to new replies.