digitalapps

as a last resort you can email me your

wp logins

wpengine logins

https://digitalapps.com/contacts/

also this might help: https://docs.wp-rocket.me/article/39-excluding-external-js-from-concatenation

the problem is with the loading order of scripts.

its either this; https://docs.wp-rocket.me/article/976-exclude-files-from-defer-js

or similar, make sure you empty cache after each setting change.

keep me posted, curious to hear how you solved this.

i followed the link https://cbbakstg.wpenginepowered.com/

slider is loaded, am i looking at the wrong site?

Please update to version 1.2.13 and let me know.

Thanks for your email.

All fixed.

As outlined in this article: https://digitalapps.com/wp-swiper-plugin-update-exciting-new-features-and-improvements-v1-2-0/

you needed to click attempt block recovery.
let me know if theres anything else.

I still seeing older version of the html markup for the slider is being generated.
even on a newly created slider.
are you sure you have updated the plugin and cleared your backend cache?

if not may be provide access to me by sending me a private email

https://digitalapps.com/contacts/

IMPORTANT

SInce my last post above, the reference to the bundle script has changed

From: ‘wpswiper-bundle-js’ must be always declared
To: ‘wpswiper-bundle’ must be always declared

the last -js is appended by wordpress so you the correct

wpswiper-bundle-js

BUT !!!!

I just pushed a new update that removes the extra -js

So to correctly target a script is to check for:

wpswiper-bundle

with version 1.2.12 I added a filter that allows you to load a script with defer or async strategies

wpswiper_frontend_js_register_args?Filter

I dont see the same object in prod, this further confirms that the scrip isnt running at the right time, it must be caching of some sort.

I have added a new filter, wpswiper_frontend_js_register_args, which allows users to customize specific parameters when enqueueing the frontend-js script.

Upgrade to v1.2.12

This filter lets you adjust script dependencies (deps), choose if the script should load in the footer (in_footer), and specify additional script loading strategies (e.g., async or defer).

How to Use This Hook

To modify these parameters, add a filter callback to functions.php or your custom plugin. Here’s an example that demonstrates the available options:

add_filter('wpswiper_frontend_js_register_args', function($args) {
    // Modify script dependencies
    // 'wpswiper-bundle-js' must be always declared
    $args['deps'] = ['wpswiper-bundle-js', 'your-custom-dependency'];

    // Example: Set the script to load in the footer
    $args['args']['in_footer'] = true;

    // Example: Specify an additional loading strategy, such as async or defer
    $args['args'] = ['strategy' => 'defer']; // Options: 'async' or 'defer'

    return $args;
});

Explanation of Options

• deps: Use this to add or remove dependencies for the script, ensuring any additional scripts load before frontend-js.
• in_footer: Set to true if you prefer the script to load in the footer, reducing load time on the page’s initial render.
• args: Specify additional script loading strategies by setting 'strategy' => 'async' or 'strategy' => 'defer' within the args array.

With this filter, you can fully customise how the frontend-js script is loaded, making it easier to optimise for your site’s specific needs.

• This reply was modified 3 weeks ago by digitalapps.

heelo, carousel slider is a classic slider with a loop enabled.

what did you have in mind? what is a carousel slider to you?

thanks

on the swiper block, enable debug, and see if you get debug data to show up in the console log. I suspect that the frontend js is not running.

the issue is environment specific and not a plugin issue

in prod frontend.js for the swiper is on line 150
staging in line 139

something definitely is different, hope this helps, let me know how it goes.

in other words, when wp-swiper frontend js is loaded and we run document.querySelectorAll(“.wp-swiper”)

we do not see wp-swiper on page