-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use "json_encode" and "json_decode" instead of unserialize #18762
Conversation
462a9b1
to
36e26c6
Compare
A new inspection was created. |
👍👍👍👍👍👍👍👍 |
@LukasReschke migration? |
@blizzz As far I see this uses the memcache, if you update to a new release the caching keys will have a new prefix (including the version) and thus there is no migration required. |
@LukasReschke never mind. I mixed it up, overnight, with settings. I give it a practical try later, so far stuff looks good. |
Tested and still works with LDAP. 👍 |
Use "json_encode" and "json_decode" instead of unserialize
@LukasReschke @blizzz Would it make sense to backport this to stable8.1 to mitigate the unserialize issue in https://github.com/owncloud/enterprise/issues/1094? Or is this too risky? |
@MorrisJobke if you include the other fix (the missing true), it's low risk. |
Sure. I just think about migration implications. @LukasReschke After an upgrade the cache gets cleared completely, right? |
Or better: it will use the version for cached entries and therefore not reuse the cache that was created before the update. Is this correct? |
Regression fix: #21999 |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
@blizzz Please review.
Fixes #16498