Skip to content
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

Display Issue - empty article and missing picture when sending multiple pictures over WhatsApp to Zammad #5163

Open
Mirtaaa opened this issue May 7, 2024 · 2 comments

Comments

@Mirtaaa
Copy link

Mirtaaa commented May 7, 2024

Used Zammad Version

6.3

Environment

  • Installation method: [e.g. source, package]
  • Operating system (if you're unsure: cat /etc/os-release ): [e.g. debian 10.4, ubuntu 20.04]
  • Database + version: [e.g. postgresql 9.3, mysql 5.7, mariadb 10.3]
  • Elasticsearch version: [e.g. 7.17]
  • Browser + version: [e.g. chrome 83, safari 14, firefox 105]

Actual behaviour

When I send multiple pictures at once over WhatsApp to Zammad, some of the articles in the ticket zoom appear emtpy.

Screenshot 2024-05-07 134529

If I refresh the tab I can "fix" the view and the pictures appear inside the articles.

Expected behaviour

When sending multiple pictures over WhatsApp to Zammad, each picture should appear in an article without disappearing or creating emtpy articles.

Steps to reproduce the behaviour

Send mulitple pictures at once over whatsapp to your Zammad Instance.

Support Ticket

No response

I'm sure this is a bug and no feature request or a general question.

yes

@rolfschmidt
Copy link
Collaborator

The issue is related to the attachment creation:

Store.create!(
object: 'Ticket::Article',
o_id: article.id,
data: data,
filename: filename,
preferences: {
'Mime-Type' => mime_type,
},
)

Store.create!(
object: 'Ticket::Article',
o_id: article.id,
data: data,
filename: filename,
preferences: {
'Mime-Type' => mime_type,
},
)

Changes in the store do not trigger the asset pipeline and updates in the UI of the old tech stack. We need to touch the article after the attachments get created or if possible directly create the article with the attachments.

@dominikklein
Copy link
Collaborator

The issue is related to the attachment creation:

Store.create!(
object: 'Ticket::Article',
o_id: article.id,
data: data,
filename: filename,
preferences: {
'Mime-Type' => mime_type,
},
)

Store.create!(
object: 'Ticket::Article',
o_id: article.id,
data: data,
filename: filename,
preferences: {
'Mime-Type' => mime_type,
},
)

Changes in the store do not trigger the asset pipeline and updates in the UI of the old tech stack. We need to touch the article after the attachments get created or if possible directly create the article with the attachments.

We are doing it in the same flow also in other channels (e.g. email or telegram). What is different? Maybe from WhatsApp side, every attachment is a single incoming webhook media message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants