Works now for me – with Quickstart flex_4.3_quickstart_with_virtuemart_J6.zip working even with warnings on install PHP 8.4.16 allow_url_fopen = 1 display_errors = STDERR max_execution_time = 300 max_input_time = -1 max_input_vars = 10000 memory_limit = 512M post_max_size = 80M upload_max_filesize = 80M

Ignored warnings – renamed folder /administrator/components/com_acym_old and both administrator and frontend loaded ok

Logged in as administrator > system > manage extensions restored folder name to /administrator/components/com_acym search extensions for “acymailing” selected all > actions > uninstalled

All is good with install now – will let you know if I have any more issues.

Hi srgestione,

I need more information from your website setup. Would you contact me directly via our email ( aplikko@gmail.com ) and we will find the way out. There are so many factors involved so I cannot tell by merely looking at the website www.scuolainfanziagoretti.com/joomla

Quick help would be from the page https://docs.joomla.org/J4.x:FatalError even though it is help (documentation) from Joomla 4 version. PHP 8.3.25 is not a problem, because Flex (4.3) has been tested with PHP 8.3.x and PHP 8.4.x.

Kind regards,

Dragan, support admin for Aplikko

Hi sirdna,

Thank you for your encouraging words!

Please allow me to share a few thoughts.

Flex has proven to be a very stable and reliable template. Even though it is built on Helix3, every part of it has been refined and improved over the years—hundreds, if not thousands, of times. With each update, we continue to strengthen it. The important point is that the underlying framework (Helix3) is not as crucial as it may seem. If you are using SP Page Builder (SPPB), apart from the header and footer rendered through Helix, the entire page is built with SPPB—which is an exceptional page builder, by the way. When we launched Aplikko (Flex) in 2016, our vision was to create something “simple but powerful.” That is why we chose to stay with the Helix3 concept: it is lightweight rather than overly complex, and it provides a clean, flexible foundation from which you can build almost anything. Our goal has always been simplicity without sacrificing capability.

This is also a good moment to mention that we are preparing some great new custom addons for SPPB, which will be included as part of Flex. Thanks to SPPB’s addon override system, these new features will be available in Flex (for both Helix3 and Helix Ultimate), as well as in our upcoming new template, “EasyOn”—a combination of Joomla + HU + SPPB + EasyStore. Based on the challenges you and others have experienced with AcyMailing, EasyOn will not include AcyMailing by default.

And while AI is incredibly helpful, it cannot yet build a complete CMS. Freelance developers like us still make our living through this work. AI is a fantastic assistant—just as ChatGPT helped you with AcyMailing—but in the end, humans must still do the building.

Again, thank you for supporting Flex. I hope we can release the next Flex update (supporting both Helix3 and HU) very soon.

Kind regards,

Dragan, for Aplikko

Hi! Same problem with flex_4.3_quickstart_with_virtuemart_J6.zip by the way. When will it be fixed? Anyone else using the quickstart installation facing that issues? Or is there another way to install the theme containing the demo content, except the quickstart installation? Actually we just would need the One Page demo content…

Hello!

Finally I found a workaround to make the quickstart installation work by removing following lines from /installation/sql/mysql/custom.sql:

1319: (105, 0, ‘FOF’, ‘library’, ‘fof’, NULL, ’’, 0, 1, 1, 0, ‘false’, ’’, ’’, NULL, NULL, 0, 0, NULL, 0),

1594: (10411, 0, ‘Helix3 framework based template installer for Flex Template’, ‘plugin’, ‘tmp_helix3’, ’’, ‘system’, 0, 0, 1, 0, ‘false’, ‘{}’, ’’, NULL, NULL, 0, 0, NULL, 0);

What are these lines good for? Without them the installation finishes without errors.

BUT – right after logging into backend a 500 error appears:

“UndefinedFunctionError” in /plugins/system/acymtriggers/acymtriggers.php:363

I had to manually disable that plugin (“AcyMailing – Joomla integration”) in the database to be able to reach the backend. The AcyMailing does not work either (maybe due to the disabled plugin) – “Call to undefined function acym_loadLanguage()” – in backend as well as in frontend. You included AcyMailing 10.5.2 in your installation files, while the current version is 10.7.0. Why?

I am wondering, how these bugs could have been overseen, as not only the installation process crashed, but also the Joomla backend. Did you ever test your installation packages with Joomla!6 ?

Looking forward to your explanations. Kind regards, Gerald

... by the way – after Joomla update to Version 6.0.2 following override files are changed and need to be reviewed in your template:

• /html/layouts/joomla/content/icons/create.php
• /html/layouts/joomla/system/message.php
• /html/mod_menu/default.php
• /html/plg_content_pagenavigation/default.php

And the current version of SP Page Builder is 6.2.2 (you integrated 6.1.2 in FLEX v4.3)

And Acymailing cannot be updated via the Joomla updater.

Hi sirdna,

We are working on “dual” version of Flex, which will be: one version on Helix3 and the second version on Helix Ultimate.

The problem is that it is not possible for existing users to update “old” Helix3 version of Flex with the Helix Ultimate version. It is almost over, but we need to fine tune the best way for “old” users and help how to do it (to switch to Helix Ultimate).

I agree that Helix Ultimate is better, but I am very confidant that our latest (Helix 3) version (Flex 4.3) is very good and super stable, with all the required “technologies” (server settings – SQL, PHP, JS, etc.). We have been working for many months on this Flex update, and after releasing it last month, I cannot find one mistake, even the tiniest console errors.

Please be patient, this is surely next step for Flex.

Kind regards,

Dragan, support admin for Aplikko

great news!

Hi chemlabros,

Thank you for sharing this info. It could be very valuable information for someone that is going through the same thing.

AcyMailing is quite robust component, and I’ve experienced a lot of issues in the past with it (AcyMailing). As we are also preparing a new product (new Joomla template), we have decided to exclude AcyMailing, because of this problems. Many times it would trigger 500 error.

We will think through this, and perhaps even exclude Acymailing from Flex template (package).

Kind regards,

Dragan, support admin for Aplikko

Hi matt0bellows,

Can you share more details about this bug that you find?

Before releasing the Flex 4.3, and after that I have been testing and debugging all the pages in demo (Quickstart) and I couldn’t find any bug, not one. The main problem before this release was Virtuemart’s compatibility with Joomla 6, but we fixed all issues.

So, can you share (here) with all of us this bug? Usually it says (debugging) on which page or location the problem is.

Remember, you have to meet all the (minimum) requirements for Joomla 6 compatibility. Here is our documentation: https://documentation.aplikko.com/flex/#Requirements

Kind regards,

Dragan, support admin for Aplikko

Hi hbproph,

None of your statements are true. Helix3 is still the present framework, that’s true, but Helix3 evolved from the time of Joomla 3. Fo every new version, Flex (Helix3 based) has been re-written in order to work with Joomla 4… and after that with Joomla 5… and now with Joomla 6. You call this process as “patched to work on Joomla 4 and 5”. You can call it what ever you want, but it is (and was) fully compatible with all mentioned Joomla versions, including full compatibility with Joomla 6.

If you don’t like Helix 3 personally, that’s your problem. As I mentioned to “sirdna”, “Dual” version of Flex is coming next (in next release), with both Helix versions (Helix3 + HU). We will provide a migration path for existing users, because you cannot run Helix Ultimate (HU) version on the “old” Helix3.

Lastly, to call it a “scam”, and “garbage code”... well… I have to react on that.

You have fixed all those bugs in two days… wow, you’re an expert… you should build your own template, based on Helix Ultimate. Why don’t you do it, instead of calling Flex a “scam” and “garbage beyond disappointing”? You should use this amazing knowledge of yours and all this energy and expertise to build your own template. You don’t need Flex. Nowadays, AI can help you as well.

No, you just want to pour the hatred and frustration… That’s all.

Hello,

Let me be very clear about this.

Your message completely ignores the core issue. Flex is sold for 99 euros, and for that price customers should expect a template that actually works out of the box. What I experienced, and what many others have reported as well, is the opposite.

If you check the number of complaints, support threads, and user reports, it becomes obvious that these problems are not imaginary. They are recurring, and they are consistent.

So instead of reacting defensively, I would honestly expect a simple, polite acknowledgment that something is not working as intended. That is the minimum any serious developer would do, especially when users encounter the same issues repeatedly.

Responding with attitude or sarcasm does not change the fact that the template is malfunctioning in several areas.

You also mentioned that everything was fully compatible and re-written for every Joomla version.

If that was truly the case, I would not have fixed this many issues in such a short time. And yes, I fixed them quickly because the problems were basic, structural, and should have been caught during testing. Which raises the obvious question: how was this tested before release?

Dismissing every criticism as frustration is simply avoiding responsibility for real technical problems that customers, paying customers, are facing.

Since you mentioned my ability to repair the issues:

If you actually need help getting your template to the standard it should be for a 99 euro product, I am available.

But only on a paid basis. If the compensation is fair, I can fix the existing issues properly and ensure the template behaves reliably.

Hi Andrea,

Please update SPPB (SP Page Builder) to version 6.1.2. You have it inside the latest Flex package (Flex 4.3), which you can download. SPPB 5.4.2 is an old version, and SPPB went through many changes and fixes, until this version 6.1.2 (latest).

If you have difficulty downloading it, contact me directly via email aplikko@gmail.com and I will send you the link (download) for SPPB 6.1.2.

Kind regards,

Dragan, support admin for Aplikko

Hi maxrebo,

In most cases, when you have server 500 (error), it is a problem with the server side, but it can be something else.

1. Check server error logs: The most direct way to find the specific cause is to look at the server’s error log. You can find this through your hosting control panel (like cPanel) in the “Logs” or “Error Log” section.
2. Enable Joomla’s debug mode: Go to System > Global Configuration > Server and set Debug System to “Yes” and Debug Language to “en-GB”. This will show more detailed error messages, though it may not work if the error is preventing the backend from loading.
3. Check your .htaccess file: A corrupted or incorrectly configured .htaccess file is a common cause. Try renaming the file to .htaccess_old to see if the site loads. If it does, you’ll need to regenerate the file or fix the rules within it.
4. Disable extensions: Conflicts with extensions, plugins, or modules are frequent culprits.
   Notice the comment from “chemlabros”, who realised that the problem was with “AcyMailing” (folder ../plugins/system/acymtriggers), and the quick fix was: 1) for this to make it work with joomla 6, php 8.3 and MariaDB 10.11.1 to rename the folder to /plugins/system/acymtriggers-bkp, in order to remove error 500 and get in the admin interface. 2. Unistall AcyMailing plugin in the admin interface.
   1. Via FTP/File Manager: Rename the folders of the plugins, components, and modules to temporarily disable them. Start with the most recently installed or updated ones.
   2. Via database: A more advanced method is to disable extensions directly in the database, but this is riskier.
5. Increase PHP memory limit: If your site requires a lot of memory, you may need to increase the memory_limit in your PHP settings.
6. Verify PHP version compatibility: An extension might not be compatible with a newer PHP version. If you recently updated PHP, check if any extensions need updating or are outdated.
7. Contact your host: If you’ve tried the above steps and are still stuck, contact your hosting provider. They can check server-side issues, such as mod_security rules, and access more detailed logs than you can.

Lastly, I have tested Article front-end and back-end editing (add an image or upload image to server), on both Joomla 5 and Joomla 6, and it was working fine. There are two ways to insert image for the article: standard “Intro image” and “Full Article Image”, or you can use “Helix Blog Options > Upload Image”, which is a kind of “override” for standard Joomla images. Please, make sure you have the latest Flex 4.3 (template only) version, which is the latest and also “stable” version, working with Joomla 5 and Joomla 6.

Common Fixes based on the likely causes, try these common solutions:

• Verify File and Folder Permissions: Incorrect permissions are a frequent cause. Folders should generally be set to 755. Files should generally be set to 644. You can check and adjust permissions using your FTP client or file manager. In the Joomla administrator panel, you can also go to System > System Information > Folder Permissions to check the status.
• Increase PHP Memory and Upload Limits: Large images can exceed default server limits, causing a 500 error.
  ✓ Access your php.ini file or adjust settings via your hosting panel’s PHP settings manager.
  ✓ Increase the following values (example values shown):
  – upload_max_filesize = 10M
  – post_max_size = 10M
  – memory_limit = 128M (ensure this is greater than post_max_size)
  ✓ Save changes and restart your server if required by your host.
• Check the .htaccess file: A misconfigured or corrupted .htaccess file can cause 500 errors.
  ✓ Rename your existing .htaccess file (e.g., to .htaccess_old) via FTP/file manager.
  ✓ Rename the default Joomla file htaccess.txt (located in the root directory) to .htaccess.
  ✓ Test the image upload again. If it works, the issue is with your original .htaccess file’s custom rules.

I hope this will help.

Kind regards,

Dragan, support admin for Aplikko

Hi chaneysc,

As I commented to “maxrebo”, in most cases, when you have server 500 (error), it is a problem with the server side, but it could be also something else.

I had a few times this “500 error”, on my testing (local) server (MAMP), and after restarting server, and even a computer (where MAMP server was installed) it would fix the error. Everything was “revived” like “nothing happened”. It was frustrating and even “shocking” to see this 500 error page, so I can relate to that what you are experiencing. Could be also that the requirements for specific Joomla version are not met ( please see: https://documentation.aplikko.com/flex/#Requirements ) or it could be that some plugin or component is giving us this “headache”. “sirdna” commented that uninstalling AcyMailing fixed his problem. Here is his comment: https://themeforest.net/comments/31808483

1. Check server error logs: The most direct way to find the specific cause is to look at the server’s error log. You can find this through your hosting control panel (like cPanel) in the “Logs” or “Error Log” section.
2. Enable Joomla’s debug mode: Go to System > Global Configuration > Server and set Debug System to “Yes” and Debug Language to “en-GB”. This will show more detailed error messages, though it may not work if the error is preventing the backend from loading.
3. Check your .htaccess file: A corrupted or incorrectly configured .htaccess file is a common cause. Try renaming the file to .htaccess_old to see if the site loads. If it does, you’ll need to regenerate the file or fix the rules within it.
4. Disable extensions: Conflicts with extensions, plugins, or modules are frequent culprits.
   Notice the comment from “chemlabros”, who realised that the problem was with “AcyMailing” (folder ../plugins/system/acymtriggers), and the quick fix was: 1) for this to make it work with joomla 6, php 8.3 and MariaDB 10.11.1 to rename the folder to /plugins/system/acymtriggers-bkp, in order to remove error 500 and get in the admin interface. 2. Unistall AcyMailing plugin in the admin interface.
   1. Via FTP/File Manager: Rename the folders of the plugins, components, and modules to temporarily disable them. Start with the most recently installed or updated ones.
   2. Via database: A more advanced method is to disable extensions directly in the database, but this is riskier.
5. Increase PHP memory limit: If your site requires a lot of memory, you may need to increase the memory_limit in your PHP settings.
6. Verify PHP version compatibility: An extension might not be compatible with a newer PHP version. If you recently updated PHP, check if any extensions need updating or are outdated.
7. Contact your host: If you’ve tried the above steps and are still stuck, contact your hosting provider. They can check server-side issues, such as mod_security rules, and access more detailed logs than you can.

I hope this will help you.

Kind regards,

Dragan, support admin for Aplikko

Hi Jennifer,

We have just released new, major update for Flex, and it is 4.3 version. It is in Envato’s review queue. They need to approve it and it can take up to “few” days (could be a day, or even 4 days…).

Earlier version, Flex 4.2 is still available for you to download (here, on ThemeForest > your account), which is both Joomla 4 and Joomla 5 compatible, but once Envato approves this new (Flex 4.3) update, Flex 4.2 (previous version) will be overwritten with the new one.

I think that the best idea would be for you to contact me (Dragan) via email, so I can send you the latest Flex 4.3 version and give you more detailed instructions, how to update. Email is: aplikko@gmail.com so please, write an email and we will fix this.

Note: Joomla is going now to version 6 (new Flex 4.3 is compatible with J4, J5 and J6), so I will explain how to upgrade your site to the desired version.

Kind regards,

Dragan, support admin for Aplikko

Hi Jennifer,

Meanwhile, Envato approved the template, so you can now download the latest package (Flex 4.3). You have all the latest extensions and the template (Flex) available. All extensions and the template in the package are J4, J5 and Joomla 6 ready (compatible) and also proved to be stable and reliable.

Again, if you have questions, or you need more detailed instructions, write to me ( aplikko@gmail.com ) and we will fix the issues.

Take a look also at our documentation, which is related to Joomla 6 version, but you can apply them (instructions) to previous versions: https://documentation.aplikko.com/flex/

Kind regards,

Dragan, support admin for Aplikko

Hi balero,

Making AP Smart LayerSlider Module fully working with Joomla 4, 5, and now version 6 was impossible mission, that’s why we removed it from Flex package. Please find at Changelog: https://themeforest.net/item/flex-multipurpose-joomla-template/14881156#item-description__changelog paragraph with “August 1 2022 – Version 3.9.7 – Joomla 4 and Joomla 3 Compatibility”.

Because this new update (Flex 4.3) that is coming up is enormously important, bringing Joomla 6 full compatibility and very much improved code overall and since we have been working on this for months and months, our whole focus is on this (Flex) update, but I can promise, once update is released, we will surely try to revive AP Smart LayerSlider Module in the future, if possible.

Since Joomla 4 version, Joomla core files were stripping html code (AP Smart LayerSlider Module), so you couldn’t update html code for slides, like it was the case with Joomla 3 before.

You will receive notification from Envato, once Flex is released (approved by Envato). It takes a few days to finish all this “protocols”.

Kind regards,

Dragan, for Aplikko team

Exciting News! Flex 4.3 – Joomla 6 Ready – Coming Soon!

Hello sirdna and everyone reading this comments,

We are thrilled to share that Flex 4.3 is just days away from release and will be fully compatible with the newly launched Joomla 6.0!

This has been an incredible journey, and we’re especially excited to share that thanks to some brilliant collaboration, we’ve successfully resolved all VirtueMart compatibility issues with Joomla 6. Your online stores will run smooth with new Joomla 6, and for those who don’t use VirtueMart, Flex will shine just as brightly with the new Joomla 6, providing you with the perfect foundation for blogs, portfolios, business sites, and so much more.

What to expect in Flex 4.3:

• Full Joomla 6.0 compatibility – ready for the latest and greatest!
• VirtueMart fully optimized – all known issues fixed for both front-end and back-end
• Enhanced performance and stability across the board
• Includes the fantastic SP Page Builder 6.1.0 with all its new features
• Updated Quickstart packages for the easiest installation yet
• ...and much more!

We are currently putting the finishing touches on the Quickstart packages and doing final testing to ensure everything works flawlessly. The wait is almost over!

Thank you for your patience and trust. We have been absent for months, but working on the new template (should be released by the end of 2025) and also working hard to ensure that Flex, along with VirtueMart, runs smoothly on Joomla 6.0.

Stay tuned for the official release announcement in the coming days. Flex 4.3 is going to take your Joomla experience to the next level!

Keep shining with Flex! ✨

With gratitude,

Aplikko team

Yes! Great to hear from you!

Exciting News! Flex 4.3 – Joomla 6 Ready – Coming Soon!

Hello everyone,

We are thrilled to share that Flex 4.3 is just days away from release and will be fully compatible with the newly launched Joomla 6.0!

This has been an incredible journey, and we’re especially excited to share that thanks to some brilliant collaboration, we’ve successfully resolved all VirtueMart compatibility issues with Joomla 6. Your online stores will run smooth with new Joomla 6, and for those who don’t use VirtueMart, Flex will shine just as brightly with the new Joomla 6, providing you with the perfect foundation for blogs, portfolios, business sites, and so much more.

What to expect in Flex 4.3:

• Full Joomla 6.0 compatibility – ready for the latest and greatest!
• VirtueMart fully optimized – all known issues fixed for both front-end and back-end
• Enhanced performance and stability across the board
• Includes the fantastic SP Page Builder 6.1.0 with all its new features
• Updated Quickstart packages for the easiest installation yet
• ...and much more!

We are currently putting the finishing touches on the Quickstart packages and doing final testing to ensure everything works flawlessly. The wait is almost over!

Thank you for your patience and trust. We have been absent for months, but working on the new template (should be released by the end of 2025) and also working hard to ensure that Flex, along with VirtueMart, runs smoothly on Joomla 6.0.

Stay tuned for the official release announcement in the coming days. Flex 4.3 is going to take your Joomla experience to the next level!

Keep shining with Flex! ✨

With gratitude,

Aplikko team

Thank you for your exciting update!