summaryrefslogtreecommitdiff
path: root/addons/website_slides/data/slide_data.xml
AgeCommit message (Collapse)Author
2020-08-11[IMP] website_slides: set level related tag to dataPatrick Hoste
Move level related tags from demo to data. Those are standard enough to fill up tags data. LINKS Task ID-2241513 PR #55698
2019-08-05[IMP] website_slides(_*): improve demo data and remove dummy dataJérémy Hennecart
PURPOSE eLearning should have its own application in manager. Indeed this is becoming a big application and having it embedded inside Website application is not enough anymore. It should also hold updated and easy-to-use menus, navigation, actions and views in backend. SPECIFICATIONS Remove "Our Documentation" dummy default existing data. It makes no sense to have void data. Instead just add a small explanation text in eLearning front-end telling the user to create its first course if he has rights to do so. In order to better show the new backend add some demo data for missing numbers, notably * sales: add confirmed sale orders in order to have revenues value; * forum: add some posts and answers; * quiz: update slide.slide.partner demo data to hold quiz attempts count; LINKS Task 1978729 PR #35061 Co-Authored-By: Thibault Delavallée <tde@odoo.com> Co-Authored-By: Jérémy Hennecart <jeh@odoo.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`
2019-02-19[REF] website_slides: improve and make access options clearerThibault Delavallée
Purpose is to ensure more advanced use cases are still supported in new elearning platform in addition to more public use cases. Fields controlling access are now * enroll: who can enroll on course: public (everyone, simply click on join button), invite (added by already members) and payment (in bridge with website_sale, if SO with product is confirmed); * enroll_group_ids: automatically add members of those groups to the channel to ease having groups for a given subset of users; * visibility: who can see a channel and its slides: public (everyone, it means channel is visible on website for example), members (hidden for non members) * website_published on channels and slides; non publishers cannot see what is not published, whatever other parameters; * upload_group_ids: who can upload on a channel; * download_security on a slide is completely removed as it makes no sense for most slide types; To ensure a better user experience responsible of a channel is added in its members. People uploading a slide are now also allowed to read it to avoid having inconsistency behavior between upload_group_ids and access rules. Some tests are added. This commit is linked to task ID 1942836 and PR #31239. Co-Authored-By: Aurélien Warnon <awa@odoo.com> Co-Authored-By: Thibault Delavallée <tde@odoo.com>
2019-02-15[REF] website_slides: propose new shiny (incomplete) demo dataThibault Delavallée
Purpose of this commit is to rewrite slides demo data. More channels, more slides, more images, less Odoo oriented content. Everything is still not completely clean but at least it begins to look like something we could show to people. Thanks to @awa-odoo who gave some demo data. No thanks to @xmo-odoo who did not give demo data about the emu war. This commit is linked to task ID 1936153 and PR #30770. Co-Authored-By: Aurélien Warnon <awa@odoo.com> Co-Authored-By: Thibault Delavallee <tde@odoo.com>
2019-02-11[IMP] website_slides: add tags and tag groups on channelThibault Delavallée
Purpose is to be able to filter, search and categorize channels. Notably with eLearning in mind there will be more channels as a channel will also be used to hold lessons. For that purpose we add a model of tag linked to channels. Those tags are organized by groups in order to be able to display them using a menu or a small hierarchy of tags. Displaying a tag group as a specific navigation element is controlled by a specific field. Those models will be used to display a new and improved home page for channels / courses. This commit is linked to task ID 1936153 and PR #30985.
2019-02-07[IMP] website_slides: clean ACLs and refactor access optionsThibault Delavallée
Purpose of this commit is to clean access rights on slide models and give less access to public / portal / internal users. Website publishers and editors have rights to edit slides content and manage channels. Another purpose is to clean and refactor access options on channels and slides. Access to a given slide depends on the current user being a member of the slide channel. A channel can be either public (joined easily) or on invitation only (manual addition of members). Slide can be flagged as preview, meaning they are accessible without any concern about channel membership. It is used as teasing or free promotion of a channel. Publish flag is orthogonal. Non published slides are not visible to everyone except website content editor. It allows to work and improve slides without displaying them to members or public people. Technically a new model is added to model membership on channels. It is a decorated m2m between channels and partners; on this m2m the state of membership is added. In a near future additional information will be stored on this model, like completion of channel or certification information. Other technical changes implied by this commit * visibility is simplified to either public or invite; * can_see and can_see_full are removed, as well as concept of 'partial' display of slides; * group_ids related to private access is removed; * a computed / searchable field is added to be able to efficiently find and search active members of a channel; This commit is linked to task ID 1937411 and PR #30847.
2018-11-19[MOV] slides: Rename and split files according to their underlying modelsqmo-odoo
Purpose of this merge is to polish a bit this module before turning it into "courses" (see task #1902304 for more details on this) Contains * split python model into separate main files to ease models understanding; * split views into separate main files to ease views finding; * rename files according to guidelines; * merge templates in the same file to have all available at hand; * move assets in their own file in order to remove noise from templates; * Split javascript widgets into their own separate files No functional behavior change should occur with this commit. Only move has been performed. Note that we might lose part of the history as splitting files creates a new history for new files. Task: #1909281 Closes: #28679