Trace: • tatj6

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
joomla:tatj6 [2026/10/26 15:40] – [Non SP Page Builder Pro pages with Helix Ultimate] Bernard Condraujoomla:tatj6 [2026/11/09 14:31] (current) – [Todo] Bernard Condrau
Line 66: Line 66:
   * For the menu, add the //Saved Item// ''Menu Tabs'', then //Duplicate// a tab within the Tabs Element's settings   * For the menu, add the //Saved Item// ''Menu Tabs'', then //Duplicate// a tab within the Tabs Element's settings
   * Copy ''default.php'' from ''mod_bethico_legal'' to ''/templates/savor/html/'' and ''chmod 444 default.php''   * Copy ''default.php'' from ''mod_bethico_legal'' to ''/templates/savor/html/'' and ''chmod 444 default.php''
 +  * Go to ''Content --> Articles --> Options --> Editing Layout'' and change ''URL A Target Window'' to //Open in new window// 
 +  * Thai language extension version 6.0.0 contains a bug in that it is still using ''JText''. Find file ''localise.php'' in both the site and the administrator language folder and add the following to the top of the file:<code>use Joomla\CMS\Language\Text as JText;</code>
 ===== Todo ===== ===== Todo =====
   - Modify calendar in ''mod_bethico_contact_form''   - Modify calendar in ''mod_bethico_contact_form''
Line 79: Line 80:
   - ''#wiki-content'' formatting   - ''#wiki-content'' formatting
   - Legal documents in German & Thai   - Legal documents in German & Thai
-  - Imprint images +  - Extend FAQ
-  - FAQ Food +
-  - FAQ Drinks and Wine+
   - Template Thai   - Template Thai
   - Template German   - Template German
   - Foto gallery   - Foto gallery
 +  - Go through all news and check links to images
 +  - Check all spaces of columns which render in one column on phone / tablet
 +  - Check wine vintages
 +  - mod_bethico_cookies
 +  - write a cookie module to route to tablet menu
 ===== Prepare content in SP Page Builder Pro ===== ===== Prepare content in SP Page Builder Pro =====
   - In the SP Page Builder //page// of your //test// site: Create a section to be designed. When it's finished delete all unused elements, then **save** the section.   - In the SP Page Builder //page// of your //test// site: Create a section to be designed. When it's finished delete all unused elements, then **save** the section.
Line 90: Line 94:
   - In the SP Page Builder //page// of your //production// site: Open //Saved Items// on the left and drag the newly created section to the desired position. You might need to close and open the page first for the //Saved Items// to update.   - In the SP Page Builder //page// of your //production// site: Open //Saved Items// on the left and drag the newly created section to the desired position. You might need to close and open the page first for the //Saved Items// to update.
  
-===== Non SP Page Builder Pro pages with Helix Ultimate ===== +===== Non-SP Page Builder Pro pages with Helix Ultimate ===== 
-  * Issue: if i point the menu entry to sp page builder pro page everything is fine. if i point it to another component, it breaks the main menu.\\ This is a known issue where Helix Ultimate fails to load its Mega Menu script or CSS on non-SP Page Builder pages, or encounters a Template Style assignment bug. When you load an SP Page Builder page, the necessary framework styles are forced to load; on core Joomla components (like Articles, Contacts, or third-party extensions), they fail to load, breaking the menu layout. +  * Issue: if i point the menu entry to sp page builder pro page everything is fine. if i point it to another component, it breaks the main menu.\\ This is a known issue where Helix Ultimate fails to load its Mega Menu script or CSS on non-SP Page Builder pages, or encounters a Template Style assignment bug. When you load an SP Page Builder page, the necessary framework styles are forced to load; on core Joomla components (like Articles, Contacts, or third-party extensions), they fail to load, breaking the menu layout. Apply the following steps to resolve this issue: 
-Apply the following steps to resolve this issue: +  * Fix the Database Template ID Bug (Most Common). If Helix is assigned to "Use Default" but doesn't accurately pass its ID to core pages, it looks for layout files in the wrong directories, breaking menu components. 
- +    - Open your hosting panel and access phpMyAdmin. 
-1. Fix the Database Template ID Bug (Most Common) +    - Open your Joomla database and look for the #__menu table (e.g., jos_menu or xyz_menu). 
- +    - Locate the specific menu item that is breaking. 
-If Helix is assigned to "Use Default" but doesn't accurately pass its ID to core pages, it looks for layout files in the wrong directories, breaking menu components. +    - Check the template_style_id column for that row. If it is set to 0 or blank, change it explicitly to match your exact Helix Ultimate Template Style ID (you can find this ID number next to your default template under System -> Site Templates in your Joomla backend). 
-1. Open your hosting panel and access phpMyAdmin. +  * Disable Aggressive Javascript/CSS Optimization. Helix Ultimate's compression system frequently conflicts with component scripts on standard pages, breaking menu behaviors. 
-2. Open your Joomla database and look for the #__menu table (e.g., jos_menu or xyz_menu). +    - Go to System -> Site Template Styles -> Open Helix Ultimate. 
-3. Locate the specific menu item that is breaking. +    - Click on Advanced tab -> Look for CSS Compression and JS Compression. 
-4. Check the template_style_id column for that row. If it is set to 0 or blank, change it explicitly to match your exact Helix Ultimate Template Style ID (you can find this ID number next to your default template under System -> Site Templates in your Joomla backend). +    - Turn both OFF, click Save, and clear your cache. 
- +    - Note: If you use third-party tools like JCH Optimize, they will completely break Helix menus if Helix's built-in compression is also running. 
-2. Disable Aggressive Javascript/CSS Optimization +  * Check Menu Assignment in the Template Settings. Sometimes the template layout isn't bound globally across all components. 
- +    - Inside the Helix Ultimate template options, go to the Menu configuration. 
-Helix Ultimate's compression system frequently conflicts with component scripts on standard pages, breaking menu behaviors. +    - Ensure that your Main Menu is explicitly chosen from the dropdown list. 
-1. Go to System -> Site Template Styles -> Open Helix Ultimate. +    - Switch over to the Assignment tab within that same Joomla template style and verify that "All" pages are checked, ensuring the Helix layout controls core component pages as well. 
-2. Click on Advanced tab -> Look for CSS Compression and JS Compression. +  * Create a Hidden "Dummy" SP Page Builder Module. If your menu layout collapses on component pages because Helix fails to enqueue its script library without an SP Page Builder asset on screen. This is what fixed it for me: 
-3. Turn both OFF, click Save, and clear your cache. +    - Go to System -> Site Modules -> Click New. 
-4. Note: If you use third-party tools like JCH Optimize, they will completely break Helix menus if Helix's built-in compression is also running. +    - Select SP Page Builder Module. 
- +    - You do not need to add content; just save it and assign it to a layout position used globally (for the //savor// template, use position //content-top//). 
-3. Check Menu Assignment in the Template Settings +    - Set the module's //Menu Assignment// to the non-SP Page Builder pages only. 
- +    - This forces Joomla to load the framework assets on core component pages, instantly stabilizing the main menu. 
-Sometimes the template layout isn't bound globally across all components. +    - Note that the sequence of CSS files loaded is different from a SP Page Builder page. You might need to change some CSS rules and add ''!important''.
-1. Inside the Helix Ultimate template options, go to the Menu configuration. +
-2. Ensure that your Main Menu is explicitly chosen from the dropdown list. +
-3. Switch over to the Assignment tab within that same Joomla template style and verify that "All" pages are checked, ensuring the Helix layout controls core component pages as well. +
- +
-4. Create a Hidden "Dummy" SP Page Builder Module +
- +
-If your menu layout collapses on component pages because Helix fails to enqueue its script library without an SP Page Builder asset on screen: +
-1. Go to System -> Site Modules -> Click New. +
-2. Select SP Page Builder Module. +
-3. You do not need to add complex content; just save it and assign it to a layout position used globally (like footer or debug). +
-4. Set the module's Menu Assignment to "On all pages". +
-5. (This forces Joomla to load the framework assets on core component pages, instantly stabilizing the main menu).+
  
 ===== Move categories and articles ===== ===== Move categories and articles =====
Line 154: Line 146:
     - Download the ''images'' directory from your Joomla 4 root folder.     - Download the ''images'' directory from your Joomla 4 root folder.
     - Upload and merge those files into the ''images'' directory of your new Joomla 6 installation.     - Upload and merge those files into the ''images'' directory of your new Joomla 6 installation.
 +
 +===== Move ignite gallery =====
 +I decided to start a new Joomla 6 site with a fresh install and transfer the previous site's Ignite Gallery categories and images to the new site. I did not use an extension or tool to do that, so I have full control on what's going on. Previous site: Joomla 4.4.14, new site: Joomla 6.2.0. The following steps are what you need to do:
 +  - Take a backup of both sites.
 +  - Install current version of Ignite Gallery v5.4.1 on your new site.
 +  - Export Tables: Open //phpMyAdmin// on your old site and export the following tables as SQL files:<code>#__igallery
 +#__igallery_profiles
 +#__igallery_img</code>
 +  - If you have set the user ID to the same ID used on the previous site as explained in [[#prepare_production_site|Prepare production site]] you don't need to do anything. If not, you need to change the ''user'' ID fields in all tables to a new site's valid user ID.
 +  - Fix the ''asset_id'' in table ''#__igallery_profiles''.\\ To find the correct ''asset_id'' go to the new site and select table ''#__assets'', then run the following SQL command:<code>SELECT * FROM `#__assets` WHERE name LIKE "com_igallery%";</code>
 +  - Take a note of the ''id'' field where ''name'' is //com_igallery.profile.1//. If you have more than one profile in your site repeat this for all profiles, then insert the found ''id'' into field ''asset_id'' in table ''#__igallery_profiles''.
  

Know How

© 2007-2026 Bernard Condrau - Powered by DokuWiki