[BUG]: Repository Base URL #1241

Closed
opened 2025-08-04 01:12:21 +00:00 by mwweb · 2 comments

What Happened?

When attempting to add a new repository for my component, when selecting GitHub, after filling in fields, then saving, the base URL is showing https://git.vdm.dev , with no option to change it, unless you go into the DB.

Steps to reproduce the Bug

New Repository, fill in all fields, any Target, access as override.

Save the repository. In the list, Base URL will show as https://git.vdm.dev

Which Joomla version are you compiling in?

5.3.2

Which PHP version are you compiling in?

8.2.24

Which Joomla versions are you targeting?

5.x

Which PHP version are you targeting?

8.2+

Which Web server is JCB running on?

Apache 2.4.62

Which Relational Database is JCB running on?

11.7.2-MariaDB-ubu2404

Which OS is JCB running on?

Ubuntu 24.04.2

Which JCB version are you using?

5.1.0

Where in JCB did this issue occur?

Other

On which browsers did you encounter the issue?

Firefox

Additional Comments

No response

### What Happened? When attempting to add a new repository for my component, when selecting GitHub, after filling in fields, then saving, the base URL is showing https://git.vdm.dev , with no option to change it, unless you go into the DB. ### Steps to reproduce the Bug New Repository, fill in all fields, any Target, access as override. Save the repository. In the list, Base URL will show as https://git.vdm.dev ### Which Joomla version are you compiling in? 5.3.2 ### Which PHP version are you compiling in? 8.2.24 ### Which Joomla versions are you targeting? 5.x ### Which PHP version are you targeting? 8.2+ ### Which Web server is JCB running on? Apache 2.4.62 ### Which Relational Database is JCB running on? 11.7.2-MariaDB-ubu2404 ### Which OS is JCB running on? Ubuntu 24.04.2 ### Which JCB version are you using? 5.1.0 ### Where in JCB did this issue occur? Other ### On which browsers did you encounter the issue? Firefox ### Additional Comments _No response_
mwweb added the
Bug
label 2025-08-04 01:12:21 +00:00
Author

It looks to be this in the field code:

class="control-group control-wrapper-username hidden"

Remove hidden, and the field appears.

It looks to be this in the field code: `class="control-group control-wrapper-username hidden"` Remove hidden, and the field appears.
Member

Thanks for raising this! Just to clarify what’s happening:

When you select GitHub as the repository type, we automatically set the base URL behind the scenes to github.com. Because this is done automatically, the URL field is hidden by default. The default value shown in the list view (git.vdm.dev) might cause confusion, but it won’t break anything—if GitHub is properly configured, everything should just work.

That said, we understand this can be a bit annoying. What we do for easier readability and sorting is:

  1. First select Gitea to reveal the URL field.
  2. Manually set the URL to https://github.com.
  3. Then re-select GitHub as the repository type.

This way, the URL field in the list view, reflects the what you expect to see (github.com).

For custom setups—like Gitea instances such as Cobeberg, Gitea, etc.—you should select Gitea so you can manually input your desired base URL.

In short:

  • Selecting GitHub auto-sets the URL to github.com and hides the field.
  • Selecting Gitea lets you manually input a custom URL.
  • Regardless of what you input, if GitHub is selected, we fix the URL behind the scenes to make sure it works.

We’re considering improving this experience, possibly with some JavaScript tweaks or conditional logic to reduce the confusion. Contributions are welcome! For now, we all know it works.

Hope this clears things up!

Thanks for raising this! Just to clarify what’s happening: When you select **GitHub** as the repository type, we **automatically set the base URL** behind the scenes to `github.com`. Because this is done automatically, the URL field is **hidden by default**. The default value shown in the list view (`git.vdm.dev`) might cause confusion, but it won’t break anything—if GitHub is properly configured, everything should just work. That said, we understand this can be a bit annoying. What we do for easier readability and sorting is: 1. First select **Gitea** to reveal the URL field. 2. Manually set the URL to `https://github.com`. 3. Then re-select **GitHub** as the repository type. This way, the URL field in the list view, reflects the what you expect to see (`github.com`). For custom setups—like Gitea instances such as Cobeberg, Gitea, etc.—you *should* select **Gitea** so you can manually input your desired base URL. In short: * Selecting **GitHub** auto-sets the URL to `github.com` and hides the field. * Selecting **Gitea** lets you manually input a custom URL. * Regardless of what you input, if GitHub is selected, we fix the URL behind the scenes to make sure it works. We’re considering improving this experience, possibly with some JavaScript tweaks or conditional logic to reduce the confusion. Contributions are welcome! For now, we all know it works. Hope this clears things up!
mwweb closed this issue 2025-08-16 19:54:56 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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