On Fri, Oct 27, 2017, at 02:39 AM, Simon Hanna wrote:
On 10/26/2017 11:51 PM, Abhilash Raj wrote:
On Thu, Oct 26, 2017, at 11:23 AM, Andrew Hodder wrote:
I have an odd one, my Hyperkitty is functionally working fine (archived several lists without issue, can login/out), however I must have done something wrong during it's setup as it's layout is completely broken (and it keeps throwing Example.com up in the top-left corner). You need to change SITE_ID in your Django's configuration to point to your domain name you want to be show there. Default is set to
example.comwhich corresponds to SITE_ID=1 in the Django's configuraiton.How to find the SITE_ID of your domain?
This is rather no-so-nice right now, you will basically have to go to the admin console (/admin/) and login as admin. Then you visit
/admin/django_mailman3/maildomain/and you should see your domain there. Clicking on it will how your it's id in URL bar, like /admin/django_mailman3/maildomain/2 or something.I understand this is rather difficult thing to do, there is an issue open to make this information visible in the UI. Ideally, SITE_ID is sequential, so if you have only one domain, it is most probably 2. You shouldn't get it from maildomain but the real site instead which is under the sites entry /admin/sites/site/
Thank you for this correction, this is probably more accurate data. But since domains are tied to sites internally anyway, they both will probably have the same values.
Also the default is actually 1 and not 2
Well, I didn't mean the default value. I meant that if example.com exists in the database, the next domain you create gets id sequentially, which would be 2 in this case. It is obviously not the best way to find out ID.
Django automatically creates a site with id 1 if the sites framework is activated. Only if you delete the existing entry and add another, you will get an id of 2.
Django automatically creates 'example.com' site with ID 1, that's true. There is no way to specify a default site at the startup time, to something other than 'example.com'. Anything you create after gets next sequential id.
Either way, that is Django's internal semantics and I only mentioned as a stupid shortcut ;-)
Just editing will leave you with 1.
as mentioned in the issue on gitlab, I think we should just drop the SITE_ID or maybe only enable it for DEBUG==True
Yeah, I agree it would make sense to not set a SITE_ID by default, that removes this extra step of finding and setting SITE_ID.
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in