-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
php lizmap/dev.php module:configure saml [error] Unknown module saml #10
Comments
Installing the source code of the module is not enough. You should execute some commands in order to activate it into your application. See installation instructions into the README.md file. Which version of Jelix are you using? Or which application if this is an open source application ? |
Hi Laurent, Thank for your reply. I'm using Jelix version 2.0.1 and Lizmap 3.6.0 root@de9a5a60d858:/var/www/lizmap/# cat vendor/jelix/version/VERSION I follow those steps for Jelix 1.7 or higher root@de9a5a60d858:/# composer require "jelix/saml-module" root@de9a5a60d858:/var/www/lizmap# cat ./var/config/localconfig.ini.php jauth.enable=0 [coordplugins] root@de9a5a60d858:/var/www/# php lizmap/install/configurator.php saml Do you have any idea of what is missing ? Thank for your help |
Hi,
I'm trying to setup saml module and I get this message:
[error] Unknown module saml
Do I miss some steps ?
jelix/saml-module is already installed with composer
bash-5.1# composer require "jelix/saml-module"
Info from https://repo.packagist.org: #StandWithUkraine
Using version ^2.1 for jelix/saml-module
./composer.json has been updated
Running composer update jelix/saml-module
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Generating autoload files
1 package you are using is looking for funding.
Use the
composer fund
command to find out more!No security vulnerability advisories found
bash-5.1#
Thank for your help.
The text was updated successfully, but these errors were encountered: