fix: add Nextcloud 34 support - #26
Conversation
|
Still working on: [Nextcloud Hub 26 Spring] (34.0.1) |
|
with this corrections occweb is working again with 34.0.1. |
|
This fixes occweb with Nextcloud 34.0.1 for me, too. Thank you very much! |
|
Works for me too, thanks! |
Remove outdated deprecation notice and point issue tracker to this fork's repo.
|
@Adphi we got number of confirmations that this keeps it working on nextcloud 34 |
|
tho @Git-Usr123 you might want to keep the fork notice out of this PR |
|
@Git-Usr123 will your fork be available in the actual app store? |
For now, I do not plan to do it, as it's not that easy to be a certified developer. |
In that case please either separate the README changes in a separate branch, or keep the PR changes in a separate branch— so this becomes mergable again |
|
Done but I doubt that this gets published. This project is death. |
|
@Git-Usr123 i can still see the README changes in https://github.com/Adphi/occweb/pull/26/changes |
|
ah nvm, github was being weird @Adphi this should be ready to merge when you have the time |
Summary
Fixes compatibility with Nextcloud 32–34 which introduced several breaking changes.
PHP backend (
OccController.php)OC::$server->getConfig()(removed in NC34) withOC::$server->get(\OCP\IConfig::class)Frontend
index.jsOC.requestTokento all AJAX requests via$.ajaxSetup()— without NC's jQuery integration, CSRF tokens were no longer injected automatically, causing 412 errors on all API callsCompatibility
max-versionfrom 31 to 34 ininfo.xml0.2.4