25 lines
2.1 KiB
Plaintext
25 lines
2.1 KiB
Plaintext
|
Ë
|
|||
|
|
*DDj9 ã ó& — d dl mZ G d„ de« Zy)é )ÚSurveyc ó$ ‡ — e Zd ZdZdˆ fd„ Zˆ xZS )ÚSurveyMultiCompanyuê Override survey controller to enforce correct company context.
|
|||
|
|
|
|||
|
|
In multi-company environments, a public/portal user accessing a survey
|
|||
|
|
URL has no explicit active company in their session. Odoo therefore
|
|||
|
|
defaults to the user's *first* allowed company, which may differ from
|
|||
|
|
the company that owns the survey. This can cause:
|
|||
|
|
|
|||
|
|
* Wrong ir.rule evaluation → AccessError or empty recordsets
|
|||
|
|
* Company-specific fields (currency, fiscal position, …) resolved
|
|||
|
|
against the wrong company
|
|||
|
|
* Sequence/numbering pulled from the wrong company
|
|||
|
|
|
|||
|
|
The fix is straightforward: after the parent resolves the survey and
|
|||
|
|
answer sudo records, we call .with_company() on both of them so that
|
|||
|
|
the rest of the survey flow runs in the correct company context.
|
|||
|
|
|
|||
|
|
Compatible with Odoo 19.0 Community where _get_access_data() still
|
|||
|
|
receives (survey_token, answer_token, ensure_token=True) and returns a
|
|||
|
|
dict with at minimum the keys 'survey_sudo' and 'answer_sudo'.
|
|||
|
|
c óø •— t ‰| � |||¬« }|j d« }|rS|j rG|j }|j |« |d< |j d« }|r|j |« |d< |S )N)Ú ensure_tokenÚ survey_sudoÚ answer_sudo)ÚsuperÚ_get_access_dataÚgetÚ
|
|||
|
|
company_idÚ with_company) ÚselfÚ survey_tokenÚ answer_tokenr Údatar Útarget_companyr Ú __class__s €ú:/mnt/extra-addons/survey_multi_company/controllers/main.pyr z#SurveyMultiCompany._get_access_data s„ ø€ ܉wÑ'Ø ˜,°\ð (ó
|
|||
|
|
ˆð —h‘h˜}Ó-ˆ Ù ˜;×1Ò1Ø (× 3Ñ 3ˆNØ"-×":Ñ":¸>Ó"JˆD� Ñ Ø Ÿ(™( =Ó1ˆKÙØ&1×&>Ñ&>¸~Ó&N��]Ñ#؈ ó )T)Ú__name__Ú
|
|||
|
|
__module__Ú __qualname__Ú__doc__r Ú
|
|||
|
|
__classcell__)r s @r r r s ø„ ñ÷* ñ r r N)Ú#odoo.addons.survey.controllers.mainr r © r r ú<module>r s ðõ
|