You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until #8 and #9 are fixed, the Midgard2 extension only loads MgdSchemas from ShareDir at start-up time. This means that either:
PHP is started with a specified config file (midgard.configuration_file INI setting), in which case the ShareDir from that is used
PHP follows the MIDGARD_ENV_GLOBAL_SHAREDIR directive
The global /usr/share/midgard2 directory is used
Now, if user later tries to open a Midgard connection with open(filename) or open_config(object) that has a different ShareDir set than what Midgard is already using (see the list above), we should log a warning about this. Otherwise users easily think their setting is working an may get into trouble.
The text was updated successfully, but these errors were encountered:
The warning could be something like Tried to change Midgard ShareDir from /original/path to /new/path in runtime. This has no effect. Use the MIDGARD_ENV_GLOBAL_SHAREDIR environment variable for this.
Until #8 and #9 are fixed, the Midgard2 extension only loads MgdSchemas from ShareDir at start-up time. This means that either:
midgard.configuration_file
INI setting), in which case the ShareDir from that is usedMIDGARD_ENV_GLOBAL_SHAREDIR
directive/usr/share/midgard2
directory is usedNow, if user later tries to open a Midgard connection with
open(filename)
oropen_config(object)
that has a different ShareDir set than what Midgard is already using (see the list above), we should log a warning about this. Otherwise users easily think their setting is working an may get into trouble.The text was updated successfully, but these errors were encountered: