Short answer: it's difficult. You can change the url of the project server in
installer.settings.json
but you lose the ability to install or update modules served by Backdrop's project server.
You can specify custom URLs for "non-official" contrib/custom modules, by adding the project status url
property in the .info file of the module. That should allow you to keep Backdrop core and "official" contrib updated from https://github.com/backdrop-contrib as per usual, while the custom module can get updates from elsewhere. I've never personally done it, so untested. But it's been there since D7 (perhaps even before).
Backdrop CMS contributed projects
Join the group at https://github.com/backdrop-ops/contrib to add your own! - Backdrop CMS contributed projects
I don't see that property mentioned in https://docs.backdropcms.org/creating-modules#info-files but it is mentioned in https://www.drupal.org/node/542202 (last in the list of .info properties).
klonos:
project status url (Only used for custom modules not submitted to drupal.org)
Allows module maintainers to define a URL to check for updates to their module using the Update status module. No module released on drupal.org should define this parameter. URL should point to an XML feed that accepts requests in the form of
http://my.domain.com/projects/{project}/{core}
. In that example,project status url
should be set tohttp://my.domain.com/projects
.
klonos: The logic seems to be there. See:
- https://github.com/backdrop/backdrop/blob/fe5c21ced7a7e3bcb9b41df15a7977ee89384a17/core/modules/update/update.fetch.inc#L305
- https://github.com/backdrop/backdrop/blob/fe5c21ced7a7e3bcb9b41df15a7977ee89384a17/core/modules/installer/installer.browser.inc#L193
- https://github.com/backdrop/backdrop/blob/fe5c21ced7a7e3bcb9b41df15a7977ee89384a17/core/modules/installer/installer.browser.inc#L291
- https://github.com/backdrop/backdrop/blob/fe5c21ced7a7e3bcb9b41df15a7977ee89384a17/core/modules/installer/installer.pages.inc#L489
Recent comments
Changing the line in eva-display-entity-view.tpl.php from <?php print $rows; ?> to <?php print render($rows); ?> solves the problem. I will add this comment to the issue I opened...
Difficulty using EVA with leaflet maps
Accepted your answer for what it is but i dont like how it is. Meanwhile ive found other more important problems and gave up.
No way to translate site information
Developing a multilingual site in Backdrop CMS is entirely possible, but it requires a lot of patience and study. I have followed the history of the project since the first versions of Backdrop...
No way to translate site information
Thanks for your quick response. I'll feed this back.
Failed to get available update data
Hi, Thank you yorkshirepudding for pushing up and reporting back ! It still doesn't work on ipv6. I don't know what the infrastructure lead did since both records already existed...
Failed to get available update data