TWiki::Configure::Load
readConfig
. It allows to
safely modify configuration variables for one single run without affecting
normal TWiki operation.
BEGIN
block of TWiki.pm
. However, when benchmarking/debugging it can be
replaced by custom code which sets the configuration hash. To prevent us from
overriding the custom code again, we use an "unconfigurable" key
$cfg{ConfigurationFinished}
as an indicator.
Note that this method is called by TWiki and configure, and only reads
TWiki.spec= to get defaults. Other spec files (those for extensions) are
not read.
The assumption is that configure
will be run when an extension is installed,
and that will add the config values to LocalSite.cfg, so no defaults are
needed. TWiki.spec is still read because so much of the core code doesn't
provide defaults, and it would be silly to have them in two places anyway.
configure
to initialise the TWiki config hash with
default values from the .spec files.
Normally all configuration values come from LocalSite.cfg. However when
configure
runs it has to get default values for config vars that have not
yet been saved to LocalSite.cfg
.
Returns a reference to a list of the errors it saw.
SEE ALSO: TWiki::Configure::TWikiCfg::load
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microchip and others, are registered trademarks or trademarks of Microchip Technology Inc. and its subsidiaries.
Arm® and others are registered trademarks or trademarks of Arm Limited (or its affiliates). Other terms and product names may be trademarks of others.
Ideas, requests, contributions ? Connect to LinksToCommunities page.