Both versions can work side by side. You can continue to use Foundry 2 alongside Foundry 3. Foundry 3 was built from scratch and does not share any code with Foundry 2. You can still edit web pages that were built with F2 and build new sites with Foundry 3.
Thanks, but my question is if there is a limitation if I upgrade and use the same registered purchase under the same email, or the correct way is to purchase version 3 as a new software, not an upgrade?
Other software vendors don’t admit to being upgraded if you want to use both versions, the last and the new one.
I guess that Foundry doesn’t have a registration code for a license, so both versions act as different apps inside Rapidweaver.
You can use both versions for as long as you like @musulungo, there is no limitation on that. As @Steve_J pointed out, they exist and work side-by-side in RW and Stacks. I’ve been using then side-by-side for 1.5+ years now.
Okay good! One of the problems I had when starting Foundry is that I mixed all the Foundry tools with the built-in RW tools and wasn’t sure if I had a way to filter them. This was probably around 2020 or 2021. I can’t remember if smart folders was a feature in Stacks 4 but I have the latest Stacks 5.1 so that is an important feature.
In the past you could search for Foundry in the library and find all of the v2 tools. Now with two separate versions we needed an easy way to sort them. Using F2 and F3 as the simple search terms was the idea of the brilliant beta testers!
Oh yeah, it would be very difficult to tell the two Foundries apart! What was confusing before was that the built in RW tool would often have nearly the same name but after using it for a long enough time I just learned what stack to not use.
I have a question concerning the upgrade too. I have bought the two last versions of Foundry and all of my Elixir software with my old email address. Now I have a new one. Is there a way to upgrade under my new email address or can it be changed in the payment system?
Alloy can certainly be used with Foundry 3. I’ve talked about that here in this blog post:
No, Thunder and Potion are not going to work in Foundry 3. Thunder and Potion are add-ons that were based on Foundry 2’s code base. Instead of making more add-on packs for Foundry 3 I simply started rolling a bunch of those features from the add-on packs into the Foundry 3 tools during development. This means some of that functionality from Thunder and Potion are found in Foundry 3 already. I talked about this in this blog post from last week a little bit:
Essentially Foundry 3 is a completely new product from the ground up.