Oooh Boi

That extension is meant to work with the Flexbox Container activated… I don’t know what else could be the problem, everything looks fine on my end.

Breaking Bad will always be available to the Sections/Columns, I don’t have any plans to remove it. However, Elementor will definitely remove them sooner or later (once the Flax Container becomes the stable “experiment”).

Anyhow, speaking of the CSS calc() and the Flexbox Container width, I have made a little addition named “Container Extras”, and if you have flex containers enabled, you can see it here:

View post on imgur.com

OK…
Breaking Bad extension makes sense for Columns and Sections. Flexbox Containers already have all of these options built-in by default.
If you enable the Flexbox Containers experiment you no longer have the option to build the layout with Sections and Columns, do you?
The question is why do you need Breaking Bad for Flex containers? Just disable it under the Experiments and the Breaking Bad extension is back. As simple as that.

The message should be gone now… but in general — YES, you’re good to go compatibility-wise.

All righty, that sounds better! As for the current slide indicator, that should be CSS handled… like:

.glider-e4adb07-gotoslide-1:active {
    /* whatever you need */
}

…far from being ideal (can be lost once clicked outside the trigger) but I doubt you can do anything else without some extra JS code.

Lottie is JS driven, you can’t use any kind of JS within the Swiper (Glider is Swiper) – unless you find a way to refresh the content of a slide every time it gets in focus. Maybe it’ll work without the endless loop being deployed. In that case, Swiper doesn’t duplicate slides and their JS.

Hope it helps!

In what sense does it become slow? I advise you to use Google Chrome Lighthouse to inspect your website and see what the bottlenecks are. Here’s a quick guide on how to use Lighthouse:
https://www.semrush.com/blog/google-lighthouse/
I believe that this tool might give you the answer bcoz I can’t, you provided too few information.

Good luck!

Dude, I’m all alone in this. No matter how many checks I make before the update is pushed, some of the errors get thru. It happens to Elementor with 50 developers.
I can’t express how sorry I am, it just happened, I’m a human only and I do make mistakes, shoot me but it won’t help! There’s no undo button in life.

Dude, I’ve made the simplest possible example that works just fine. You can try to download it and see what it looks like at your end:
https://drive.google.com/file/d/1vH7wqvT7XnT02Yzs2VoSkpvMwS-USe_U/view?usp=sharing

…unzip and simply import as any other Elementor template

From this plugin’s point of view, it’s time for you to decide whether you go for the Flexbox or still keep the Sections/Columns for a while. It can’t be both any longer! If you want to continue using the Sections/Columns then disable Flexbox Containers under the Elementor experiments. Otherwise, convert all the Sections/Columns to Flexbox Container.
The Breaking Bad extension has nothing to do with the Flexbox Container. That feature is both technically and code-wise completely different.
There’s no way to “convert” any Breaking Bad extension made layout to the Flexbox automatically. It would have if the default Elementor’s converter took the Breaking Bad into consideration which — unfortunately, is not the case.

Sorry mate, my bad!

https://www.ads-software.com/support/topic/1-9-5-critical-error-fix/

Sorry!
https://www.ads-software.com/support/topic/1-9-5-critical-error-fix/

Thanks!
Yes, sure, why not ?? Noted!

OMG! That was a real nightmare buddy, I thought I was losing my mind…

YES, I can confirm that the patch works now! Please push it with the next update.

Thank you very much for understanding!!!

But the problem IS that neither of these two work Jory!!!

“the_archive_description()” doesn’t get replaced at all with my auto template.

As a side note, I have some WP experience (8 years), I’ve made some plugins and themes so I’m not a total noob.

Could you post the simplest possible “archive.php” code here?
Maybe I’m missing something obvious with regards to the Pod settings but I’m trying to figure out the logic behind it for over a week.

Thanks!!!