⚠️ This issue respects the following points: ⚠️
Bug description
After upgrading from nextcloud 32.0.2 to nextcloud 33.0.1 installed joplin client cannot sync to the nextcloud server any more.
The following error will be displayed:
Error: PUT xy.md: Call to undefined method OC\DB\QueryBuilder\QueryBuilder::execute() (Exception Error) (500): <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"> <s:exception>Error</s:exception> <s:message>Call to undefined method OC\DB\QueryBuilder\QueryBuilder::execute()</s:message> </d:error>
Steps to reproduce
- Upgrade your nextcloud instance to the latest version 33.0.1
- start joplin - change anything and try to sync
Expected behavior
joplin client should be able to sync to the nextcloud folder as before the upgrade to the latest nextcloud version.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Nginx
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Bug description
After upgrading from nextcloud 32.0.2 to nextcloud 33.0.1 installed joplin client cannot sync to the nextcloud server any more.
The following error will be displayed:
Error: PUT xy.md: Call to undefined method OC\DB\QueryBuilder\QueryBuilder::execute() (Exception Error) (500): <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"> <s:exception>Error</s:exception> <s:message>Call to undefined method OC\DB\QueryBuilder\QueryBuilder::execute()</s:message> </d:error>
Steps to reproduce
Expected behavior
joplin client should be able to sync to the nextcloud folder as before the upgrade to the latest nextcloud version.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Nginx
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The error listed here is not the same and not related.
I personally think the issue here was caused by the memories app because it still uses the
execute()method that was removed.See also pulsejet/memories#1625