-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Very Annoying Behaviour #3082
Comments
I agree, this really is annoying and completely unexpected. Re-ordering should not trigger this alert. I'll take a look. |
Can you confirm which version of Cachet you're using. |
@jbrooksuk Is safe to use the 2.4 branch? |
2.4 is changing a lot at the moment so I’d hold off if you’re not prepared :) |
@jbrooksuk Any estimated release date? |
No release date yet. 2.4 will work for you currently, but it's changing often :) |
Any guide to migrate to 2.4? 😅
On Jun 25, 2018 09:47, "James Brooks" <[email protected]> wrote:
No release date yet.
2.4 will work for you currently, but it's changing often :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3082 (comment)>,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ASW_qMZ9DgXmkYohJycNwlljFnidSy9Fks5uAJWJgaJpZM4Uqcdg>
.
|
Hey @jbrooksuk |
When you re-order any component, a notification update of ALL components is sent to ALL subscribers
This is very annoying, as it bothers users a lot and it costs money due to SMTP email providers
And what's more, the component order is not updated until all emails are sent
Is there any way to fix this?
The text was updated successfully, but these errors were encountered: