You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 a new comment on a card, the counter on the card is not being updated. In combination with the Client Push app, this results in comments not being updated on other devices until a page reload. Interestingly, if the commenter reloads the page, the content (including comments and the counter on the card) gets updated on all devices.
This is a regression which came with some recent update of NC or Deck.
To Reproduce
Steps to reproduce the behavior:
Go to a deck
Click on a card
Add a comment to the card
Expected behavior
The counter of comments on the card should change (+1).
Actual behavior
The counter doesn't change until a page reload.
viewer-main.mjs?v=4ce083d9-28:18309 [WARN] viewer: Some mimes were ignored because they are not enabled in the server previews config Object
log @ viewer-main.mjs?v=4ce083d9-28:18309
listener.js:184 [Deprecation] Listener added for a 'DOMNodeRemoved' mutation event. This event type is deprecated, and will be removed from this browser VERY soon. Usage of this event listener will cause performance issues today, and represents a large risk of imminent site breakage. Consider using MutationObserver instead. See https://chromestatus.com/feature/5083947249172480 for more information.
(anonymous) @ listener.js:184
session-heartbeat.js:103 session heartbeat polling started
The text was updated successfully, but these errors were encountered:
LostinSpacetime
changed the title
comments on a card are not being synced properly
Regression: comments on a card are not being synced properly, with consequences for Client Push
Aug 22, 2024
I tested some more, and it's not necessary to reload the page. It's enough to switch to another tab and back to the NC-tab to update the comments counter on the deck and (I assume) consequently the comments on any other machines when using the Client Push app. This behavior is consistent on different Browsers (Firefox, Chromium) and OSs (Fedora 40, Windows 11).
How to use GitHub
Describe the bug
When I add a new comment on a card, the counter on the card is not being updated. In combination with the Client Push app, this results in comments not being updated on other devices until a page reload. Interestingly, if the commenter reloads the page, the content (including comments and the counter on the card) gets updated on all devices.
This is a regression which came with some recent update of NC or Deck.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The counter of comments on the card should change (+1).
Actual behavior
The counter doesn't change until a page reload.
Client details:
Server details
Operating system:
Ubuntu 22.04.4
Web server:
Apache
Database:
MariaDB 10.6.18
PHP version:
8.2.22
Nextcloud version:
29.0.5
Where did you install Nextcloud from:
Signing status:
No errors have been found.
List of activated apps:
Nextcloud configuration:
{
"system": {
"passwordsalt": "REMOVED SENSITIVE VALUE",
"secret": "REMOVED SENSITIVE VALUE",
"trusted_domains": [
"REMOVED SENSITIVE VALUE",
"localhost",
"REMOVED SENSITIVE VALUE"
],
"datadirectory": "REMOVED SENSITIVE VALUE",
"dbtype": "mysql",
"version": "29.0.5.1",
"overwrite.cli.url": "https://cloud.schloss-schule.wien/",
"dbname": "REMOVED SENSITIVE VALUE",
"dbhost": "REMOVED SENSITIVE VALUE",
"dbport": "",
"dbtableprefix": "oc_",
"dbuser": "REMOVED SENSITIVE VALUE",
"dbpassword": "REMOVED SENSITIVE VALUE",
"installed": true,
"instanceid": "REMOVED SENSITIVE VALUE",
"mail_smtpmode": "smtp",
"mail_smtpsecure": "tls",
"mail_sendmailmode": "smtp",
"mail_from_address": "REMOVED SENSITIVE VALUE",
"mail_domain": "REMOVED SENSITIVE VALUE",
"mail_smtphost": "REMOVED SENSITIVE VALUE",
"mail_smtpauthtype": "LOGIN",
"simpleSignUpLink.shown": false,
"maintenance": false,
"maintenance_window_start": 1,
"mysql.utf8mb4": true,
"default_language": "de_DE",
"default_locale": "de_AT",
"default_phone_region": "AT",
"app_install_overwrite": [
"auto_mail_accounts",
"whiteboard",
"discoursesso"
],
"theme": "",
"loglevel": 2,
"memcache.local": "\OC\Memcache\Redis",
"memcache.locking": "\OC\Memcache\Redis",
"memcache.distributed": "\OC\Memcache\Redis",
"redis": {
"host": "REMOVED SENSITIVE VALUE",
"port": 6379
},
"updater.release.channel": "stable",
"ldapIgnoreNamingRules": false,
"overwritehost": "cloud.schloss-schule.wien",
"auth.bruteforce.protection.enabled": true,
"app.mail.verify-tls-peer": false,
"encryption.legacy_format_support": false,
"encryption.key_storage_migrated": false,
"mail_smtpauth": 1,
"mail_smtpname": "REMOVED SENSITIVE VALUE",
"mail_smtppassword": "REMOVED SENSITIVE VALUE",
"allow_local_remote_servers": true,
"trusted_proxies": "REMOVED SENSITIVE VALUE"
}
}
Are you using an external user-backend, if yes which one:
No
Nextcloud log (data/nextcloud.log)
nextcloud.log
Browser log
viewer-main.mjs?v=4ce083d9-28:18309 [WARN] viewer: Some mimes were ignored because they are not enabled in the server previews config Object
log @ viewer-main.mjs?v=4ce083d9-28:18309
listener.js:184 [Deprecation] Listener added for a 'DOMNodeRemoved' mutation event. This event type is deprecated, and will be removed from this browser VERY soon. Usage of this event listener will cause performance issues today, and represents a large risk of imminent site breakage. Consider using MutationObserver instead. See https://chromestatus.com/feature/5083947249172480 for more information.
(anonymous) @ listener.js:184
session-heartbeat.js:103 session heartbeat polling started
The text was updated successfully, but these errors were encountered: