v1.19.0

[sojan-official]

Changelog

• Ability to snooze conversations
• Keyboard shortcuts
• Campaigns tab which now includes one-off SMS campaigns
• Email conversations now show subject, cc, and bcc
• Mobile app push notifications for self-hosted installations
• Docker image sizes are reduced by 50% ( special thanks to @paescuj )
• Chatwoot now blocks and throttle abusive requests
• Upgrade the ruby and rails version
• API for custom attributes
• API exposing widget configurations
• Numerous bug fixes and enhancements

Thanks to @SanjuSudheerM, @sbreiler-work, @paescuj, @raikasdev, @HariniKrishnan, @vishal-pandey, @shailesh-kalamkar, @patrickobriain for the contributions

---

This discussion was created from the release v1.19.0.

[Stephen-Lobo]

Thank you for new release and lot of new features.

I just tried to upgrade Chatwoot from 1.18 to the latest version, but it failed.

Ubuntu on Caprover DigitalOccean as per upgrade instructions at https://www.chatwoot.com/docs/self-hosted/deployment/caprover

We received following error.

[Warning] One or more build-args [VAPID_PRIVATE_KEY POSTGRES_USERNAME REDIS_URL SMTP_ENABLE_STARTTLS_AUTO SMTP_PASSWORD MAILER_SENDER_EMAIL RAILS_INBOUND_EMAIL_PASSWORD MAILER_INBOUND_EMAIL_DOMAIN RAILS_LOG_TO_STDOUT ACTIVE_STORAGE_SERVICE SMTP_PORT POSTGRES_PASSWORD POSTGRES_HOST S3_BUCKET_NAME AWS_REGION IP_LOOKUP_SERVICE RAILS_INBOUND_EMAIL_SERVICE RAILS_ENV REDIS_PASSWORD SMTP_DOMAIN SMTP_USERNAME FRONTEND_URL POSTGRES_DATABASE AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY SMTP_ADDRESS SMTP_AUTHENTICATION SECRET_KEY_BASE IP_LOOKUP_API_KEY VAPID_PUBLIC_KEY] were not consumed

[vishnu-narayanan]

@Stephen-Lobo This is due to an upstream issue with docker and alpine Linux on which chatwoot is based. We are working on a fix from our end.

Ref: #2845

[Stephen-Lobo]

I am glad to know that this issue is confirmed as a bug due to ruby-alpine-docker conflict & you are working on it.

BTW, you guys are terrific. The way Chatwoot Team, listens their customers / product-users & tries to help them, I am sure ChatWoot is just few years to become another successful Unicorn startup like PostMan.com

[vishnu-narayanan]

Thank you for your kind words. We are humbled. 🙇

[vishnu-narayanan]

Check out this comment to get it working in the interim.
#2843 (comment)

[Stephen-Lobo]

Thank you.

The hot-fix version has fixed the issue.

[helpobras]

my update is OK. but I found something that appears to be a glitch. an agent or an administrator user is able to create another account freely on mine where the username is.
I tested it with an admin user and a common agent

[sojan-official]

Did you mean that other people can sign up?
if so please check the value of ENABLE_ACCOUNT_SIGNUP env variable

[helpobras]

Is not it. I'm saying that a user agent can create another account after logged in.
look at the video. https://youtu.be/cRn0h9BKS-Q
the ENABLE_ACCOUNT_SIGNUP parameter is api_only
I believe that the agent could not have this type of permission...

[sojan-official]

Did you change any of the installation configs?
In production environments, Chatwoot has installation config CREATE_NEW_ACCOUNT_FROM_DASHBOARD set as false. If you change that to true, the create button will appear.

[helpobras]

the only modification I made was to the .env file
ENABLE_ACCOUNT_SIGNUP=api_only

[helpobras]

I didn't find this parameter in the setup.sh file or in the .env file:
CREATE_NEW_ACCOUNT_FROM_DASHBOARD

[Stephen-Lobo]

Changelog of v1.19.0 mentions:

Mobile app push notifications for self-hosted installations

But, after installing the latest version, we are not getting any notifications of new conversation on Mobile.

Please clarify.

[sojan-official]

Could you reach out on [email protected]. We will have one of our engineers take a look at the installation.