joomla/Component-Builder
40
26
Fork 12
Code Issues 82 Pull Requests 2 Projects 4 Wiki Activity

[BUG]: Custom Code (Hash Automation) & Own Powers is not pushed to package (github) of component it belongs to #1249

New Issue
Closed
opened 2025-09-01 07:54:50 +00:00 by Tom van der Laan · 4 comments
Tom van der Laan commented 2025-09-01 07:54:50 +00:00
Member
Copy Link

What Happened?

When i push my component to my github package repo, the 2 hash automation custom codes (needed to fix the empty date issue #1245) are not added to the repo. Also my custom Powers is not added to the package either.

Steps to reproduce the Bug

create hash automation custom code. Push package to your repo.

Which Joomla version are you compiling in?

5.3.3

Which PHP version are you compiling in?

8.4

Which Joomla versions are you targeting?

5.x

Which PHP version are you targeting?

8.4

Which Web server is JCB running on?

litespeed

Which Relational Database is JCB running on?

mariadb 10.11

Which OS is JCB running on?

almalinux 9

Which JCB version are you using?

v5.0.0-alpha 1 release

Where in JCB did this issue occur?

Joomla Components(admin_views)

On which browsers did you encounter the issue?

Safari

Additional Comments

No response

### What Happened? When i push my component to my github package repo, the 2 hash automation custom codes (needed to fix the empty date issue #1245) are not added to the repo. Also my custom Powers is not added to the package either. ### Steps to reproduce the Bug create hash automation custom code. Push package to your repo. ### Which Joomla version are you compiling in? 5.3.3 ### Which PHP version are you compiling in? 8.4 ### Which Joomla versions are you targeting? 5.x ### Which PHP version are you targeting? 8.4 ### Which Web server is JCB running on? litespeed ### Which Relational Database is JCB running on? mariadb 10.11 ### Which OS is JCB running on? almalinux 9 ### Which JCB version are you using? v5.0.0-alpha 1 release ### Where in JCB did this issue occur? Joomla Components(admin_views) ### On which browsers did you encounter the issue? Safari ### Additional Comments _No response_
Tom van der Laan added the
Bug
 label 2025-09-01 07:54:50 +00:00
Tom van der Laan changed title from [BUG]: Custom Code (Hash Automation) is not pushed to package (github) of component it belongs to to [BUG]: Custom Code (Hash Automation) & Own Powers is not pushed to package (github) of component it belongs to 2025-09-01 08:09:54 +00:00
Lemuel commented 2025-09-01 20:48:16 +00:00
Member
Copy Link

@TLWebdesign Thank you for raising this issue. Let me clarify how the system is currently designed and why you are seeing this behavior.

Hash Automation Custom Codes

It is by design that hash automation custom codes are not shipped with the component via the JCB packaging engine. This functionality has not yet been implemented, so those codes will not be included when packaging a component.

Custom Powers

For pushing out custom powers, the workflow is different since they are not part of the JCB package:

  1. Create a repository for your custom powers.
  2. Set the target content to either Joomla! Power or Super Power.
  3. Once that is configured, navigate to the Super Power tab in the powers area.
  4. Your custom power should be ticked as approved.
  5. Select the approved path for that power, which will point that power to your repository that was configured.

This ensures that your custom powers are properly managed and deployed.

✅ Summary:

  • Hash automation custom codes are not packaged (current limitation, by design).
  • Custom powers require setting up a repository and approval under the Super Power tab before they can be deployed.
@TLWebdesign Thank you for raising this issue. Let me clarify how the system is currently designed and why you are seeing this behavior. #### Hash Automation Custom Codes It is **by design** that hash automation custom codes are **not shipped with the component** via the JCB packaging engine. This functionality has not yet been implemented, so those codes will not be included when packaging a component. #### Custom Powers For pushing out custom powers, the workflow is different since they are not part of the JCB package: 1. **Create a repository** for your custom powers. 2. Set the **target content** to either **Joomla! Power** or **Super Power**. 3. Once that is configured, navigate to the **Super Power** tab in the powers area. 4. Your custom power should be ticked as **approved**. 5. Select the approved path for that power, which will point that power to your **repository that was configured**. This ensures that your custom powers are properly managed and deployed. --- ✅ **Summary:** * **Hash automation custom codes** are not packaged (current limitation, by design). * **Custom powers** require setting up a repository and approval under the Super Power tab before they can be deployed.
❤️ 1
Tom van der Laan commented 2025-09-02 09:36:57 +00:00
Author
Member
Copy Link

HI,

Ahh ok i was trying to work together with other developers on a JCB project. Thats why i ran into this issue. Normally i stay far away from hash automation custom codes but the DATE field issue made me do it haha.

I figured out to push those Powers to a diff branch in my repo. Maybe we should keep the naming conventions in sync tho. Sometimes it's called Powers, and then it's called Super Powers. Makes it confusing.

HI, Ahh ok i was trying to work together with other developers on a JCB project. Thats why i ran into this issue. Normally i stay far away from hash automation custom codes but the DATE field issue made me do it haha. I figured out to push those Powers to a diff branch in my repo. Maybe we should keep the naming conventions in sync tho. Sometimes it's called Powers, and then it's called Super Powers. Makes it confusing.
Llewellyn commented 2025-09-02 09:59:43 +00:00
Owner
Copy Link

Sometimes it's called Powers, and then it's called Super Powers. Makes it confusing.

Super Powers are an advanced way of using Powers across multiple projects in Joomla Component Builder (JCB). Normally, a Power is just a simple PHP class stored in your local database, available to your component. The Super Power concept extends this by allowing you to reference a Power through a special key, the SPK (Super Power Key).

When you use an SPK, JCB will automatically check your local database for the Power. If it’s missing, JCB can fetch it directly from an external repository and link it into your project. This makes Powers reusable and shareable between projects without duplicating code manually.

Think of it as a smarter, more flexible linker system for PHP within Joomla. Powers remain normal PHP classes, but the Super Power mechanism integrates them seamlessly across projects and repositories. That’s why the tab in JCB where you link a Power to a repository is important—it’s the step where a regular Power effectively becomes a Super Power.

In short, Super Powers turn ordinary Powers into shared, portable, and auto-synced code assets, making JCB’s extension-building ecosystem far more powerful and collaborative.

> Sometimes it's called Powers, and then it's called Super Powers. Makes it confusing. Super Powers are an advanced way of using Powers across multiple projects in Joomla Component Builder (JCB). Normally, a Power is just a simple PHP class stored in your local database, available to your component. The Super Power concept extends this by allowing you to reference a Power through a special key, the SPK (Super Power Key). When you use an SPK, JCB will automatically check your local database for the Power. If it’s missing, JCB can fetch it directly from an external repository and link it into your project. This makes Powers reusable and shareable between projects without duplicating code manually. Think of it as a smarter, more flexible linker system for PHP within Joomla. Powers remain normal PHP classes, but the Super Power mechanism integrates them seamlessly across projects and repositories. That’s why the tab in JCB where you link a Power to a repository is important—it’s the step where a regular Power effectively becomes a Super Power. In short, Super Powers turn ordinary Powers into shared, portable, and auto-synced code assets, making JCB’s extension-building ecosystem far more powerful and collaborative.
❤️ 1
Tom van der Laan commented 2025-09-02 16:16:34 +00:00
Author
Member
Copy Link

Ahh ok so it's a power when it's only local. But becomes a SUPER POWER!!! :D when it is linked to a repo. Good to know the difference there thanks 👍

Ahh ok so it's a power when it's only local. But becomes a SUPER POWER!!! :D when it is linked to a repo. Good to know the difference there thanks 👍
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Beta
Issues related to the a beta release
Bug
Documentation
enhancement
help wanted
invalid
joomla
Joomla related changes
question
URGENT
wontfix
No Label
Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aamigo Lemuel Llewellyn Malachi Roline vistamedia Martin Martin Kopp aB0t Robot ro-ot root TLWebdesign Tom van der Laan
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: joomla/Component-Builder#1249
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?