91e91fe1b8
community_classifieds: a member-gated classifieds board. community.classified (title/category/description/up-to-3-images via a child .image model/contact info/state) with a public board at /classifieds, detail pages that track view_count, portal posting at /classifieds/new (soft-detects community_membership - blocks non-active-members only if that module is installed, otherwise anyone logged in can post), a "my listings" portal page with self-service renew, and an admin moderation queue (publish/reject). Daily crons expire past-due listings and send a 7-day expiry warning; a new-submission notice goes out to the Classifieds Moderator group. Listing duration is configurable (Settings), never hardcoded. community_benefits: community.benefit.partner (benefit centres) offer community.benefit entitlements scoped to specific community_membership tiers via tier_ids. community.benefit.redemption logs a redemption but its create() is guarded by a constraint that re-checks the same active-membership condition the membership QR verification page uses (membership_state in active/renewal_due) plus tier entitlement, refusing the redemption otherwise. Public directory at /benefits, portal page at /my/benefits listing only benefits the member's tier actually entitles them to. Two more real Odoo 19 API changes hit here: search-view <group> elements for "Group By" sections no longer accept a `string` attribute (must use `name` only - same fix as community_membership's partner search view, applied here to a fresh module), and res.groups.users was renamed to user_ids. Verified against a live Odoo 19 + Postgres 16 container: 7+4 automated tests pass, plus a full manual live run covering the Phase 4 gate exactly - confirmed a non-member is blocked from /classifieds/new, activated a real membership, posted a classified (pending_review), published it via the moderator action, confirmed it appears on the public board and detail page with view_count incrementing, entitled a tier to a benefit, logged a redemption for the active member, confirmed it shows on /my/benefits, and confirmed redemption creation is refused for a non-member. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
20 lines
921 B
Python
20 lines
921 B
Python
from odoo import http
|
|
from odoo.http import request
|
|
|
|
|
|
class BenefitsController(http.Controller):
|
|
|
|
@http.route(['/benefits'], type='http', auth='public', website=True, sitemap=True)
|
|
def benefits_directory(self, **kwargs):
|
|
centres = request.env['community.benefit.partner'].sudo().search([('active', '=', True)])
|
|
return request.render('community_benefits.benefits_directory_page', {'centres': centres})
|
|
|
|
@http.route(['/my/benefits'], type='http', auth='user', website=True)
|
|
def my_benefits(self, **kwargs):
|
|
partner = request.env.user.partner_id
|
|
benefits = request.env['community.benefit'].sudo().search(
|
|
request.env['community.benefit']._entitled_domain_for_partner(partner)
|
|
)
|
|
benefits = benefits.filtered(lambda benefit: benefit.is_entitled(partner))
|
|
return request.render('community_benefits.portal_my_benefits', {'benefits': benefits})
|