[BUG?]: Initialization Failed for Joomla Powers #1190

Open
opened 2024-11-14 09:37:36 +00:00 by SimonvanDoorne · 7 comments
Member

What Happened?

Attempting to init the joomla powers gives error:

image

The 'normal' powers have been initialised without error

Steps to reproduce the Bug

  1. Clean install of Joomla 4.4.2 and JCB 4.0.4-beta1
  2. Click init button on joomla powers
  3. Checked that i have a VDM Access Token

Temporary fix is taking the Joomla powers from an already existing site and exporting/importing them into the new site.

Which Joomla version are you compiling in?

4.4.2

Which PHP version are you compiling in?

8.1

Which Joomla versions are you targeting?

4

Which PHP version are you targeting?

8.1

Which Web server is JCB running on?

Apache

Which Relational Database is JCB running on?

Mysql

Which OS is JCB running on?

CentOS

Which JCB version are you using?

4.0.4-beta1

Where in JCB did this issue occur?

Powers(admin_views)

On which browsers did you encounter the issue?

Firefox

Additional Comments

No response

### What Happened? Attempting to init the joomla powers gives error: ![image](/attachments/133e81bc-6848-422b-8f35-5f4b85d8c8cb) The 'normal' powers have been initialised without error ### Steps to reproduce the Bug 1) Clean install of Joomla 4.4.2 and JCB 4.0.4-beta1 2) Click init button on joomla powers 3) Checked that i have a VDM Access Token Temporary fix is taking the Joomla powers from an already existing site and exporting/importing them into the new site. ### Which Joomla version are you compiling in? 4.4.2 ### Which PHP version are you compiling in? 8.1 ### Which Joomla versions are you targeting? 4 ### Which PHP version are you targeting? 8.1 ### Which Web server is JCB running on? Apache ### Which Relational Database is JCB running on? Mysql ### Which OS is JCB running on? CentOS ### Which JCB version are you using? 4.0.4-beta1 ### Where in JCB did this issue occur? Powers(admin_views) ### On which browsers did you encounter the issue? Firefox ### Additional Comments _No response_
SimonvanDoorne added the
Bug
label 2024-11-14 09:37:36 +00:00
Owner

I have started with a new decentralized system, that will give us a far more stable solution for this part of JCB, and it will be fully automated.

You can already see the ground work here: https://status.vdm.dev/status/jcb

This part of the project is still in development, but you can manually swap out any of the endpoints when the current codeberg.org system is down.

Example you can swap:

https://codeberg.org/joomla/super-powers

With:

https://tildegit.org/joomla/super-powers

So you can use any of the other active systems. Just open the repository and change the BASE URL value with the target systems.

From this:
image

To this:
image

We prefer that you don't use git.vdm.dev since our system is very small, and can not carry all the weight.

I have started with a new decentralized system, that will give us a far more stable solution for this part of JCB, and it will be fully automated. You can already see the ground work here: https://status.vdm.dev/status/jcb This part of the project is still in development, but you can manually swap out any of the endpoints when the current `codeberg.org` system is down. Example you can swap: ``` https://codeberg.org/joomla/super-powers ``` With: ``` https://tildegit.org/joomla/super-powers ``` So you can use any of the other active systems. Just open the repository and change the BASE URL value with the target systems. From this: ![image](https://git.vdm.dev/attachments/ca5ae8a2-3bcf-40d0-8535-328eeead246d) To this: ![image](https://git.vdm.dev/attachments/531f33a3-376d-4f3f-971d-1d34212fdc52) We prefer that you don't use `git.vdm.dev` since our system is very small, and can not carry all the weight.
Owner

This is the same for the Joomla Powers you just open the repository and update the base url.

image

image

This is the same for the `Joomla Powers` you just open the repository and update the **base url**. ![image](https://git.vdm.dev/attachments/510ccedc-6011-4974-9180-58724ec5c41e) ![image](https://git.vdm.dev/attachments/ac72b62f-bb3c-4b68-85fb-7506fbdd4cde)
Owner

So we basically already decentralized it, but it needs manual updating at this point. All the repositories are kept in sync at all times, so what ever repository you use, it should not matter. You can even fork the repo to another Gitea system of your own, or another community system. Send us the details and we will add that system to the bundle. We just selected the top most well known systems in the freedom software space.

So we basically already decentralized it, but it needs manual updating at this point. All the repositories are kept in sync at all times, so what ever repository you use, it should not matter. You can even fork the repo to another Gitea system of your own, or another community system. Send us the details and we will add that system to the bundle. We just selected the top most well known systems in the freedom software space.
Owner

The VDM Access token is only used for the git.vdm.dev system, to see if there is updates.

So when using global in the repository and its not a git.vdm.dev it will fail at times... to fix this at this time just select override and leave the username and token empty. I will also update this so that the call will auto ignore global tokens if the system is not git.vdm.dev :)

This is a massive new additionally set of features to JCB that is phenomenally powerful, and yet little documented at this time. We are already using these features aggressively, its maneuverability across all our projects are just simple stunning.

We are planning some sessions on this for those interested, and will keep you posted.

The VDM Access token is only used for the `git.vdm.dev` system, to see if there is updates. So when using global in the repository and its not a `git.vdm.dev` it will fail at times... to fix this at this time just select override and leave the username and token empty. I will also update this so that the call will auto ignore global tokens if the system is not `git.vdm.dev` :) This is a massive new additionally set of features to JCB that is phenomenally powerful, and yet little documented at this time. We are already using these features aggressively, its maneuverability across all our projects are just simple stunning. We are planning some sessions on this for those interested, and will keep you posted.

Hello,

Having a hard time to get this fixed, but I am stuck. I get this error when I compile for a Joomla 5 component. The url's are not pointing to a valid repository. See attached image. How can I fix this?

Hello, Having a hard time to get this fixed, but I am stuck. I get this error when I compile for a Joomla 5 component. The url's are not pointing to a valid repository. See attached image. How can I fix this?
Owner

Thank you for bringing this up! For now, the best approach is to point to the Codeberg repositories as a temporary solution while we work on resolving this issue.

I'm happy to share that the API is complete and available here: https://api.joomlacomponentbuilder.com/v1/network/community/jcb. This development should allow us to address the issue in the next stable release.

As the community grows, my available time does seem to shrink, but we're making steady progress! 😊

The core challenge here is ensuring JCB communicates with a repository that is active. Updating just one repository isn't sufficient; all repositories configured on your system must be active during a build or import. If any are down, you'll need to manually update the domain to point to an active repository. This should resolve the issue temporarily.

To put it into perspective: when one repository on a system is down, it's often the case that all repositories on that system are down. Therefore, all repository configurations should be updated to point to an alternative system that is online and operational.

Thank you for your patience and support as we work to improve this process!

Thank you for bringing this up! For now, the best approach is to point to the Codeberg repositories as a temporary solution while we work on resolving this issue. I'm happy to share that the API is complete and available here: [https://api.joomlacomponentbuilder.com/v1/network/community/jcb](https://api.joomlacomponentbuilder.com/v1/network/community/jcb). This development should allow us to address the issue in the next stable release. As the community grows, my available time does seem to shrink, but we're making steady progress! 😊 The core challenge here is ensuring JCB communicates with a repository that is active. Updating just one repository isn't sufficient; all repositories configured on your system must be active during a build or import. If any are down, you'll need to manually update the domain to point to an active repository. This should resolve the issue temporarily. To put it into perspective: when one repository on a system is down, it's often the case that all repositories on that system are down. Therefore, all repository configurations should be updated to point to an alternative system that is online and operational. Thank you for your patience and support as we work to improve this process!
Member

Hi @PWRM, Please note that the link provided above will give you all the necessary information you need to connect the git API's to your system. So if you open that link you'll see a list of all the different git systems that can be used to access the necessary repositories (for example: you can use this link [https://codeberg.org/joomla/joomla-powers] to access the joomla powers repository on codeberg through the API).

Further more, to see the list of git systems that are available you can go to this page: https://status.vdm.dev/status/jcb. Here you will see a list of all the alternative git systems we currently have available and running.

We are planning on making some detailed tutorials on this soon. I'm not sure if this helps solve your problem. Please let me know.

Hi @PWRM, Please note that the [link](https://api.joomlacomponentbuilder.com/v1/network/community/jcb) provided above will give you all the necessary information you need to connect the git API's to your system. So if you open that link you'll see a list of all the different git systems that can be used to access the necessary repositories (for example: you can use this link [https://codeberg.org/joomla/joomla-powers] to access the joomla powers repository on codeberg through the API). Further more, to see the list of git systems that are available you can go to this page: https://status.vdm.dev/status/jcb. Here you will see a list of all the alternative git systems we currently have available and running. We are planning on making some detailed tutorials on this soon. I'm not sure if this helps solve your problem. Please let me know.
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

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