TechnoLibre/bemade-addons
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

mig to 18.0 for bemade's modules

Browse source
This commit is contained in:
Marc Durepos 2024-12-05 16:56:28 -05:00
parent 56b755039d
commit f34860bfac
7 changed files with 48 additions and 42 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
bemade_odoo_partner_scrapper/__manifest__.py
View file

@ -1,7 +1,7 @@
# -*- coding: utf-8 -*-
{
'name': 'Bemade Odoo Partner Scrapper',
'version': '17.0.0.0.0',
'version': '18.0.0.0.0',
'category': 'Administration',
'summary': 'Module for scraping partners from odoo.com.',
'description': """

72
bemade_odoo_partner_scrapper/data/res_partner_relation_type.xml
View file

@ -1,37 +1,43 @@
<?xml version="1.0" encoding="UTF-8" ?>
<odoo>
<!-- Added partner categories and partners to this file, because it
turned out to be a bad idea to rely on demo data in base module,
that can change from release to release. Only dependency on
countries remain. They are less likely to change/disappear.
-->
<!-- Partner relation types -->
<record id="rel_type_odoo_partner" model="res.partner.relation.type">
<field name="name">Is Odoo Partner Of</field>
<field name="name_inverse">Is Odoo Client Of</field>
<!-- Commented two lines below due to data integrity issue when migrating to 17.0. Are they really needed? -->
<!-- <field name="contact_type_left">c</field>-->
<!-- <field name="contact_type_right">c</field>-->
</record>
<data noupdate="1">
<!-- Added partner categories and partners to this file, because it
turned out to be a bad idea to rely on demo data in base module,
that can change from release to release. Only dependency on
countries remain. They are less likely to change/disappear.
-->
<!-- Partner relation types -->
<record id="rel_type_odoo_partner" model="res.partner.relation.type">
<field name="name">Is Odoo Partner Of</field>
<field name="name_inverse">Is Odoo Client Of</field>
<!-- Commented two lines below due to data integrity issue when migrating to 17.0. Are they really needed? -->
<!-- <field name="contact_type_left">c</field>-->
<!-- <field name="contact_type_right">c</field>-->
</record>
<!-- Categories -->
<record id="res_partner_category_odoo_partner" model="res.partner.category">
<field name="name">Odoo Partner</field>
</record>
<record id="res_partner_category_odoo_partner_learning" model="res.partner.category">
<field name="name">Learning Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner" />
</record>
<record id="res_partner_category_odoo_partner_ready" model="res.partner.category">
<field name="name">Ready Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner" />
</record>
<record id="res_partner_category_odoo_partner_silver" model="res.partner.category">
<field name="name">Silver Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner" />
</record>
<record id="res_partner_category_odoo_partner_gold" model="res.partner.category">
<field name="name">Gold Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner" />
</record>
<!-- Categories -->
<record id="res_partner_category_odoo_partner" model="res.partner.category">
<field name="name">Odoo Partner</field>
</record>
<record id="res_partner_category_odoo_partner_learning"
model="res.partner.category">
<field name="name">Learning Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner"/>
</record>
<record id="res_partner_category_odoo_partner_ready"
model="res.partner.category">
<field name="name">Ready Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner"/>
</record>
<record id="res_partner_category_odoo_partner_silver"
model="res.partner.category">
<field name="name">Silver Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner"/>
</record>
<record id="res_partner_category_odoo_partner_gold"
model="res.partner.category">
<field name="name">Gold Partner</field>
<field name="parent_id" ref="res_partner_category_odoo_partner"/>
</record>
</data>
</odoo>

4
bemade_odoo_partner_scrapper/views/res_partner_views.xml
View file

@ -18,14 +18,14 @@
<group name="container_row_2" position="after">
<group name="container_row_3">
<field name="relation_all_ids">
<tree>
<list>
<field name="other_partner_id" required="True" options="{'no_create': True}"
string="Customer" domain="[['relation_all_ids.type_selection_id.id', '=', 1]]"/>
<field name="date_start"/>
<field name="date_end"/>
<field name="active" invisible="1"/>
<field name="active" invisible="1"/>
</tree>
</list>
</field>
</group>
</group>

2
bemade_payslip_done_as_not_paid/__manifest__.py
View file

@ -18,7 +18,7 @@
#
{
'name': 'Payslip Done as To Pay',
'version': '17.0.1.0.0',
'version': '18.0.1.0.0',
'summary': 'Payslips in "Done" state appear as "To Pay"',
'category': 'Human Resources/Payroll',
'author': 'Bemade Inc.',

2
bemade_pwa_config/__manifest__.py
View file

@ -1,6 +1,6 @@
{
'name': 'Bemade PWA Configuration',
'version': '1.0',
'version': '18.0.0.1.0',
'summary': 'Manage PWA settings including dynamic app icons',
'description': """
Manage Progressive Web App Settings

2
caldav_sync/__manifest__.py
View file

@ -8,7 +8,7 @@
{
"name": "CalDAV Synchronization",
"version": "17.0.0.6.0",
"version": "18.0.0.6.0",
"license": "LGPL-3",
"category": "Productivity",
"summary": "Synchronize Odoo Calendar Events with CalDAV Servers",

6
website_geoip_extended/__manifest__.py
View file

@ -1,11 +1,11 @@
{
'name': "Bemade Custom Module",
'version': "17.0.0.1.0",
'version': "18.0.0.1.0",
'summary': "Module personnalisé pour Bemade Inc",
'sequence': 10,
'description': """
Ce module personnalisé est développé pour étendre les fonctionnalités de base d'Odoo.
Ce module personnalisé est développé pour étendre les fonctionnalités de base d'Odoo
Fonctionnalités:
- Ajout de champs supplémentaires pour collecter plus d'informations sur le visiteur
- Logger les informations de la requête