Is there a limitation on saving projects in the Elements Trial?
I’ve been playing around without saving anything but thought it time to save my work and pick up later. I’ve saved a very basic project with a couple of pages, a few elements and half a dozen Resources as linked images.
To my horror trying to open the file later in the day leads to a ‘Something went wrong…’ pop up.
Likely created some, misspelt, saw it was incorrect then retyped link correctly.
Yes. Created folders.
Please note that at this early stage I hadn’t added a lot of image links as resources, maybe only half a dozen. Once I’m up and running there will be thousands. If a tiny Elements project falls over with half a dozen links the crashes once I get going on this will make RW/Stacks look like a stable partnership!
To be able to deal with large sites with a lot of image links creating resources will be almost prohibitive. The idea of linking to images (in my case anyway) is to reduce project size and making a linked image a resource sort of defeats this.
Having 10000+ image links as a list of resources is in no way manageable. They are not resources anyway they are exactly as they are titled ‘image links’. If resources were page dependant it might be more manageable but as it stands it will quickly become a bloated mess.
For me I’d like to see the stacks way of handling a linked image, i.e. completely separate to the project. Drag in an image element then reference an image by link, not having to make them a project resource.
I will also need to be linking to a large number of pdf’s.
To be able to get even close to reproducing our RW based business site in Elements we need to be linking to external resources not referring to them within a project.
Thanks so much for all the detailed info, it’s incredibly helpful and will definitely make it easier to track down the source of the issue.
We’re planning to add a text field to the Image component so you can paste in an image link directly, which should make things easier for you. We’re also going to improve the remote resource dialog, allowing you to add multiple remote resources at a time.
Elements is generally very stable now and we’re only seeing around 3 to 4 crashes per day. This is a stark contrast to the 40 to 50 daily crashes we currently see from the old stacks plugin, and one of the reasons we developed Elements. There’s more work to be done but we’re definitely heading in the right direction!
You might also want to check out the recently released CMS which is currently in beta. It could be a much better fit for a project of this size. It has the potential to streamline your workflow quite a bit and speed up your transition to Elements.
Update: I’d like to add that Elements is already very capable when handling a large number of resources. I was able to add over 7,000 images to a project without an issue. The initial save was a little slow for my liking, maybe 30 seconds and that’s something we can improve on. But Elements can handle an impressive number of resources already so this may be something you’d like to consider.
I’ve had a play around with this and vastly improved it. It’s now super quick to add so many resources, 0.06 seconds! We need to do some more testing but if all is well it’ll be in the next release.
This should help me as well. I have ~2600 images in resources, and I usually get the pinwheel for about 6-7 seconds on each save. Used to be around 30 seconds prior to the last work you did with saving.