summaryrefslogtreecommitdiff
path: root/addons/website_customer/data
AgeCommit message (Collapse)Author
2020-05-01[IMP] website: simplify website menuDramixDw
Some apps, once installed, automatically create a menuitem in website. What complexify the UI and create useless menu withtout plusvalue. It is not because you install livechat to make support online, that you want a link in your menu to show stats e.g. Now we remove the default menu created, and help user to find it when he create a link. The autocomplete suggest most of the main App's controllers task-2189613 closes odoo/odoo#49081 Related: odoo/enterprise#9733 Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
2019-08-03[IMP] *: correctly read/write website_publishedRomain Derie
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`
2018-07-25[IMP] base: Improve partners/employees demo dataYannick Tivisse
- Update all the pictures - Rename the partners with a name that is easy to say for an English speaker (No more 'Agwoleight') - Update all the addresses/phone numbers in the american format - Unify the demo data with the new theme (Wood shop/manufacture,...)
2018-05-29[IMP] portal, website, website_*: make footer content easy to customizeNirali Sapra
Previously, customizing the website footer was not very easy. This commit will allow users to customize the footer like any other snippet area. There are several behavior changes, as mentioned below: - Removed toggles 'Automatic Footer' and 'Payment Icons' from the Customize menu - Language Selector was moved near the 'Copyright' section of the footer and features a dropdown (dropup technically) to select the language - Moved some footer links from various modules to top menu List of the added menus / changed menus: (a) Resellers (new menu for previous footer link 'Resellers') (b) References (new menu for previous footer link 'Our References') (c) Forums (renamed from 'Forum', as a replacement of 'Forums' footer link, showing all the forums instead of 'Help', as there is no link available to all forums after this commit) (d) Live Support (new menu for previous footer link 'Livechat Support') (e) Mailing Lists (new menu for previous footer link 'Mailing List') (f) Members (new menu for previous footer link 'Members') - Links which were already available as a website menus (Presentations, Jobs, Events, News, Documentation, etc) are simply removed Technical Notes: - Introduced a new template called 'brand_promotion' in website. This will help to avoid adding redundant footer content (like copyright, language selector etc) from several modules (website_sale, website_event, website_quote, etc) while the only intention is to replace module page links. - Removed summernote related fix in portal.less (caused by xpath) because footer is now customizable and added padding to structure instead of footer itself so that bg-color/img can be applied on whole footer. - Few of the tours are improved to drag and drop snippets at proper places and not inside the footer. - Used Flex in copyright portion of footer, so that text will always be horizontally centered (Some themes have different padding for buttons, etc, so if we don't align text dynamically, it has to be managed in particular theme and in particular layouts like full-screen / boxed. And if someone changes height of this portion, we have to re-design this portion again, etc). task-38069 Closes https://github.com/odoo/odoo/pull/22298 Co-authored-by: Dharmraj <dja@odoo.com>
2016-07-12[MIG] website_customer : migraton to new apiJérome Maes
2016-07-12[MOV] website_customer : move filesJérome Maes