Elements 1.0.7 (23730)

Hello again,

You guessed it… another build! We’re getting it out today because, well, no one wants a Friday release. Have fun!

What’s New in Elements 1.0.7?

  • Add a page changed status indicator
  • Removed Google fonts from published content if they’re unused
  • Fixes another problem where images had a filename prefix of “1__#$!@%!#__

Try the Demo

The new trial mode in Elements lets you explore the full app and build up to three pages, giving you a feel for the design workflow and features. While export and publishing are disabled in the trial, everything else is fully functional, so you can see exactly how Elements works before committing.

It’s the best way to experience the speed and simplicity of modern website building with Elements. You can now Download Elements with the new trial mode.

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.

2 Likes

You guys are on a roll - rapidly accelerating towards version 1.1! :grinning_face:

@logrunner i don’t believe it yet … maybe the next version will be 1.0.7.1 ^^ :smiling_face_with_horns:

@pegasus I guess, still 1.0.8 and 1.09 to go before we get to 1.1 with the CMS? :wink:

i hope so … Ben is probably spending a couple of days at the beach to recharge his batteries and find the final inspiration for the CMS release :wink:

1 Like

Hi @tpbradley,

thank you for fixing the “1__#$!@%!#__” image files, but one question remains: Why does the /files directory even exist? When I run grep -r "image-square" *, nothing is found.

Hmmm, the files folder contains resources for the Components, like this:

Does that help?

The files directory contains files required for the components in use on the page, in this case it’s publishing the placeholder images, even if you’ve set an image. This isn’t ideal and I’ve added a ticket to see if we can tidy this up.

Sorry, but nothing on my website uses these images. So why are they exported?

I’ve searched everywhere: grep -r "image-square" * didn’t yield any results.

What component does this need? Wouldn’t it be better to keep it in the /rw/ directory?

Yes, we should be able to do this!

Please excuse me for being such a pedant. I’m a software developer myself, and whenever I’m not 100%, it catches up with me.

All good, you’re absolutely right to question these things. The consistent feedback is exactly what’s making Elements such a great platform!