19.0 tutorials karad#1364
Open
karad-odoo wants to merge 21 commits into
Open
Conversation
Some imports are missing in the manifest causing some warnings and the css doesn't load properly. Fix was fixed in the master branch, backporting it in 19.0 for the onboarding classes that always happen in the lastest stable. task-none Part-of: odoo#1037 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
`json` routes were deprecated to `jsonrpc` in 19.0, let's get rid of the warning to avoid confusion for the newdoos. task-none closes odoo#1037 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Set up the core module architecture to allow the Odoo server registry to recognize and install the 'estate' module for real estate management.
Specify missing author and open-source license attributes in the manifest file to prevent server warnings during module registration.
Remove unused default configuration keys from the manifest file to keep overall module metadata minimal and clean.
Define the core estate.property business object in PostgreSQL to enable storing real estate listing attributes like prices, bedrooms, living area, and availability.
Format Python files to adhere strictly to Odoo's official code style standards, ensuring continuous integration tests pass cleanly.
Configure security access control rules (ir.model.access.csv) to allow standard internal users to access and manage real estate property records without permission errors.
Create top-level menus and actions so users can open properties in the web interface. Set default availability dates and protect selling prices from unauthorized manual editing.
Add local IDE configuration folders (.idea/) to .gitignore to keep local development cache out of shared repository history.
Define a tabular list view so real estate agents can browse and compare multiple property records from a single overview screen.
Correct XML view field names to match Python model field definitions, fixing ParseErrors that prevented the module from loading.
Build a detailed form view with title headers, grouped pricing fields, and notebook tabs to structure property data entry for users.
Define search criteria on the property search view so users can search listings by typing titles, postcodes, or price ranges directly in the search interface.
Add an Available quick filter button and a 'Group By Postcode' option to help agents filter out sold listings and organize properties geographically.
Disable record duplication on price and availability fields during copy operations to enforce clean data when creating new property listings.
Increment manifest version number to force Odoo to reload the module and synchronize recent database schema updates on service restart.
Reorder model fields to position state attributes cleanly Remove redundant label overrides so search fields inherit standard model names and Ensure status tracking fields appear on list and form views to monitor property state progression.
bit-odoo
reviewed
Jul 21, 2026
bit-odoo
left a comment
There was a problem hiding this comment.
Hello @karad-odoo
Good Start!
Can you please improve all your commit titles and message as well?
And you have left many unneccary empty lines.
Also, improve the PR title and description.
Thanks
| @@ -0,0 +1,2 @@ | |||
| id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink | |||
| access_estate_property,access_estate_property,model_estate_property,base.group_user,1,1,1,1 No newline at end of file | |||
There was a problem hiding this comment.
Should be one empty line at the end of the file.
Comment on lines
+8
to
+10
| <menuitem id="estate_menu_root" name="Real Estate"/> | ||
| <menuitem id="estate_first_level_menu" name="Advertisements" parent="estate_menu_root"/> | ||
| <menuitem id="estate_property_menu_action" name="Properties" parent="estate_first_level_menu" |
There was a problem hiding this comment.
You can create a separate file for the menu.
| <field name="name">estate.property.list</field> | ||
| <field name="model">estate.property</field> | ||
| <field name="arch" type="xml"> | ||
|
|
| <field name="date_availability" string="Available From"/> | ||
| <field name="state" string="State"/> | ||
| </list> | ||
|
|
| <field name="name">estate.property.form</field> | ||
| <field name="model">estate.property</field> | ||
| <field name="arch" type="xml"> | ||
|
|
| </group> | ||
| </page> | ||
| </notebook> | ||
|
|
|
|
||
| </sheet> | ||
| </form> | ||
|
|
| <field name="selling_price"/> | ||
| </group> | ||
| </group> | ||
|
|
| </field> | ||
| </record> | ||
|
|
||
| </odoo> No newline at end of file |
There was a problem hiding this comment.
Should be one empty line at the end of the file.
Extract menu items out of estate_property_views.xml and move them into views/estate_menus.xml. This maintains architectural separation between view layouts and navigation controls, keeping the module organized as it grows Update manifest load order to process views before menus.
karad-odoo
force-pushed
the
19.0-tutorials-karad
branch
from
July 21, 2026 09:13
8208a5f to
f2a88fc
Compare
karad-odoo
marked this pull request as ready for review
July 21, 2026 09:26
karad-odoo
force-pushed
the
19.0-tutorials-karad
branch
3 times, most recently
from
July 24, 2026 12:52
bc467de to
09f5cf4
Compare
Created the estate.property.type model to support property categorization, such as residential, commercial, or land. Having a dedicated model allows us to link each property to a single type via a many2one relationship, making it much easier to organize, filter, and search listings based on business needs.
karad-odoo
force-pushed
the
19.0-tutorials-karad
branch
from
July 24, 2026 12:57
09f5cf4 to
d69a6a7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

[ADD] estate: property model, security rules, and UI views
Initial setup for the
estatetutorial module.estate.propertymodel with fields and defaultsir.model.access.csv)