fix(community_classifieds): admin gets moderator access automatically
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.
This commit is contained in:
parent
35e62e8c61
commit
a79cb2a762
@ -1,6 +1,14 @@
|
||||
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
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
{
|
||||
'name': 'Community OS - Classifieds',
|
||||
'version': '19.0.1.0.0',
|
||||
'version': '19.0.1.0.1',
|
||||
'category': 'Website/Website',
|
||||
'summary': 'Member-gated classifieds board with moderation queue and auto-expiry',
|
||||
'description': """
|
||||
|
||||
@ -16,4 +16,19 @@
|
||||
<field name="implied_ids" eval="[(4, ref('base.group_user'))]"/>
|
||||
<field name="comment">Can review, publish, and reject classified listings.</field>
|
||||
</record>
|
||||
|
||||
<!-- This module is meant to run standalone (see soft-detection of
|
||||
community_membership in controllers/main.py) - it can't assume a
|
||||
deployment layer exists to grant this group to anyone. Without
|
||||
this, a fresh install leaves the installing Administrator unable
|
||||
to see the Classifieds app or Moderation queue at all, since
|
||||
group_classifieds_moderator isn't implied by anything the admin
|
||||
already has - a deployment layer can hit the same gap by seeding
|
||||
its own client role groups and forgetting to grant this one too.
|
||||
Every Odoo Administrator (Settings > Users & Companies > Users >
|
||||
Administrator access) gets moderator rights automatically
|
||||
instead, so no deployment-layer wiring is required. -->
|
||||
<record id="base.group_system" model="res.groups">
|
||||
<field name="implied_ids" eval="[(4, ref('group_classifieds_moderator'))]"/>
|
||||
</record>
|
||||
</odoo>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user