Elements 0.9.6 (23600)

Hello again,

As you know we’re still hard at work on three major new features: the CMS, the Store, and Templates! But they’re not quite ready to ship… In the meantime, we have a fresh new build packed full of bug fixes and improvements based on your feedback!

What’s New in Elements 0.9.6?

  • Added lazy loading support to the Image Component
  • Always show the Project Chooser window when creating new documents
  • Fixed aspect rations on thumbnails in Project Chooser
  • Fixed the YouTube/Vimeo thumbnail aspect ratio in the Gallery Component
  • Added Accordion Summary background colour controls
  • The Modal now closes when links are clicked
  • The Menu now closes when links are clicked
  • Fixed a syntax issue in deployed packs
  • Fixed the page load flashing issue
  • Fixed an issue when generating backend folders

Purchase a License

You can visit the elementsapp.io website to purchase a license.

Get the Update

Elements should prompt you while it’s running to let you know there’s an update. If it doesn’t, you can select the “Check for Updates…” menu option from the “Elements” app menu.

Alternatively, you can always download the latest build of Elements here.

Give Feedback

If you are running a licensed copy of Elements, please post all feedback in the Feedback Forum. You can use the Elements > Send Feedback… menu item to automatically pre-fill the build number into a new topic.

1 Like

Reveal still operates in reverse when no component/height is added to page

is this still planned to be fixed?

Thanks for all the fixes.

Happy to see the background color for the accordion, but could we also add the option to have a hover color so we can easily provide the user with feedback that they are over an actionable section of the accordion?

it does change color on hover. Play with it and see. The open color will appear when the accordion is closed and you hover over the Summary section

I’ll try again it didn’t work for me when i tried it.

OK, I now see that it works using the open and close, which is fine when it is collapsed, but you get no feedback when it is open. So it partially works but not how I would expect. I’ll stick with my hack using a Flex inside the summary.

@dan Another problem I just discovered with the Accordion, if you apply a SUMMARY color it does not respect the corner radiussettings. In my testing the corners are never rounded on the summary but they are on the content when expanded.

I remove the summary color and set a background color for the accordion then the corners are rendered correctly.

Hi @dan: Not a functional issue, but I guess you might want to adjust the copyright date in the about dialog from ‘Copyright © 2002-2024 Realmac’ to ‘Copyright © 2002-2025 Realmac’?

1 Like

Hey

Its nice to added llazy loading page and Accordion Summary background.

I hope fixed:

  • Background: issue :warning: while change themes
  • Accordion; issue :warning: while add new icon svg than change icon color, but color not change it.

Thank you to the entire team for your hard work and dedication in improving our elements.

I’m not familiar with this issue, can you explain a little more or demo the bug in a video?
btw. Make sure you have the correct tags in the Template.

You need to ensure the SVG has “currentColor” set as the fill colour.
Take a look at the docs here: SVG | RapidWeaver Elements Docs

Hope that helps!

Since I updated to 0.9.6, the publishing dialog mentions over 3000 Files to be uploaded for my site. That’s much more than with the last version. And - the upload fails, after about 900 files.

Could you try reducing the number of connections and then publish again?

Hey ben, thanks for the reply. But unfortunately that doesn’t help. More files (about 1500) are uploaded, but then the upload also aborts. I also wonder why thousands of files should be transferred every time, and why there are more and more after each update of elements.

1 Like

Who are you hosting your site with? It might be worth reaching out to their support team to see if they can provide logs or any insight into why the upload is failing or being interrupted. Sometimes hosts have restrictions on file upload limits, connection durations, or timeouts that could cause this kind of issue.

This is something we’re aware of, and we agree — publishing should be more efficient.

Currently, Elements might miss some files that have already been uploaded, so it might re-upload those. We’ll be ensuring Elements only transfers new or changed files in a future update.

Great question. As we introduce new features — especially complex components like Forms and the CMS — we need to include more supporting backend files to handle things like submission processing, content loading, validation, and more.

While many components add little to no extra files, components like Forms and the upcoming CMS are more sophisticated and require server-side logic. That’s why you’re seeing an increase in the number of files during updates.

That said, this will level out over time. Once the foundational work for these advanced components is in place, future updates will typically involve fewer new files being added.

Hope that helps explain what’s going on :slightly_smiling_face:

mine went from 1800 files to 3400 without altering anything on my site?

1 Like

that’ll be due to the work I’ve been doing for the Forms and CMS — there’s a lot of code that goes in to ensuring those types of components will “just work” :slight_smile:

1 Like

There could still be an issue with publishing Forms.

Original (simple) site published around 450 files.

Added contact page using a Form and the number of files did not change dramatically – I wasn’t taking too much notice at the time but think still <500.

Altered page suffix to .php to see if that got it to work and it published 1,400 files.

Upgraded version of Elements to 0.9.6 and pretty certain the first full publish did over 4,000 files of the same site.

Made some changes to credentials to try and get the Form to work. Next full republish was 3,203 files.

Had about 20 attempts at different credentials to get the Form to work. Marked all pages and all resources as changed each time and did full republish. Every time it was 3,203 files.

Deleted contact page from site, deleted all files on host server, republished and it was 3,203 files again making me suspect it had not previously been uploading the changes to the Form and thus why my 20 odd tests all gave the same result.

To try and replicate it I deleted all files from the host server again and did another full republish with the contact page version of my site and there were 2,464 files. It just gets weirder. I again deleted all files from the host server and all files from my export directory, republished the file with no contact page and there were 2,458 files.

The variance in the number of files published makes me wonder whether it is working correctly, I suspect it has something to do with the Forms.

1 Like

Hello @ben , Thank you very much for taking the time to address my problem. Yes, it may of course be that these aborts occur due to a restriction at the hosting company. I tried it several times today in different ways and it always broke off. This is quite disappointing. I don’t know if and when I will find time to continue looking for a solution. My little project of a simple website gets much more complex than I thought it would be. To me, it seems that setting up a simple website was much easier a few years ago.

As an interim solutions. You can try exporting it locally and using a third-party ftp client (like CyberDuck or Transmit) and upload it manually!

We have some more work scheduled for the FTP engine in Elements, so we’ll be sure to get everything resolved and working all in good time.

Thanks for hanging in there!

This workaround works fine. The problem thus does not seem to lie with the hoster.

1 Like

@dan : The problem with the cancellation of the upload also exists for me in v 0.9.7. but now I get at least an error message:

The message “access denied” occurs randomly with any file. If you try it several times, it is a different file each time. I continue to work with the workaround via local export and upload via FTP program.