Users won't be prompted whenever the site goes into read-only mode.
Instead, a banner will be shown at the top of every pages.
Also, the browser won't automatically reload whenever read-only mode is
disabled. This really was bad UX.
- Replace implicit return code-system in Email::Receiver with proper exception system
- Update tests to check for exceptions instead
- Test the PollMailbox for expected failures
- Add proper email-handling of problematic emails
"
- Adds the advanced option to accept email from non-users per category email-address
- Adds tests covering the new feature
- Adds UI to configure this feature in the frontend
- allow the configuration of an inbox-email-address per category
- post emails to that email into that category instead of global
- Adds UI for configuration
- Adds Documentation for configuration
- Adds Tests for new feature
With the new email_in admin configuration setting, emails to the email_in_address fetched via POP will now be processed and posted as new topics to the forum.
With the email_in_min_trust you can control the trust level the user needs to have at least to be able to post an email as a new topic.
Also contains tests for the email-in feature and minor clean ups
This simply changes the strings in the order clauses in the model. The
reason of the change is because the SQL generated when using symbols
automatically name spaces the column with the table name.
Topic.order(:title).to_sql
=> SELECT "topics".* FROM "topics" ORDER BY "topics"."title" ASC
This also changes the scopes using lamba to use stabby lambas for
consistency with other scopes.
* Avoid editing /etc/apt/sources.list add nginx repo, instead create
/etc/apt/sources.list.d/nginx.list
* Avoid editing /etc/nginx/nginx.conf, instead put server_name_hash_buckets
setting into discourse.conf
* Proper-case Discourse when it is referring to the product name, so that all
the lowercase references are to the user created during the installation
