Hello Graficherò,

Thank you for reaching out to our technical support forum. I’m sorry to hear about the trouble you’re experiencing. Rest assured, I will look into this issue for you and work to resolve it as quickly as possible.

Please disable this module and the contact form will work.

prnt.sc/jB1uBpTIUXfL

Best regards

Can you please tell me the exact name of the module? Looking at the backend area editor I cannot determine which one it is.

The module name is Ba Gallery - Contatti EN

prnt.sc/7ua_UK9c87Qz

prnt.sc/1e317ICKzLYh

Hi, I have found the module and the related page, but since the other contact pages in the other languages work fine despite inside the page there is the same BA Gallery module it is undeniable that the problem descends from your javascript: is it possible to get an update or a bugfix?

Apology for the delay. I have checked the issue further. The issue is on id 11. If I change the id to 17, then the form works like other language pages. Please check your module and gallery id 11.

prnt.sc/1bTj0gAjkHON

Hi Ofi,

you are absolutely right, thank you very much for your help. The issue was caused by the fact that only Gallery ID 11 had Load jQuery enabled, which was creating the conflict. After disabling it, everything works correctly now. https://prnt.sc/H5LOVvBPEnN6

I’d like to take advantage of your availability to ask for some guidance about updating this site, which is currently based on Shaper Helix3. I would like to migrate it to Helix Ultimate, keeping the current visual appearance as much as possible, without having to spend days restructuring the whole site.

This is also because I’ve implemented EasyStore, and I’d like to manage and customize its layout more easily compared to what I can do with Helix3. https://prnt.sc/JOQLi0UFrwZs

Thank you again for your support. Best regards, Rosita

Thank you for reaching out and for the detailed context. I’m happy to clarify how you can approach the migration from Helix3 to Helix Ultimate.

First, it’s important to note that Helix3 and Helix Ultimate are fundamentally different frameworks. Due to architectural and structural changes, there is no direct or automated migration process that can transfer layouts, styles, or settings from Helix3 to Helix Ultimate while preserving everything exactly as-is.

That said, you can still migrate efficiently and minimize rework by following a structured approach:

Recommended Migration Approach

1. Install Helix Ultimate alongside Helix3 You can keep Helix3 active while setting up Helix Ultimate. This allows you to reference the existing design during rebuilding.

2. Recreate the layout structure manually Header, footer, module positions, and page structure will need to be rebuilt using Helix Ultimate’s layout builder. While this is manual, it is usually faster than expected, especially for standard layouts.

3. Match visual styles via custom CSS Colors, typography, spacing, and other visual elements can be closely matched by:

   • Configuring Typography, Colors, and Layout settings in Helix Ultimate
   • Reusing or adapting custom CSS from Helix3 where applicable

4. Menu and content remain intact Joomla articles, menus, categories, and EasyStore data are not affected by the template change. Only template-specific layout and styling need to be recreated.

5. EasyStore integration advantage Helix Ultimate offers significantly better flexibility for EasyStore customization—especially when used with SP Page Builder—making it much easier to control layouts, product pages, and styling compared to Helix3.

Expectation Setting While it’s not possible to avoid rebuilding entirely, most users find that recreating the layout in Helix Ultimate is far more manageable than anticipated, and the long-term benefits (performance, flexibility, EasyStore control, and future updates) outweigh the initial effort.