#106222Offline Mode / externally maintained
Description
There are some TYPO3 users who manage their instances centrally externally, sometimes even in read-only systems or without backend internet access, as they are located in a DMZ.
For these instances, it is important that no hard errors are thrown when the TYPO3 version endpoint cannot be reached, for example, when the backend tries to fetch versions via cURL.
Additionally, the system should only display an informational message and prevent editing when files cannot be written, instead of throwing a hard error.
Perhaps the feature-toggle mechanism could actually be used to implement this functionality. With feature toggles.
For example, a toggle could ensure that when attempting to fetch the versions, instead of a hard error, an informational message is displayed if the endpoint is unreachable. Similarly, editing files in a ‘read-only’ mode could be disabled via a toggle, without overloading the instance.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[FEATURE] Offline Mode / externally maintained Resolves: #106222 Releases: main