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

ts fied automaticaly added when author_name is used in webhook attachments #13001

Closed
ghost opened this issue Dec 20, 2018 · 4 comments
Closed

Comments

@ghost
Copy link

ghost commented Dec 20, 2018

Description:

When using the author_name field in attachments posted through webhook the ts field is automatically added with a wrong value (seems unixtime 1).

Steps to reproduce:

  1. Creation a webhook (without or with a script enabled)
  2. Send a message with attachment that contain the author_name field through the webhook
  3. Verifying the result on the channel where the webhook post the message

Expected behavior:

author_name displayed without any extra date, wrong or not.

Actual behavior:

A wrong date is added at right of the author_name field

Server Setup Information:

  • Version of Rocket.Chat Server: 0.73.2
  • Operating System: CentOS 7.6
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: disabled
  • NodeJS Version: 8.11.3
  • MongoDB Version: 3.6.9

Additional context

Example of problematic message :

{
  "text": "Example message",
  "attachments": [
    {
      "author_name": "Me",
      "title": "Rocket.Chat",
      "title_link": "https://rocket.chat",
      "text": "Rocket.Chat, the best open source chat",
      "image_url": "/images/integration-attachment-example.png",
      "color": "#764FA5"
    }
  ]
}

Relevant logs:

screenshot from 2018-12-20 09-30-46

@petersonbasso
Copy link

+1

@frdmn
Copy link
Contributor

frdmn commented Feb 14, 2019

#13428 will fix this which will probably included in 0.75.0

@MarcosSpessatto
Copy link
Contributor

@tsr-caubry can we close this?

@ghost
Copy link
Author

ghost commented Jun 5, 2019

Yes, everything seems fine right now, thank you.

@ghost ghost closed this as completed Jun 5, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants