diff --git a/Classes/Utility/ConfigurationUtility.php b/Classes/Utility/ConfigurationUtility.php index 27457f65..9ebe35a5 100644 --- a/Classes/Utility/ConfigurationUtility.php +++ b/Classes/Utility/ConfigurationUtility.php @@ -211,7 +211,7 @@ public static function isAnalysisModuleDisabled(): bool public static function isExceptionLoggingActivated(): bool { $extensionConfig = self::getExtensionConfiguration(); - return $extensionConfig['enbaleExceptionLogging'] === '1'; + return $extensionConfig['enableExceptionLogging'] === '1'; } /** diff --git a/Documentation/Technical/Changelog/Index.md b/Documentation/Technical/Changelog/Index.md index 5a8e1839..b5c916df 100644 --- a/Documentation/Technical/Changelog/Index.md +++ b/Documentation/Technical/Changelog/Index.md @@ -9,6 +9,7 @@ Double check if you have cleared all caches after installing a new LUX version t | Version | Situation | Upgrade instructions | |--------------------------------|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| From former versions to 36.5.0 | Typo in extension configuration | Changed option from `enbaleExceptionLogging` to `enableExceptionLogging` if you turned on exception logging, you have to update your configuration | | From former versions to 35.0.0 | Multiclient usage on some records need some time to work | Nothing to do for you - just a note: Some records have to be extended with site information, but this can only be done with new records - not with existing (affected tables: Logs, Search, Fingerprint and some boxes on Lead Dashboard). To ensure that privacy is guaranteed, you need to remove all existing LUX data in a multiclient environment. | | From former versions to 35.0.0 | Define storage pid for editors (linklistener, shortener, utmgenerator) | Records of different tables (tx_lux_domain_model_linklistener, tx_luxenterprise_domain_model_shortener, tx_luxenterprise_domain_model_utmgenerator_uri) can be stored on different pids depending on the backend user - see [Editors configuration](../Editors/Index.md) for details. | | From former versions to 35.0.0 | Add sites data to existing records to allow multiclient usage | Run upgrade wizard `addSitesUpgradeWizard` to add site information on various tables. Recommendation: We strongly recommend you to run the wizard on CLI to prevent timeouts on larger databases. | diff --git a/ext_conf_template.txt b/ext_conf_template.txt index 3f333138..6225881f 100644 --- a/ext_conf_template.txt +++ b/ext_conf_template.txt @@ -56,4 +56,4 @@ showRenderTimes = 0 useCacheLayer = 1 # cat=advanced/enable/280; type=boolean; label= Enable exception logging: If the user is not logged in into backend and an exception happens, those exceptions can be logged as warning in var/log/typo3_[hash].log -enbaleExceptionLogging = 0 +enableExceptionLogging = 0