Static settings reference
This is the reference of all static settings defined by Misago. Reference of settings defined by Django can be found on Django documentation.
List of Misago ACL framework extensions.
On Misago admin panel home page you will find a message telling you if you have entered the correct value, or what value is correct in case you've didn't.
Link namespaces that are administrator-only areas that require additional security from Misago. Users will have to re-authenticate themselves to access those namespaces, even if they are already signed in your frontend. In addition they will be requested to reauthenticated if they were inactive in those namespaces for certain time.
Defautly misago:admin and admin namespaces are specified, putting both Misago and Django default admin interfaces under extended security mechanics.
Path prefix for Misago administration backend. Defautly "admincp", but you may set it to empty string if you with to disable your forum administration backend.
Maximum allowed lenght of inactivity period between two requests to admin namespaces. If its exceeded, user will be asked to sign in again to admin backed before being allowed to continue activities.
Default file that should be served if user has no permission to see requested attachment.
Default file that should be served if user has requested nonexistant attachment.
Max dimensions (width and height) of user-uploaded images embedded in posts. If uploaded image is greater than dimensions specified in this settings, Misago will generate thumbnail for it.
Because user-uploaded GIF's may be smaller than dimensions specified, but still be considerably heavy due to animation, Misago always generates thumbnails for user-uploaded GIFS, stripping the animations from them.
Length of attachment's secret (filenames and url token). The longer, the harder it is to bruteforce, but too long may conflict with your uploaded files storage limits (eg. filesystem path length limits).
In order for Misago to support clustered deployments or CDN's (like Amazon's S3), its unable to validate user's permission to see the attachment at its source. Instead it has to rely on exessively long and hard to guess urls to attachments and assumption that your users will not "leak" source urls to attachments further.
Generaly, neither you nor your users should use forums to exchange files containing valuable data, but if you do, you should make sure to secure it additionaly via other means like password-protected archives or file encryption solutions.
Path to directory containing avatar galleries. Those galleries can be loaded by running loadavatargallery command.
Feel free to remove existing galleries or add your own.
If you create gallery named __default__ and set avatar gallery as default user avatar, Misago will select new users avatars from it while keeping this gallery hidden from existing users.
Misago uses avatar cache that prescales avatars to requested sizes. Enter here sizes to which those should be optimized.
It's impossible to regenerate user avatars store for existing avatars. Misago comes with sane defaults for avatar sizes, with min. height for user avatar being 400 pixels square, and steps of 200, 150, 100, 64, 50 and 30px. However if you need larger avatar or different pregenerated dimensions, changing those will require you to manually remove avatars directory from your media storage as well as running misago.users.avatars.set_default_avatar function against every user registered.
This path to static image file that Misago should use as blank avatar. Defaults to misago/img/blank-avatar.png.
Custom callbacks for bleach to customize automatic links substitution with bleach.linkify.
Function used to create unique avatar for this user. Allows for customization of algorithm used to generate those.
URL to API endpoint used to authenticate sign-in credentials. Musn't contain api prefix or wrapping slashes. Defaults to 'auth/login'.
List of python modules extending Misago markup.
List of Moment.js locals available.
List of functions to be called when somebody attempts to register on forums using registration form.
List of post search filters that are used to normalize search queries and documents used in forum search engine.
List of post validators used to validate posts.
List of middleware classes participating in posting process.
Defines list of groups of profile fields used on users profiles "details" tab.
Should be list of dicts defining name key that's string with name of fields group and fields that is list of paths to Python types implementing fields:
MISAGO_PROFILE_FIELDS = [{'name': _("Personal"),'fields': ['misago.users.profilefields.default.FullNameField','misago.users.profilefields.default.GenderField',],},{'name': _("Contact"),'fields': ['misago.users.profilefields.default.TwitterHandleField','misago.users.profilefields.default.WebsiteField',],},]
PostgreSQL text search configuration to use in searches. Defaults to "simple", for list of installed configurations run "\dF" in "psql".
Standard configs as of PostgreSQL 9.5 are: dutch, english, finnish, french, german, hungarian, italian, norwegian, portuguese, romanian, russian, simple, spanish, swedish, turkish.
Example on adding custom language can be found here.
Items in Misago are usually indexed in search engine on save or update. If you change search configuration, you'll need to rebuild search for past posts to get reindexed using new configuration. Misago comes with rebuildpostssearch tool for this purpose.
Path to function or callable used by Misago to generate slugs. Defaults to misago.static.slugify.default. Use this function if you want to customize slugs generation on your community.
Change this setting to False to display categories list instead of threads list on board index.
List of clasess defining thread types.
Path to the directory that Misago should use to prepare user data downloads. Should not be accessible from internet.
