Helix Ultimate 2.0 started strong and paved the way for developing effective and modern Joomla websites. What a long way we have come! Today, we're thrilled to announce the Helix Ultimate 2.0 Beta 3 is now available to test with new additional features and shiny new improvements.
Today’s (May 10th) Beta version is an experimental release and not ready for production sites. We wholeheartedly appreciate your interest in Helix Ultimate 2.0. You are invited to try this Beta version, but DO Not use it on a production site.
Please note the template framework is still under development and is not ready for use on any production site. However, feel free to experiment with the release on a staging site and let us know your thoughts.
Can Helix Ultimate 2.0 Beta 3 live up to the hype? Let’s see what it has in store for you.
Helix Ultimate 2.0 Beta 3 changelog:
Update: Bootstrap 5 stable version
New: New field for injecting custom code after opening the body tag
Fix: Breadcrumb issue fixed
Fix: Pagination issue solved
Fix: Custom CSS issue solved
Fix: Frontend article editing issues Joomla 3 & 4
Fix: PHP error issue in header variations solved
Update: Improved accessibility
Update: Improved Responsive
Updated to Bootstrap 5 Stable Version
As you know, the stable release of Bootstrap 5 has been officially out a few days ago, we have also updated Bootstrap to the stable version. Now you can enjoy all the exciting features the stable version has to offer like RTL support, brand new utility API, new off-canvas component, updated forms, and more with Helix Ultimate 2.0. Find out more about the Bootstrap 5 stable version HERE.
Add Custom Code After The Body Tag
Make your Helix Ultimate 2.0 more yours with the new field for injecting custom code after opening the body tag. You can now add custom code immediately after the body tag to enhance your site's specific parts or individual pages.
Also, if you want to use Google Tag Manager with your Helix-powered site, you can add your Google Tag Manager code immediately after the body tag. There you have it - a clean and efficient way to inject your code after the opening of the body tag.
Some Notable Improvements
You'll enjoy several bug fixes and performance improvements with the new beta release. Some of the CSS styles went missing for the breadcrumbs in the last release, which has been fixed now. Pagination was not working with Joomla 4 in the last build, which has been made compatible with the update too.
Give the changelog a read to find out the other minor fixes and improvements.
More Accessibility-Ready
As promised, with the beta 3 release, Helix Ultimate 2.0 is now even more WCAG friendly! Accessibility is very important these days and is required by law in many situations. Your favorite template framework has been carefully designed and developed in our dedication to making websites more accessible to users.
Improved Responsiveness for Better Performance and UX
All our efforts to improve the responsiveness of your Joomla website built with Helix Ultimate 2.0 will now make a great impact. As the beta 3 drops, you can enjoy the best and smooth performance at all times and on any device.
Wrapping Up
With the release of Helix Ultimate 2.0 Beta 3, we are only an update away from the stable release! Excited? You should be. You all have made the Helix Ultimate 2.0 journey a wonderful one with your immense support and valuable feedback! Wonderful is an understatement when I say Helix Ultimate 2.0 RC will be soon up for grabs!
Time to try! Helix Ultimate 2.0 Beta 3 is now out on GitHub. Go ahead, try it out, and share your thoughtful feedback with us in the comments.
Keep your eyes on our blog and our newsletters for more updates on Helix Ultimate 2.0 and releases. Happy developing!
Warning: This is an experimental build intended for testing purposes. Please don't use this experimental version in production sites!
Hello have a problem when the template is installed after change name in xml files. To reproduce the error, you must change the name of the template and Install in a new installation or where you do not have a template called shper_helixultimate installed. Tested in Joomla 4 bte7 and Joomla 3.9.26
Notice: Trying to get property 'template' of non-object in plugins\system\helixultimate\src\Platform\Helper.php on line 339
Warning: Creating default object from empty value in plugins\system\helixultimate\src\Platform\Helper.php on line 348
So I don't understand what is wrong, users can create new tickets and share links inside. About possible issues - share your thoughts here: https://github.com/JoomShaper/helix-ultimate/issues
we just tested the new Helix Ultimate and it looks really great :-) The new Header Styles rock!
One small thing regarding Blog Images though - We usally use the Joomla-based image fields (intro_image, fulltext_image) for our client's websites, since it enables us to differentiate between list and detail view - this makes the tab "Blog Options" obsolete and usually causes confusion. Do you think you could implement an option in the plugin to disable this tab?
Will there be an upgrade path from Ultimate to Ultimate 2.0? Is it worth me starting a new project using Ultimate or should I wait for the stable release of 2.0? Thanks
Pls step up your Github precense though there is no feedback or coolaborative work with customers and their reports there. It should be a priority for a Joomshaper Helix Ultimate developer to have attention and get feedback for bug reports for Helix Ultimate. If you ask people to report bugs there but dont care whats the idea??
Notice: Trying to get property 'template' of non-object in plugins\system\helixultimate\src\Platform\Helper.php on line 339
Warning: Creating default object from empty value in plugins\system\helixultimate\src\Platform\Helper.php on line 348
we just tested the new Helix Ultimate and it looks really great :-) The new Header Styles rock!
One small thing regarding Blog Images though - We usally use the Joomla-based image fields (intro_image, fulltext_image) for our client's websites, since it enables us to differentiate between list and detail view - this makes the tab "Blog Options" obsolete and usually causes confusion. Do you think you could implement an option in the plugin to disable this tab?
thanks!