[BUG?]: Initialization Failed for Joomla Powers #1190
Labels
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#1190
Loading…
Reference in New Issue
Block a user
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?
What Happened?
Attempting to init the joomla powers gives error:
The 'normal' powers have been initialised without error
Steps to reproduce the Bug
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
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.orgsystem is down.Example you can swap:
With:
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:
To this:
We prefer that you don't use
git.vdm.devsince our system is very small, and can not carry all the weight.This is the same for the
Joomla Powersyou just open the repository and update the base url.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.
The VDM Access token is only used for the
git.vdm.devsystem, to see if there is updates.So when using global in the repository and its not a
git.vdm.devit 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 notgit.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?
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!
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 @Lemuel. Thank you for your reply. The lack of information, video, tutorial, about this section is the issue. When I entered another repo, the link didn't match because it generated extra path elements in it like /V1/api etc. I did not write down the exact url, sorry for that but it had similar path elements in it. I didn't had info how to set it up so I could see the url was not correct but had no info on how to get it right. Anyhow, it didn't lead to a valid repo connection. Add that moment Codeberg was down. So a tutorial could be very helpful. After a few hours trying to get it fixed, I succeeded in a working installation with this stuff set up right so I hope it stays working.
What can I say, welcome to freedom software :) we are doing our best to support our families and then our friends and opensource is normally at the end of the list, right?
You can help... over here 👍
JCB v5.0.4-beta2 now has the new networking engine in place, and this should help resolve this issue as much as 99% of the time.
@SimonvanDoorne if you can test this, take a look at the https://status.vdm.dev/status/jcb when you see Codeberg is down... then run a test. I know this does not happen often, but from our tests it works very well now.