summaryrefslogtreecommitdiff
path: root/addons/website_event/data
diff options
context:
space:
mode:
authorRomain Derie <rde@odoo.com>2019-05-13 17:29:24 +0000
committerJeremy Kersten <jke@odoo.com>2019-08-03 09:51:22 +0000
commitcc1d78a80b518bd5eaec7eb70d7bc14ec4c31275 (patch)
tree9f5dff2b44804e14701e4fe7bc9603086df9af55 /addons/website_event/data
parentf9c2716b3e76ce9bc36d87d69a37a897391c9cdb (diff)
[IMP] *: correctly read/write website_published
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`
Diffstat (limited to 'addons/website_event/data')
-rw-r--r--addons/website_event/data/event_demo.xml14
1 files changed, 7 insertions, 7 deletions
diff --git a/addons/website_event/data/event_demo.xml b/addons/website_event/data/event_demo.xml
index 85b3a6d33ea..b1c120dc471 100644
--- a/addons/website_event/data/event_demo.xml
+++ b/addons/website_event/data/event_demo.xml
@@ -2,11 +2,11 @@
<odoo>
<record id="base.res_partner_1" model="res.partner">
- <field name="website_published">True</field>
+ <field name="is_published">True</field>
</record>
<record id="event.event_0" model="event.event">
- <field name="website_published">True</field>
+ <field name="is_published">True</field>
<field name="twitter_hashtag">odoo</field>
<field name="description"><![CDATA[
<section class="s_cover parallax s_parallax_is_fixed pt96 pb96" data-scroll-background-ratio="1">
@@ -168,21 +168,21 @@
]]></field> </record>
<record id="base.res_partner_3" model="res.partner">
- <field name="website_published">True</field>
+ <field name="is_published">True</field>
</record>
<record id="base.res_partner_4" model="res.partner">
- <field name="website_published">True</field>
+ <field name="is_published">True</field>
</record>
<record id="event.event_2" model="event.event">
- <field name="website_published">True</field>
+ <field name="is_published">True</field>
<field name="twitter_hashtag">odoo</field>
</record>
<record id="base.res_partner_2" model="res.partner">
- <field name="website_published">True</field>
+ <field name="is_published">True</field>
</record>
<record id="base.res_partner_address_4" model="res.partner">
- <field name="website_published">True</field>
+ <field name="is_published">True</field>
</record>
</odoo>