UPDATE #1: Info on the weird “start-Container-” debug message in Preview in this build.
After publishing this beta we had reports of the debug scroller guides being visible in preview. We’ve looked into this, and it’s an issue with this beta. It will be fixed in the next beta. Those “guides” should only be shown when the Debug markers for Scroll effects is switched on. Sorry for the inconvenience!
UPDATE #2: Scroll Effects Missing
Okay, so it turns out the latest Components didn’t get converted and included in the build. This means there’s no scroll effects in this build. They will be included in next weeks beta build. Sorry for the delay!!!
Hello again,
Today’s beta fixes a bunch of issues as well as adding an “experimental” scroll effects feature to the grid item and container (Flex support will be added in the next beta). It’s worth mentioning that the scroll effects are still in-development and unfinished, however, we wanted to get feedback as early as possible from everyone to ensure it does what you need.
Important Information about Hover Effects
If you are using any Hover Effects you will need to switch them on using the new on/off toggle.
What’s New in Beta 11?
Added an On/Off toggle for Effects
Add page button now always visible
Foreign characters now render correctly on export
Restore value shown in Inspector when removing a global override
Globals are now renamed correctly when clicking out of the text field
Ensure all custom class names in Theme Studio are now web safe
Added Scroll Effects to Grid Item and Container Components (more support coming in next beta)
Added support for globals to text fields, numbers fields, and text areas
Added support for responsive break points to text fields, numbers fields, and text areas
Update to the latest Beta
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. You can also download the latest build of Elements from the confirmation email you received as that link will ALWAYS give you the latest version
Give Feedback on the Beta
If you are using the beta, please post all feedback in the Elements Beta Feedback Forum. You can use the Elements > Send Feedback… menu item to automatically pre-fill the build number into a new topic.
Get the Beta
If you’ve already signed-up for the beta, it might be a while before you get an email as we’re working our way through all the feedback. Hang tight for a little longer, you will get access in the coming weeks and months. If you’re not on the list, you should sign-up up here to be notified when the beta is publicly available.
I was a little confused by this latest beta as it is listed here as BETA 11 but in the About Box it is still shown as BETA 10. Fortunately, the build number told me this was the correct build - 22896.
BTW, the copyright dates in the About Dialog show the current year as 2022, shouldn’t that be 2024?
There’s a whole bunch of little house keeping things left that I imagine will get tackled in the final polishing phases (ie. references to rapidweaver, app id, about, etc)
Dan stated earlier this week that he currently has as many beta testers as they can properly handle. The people who are testing are providing good feedback, and the bug list is being prioritized and completed bit by bit. He said it is important to maintain control over the process to deliver a great product.
I would also like to remind everyone that this is not a general release, and currently, it is very difficult to build a complete website. Additionally, the work completed is often broken with new beta releases that fix issues. This is a full-on beta program where we are looking for ways to break the system and make suggestions on how to fix it when such feedback is appropriate.
Got it. I jumped ahead and bought the professional option. However, I was asked to promise to not publish websites using RapidWeaver. Will we be able to publish websites soon? I ask because I just paid for the pro option.
I think the reason was because too many features are in limbo. Things can get broken. If you sell a feature to a client and then it gets broke, it puts both you and RM at risk.
Unfortunately, I’m thinking @dan is going to say when the app ships version 1.0 or at least is feature locked just before version 1.
I think Flash summed it up pretty well, but let me just add a few more details.
This semi-private (and early) beta is a chance for us to make big changes based on user feedback, and as such project files may break (we’ve avoided it so far, and hope it stays that way), but it was important to us to warn users that are jumping onboard early.
We hope to have a stable version of Elements in the next few months that you can start to confidently publish websites with. Once we hit an open beta, we’ll ensure project files never break.
