Romain Derie
cc1d78a80b
The `website_published` field from the website's mixins is basically a readonly
from `is_published` field.
On read, this field will simply read `is_published` and check if the record's
website_id is accessible (only for the multi mixin).
On write, it will always write on `is_published`.
This commit improves a few things:
- A lot of code was writting on website_published which was just then writting
on is_published. Writting directly on is_published makes more sense.
- Some backend fields would still reference `website_published` instead of
`is_published` which would just go through the related for no reason.
Plus, using `is_published` will make the field tooltip more accurate as we
are not in a website context ('Visible on current website' to 'Is Published')
- Filter and search on tree view were still using the `website_published`
related field, which is just a readonly when we are not in a frontend
context.
- Some create and write function would have security check on
`website_published` value but that was wrong as the user could bypass that by
simply writting on `is_published`. For the write method, check `is_published`
is more accurate as it will cover both case since `website_published` will
then call the write method on `is_published`
13 lines
497 B
XML
13 lines
497 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo><data noupdate="0">
|
|
<record id="website_slides.badge_data_certification" model="gamification.badge">
|
|
<field name="is_published" eval="True"/>
|
|
</record>
|
|
<record id="website_slides.badge_data_certification_goal" model="gamification.goal.definition">
|
|
<field name="domain">[
|
|
('survey_quizz_passed', '=', True),
|
|
('slide_id.slide_type', '=', 'certification')
|
|
]</field>
|
|
</record>
|
|
</data></odoo>
|