#6469 (Move today() from Site to User)
by Luc Saffre · in Developers
Summary
When today() is called, it must load the SiteConfig object and read SiteConfig.simulate_today. One tenant can have this field empty and another not. So making today() multitenant-proof is probably a good preparation for #5904 (Multitenancy (multiple "user spaces, "ledgers" or "communities")).
Children
Comments
- 9 months, 2 weeks ago by Luc Saffre about #6469 (Move today() from Site to User) : todo: the SiteConfigCache is still not perfect.
- 9 months, 2 weeks ago by Luc Saffre about #6469 (Move today() from Site to User) : There might still be minor failures in some test suite. I'll try to check this asap.
- 9 months, 2 weeks ago by Luc Saffre about #6469 (Move today() from Site to User) : I now pushed my changes for this. There is no functional change yet (this will come later when we add the User.tenant_id database field).
- 9 months, 2 weeks ago by Luc Saffre in reply to Luc Saffre about #6469 (Move today() from Site to User) : That's why we will have a new actor MySiteConfig (with a default_record_id).
- 9 months, 3 weeks ago by Luc Saffre about #6469 (Move today() from Site to User) (1 reply) : TODO: The System -> Site configuration menu command needs to get reimplemented
- 9 months, 3 weeks ago by Luc Saffre about #6469 (Move today() from Site to User) : I started this from scratch, in a series of local code changes.
- 11 months, 2 weeks ago by Luc Saffre about #6469 (Move today() from Site to User) : Created new Ticket #6469 (Move today() from Site to BaseRequest).