Splider 2 - Shaking The Habitual

Just a hobbyist here who keeps checking how Stacks 6 is going. Just updated to Beta 77 and Splider 2 still doesn’t seem to work for me. My sites are Source but I didn’t think that Splider was Source framework dependent. Splider is integral to a large Poster 2 blog that I would need to port into Stacks 6. Any feedback would be welcome.

I’m in the exact same boat, and I honestly share your fear about the future.

I have a massive number of websites—pretty much all of them built with Source—and this uncertainty is really tough to deal with. By the end of the year, I’ll have to make a hard decision: either keep waiting for something with no clear timeline (not knowing if or when everything will actually be ready and compatible), or bite the bullet and rebuild everything from scratch on a different platform.

Neither option is a great prospect right now.

1 Like

Can you share a link to an exported website?

I guess it’s a JavaScript issue which can be fixed.

Source does have a beta for Stacks 6.0. Not sure how it works, as I am moving rather slowly with my testing. That is beta for the Source framework, not Splider.

I was able to get it running with a just a couple of code line changes regarding the loaded JavaScript files. This change would have to be done inside Splider 2 itself.

@habitualshaker might still be willing to release a fix, if it is not much of a work

If a stack works in Stacks 5 but not in Stacks 6 then it is a Stacks 6 issue. The way S6 resolves file paths has changed and so unless full backward compatibility is added then there will be a good number of stacks that will fail in S6. I am sure this was added to the Stacks Issue tracker at some point a while back.

1 Like

I may be entirely wrong here, but my understanding is that Rapidweaver Classic has had, or is about to get an update. Stacks 5 is also being updated. So it appears both are firmly back on the table.

Rapidweaver Classic can be purchased from the Realmac site. Which would indicate it’s back in, if not active development at least active support.

Frameworks from devs who have left the community are not hard to maintain yourself with the aid of AI. I still have a number of F3 sites and they are still ticking over nicely.

I’d suggest anyone panicking about not being able to run F3, Source, and any other unsupported frameworks/stacks on the fabled Stacks 6 is worrying about a problem that doesn’t yet exist. First and foremost, in a commercial form, Stacks 6 doesn’t even exist! Furthermore, if my understanding above is correct, RWC and Stacks 5 still has legs.

1 Like

I’ve started re-building my main business site in Blocs. Currently it’s F3 and was going to be Source but both of those are now off the table. My main concern was that stacks 5 and RW would stop working or either framework would ‘break’.

Yes - the latest RW version and S5 should work for a long time to come. I believe all is still well even with RW8.

1 Like

Thanks for confirming.

I’ve just added a issue for your case:

2 Likes

I haven’t exported anything from Stacks 6. At the moment I’ve copied the home page stacks from a RW built site into a test project in Stacks 6. Besides the Splider problem it’s interesting to note the difference in performance between RW and the current Stacks 6 Beta 77. My home page is a Poster 2 blog that has over 400 posts, nearly all with images and video links. Page opening in Edit mode in Stacks 6 is painfully slow, making RW look like a greyhound. Preview mode works but is also much slower than RW. All Splider content in the posts doesn’t show as a carousel, just displaying the images in a vertical stack. I’m on an M4 iMac with 24GB and RW 9.2.0. The site I’ve ported into Stacks 6 is https://www.bobgoesfishing.uk

That’s the issue mentioned above.

Hi Stuart, happy to see you.

Splider2 isn’t working on iPhone (I have iOS27.2.1) or iPad (17.7.11) anymore. Slides need to be moved manually. RW8 with Stacks5.

Hello!

It looks ok to me. Maybe you have reduced motion enabled on your phone? Splider respects that choice and so doesn’t automatically animate anything when it is enabled.

Yes, that was it. Thank you, and kind regards!

If you ever start doing stacks work again, you should use the library API, not assets, for things like that.