a79cb2a762
group_classifieds_moderator wasn't implied by anything an Administrator already has, so a standalone install of just this module (no deployment layer to seed role groups - the exact scenario this module's soft membership-detection is designed for) left the installing admin unable to see the Classifieds app or Moderation queue at all until someone manually granted the group. Make base.group_system imply group_classifieds_moderator instead, so every Odoo Administrator gets it automatically with zero extra wiring. Verified on a from-scratch database with only community_classifieds installed (community_membership and tncsc_deployment both uninstalled): admin's has_group() returns True and "Classifieds" appears in their app switcher immediately after install.
18 lines
620 B
ReStructuredText
18 lines
620 B
ReStructuredText
Changelog
|
|
=========
|
|
|
|
19.0.1.0.1 (2026-08-24)
|
|
~~~~~~~~~~~~~~~~~~~~~~~~
|
|
* Every Odoo Administrator now automatically gets the Classifieds
|
|
Moderator group, instead of needing it granted by hand. Without this,
|
|
a standalone install (no deployment layer seeding roles) left the
|
|
installing admin unable to see the Classifieds app or Moderation queue
|
|
at all.
|
|
|
|
19.0.1.0.0 (2026-08-17)
|
|
~~~~~~~~~~~~~~~~~~~~~~~~
|
|
* Initial release: public classifieds board, member-gated posting
|
|
(soft-detects ``community_membership``), admin moderation queue.
|
|
* Auto-expiry, 7-day expiry warning, and new-submission notification
|
|
crons.
|