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
What happens here is that our awesome code-base has the "is config writable check" in at least three different places and the logic is all different - yay.
A check in lib/private/config.php whether the file config/config.php exists (
A check in lib/private/util.php which checks whether the config directory is writable. The even more funny thing here is that this code path is only called for new sessions, thus all existing sessions will work happily but as soon as you start a new one things will explode.(
For the sake of having an usable documentation I'd say that we adjust the documentation for now and in the future unify these insane checks somehow in core - but that is unrelated… No need to have them at three different places and also no need to be different everywhere. Especially the third check is really some magic voodoo which abuses the session storage totally ;-)
From owncloud-archive/documentation#731 (comment):
Oh fun, oh fun.
What happens here is that our awesome code-base has the "is config writable check" in at least three different places and the logic is all different - yay.
lib/private/config.php
whether the fileconfig/config.php
exists (core/lib/private/config.php
Lines 172 to 178 in c36bac3
lib/base.php
whether the fileconfig/config.php
is writable or the read-only mode is set (core/lib/base.php
Lines 198 to 216 in 891474b
lib/private/util.php
which checks whether the config directory is writable. The even more funny thing here is that this code path is only called for new sessions, thus all existing sessions will work happily but as soon as you start a new one things will explode.(core/lib/private/util.php
Lines 509 to 516 in aec79b0
For the sake of having an usable documentation I'd say that we adjust the documentation for now and in the future unify these insane checks somehow in core - but that is unrelated… No need to have them at three different places and also no need to be different everywhere. Especially the third check is really some magic voodoo which abuses the session storage totally ;-)
Related to #11843
The text was updated successfully, but these errors were encountered: