• Resolved wpnpc420

    (@wpnpc420)


    WP Swiper 1.2.0 triggered a fatal error that took down all our WordPress sites (back-office included).

    The error seems to be easy to fix, as it seems to only be a missing file (class-wp-swiper-settings.php) in the /includes/ folder, which is asked for in the file class-wp-swiper.php at line 27:

    E_COMPILE_ERROR on line 27:
    /var/www/vhosts/[...]/wp-content/plugins/wp-swiper/includes/class-wp-swiper.php.

    Error message: require_once():
    Failed opening required '/var/www/vhosts/[...]/wp-content/plugins/wp-swiper/includes/class-wp-swiper-settings.php'

    I’ve rolled back to version 1.1.13 and disabled auto-updates for WP Swiper for now.

    Thanks in advance for your help!

    • This topic was modified 1 month, 3 weeks ago by wpnpc420. Reason: Added version detail
Viewing 6 replies - 1 through 6 (of 6 total)
  • Same here ??

    Plugin Author digitalapps

    (@digitalapps)

    Sorry about the mix-up with SVN. I’m more used to working with Git so my svn routine is a bit rusty. All should be working as expected.

    • This reply was modified 1 month, 3 weeks ago by digitalapps.

    Same problem here, now it’s ok with 1.2.1

    • This reply was modified 1 month, 3 weeks ago by antoaltsrl.

    Thanks for the quick update. Unfortunately, the back-end page with the slider no longer loads. Even when I have removed the slider from the page. Can you please look at this again.
    Thank you!

    the fatal error no longer appears with 1.2.1 but the plugin no longer works

    thank you

    Thread Starter wpnpc420

    (@wpnpc420)

    I see that 1.2.1 released but that it’s still buggy (on the back-end only apparently) now according to the other comments on here. I think I’ll wait for 1.2.2 to release and then wait another few days to actually update.

    At least downgrading worked so there’s no immediate sense of urgency for me anymore.

    Thanks for the quick reply anyway, @digitalapps!

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.