Skip to content
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

Can't get qgis_global_settings.ini working on macOS #37482

Closed
Frzk opened this issue Jun 29, 2020 · 2 comments
Closed

Can't get qgis_global_settings.ini working on macOS #37482

Frzk opened this issue Jun 29, 2020 · 2 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers

Comments

@Frzk
Copy link

Frzk commented Jun 29, 2020

Hi,

I'm trying to deploy QGIS (3.10.7-A Coruña) and a few plugins in a corporate environment under macOS >= 10.14.

I'd like to put the plugins in their own directory (i.e. /Library/Application Support/QGIS/QGIS3/plugins/) so I can easily upgrade things independently.

My idea was to create a global config file with customEnvVars set to "append|QGIS_PLUGINPATH=/Library/Application Support/QGIS/QGIS3/plugins/" and customEnvVarsUse set to true.

From what I've read here and there (and also from QGIS source code), putting a file named qgis_global_settings.ini in one of the StandardPaths should be enough for QGIS to pick it up:

QStringList startupPaths = QStandardPaths::locateAll( QStandardPaths::AppDataLocation, QStringLiteral( "qgis_global_settings.ini" ) );

But for some reason, it just doesn't :-(

I checked the paths from QGIS Python console:

>>> print(os.getenv("QGIS_GLOBAL_SETTINGS_FILE"))
None

>>> from PyQt5.QtCore import QStandardPaths
>>> print(QStandardPaths.locateAll(QStandardPaths.AppDataLocation, "qgis_global_settings.ini"))
['/Library/Application Support/QGIS/QGIS3/qgis_global_settings.ini']

If I launch QGIS from the command line with the --globalsettingsfile option set to /Library/Application Support/QGIS/QGIS3/plugins/, it works as expected (but that's obviously not a solution for the end-users).

Any idea what I'm doing wrong ?
Is that the expected behavior ?
Any idea how I can achieve my goal here ?

Thanks a lot !

@Frzk Frzk added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jun 29, 2020
@gioman
Copy link
Contributor

gioman commented Jun 29, 2020

Any idea what I'm doing wrong ?
Is that the expected behavior ?
Any idea how I can achieve my goal here ?

@Frzk please ask questions in the users or developers mailing lists, if it turns out to be a bug then open a ticket here.

@gioman gioman added the Feedback Waiting on the submitter for answers label Jun 29, 2020
@Frzk
Copy link
Author

Frzk commented Jun 30, 2020

Hi Giovanni,

Thanks for you answer. Also, sorry for posting here, it seemed to me it was the right place.
I forwarded my question to the developers mailing-list.

Please also note, FWIW, that it's working properly with 3.14. I'll close this for now, and maybe re-open later, depending on what happens on the ML.

Thanks again.

@Frzk Frzk closed this as completed Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers
Projects
None yet
Development

No branches or pull requests

2 participants