figure002 reports that a new user on their Discourse community is receiving the “You’re a New User of the Month! #1” email daily, despite being on the latest version installed via cloud instructions. They suspect it may relate to bootstrap mode, which enables daily email summaries for new users, though they believe this shouldn’t affect monthly recognition emails figure002. gerhard suggests the issue was fixed three weeks prior and asks if they’re on the beta branch, noting that updating should resolve it. figure002 confirms they’re on a feature branch, not master, and manually rebases to master with ./launcher rebuild app to test. In post 5, they realize they’re on the beta branch (2.6.0.beta3) due to #version: tests-passed in app.yml, and plan to switch to stable as per Discourse’s guide to resolve the recurring email bug.
I’m working on building a community using Discourse and only recently people have started joining and participating. One user in particular has been participating a lot recently, which is awesome. But since the start of the following month this user has been receiving the “You’re a New User of the Month! #1” email daily. That is, every day Discourse will send out the same notification email to this user. The last thing I want to do is scare away new users with mail spam.
I’m using the latest version of Discourse which I installed using the instructions for the cloud. I just updated yesterday to see if the problem persists, but it is still happening. Is there anything else I can do to troubleshoot the problem? I’m also not aware of any topics that discuss the same issue.
This may be relevant to the issue. My site is still in bootstrap mode:
To make launching your new site easier, you are in bootstrap mode. All new users will be granted trust level 1 and have daily email summary emails enabled. This will be automatically turned off when 50 users have joined.
So daily email summary emails are enabled, but surely this should not affect “New User of the Month” emails.
Glad to see that this has been fixed already. Strange that the issue isn’t fixed for me though. I upgraded the site using the admin panel. But I am on a feature branch, not master. Maybe that’s the issue? I just manually rebased on master and executed ./launcher rebuild app to see if that makes any difference.