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
No resources are shown in the calendar ressource booking tab #3907
Comments
Could this be related to my issue nextcloud/calendar_resource_management#44 : |
I started from scratch by deleting all entries and created new ones where no capital letters or spaces are used. Still nothing appearing… 😞 Which NC version are you using? |
I am in the stable v23 |
Can someone provide information on a working setup/configuration? So which versions of Server, Calendar & Calendar Ressource management? And maybe the used commands for adding a ressource? Is there anything I can check? Any external dependencies etc.? |
Investigated a little bit more... Added another floor and few resources with different combinations:
In parallel I watched the Sql database. After some time, all entries appeared in the In the logging nothing apears with log level >=1 Few seconds later the search again returned nothing... From time to time I can find the rooms, but not reliable. nc_resources.mp4 |
Thanks a lot for this debugging session @q-wertz. Very well done. I have to admit I can't see where this randomness comes from. Could you possibly inspect the XHR requests sent to the server? Do they contain the string you put into the search field? There seems to be some debounce logic in place, maybe it swallows some of the characters before the request is sent? |
Thanks for your response. I think I found now the issue. It works as long as only a single character is entered. (I can now find all of my rooms 🎉 😊) The reason why I saw it sometimes in the video was as you supposed some kind of debounce issue. nc_resources2.mp4If you need the browser log I can provide it to you too, just a lot of stuff that has to be cleared from the log 😅 |
nextcloud/cdav-library#637 could be related. Apparently we match display name and the resource's email address for the search. So if you have a display name string that isn't part of the email then you can't search for that resource. |
That makes of course more sense :D
Thanks for the fix :) |
Not sure if I am missing something but with Calendar 3.1.0 on NC 22.2.5 I still don't get any suggestions. Can check on NC 23 at home. What seems strange is that the How can I find out which cdav-library version is in use? |
That is weird, I updated to 3.1.0 and resources are now showing up just fine. (using both capital and small letters, so that does not make a difference). |
That should be v1.1 https://github.com/nextcloud/calendar/blob/v3.1.0/package.json#L49 |
Ok. I find now one of two. Maybe a space in the |
Thanks @q-wertz. Please do and let us know if the space or something else still causes trouble. |
I added now several rooms. The only one that I can find is the one with ID Failing request (with e.g. <x0:principal-property-search xmlns:x0="DAV:" test="allof">
<x0:property-search>
<x0:prop>
<x0:displayname/></x0:prop>
<x0:match>Bespr</x0:match></x0:property-search>
<x0:prop>
<x0:displayname/>
<x1:calendar-user-type xmlns:x1="urn:ietf:params:xml:ns:caldav"/>
<x1:calendar-user-address-set xmlns:x1="urn:ietf:params:xml:ns:caldav"/>
<x0:principal-URL/>
<x0:alternate-URI-set/>
<x2:email-address xmlns:x2="http://sabredav.org/ns"/>
<x3:language xmlns:x3="http://nextcloud.com/ns"/>
<x1:calendar-home-set xmlns:x1="urn:ietf:params:xml:ns:caldav"/>
<x1:schedule-inbox-URL xmlns:x1="urn:ietf:params:xml:ns:caldav"/>
<x1:schedule-outbox-URL xmlns:x1="urn:ietf:params:xml:ns:caldav"/>
<x3:resource-type xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-vehicle-type xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-vehicle-make xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-vehicle-model xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-vehicle-is-electric xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-vehicle-range xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-vehicle-seating-capacity xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-contact-person xmlns:x3="http://nextcloud.com/ns"/>
<x3:resource-contact-person-vcard xmlns:x3="http://nextcloud.com/ns"/>
<x3:room-type xmlns:x3="http://nextcloud.com/ns"/>
<x3:room-seating-capacity xmlns:x3="http://nextcloud.com/ns"/>
<x3:room-building-address xmlns:x3="http://nextcloud.com/ns"/>
<x3:room-building-story xmlns:x3="http://nextcloud.com/ns"/>
<x3:room-building-room-number xmlns:x3="http://nextcloud.com/ns"/>
<x3:room-features xmlns:x3="http://nextcloud.com/ns"/></x0:prop>
<x0:apply-to-principal-collection-set/></x0:principal-property-search> Response: <?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DAV\Exception\NotFound</s:exception>
<s:message>Principal with name 38 not found</s:message>
</d:error> Output of the resource backend:
Content of the
|
Please put this into a new ticket. |
Steps to reproduce
Expected behaviour
The previously added resources are listed
Actual behaviour
No ressources can be found
It looks like they are written to different tables (no idea why there are so many with redundant information):
Also see nextcloud/calendar_resource_management#36
Calendar app
Calendar app version: 3.0.5
CalDAV-clients used: Webcalendar
Client configuration
Browser: Firefox 96.0
Operating system: Ubuntu
Server configuration
Operating system: Ubuntu 20.0.4
Web server: Nginx 1.18
Database: MariaDB (mysql Ver 15.1 Distrib 10.3.32-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2)
PHP version: 7.4
Nextcloud Version: 22.2.3
Updated from an older installed version or fresh install: Updated
List of activated apps:
Nextcloud configuration:
Logs
Web server error log (e.g. /var/log/apache)
Log file (data/nextcloud.log)
Browser log
The text was updated successfully, but these errors were encountered: