-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
fix ocm-provider rewrite rules #40745
Conversation
Signed-off-by: Maxence Lange <[email protected]>
Co-authored-by: Benjamin Gaussorgues <[email protected]> Signed-off-by: Maxence Lange <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not tested, but LGTM
@ArtificialOwl can you install an older version and then update, to see if the htaccess change is correctly handled by the updater? |
/backport to stable27 |
/backport to stable26 |
The backport to stable27 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable27
git pull origin stable27
# Create the new backport branch
git checkout -b fix/foo-stable27
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
Fix the rewrite rules about
ocm-provider
in 2 locations:Setup.php
I were only able to reproduce the issue in some conditions, each time it seems that this patch fixed them.