1.2.3 Errors

  • Resolved 2chicks

    (@2chicks)


    1 month, 3 weeks ago

    1.20 created a fatal error, so I updated to 1.2.3 just now. Now I get different errors:

    Deprecated: preg_split(): Passing null to parameter #2 ($subject) of type string is deprecated in /home/xxx/xxx.com/wp-includes/formatting.php on line 3494

    Deprecated: preg_split(): Passing null to parameter #2 ($subject) of type string is deprecated in /home/xxx/xxx.com/wp-includes/formatting.php on line 3494

    Here’s that line of code:

    $textarr = preg_split( ‘/(<.*>)/U’, $text, -1, PREG_SPLIT_DELIM_CAPTURE ); // Capture the tags as well as in between.

    • This topic was modified 1 month, 3 weeks ago by 2chicks.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter 2chicks

    (@2chicks)

    I should mention that the errors above are only on the page with WP Swiper AND the Swiper doesn’t loop, nor do the arrows navigate. I can swipe with finger or mouse, but the fade and loop and click are gone.

    Also getting errors with 1.2.3

    When adding a block or editing a block, the navigation goes away. Error says to attempt block recovery. After recovery it works again but each edit breaks it.

    Plugin Author digitalapps

    (@digitalapps)

    @2chicks

    This code is not part of WP Swiper $textarr = preg_split
    Perhaps you have some custom php running behind the scenes?

    To get the blocks to work you would need to go through block recovery process by clicking Attempt Block Recovery.

    If you want your frontend to remain operational while you are recovering blocks, enable Legacy Mode in version 1.2.4 by going to Settings > WP Swiper

    ——-

    @llljr you will need take the same steps, please check above

    —

    Let me know how it goes.

    Thread Starter 2chicks

    (@2chicks)

    @digitalapps 1.2.3 didn’t offer block recovery, however I just updated to 1.2.4 and refreshed that page in the back end and it finally gave me block recovery. Seem to be back in business now. Thank you.

    • This reply was modified 1 month, 3 weeks ago by 2chicks.
    Plugin Author digitalapps

    (@digitalapps)

    @2chicks great to hear!

    I also updated my blog post with migration steps that some might find usefull

    https://digitalapps.com/wp-swiper-plugin-update-exciting-new-features-and-improvements-v1-2-0/#migration-steps

    Keep me posted if anything else comes up. This update is a big one, and while I expected it to be challenging, it had to happen. I have more features to roll out soon, and without this update, scaling was becoming increasingly difficult.

    Thread Starter 2chicks

    (@2chicks)

    @digitalapps I would add that if people were already on the page in question, on the back end, to remind them to hard refresh the page AFTER updating the plugin. That makes the Block Recovery thing appear. That’s what screwed me up, was not seeing it, because I hadn’t thought to refresh the page.

    I have to say that you are one of my favorite devs, because you are so kind and responsive. You exhibit a spirit of gratitude and team work. Thanks so much.

    The update fixed my issue. Thanks.

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