@dan have you received my mail with the project file and were you able to identify the issue? I now had the third support mail with exactly this behaviour.
I thought we fixed most of these issues in the latest build(s) of Elements 3.
What issues are you still seeing?
This bug is still sneaking around ![]()
The images looks like below screenshot in Elements 2.4.4
And like this in Elements 3.0.3
Simple solution: click on the images, width is set to “auto”, then re-click “auto” and the size is correct.
That’s exactly the behaviour the file I sent you has. I got some support questions exactly on this matter for some of my templates.
We’ve fixed a lot of these conversion issues from Tailwind 3 to Tailwind 4, but for this one, you’ll need to re-select the “auto” setting.
Ok, understand. I will update my templates to Elements 3 and go through this process. The good thing is, it hurts only once ![]()
Exactly ![]()
I’m just curious to hear from the beta testers: How stable is the current beta in your experience, and are there any more beta updates planned before the final release?
I’m still on version 2.4.4 and I’m considering switching to the beta.
The Beta is stable for a Beta. But due to the Transition to Tailwind 4 you still find some unexpected things. For an important live Website I would stay at 2.4.x. I have installed both on my Computer to play around with version 3 and have still my produktive System available. Works Fine ![]()
We believe the beta is very stable, and Tailwind 4 is working as expected. We don’t anticipate any further fundamental changes.
At this point we’d recommend ALL users upgrade to Elements 3.0
@dan Custom Text Shadow is not working. It’s gone when upgrading from 2.4.4 to 3.0.3.
I prefer to use my own in the Solar Theme Shadows. Custom Shadows are not working on Buttons, Photos and Containers either.
I’ve tested it here and it seems to be working just fine, can you provide a test project via Elements Cloud that shows the issue so we can take a look?
@dan In the mail. I have tried all my 5 Custom Shadows, none is giving a shadow in 3.0.3
Can you try removing the . and slashes from the class names. Ideally you should stick to using web safe naming. Give that a go and let me know how you get on.
Edit: you will probably need to choose a different shadow, then re-select it.
That seems to be the trick: shadow-00-10-a is now working instead of “Shadow 0.0 / 1.0 a”. I will have safe names in the future. All 5 are working now.
@dan You can remove my posts if they take up too much space in this topic.
Sa’ll good, glad it’s now working for you!
Edit: This is now fixed in Elements 3.0.4 ![]()
@dan
Unfortunately, an old bug has returned in the beta.
The child categories in the Tab Component disappear again. The only way to restore them is to close Elements completely and reopen it.
Please see the attached screenshots. I’m currently running Beta 3.04.
Thank you for the the new options for the Table Component. I really like them.
I have a question about the new sort option. Suppose the table has 20 pages and I’ve clicked to page 5. If I then click on another column header to sort by that column, it stays on page 5 (of the new sort order). Is this how it should work? I would expect it to go to page 1 since it’s applying a new sort order.
Ideas for future improvements:
It would be nice to have an option to go to page 1 or the last page. If the user is on page 15, it takes quite a few clicks to get back to page 1 ;-). Perhaps don’t display these (“Start” and “End”) by default, but offer them as an option to enable in the settings, because this is only relevant if the table has more than a few pages.
All the text is in English. It would be nice if the settings allowed you to enter different text for “Search,” “Previous,” and “Next” so that these terms can be displayed in the website’s language. My website is in Dutch.
Hi @Lalla
Glad you’re enjoying the Table component updates ![]()
These are all great suggestions, I’ve actually already gone ahead and added these features to the Table component, they’ll all be included in the next release of Elements ![]()
Wow, that is great and fast! Thanks a lot ![]()





