Composer updates

Configuration/Setup
1

Describe the issue / Steps to reproduce:
I am trying to install some extensions using composer, but when I run:

composer update

It won’t let me install te extenstions

In my composer.json (it wouldn’t let me add it to the composer.local.json) I have added:

                  "mediawiki/semantic-media-wiki": "~4.2",
                  "mediawiki/chameleon-skin": "~4.4",
                  "mediawiki/semantic-bundle": "~6.1",
                  "professional-wiki/network": "~2.0"

But it fails.

Expected behavior:
I would expect it to install the required extensions

What was the error message/error log?

git@gitlab.hallowelt.com’s password:

Screenshots
NA

System info:

Product Version
MediaWiki 1.39.8
PHP 8.1.29 (litespeed)
MySQL 8.0.36-cll-lve
ICU 64.2
Pygments 2.11.2
BlueSpice (Credits) 4.5.1 (build:20240717180547)
OS Linux mi3-sr113.supercp.com 4.18.0-513.9.1.lve.el8.x86_64 #1 SMP Mon Dec 4 15:01:22 UTC 2023 x86_64-
Browser version Chrome
2

Hi!

Can you please share the error messages you are receiving? Thanks!

3

The error I get when I try and install SMW is a 500 error, when I enable Maps, I get:

[ZuAh_2A6qilEkWYUZvG0awAAAA4] /wiki/index.php/Main_Page Exception: Maps needs to be installed via Composer.

Backtrace:

from /home/cheekyfactor/public_html/wiki/extensions/Maps/src/MapsRegistration.php(31)
#0 /home/cheekyfactor/public_html/wiki/includes/Setup.php(532): Maps\MapsRegistration::Maps\{closure}()
#1 /home/cheekyfactor/public_html/wiki/includes/WebStart.php(86): require_once(string)
#2 /home/cheekyfactor/public_html/wiki/index.php(44): require(string)
#3 {main}

But, when I run

composer install

I am prompted for a password:

git@gitlab.hallowelt.com](mailto:git@gitlab.hallowelt.com)’s password:

Which obviously, I don’t have.

If I just enter twice, I get:

Failed to execute git clone --mirror – ‘git@gitlab.hallowelt.com:HalloWelt/mediawiki-extensions-notifi
cations’ ‘/home/cheekyfactor/.composer/cache/vcs/git-gitlab.hallowelt.com-HalloWelt-mediawiki-extension
s-notifications/’

Cloning into bare repository ‘/home/cheekyfactor/.composer/cache/vcs/git-gitlab.hallowelt.com-HalloWelt
-mediawiki-extensions-notifications’…
Permission denied, please try again.
Permission denied, please try again.
git@gitlab.hallowelt.com: Permission denied (publickey,password).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

4

Well, unfortunately, we have not published Extension:Notifications yet. This will be done soon.

5

Hi,
I have a similar issue I downloaded the 4.5.2 free version but in the composer.lock file the url for the pageHeader extension is set to gitlab.helloworld.com where I have no access and therefore the composer update/install fails. Is this intended or maybe accidential and is there any workaround?

Background:
I install bluespice free in a docker container using Ansible. One of the setup steps is to run the composer update/install which is currently failing.
Without running the command the system is woking but I am not sure if everything ist working correct so far.

Thanks

6

Hello role-end,

welcome to the community forums!

Yes, indeed, Extension:PageHeader is another unpublished extension. We’ll hopefully be able to make it public soon. Please stay tuned.

7

Is there any update on this issue, I’m trying with version 5.1.1 and still the same problem.

8

Hello role-end,

the extension PageHeader is planned to get merged into the BlueSpiceDiscovery skin in a future minor release, for which we created internal tracker #40265.

The code of the extension, despite the private GitLab repo, is implicitly published together with the built code base of BlueSpice free edition, see bluespice-free-release/extensions/PageHeader at main · BlueSpice-Wiki/bluespice-free-release · GitHub . With this, I can provide the following workaround:

  1. Get the PageHeader folder from the mentioned repo, and paste it into the extensions directory of your code base
  2. Remove the "mediawiki/page-header": "dev-REL1_43-3.0.x",line from the _bluespice/build/bluespice-free-distribution/composer.json file in your code base
  3. Run composer update in your preferred way

We will updated this thread again as well, when the extension is eventually merged and the workaround is no longer needed.

Best regards,

Hua