[ENHANCEMENT]: Export and Import JCB-Packages #1214

Open
opened 2025-03-30 21:34:31 +00:00 by heinzarden · 1 comment

Enhancement Details

Is there currently a feature in Joomla 5 / JCB 5 to export and import JCB packages, similar to the functionality in Joomla 3 / JCB 3?

If not, will this functionality be implemented in JCB 5 and what is the estimated timeline?"

Best regards
heinzarden

I am referring to a previous comment:

"Llewellyn hat 2024-04-28 20:00:35 +00:00 kommentiert
This feature will also be removed to get the next stable version released, but it is also a very important part of JCB, and will be added back soon as we can.
Currently the normal Joomla upgrade path is the best way to move your JCB instance to the next version of Joomla and JCB. So making a clone of your development system (so you have the original Joomla 3 "with JCB 3" system as back-up to fallback unto), and then migrate it to Joomla 4, and then to Joomla 5, and then install JCB 5.0.0-rc1 and you will have migrated JCB to the newest version and still have all your component in JCB."

Which part of the extension will be affected by this enhancement?

No response

Additional Context

No response

### Enhancement Details Is there currently a feature in Joomla 5 / JCB 5 to export and import JCB packages, similar to the functionality in Joomla 3 / JCB 3? If not, will this functionality be implemented in JCB 5 and what is the estimated timeline?" Best regards heinzarden I am referring to a previous comment: _"Llewellyn hat 2024-04-28 20:00:35 +00:00 kommentiert This feature will also be removed to get the next stable version released, but it is also a very important part of JCB, and will be added back soon as we can. Currently the normal Joomla upgrade path is the best way to move your JCB instance to the next version of Joomla and JCB. So making a clone of your development system (so you have the original Joomla 3 "with JCB 3" system as back-up to fallback unto), and then migrate it to Joomla 4, and then to Joomla 5, and then install JCB 5.0.0-rc1 and you will have migrated JCB to the newest version and still have all your component in JCB."_ ### Which part of the extension will be affected by this enhancement? _No response_ ### Additional Context _No response_
heinzarden added the
enhancement
label 2025-03-30 21:34:31 +00:00
Owner

We understand the importance of seamless component migration in JCB and want to assure the community that this feature is not only coming back but will be significantly improved. Our current development efforts are focused on rethinking the entire process of exporting and importing components, making it more robust, flexible, and scalable.

Progress & Key Improvements

  1. Advanced Demo Component:
    To bridge the gap in the meantime, we have significantly enhanced the demo component that ships with JCB. The latest version—JCB 5.1.1 Alpha 4—introduces the most advanced demo component we’ve ever released, showcasing JCB’s full capabilities, from basic to advanced features. This helps users understand how JCB works and provides a solid foundation for component development.

  2. Global Unique IDs for Seamless Data Migration:
    A major shift has been made in how entities within JCB link to each other. Previously, internal ID-based linking made data movement cumbersome. Now, fields, admin views, and components are connected via global unique IDs (GUIDs) instead of database IDs. This ensures that data can be transferred between different JCB installations without ID conflicts, making migrations much smoother.

  3. Repository-Based Export & Import System:
    We have already implemented a new approach to managing and sharing field types via a global repository. In the field type area, users now see an init, push, and reset system that connects to a shared repository.

    • Reset: Pulls the latest version of a field type from the global repository.
    • Push: Allows users to update the repository with their own field types.
    • Forking & Custom Repositories: Users can fork the global repository and maintain their own private repository for in-house use.

    This same architecture will be expanded to layouts, templates, admin views, and entire components, eventually allowing full component export/import through repositories. This will introduce multiple backup options at different levels, enabling granular control over component migration.

  4. Future Vision: Complete Component Portability
    With the repository-based system in place, JCB will support component-level migration, allowing users to push and pull entire components with all relationships intact. Thanks to the GUID-based architecture, we can eliminate ID conflicts and introduce mechanisms for merging or updating existing elements intelligently.

  5. Ongoing Development & Prioritization
    While we have already laid the groundwork for this system—first in the Power area, then in field types, and soon for layouts and templates—fully implementing it at the component level is a significant task. We are actively working on it but are balancing this effort with ongoing client projects. This means we cannot commit to a specific release date, but we are prioritizing it because we recognize its transformative impact on JCB.

  6. Latest Updates: Joomla 5 Modal Select Field
    In parallel with these improvements, we have successfully implemented the modal select field type for Joomla 5 components in the latest alpha release. This is a significant enhancement over the previous custom field type for creating table relationships, and we expect it to become the preferred method for such tasks moving forward.

Conclusion

The return of JCB’s export/import feature is not only certain but will be significantly better than before. By transitioning to GUID-based linking and a repository-driven migration system, we are ensuring that JCB remains the most powerful and flexible component builder available. This change will make it easier to move fields, layouts, admin views, and entire components across different systems while avoiding ID conflicts and streamlining collaboration.

We appreciate the community’s patience as we implement these improvements, and we are excited about the future of JCB. Stay tuned for further updates as we continue rolling out these advancements!

We understand the importance of seamless component migration in JCB and want to assure the community that this feature is not only coming back but will be significantly improved. Our current development efforts are focused on rethinking the entire process of exporting and importing components, making it more robust, flexible, and scalable. ### **Progress & Key Improvements** 1. **Advanced Demo Component:** To bridge the gap in the meantime, we have significantly enhanced the demo component that ships with JCB. The latest version—JCB 5.1.1 Alpha 4—introduces the most advanced demo component we’ve ever released, showcasing JCB’s full capabilities, from basic to advanced features. This helps users understand how JCB works and provides a solid foundation for component development. 2. **Global Unique IDs for Seamless Data Migration:** A major shift has been made in how entities within JCB link to each other. Previously, internal ID-based linking made data movement cumbersome. Now, fields, admin views, and components are connected via **global unique IDs (GUIDs)** instead of database IDs. This ensures that data can be transferred between different JCB installations **without ID conflicts**, making migrations much smoother. 3. **Repository-Based Export & Import System:** We have already implemented a new approach to managing and sharing field types via a global repository. In the field type area, users now see an **init, push, and reset** system that connects to a shared repository. - **Reset**: Pulls the latest version of a field type from the global repository. - **Push**: Allows users to update the repository with their own field types. - **Forking & Custom Repositories**: Users can fork the global repository and maintain their own private repository for in-house use. This same architecture will be **expanded to layouts, templates, admin views, and entire components**, eventually allowing full component export/import through repositories. This will introduce multiple backup options at different levels, enabling granular control over component migration. 4. **Future Vision: Complete Component Portability** With the repository-based system in place, JCB will support component-level migration, allowing users to push and pull **entire components with all relationships intact**. Thanks to the **GUID-based architecture**, we can eliminate ID conflicts and introduce mechanisms for merging or updating existing elements intelligently. 5. **Ongoing Development & Prioritization** While we have already laid the groundwork for this system—first in the Power area, then in field types, and soon for layouts and templates—fully implementing it at the component level is a significant task. We are actively working on it but are balancing this effort with ongoing client projects. This means we cannot commit to a specific release date, but we are prioritizing it because we recognize its transformative impact on JCB. 6. **Latest Updates: Joomla 5 Modal Select Field** In parallel with these improvements, we have successfully implemented the **modal select field type** for Joomla 5 components in the latest alpha release. This is a significant enhancement over the previous custom field type for creating table relationships, and we expect it to become the preferred method for such tasks moving forward. ### **Conclusion** The return of JCB’s export/import feature is not only certain but will be significantly better than before. By transitioning to **GUID-based linking** and a **repository-driven migration system**, we are ensuring that JCB remains the most powerful and flexible component builder available. This change will make it easier to move fields, layouts, admin views, and entire components across different systems while avoiding ID conflicts and streamlining collaboration. We appreciate the community’s patience as we implement these improvements, and we are excited about the future of JCB. Stay tuned for further updates as we continue rolling out these advancements!
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: joomla/Component-Builder#1214
No description provided.