nextcloud / nextcloud/spreed

Talk bots still shown after disabling apps + duplicate language entries

Open
#17,573 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: bots 🤖
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

Hi,

I am testing this on:

  • Nextcloud AIO 12.9.0 Beta
  • Nextcloud Hub 25 Autumn (32.0.6)
  • Nextcloud Talk 22.0.10

I noticed behavior in Talk / Bots that looks inconsistent and I would like to clarify whether this is expected or a bug.

What I am seeing

I have the following apps disabled in the app settings:

  • Agenda bot
  • Call summary bot
Image

However, in Administration settings → Talk → Bots, these bots are still shown in the list as if they are available on the server.

Image

Also, inside conversation settings → Bots, I can still see entries for these bots and they can still be enabled there.

Image
Additional thing I noticed

There are also multiple seemingly duplicated entries for the same bot in different languages.

For example:

  • Call summary
  • Zhrnutie hovoru (Slovak)
  • other language variants as well

The same applies to Agenda, where multiple language variants are listed too.

So I am trying to understand:

  1. Why are Call summary and Agenda still shown in Talk bot settings even though both related apps are disabled?
  2. Why are there multiple entries for the same bot in different languages?
  3. Is this expected behavior, or should only the relevant localized variant be shown?
What I already tried

After disabling both bot apps, I removed/stopped the related containers and then started everything again cleanly. I also restarted all containers afterwards.

The behavior remains the same.

Is this expected behavior in Hub 25 / AIO 12.9.0 Beta, or could this be a bug in how Talk bot availability is displayed?

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 reproducing the issue in Administration settings → Talk → Bots and conversation settings → Bots with Agenda bot and Call summary bot disabled. Trace how both settings views obtain their bot lists and how localized entries are represented. Done means the behavior for disabled bots and duplicate language variants is determined and covered by an appropriate regression check.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.