nextcloud / nextcloud/deck

Deck event treated as "task" and not "event". Will not integrate with DAV calendar

Open
#2,774 1 comment 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug integration: tasks / calendar
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Describe the bug
When I add an item that is calendar driven, it is integrating it as a 'task' and not as an 'event'. Therefore other software that link to it (in this case Thunderbird) are not displaying it as a calendar item. How to modify this behavior so it is treated like a native calendar event.

Is this a bug / built in hardwire or is this changeable somewhere? Cannot find it.

Screenshots
Created a short video to better highlight the issue:

Operating system: Ubuntu 20.04

Web server: Linux

Database: Mysql

PHP version: 7.2

Nextcloud version: (see Nextcloud admin page) 20

Where did you install Nextcloud from: Source

Signing status:

Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.

No errors have been found.

List of activated apps:

Accessibility
Calendar Collaborative tags Comments Community Document Server Contacts Interaction Custom CSS Dashboard Deck Deleted files Federation  File sharing First run wizard Group folders LDAP user and group backend Log Reader Monitoring Nextcloud announcements Notifications Notifications for calendar event updates ONLYOFFICE Password policy PDF viewer Photos Privacy Recommendations Right click Share by mail Support Text Theming Update notification Usage survey User status Versions Video player Weather status 

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or

Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
{
    "system": {
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "cloud.compumatter.biz"
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "20.0.6.1",
        "overwrite.cli.url": "https:\/\/cloud.compumatter.biz",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "mysql.utf8mb4": true,
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "onlyoffice": {
            "verify_peer_off": true
        },
        "maintenance": false,
        "theme": "",
        "loglevel": 2,
        "ldapIgnoreNamingRules": false,
        "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory",
        "mail_smtpmode": "smtp",
        "mail_smtpsecure": "tls",
        "mail_sendmailmode": "smtp",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpauthtype": "LOGIN",
        "mail_smtpauth": 1,
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "587",
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***"
    }
}

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
LDAP

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing Deck's calendar-driven item integration and the DAV export path, then reproduce the result in Thunderbird using the issue's Ubuntu, Nextcloud 20, and MySQL setup. Determine where the item type is assigned and verify completion by confirming that the exported item is recognized as a calendar event rather than a task.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.