Hi - I’m running Classic and suddenly can’t use Stacks 3. I know it’s old but I’m reluctant to upgrade to Stacks 5 as I hope eventually to go with Elements
Your dilemma, do you go to Stacks APP (6) Standalone - new beta or go to ELEMENTS as you have to upgrade? There’s a very interesting thread on Weaverspace forum perhaps you should read before making your decision. (Stacks6 or Elements - Mature debate required CONVINCE ME! (long post)). Good luck in your decision - I would be cheeky and ask Issaiah for a free upgrade to 5 as you might be changing to ELEMENTS and see what he says! I know which way I am going but that does not help you - get the free trail of Elements to try.
Hi Paul - that’s exactly where I am. (Thanks for the thread recommendation - very interesting).
But I still dont understand why my Stacks 3 suddenly stopped working with Classic - It worked fine 2 months ago.
However - of my options going forward … Classic, Elements, Stacks 6 (or really WordPress): I do want to believe but Elements is the new kid on the block with the most to prove and also has it’s pricing quite wrong for people like me.
If you updated your Mac recently then Stacks 3 would stop working regardless of what version of RapidWeaver you were using. Stacks 3 doesn’t work on Apple Silicon Macs or the new macOS versions.
I haven’t seen Stacks 3 working on any RapidWeaver Classic install though, only Stacks 4 or 5 has worked.
We’re currently running a discount until the end of August. 
Use the coupon code CLASSICUPGRADE at checkout to receive 30% off the purchase price.
You will receive 1 year of app updates which will auto-renew, however you can cancel the auto-renewal so you can manage it manually (i.e. renew it whenever you need another 1 year of app updates, don’t have to pay anything else until then).
Interesting - I’ve been on Apple Silicon for 3 years with an M1 mini and Stacks 3 has worked just fine with Classic. I updated to Tahoe - so I’m guessing that’s done it. I think it’s knocked Rosetta 2 out - unclear how to get it working again.
Get info on RapidWeaver Classic in the Finder and check the “Open using Rosetta” option. This should allow you to then run legacy plugins.
It’s worth noting that Apple have stated that they are phasing out Rosetta.
No that did’t work Dan - but thank you for your suggestion.
Stacks 3 still loads, but with an upgrade notice … seems it’s deemed my time is up.
I will contact them directly
Thanks again for your input Dan - it’s always appreciated
@jbob save the money and go with Elements … 
2 Likes
I have 2 sites of my own - for one I need a blog, for the other a shop.
Then I have a very old, very huge but well maintained website belonging to a yacht friend that I fear would take me a year to port. It also needs a blog.
Mmm
Did you try emailing support@yourhead.com for help on this one?
Anyway… It looks like you are running Stacks 4, that’s why it’s asking for the Stacks 4 license number. You’ll need to download and install Stacks 3.
Here’s a link to the Stacks Archive, and here’s a direct download Link for the last version of Stacks 3 — Download Stacks 3.6.9
Remove the Stacks 4 plugin, and Install the Stacks 3 plugin. Your stacks license should then work.
Let me know how you get on.
Quite a read that was.
This comment was especially interesting.
what happens when Tailwind falls out of graces with the web dev community.
Since outside of Joe would Foundation have continued or just been archived ?https://github.com/foundation/foundation-sites/graphs/contributors
2021 “I definitely plan on making headway on Foundation 7 this year.”
2025 “I do not have an ETA at this time.”
Tailwind development seems very active by contrast.
https://github.com/tailwindlabs/tailwindcss/releases
If Foundation 7 is ever released will it surpass Bootstrap or Tailwind — No.
Tailwind has a bright future so no need for the fear mongering about Tailwind falling out of graces with the web dev community. Plus its just a CSS Framework, “to-MAY-to” vs "to-MAH-to”, replace within Elements and move on if that day ever comes. Flexbox and CSS Grid are super mature so using vanilla CSS is just fine if an abstraction of using a framework is eventually not desired.
2 Likes
We demoed a few weeks ago that Elements is not tied to a particular framework, if something new and better comes along we can add support for it inside of Elements.
@ben went so far as to show how easy it was to get Foundation up and running in Elements! Not that we’d want to do that, but it shows how we’re not tied to any Framework…
Exactly this! We chose Tailwind CSS now as it’s hands-down the best (and fastest growing) CSS framework out there and it shows no signs of slowing down any time soon.
Elements is a flexible platform, built for the future… whatever that may look like 
1 Like
Missed this questions, but I’m pretty sure Foundation would/should have been archived.
I use Cartloom for my shop and it’s written in Tailwind too! It just a case of copying snippets into custom HTML components in ELEMENTS and it just works.
It’s interesting that Joe said this, considering he also uses Cartloom which uses Tailwind.
The commit history on Foundation looks really bleak, not much happening over there 
Maybe I am old fashioned, but it seems to me many on here keep pushing Elements, including those doing the building. When I constantly get pushed on going in a certain direction, for whatever reason, my radar goes up and I tend to go in a different direction. I don’t feel there is a need to constantly push Elements for almost every post that has to do with RW Classic, as I already know about Elements and it seems the push means that RW Classic is in deep trouble and will be left behind. Sorry, but I like what I have and I don’t need the constant reminder there is something better. Just my two cents, perhaps a bit harsh, but I think I can decide for myself which is the best software for me.
Hi @Pete,
Thanks for being so candid. I completely understand where you’re coming from. If RapidWeaver Classic is working great for you, there’s absolutely no obligation to move away from it. You know what’s best for your workflow.
That said, we’ve found that many existing users simply aren’t aware of what Elements offers and how it differs from RapidWeaver Classic. It’s a completely new approach to building sites using a modern framework called Tailwind, an effortless WYSIWYG editor and a far more flexible and future-proof architecture.
We feel it’s important to make sure our current users are aware of these changes and opportunities. It wouldn’t feel right not to share information that could potentially impact long-term workflows and project planning.
I hope you understand where we’re coming from and happy weaving.
Cheers
Tom:
I am not knocking Elements, as I am certain that the Realmac team is doing a wonderful job creating their own unique product. As I stated, overkill may do more harm than good, as there is plenty of information on Elements and what it does. I will keep it at that. I have been a supporter of RW since version 6 and am down to only having one personal site that keeps my mind active. RW Stacks has been fun and the support from your group and independent stack builders has been super until the last fall out when some stack builders left the ranch for their own new pastures. When I am being told that there is a better meadow down the road, I am wondering if my old arena is going to be sold for condos sooner than later…..ha, ha.
Thanks, really appreciate it!
Haha, you’re safe with RapidWeaver Classic, there are no condos in sight! 
RW Classic is still fully supported and will continue to be for the foreseeable future. That said, I can’t speak for third-party plugins directly, but I do hope developers continue actively supporting their stacks and addons as much as we’re supporting RW Classic.
Not all of the work happens on the framework side. The Foundation 6 stacks got its 153rd update last week. I am pretty sure that is more updates than RapidWeaver has ever had, ever. The Foundation stacks are ahead of the framework by quite a lot. For example, Custom CSS Properties for theming have not made their way into the framework, even though the stacks have supported them for years now. The work that I am doing there is private on GitHub. It will eventually make its way into the open-source project. I have that slated for Foundation 7 in 2026.
I am not allowed to post images (on my supposedly non-moderated account) so here is a link to an image of my GitHub contributions.
How many open-source contributions has anyone at Realmac made to the web community? From looking at your GitHub profiles, I see zero. I am sure that I am wrong, though… I have to be, right?
Cartloom is an amazing service. Yes, it uses Tailwind but who cares? All I need to do is throw a script tag on my page, and I am good to go. I never have to deal with any of that TW B.S. Tailwind has it’s place. I can see it being useful for large web application code bases. Especially for large teams of developers. That is not the target market for us. For small to medium websites, I think TW is a bad choice.
But all of this is developer talk. No one here using your new app will actually be using Tailwind. They will be using settings in the sidebar. Everything that I have said about Tailwind was about Tailwind. It had nothing to do with your app. I am on record for hating TW before you destroyed the community 3 years ago. So please stop slinging 
…
1 Like