spp_farmer_registry carries its own copy of the registry-restriction implementation that #411 reworked in spp_starter_sp_mis: a registry_restriction.js controller patch plus the original config-parameter pattern.
#411 replaced that pattern for the starter module — explicit persistence for the setting (so "off" survives reloads and upgrades) and enforcement moved into a res.partner._check_access override, with the JS deleted. The same treatment should be ported here so both modules behave consistently.
Scope:
Refs: #411 (starter rework), #455 (exemption follow-up).
spp_farmer_registrycarries its own copy of the registry-restriction implementation that #411 reworked inspp_starter_sp_mis: aregistry_restriction.jscontroller patch plus the original config-parameter pattern.#411 replaced that pattern for the starter module — explicit persistence for the setting (so "off" survives reloads and upgrades) and enforcement moved into a
res.partner._check_accessoverride, with the JS deleted. The same treatment should be ported here so both modules behave consistently.Scope:
set_values/noupdatepersistence fix for the farmer-registry setting_check_accessenforcement (scoped to registrants, admin exempt), including theis_registrantpromotion guard from fix(starter_sp_mis): make registry access control persist and enforce #411's reviewspp_farmer_registry/static/src/js/registry_restriction.jsand its asset entrytest_registry_restriction.py) and adapt to this module's config parameterRefs: #411 (starter rework), #455 (exemption follow-up).