Basic content to showcase the CMS delete content
auto_awesome What this module does
AI-generated from the code · Odoo 13.0Demonstration module that shows how website visitors can delete content directly from a public page, using a sample list of records with a Delete button.
This is a demo module built on top of the CMS delete content feature. It creates a simple model called cms.delete.content.example with a single name field, and installs ten sample records (Record 1 to Record 10) so you can try the feature immediately.
A public web page is added at the address /list-delete-content-example. It shows the heading "List of examples" and the instruction to click the delete button to remove an item. Each sample record appears in a list with its name and a red Delete button.
- The page is only available to logged-in users (authentication is required).
- Clicking Delete uses the confirmation mechanism provided by the CMS delete content module, so the visitor is asked to confirm before the record is removed.
- After a record is deleted, the visitor is sent back to the same list page.
The module depends on website and cms_delete_content. It does not add any menu in the Odoo backend; everything happens on the website page. Access rights are fully open (read, write, create and delete) for all users on the sample model, which is normal for a demonstration.
Use this module as a working example to understand how to plug the CMS delete content feature into your own website pages and models.
Depends on
Models and fields (1)
- cms.delete.content.example · new modelname
Text generated by AI (DeepSeek) from reading the Odoo 13.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/website-cms.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.