Astroid Framework Version 3.1.10

[sonvnn]

Hi Astroiders

We are excited to announce the release of Astroid 3.1.10. In this version, we improved the Sidebar interface and added a new Sidebar type. Along with that, we fixed some bugs found in previous versions. I would like to thank my friends @Dnsftl, @WM-Loose, @Joomlaplates, @deltapapa01, @felixkat @salahjaafar and others who helped me complete this version.

• For more information please visit Astroid Official Site.
• To view the preview page please visit Demo Site
• To view the Widget demo please visit Astroid Widgets
• To donate to the project please visit Donate Page
• To rate/review for Astroid please visit JED
• Unlock the Full Range of Pro Features Go Pro

Added

• Add countdown script
• Add Sidebar Topbar Layout
• Add Blog Overlay Layout

Improved

• Remove FontAwesome Vue Lib
• Call non minified path when Joomla Debug is enabled
• Save sublayout content to Params folder
• Improve style of Typography
• Option display thumbnail only on Articles Widget
• Refresh Astroid Cache after update
• Update border style for Element
• Update Back to top icon Style
• Add Responsive option to Range field
• Add border style for Element settings
• Improve ResponsiveToggle style
• Add new responsive system (xs, sm, md, lg, xl, xxl) to all functions. Need help test this carefully on (Typography, Margin, Padding...)
• Re-order menu of template options

Fixed Bugs

• Fix issue $(...).rating is not a function
• Fix issue conflict with Advanced Module Manager
• Fixed issue Warning: Undefined variable $block_3_type
• Fix issue Open Graph title does not parse double quotes Open Graph title does not parse double quotes #945
• Fix issue Form Builder - Redirect option not working Astroid
• Fix issue on rtl mode.
• Fix issue Offline Image is not shown
• Fix issue New layout not visible in category
• Fix issue can't save HTML on Module Astroid Layout

---

This discussion was created from the release Astroid Framework Version 3.1.10.

[Terresco]

Update done without any probleme. Thanks for the new version

[Joomlaplates]

Please check the mobile view > Blog.
They are all in a row and not below each other.

[Terresco]

Hi, I don't use the view blog, if you have an URL you want me to test, send me, I will check
Edith: Yes I saw the issue, I don't know very well the blog view but I saw an issue

[sonvnn]

I fixed it. Please help me re-download 3.1.10 and retest it.

[patrickus33]

@sonvnn
Hi Sonny,
Here the update of the french language file. (3.1.10)
fr-FR.astroid.ini.zip

[Joomlaplates]

Thanks, just updated.
Greating Peter

[sonvnn]

@patrickus33 Please cooperate with @YGomiero in translating Astroid into French. We can discuss about it at #967

[WM-Loose]

Hello Sonny,

the switch from Astroid 3.1.9 to Astroid 3.1.10 has created a lot of work that we as an agency hadn't actually planned for and now we have to see how we can manage it all. Because you have integrated additional display sizes, all sections and module positions have to be checked and usually adjusted.

Previously there were 2 display sizes: small tablet and desktop. If you have configured different values ​​for padding and margin here, the new display sizes will use the standard setting wherever no number 0 was entered. So if I have only set 10% padding all around in a section for desktop and didn't want that for smaller displays, I now have to enter the values ​​everywhere in this display size. I have customers who use 15 template styles in a Joomla installation and yesterday I spent 6 hours adjusting all of this for one customer.

I think it's great that you're integrating new functions, but if existing configurations are changed that way, it's simply unmanageable.

All the sizes of the typography settings also have to be revised. Then there's the Pro version, where I now have to specify the rows for each menu item in the Joomla standard category blog so that it fits on tablets and mobile phones. If you at least had a standard that didn't cause this kind of thing during updates and all these new features only had to be changed when the pro version was activated, that would be a great help to all of us.

Perhaps a solution in the future.

Regards Dirk

[sonvnn]

I understand your feelings. I really thought a lot when I made this reform. As you know, technology is evolving so fast. Screen sizes are getting bigger and bigger. Since we had Mobile, Tablet, Desktop. Now it has become X-Small Devide, Small Device, Large, X-Large, XX-Large.

And I see that the resolution in the future will be bigger and bigger. And Bootstrap is also evolving like that. So redefining responsive by min-width instead of max-width is necessary because the screen resolution will be bigger and bigger. So if in the future we have another device with a larger resolution, for example XXX-Large, it will not affect the current configurations. Because it simply adds another size.

Bootstrap also explained this in their notes below, you can read and refer to it here

Since Bootstrap is developed to be mobile first, we use a handful of media queries to create sensible breakpoints for our layouts and interfaces. These breakpoints are mostly based on minimum viewport widths and allow us to scale up elements as the viewport changes.

I also guarantee that this is only done once and you only have to configure responsive this time and it will be stable forever. No matter how many screen resolutions you add, it will not be affected.

Best Regards,
Sonny

[sonvnn]

@WM-Loose Please discuss about this issue here #984

[srcarney]

This update also made some extra work for me because some of the padding changed, etc... but I actually think it is an improvement so I am going to be happy to make changes to my site accordingly. That said, I only have one site using Astroid now. Soon I will start converting older site on other frameworks to Astroid.