Российская локализация для v17

act_revise/README.md

@@ -1,93 +0,0 @@
-# act_revise
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.inf-centre.ru/mklab-base/l10n-russia/act_revise.git
-git branch -M v17-dev
-git push -uf origin v17-dev
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.inf-centre.ru/mklab-base/l10n-russia/act_revise/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

base_russian_localization/README.md

@@ -1,93 +0,0 @@
-# Base Russian Localization
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.inf-centre.ru/mklab-base/l10n-russia/base_russian_localization.git
-git branch -M v17-dev
-git push -uf origin v17-dev
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.inf-centre.ru/mklab-base/l10n-russia/base_russian_localization/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

base_russian_localization/models/res_config_settings.py

@@ -1,30 +0,0 @@
-# -*- coding: utf-8 -*-
-# Part of Odoo. See LICENSE file for full copyright and licensing details.
-
-from odoo import _, api, fields, models
-
-class ResConfigSettings(models.TransientModel):
-    _inherit = 'res.config.settings'
-
-    module_act_revise = fields.Boolean(_("Act revise"))
-    module_contract = fields.Boolean(_("Contract"))
-    module_report_xml = fields.Boolean(_("Report_xml"))
-    module_l10n_ru_doc = fields.Boolean(_("Print forms"))
-    module_fehu_base_consent = fields.Boolean(_("Consent"))
-    company_status_rf = fields.Boolean('', compute='_compute_company_status')
-
-    def _compute_company_status(self):
-        company_state = False
-        if self.env.company:
-            company_state = self.env.company.state_id.code == 'RU'
-        self.company_status_rf = company_state
-
-    @api.onchange('company_status_rf')
-    def _onchange_company_status_rf(self):
-        if self.company_status_rf:
-            self.module_act_revise = False
-            self.module_contract = False
-            self.module_report_xml = False
-            self.module_l10n_ru_doc = False
-            self.module_fehu_base_consent = False
-

fehy_base_consent/README.md

@@ -1,93 +0,0 @@
-# fehy_base_consent
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.inf-centre.ru/mklab-base/l10n-russia/fehy_base_consent.git
-git branch -M v17-dev
-git push -uf origin v17-dev
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.inf-centre.ru/mklab-base/l10n-russia/fehy_base_consent/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

fehy_base_consent/security/ir.model.access.csv

@@ -1,2 +0,0 @@
-id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink
-access_fehu_base_consent,fehu.base.consent,model_fehu_base_consent,base.group_user,1,1,1,1

l10n_ru_act_rev/README.md

@@ -0,0 +1,14 @@
+# Российская локализация - Акт сверки
+name: l10n_ru_act_rev
+
+
+## Описание
+Добавление печатной формы акт сверки из контактов, с помощью которой можно легко отслеживать дебеторские и кредиторские проводки с клиентами.
+        
+### Для печати:
+1. Выбираем меню Контакты - карточку конкретного партнера - Действия - "Печать акт сверки";
+2. В визарде выбираем: 
+    2.1. Компанию (для которой нужна сверка с выбранным контактом);
+    2.2. Период сверки; 
+    2.3. Цель (один из режимом: все проведенные проводки или все проводки, включая черновики);
+3. Кнопка "Печать"

l10n_ru_act_rev/__manifest__.py

@@ -1,6 +1,6 @@
 # -*- coding: utf-8 -*-
 {
-    'name': "act_revise",
+    'name': "Российская локализация - Акт сверки",
 
     'summary': """
        Добавление отчета акт сверки""",
@@ -18,14 +18,14 @@
         
     """,
 
-    'author': "Odoo Community Association (OCA), MK Lab",
+    'author': "MK.Lab",
     'website': "https://www.inf-centre.ru/",
 
     'category': 'Uncategorized',
     'version': '0.1',
 
     # any module necessary for this one to work correctly
-    "depends": ["account", "portal", "website", "l10n_ru_doc", 'contract'],
+    "depends": ["account", "portal", "website", 'contacts', "l10n_ru_doc", 'l10n_ru_contract', 'l10n_ru_base'],
     "data": [
         "security/ir.model.access.csv",
         "wizard/general_ledger_wizard_view.xml",

l10n_ru_act_rev/controllers/controllers.py

@@ -28,7 +28,7 @@ class ActRevise(http.Controller):
         }
         wizard_record = request.env['general.ledger.act_revise.wizard'].sudo().create(wizard_data)
 
-        action = request.env.ref('act_revise.action_general_ledger_wizard').read()[0]
+        action = request.env.ref('l10n_ru_act_rev.action_general_ledger_wizard').read()[0]
         action['res_id'] = wizard_record.id
         action['context'] = dict(request.env.context)
         return request.redirect('/web#action=' + str(action['id']) + '&id=' + str(wizard_record.id) + '&view_type=form')
@@ -84,6 +84,6 @@ class ActRevise(http.Controller):
         t = request.env['general.ledger.act_revise.wizard'].sudo().create(wizard_data)
         data = t._prepare_report_general_ledger()
         pdf, _ = request.env['ir.actions.report']._render_qweb_pdf(
-            'act_revise.action_print_report_general_ledger_qweb', res_ids=t.id, data=data)
+            'l10n_ru_act_rev.action_print_report_general_ledger_qweb', res_ids=t.id, data=data)
         pdfhttpheaders = [('Content-Type', 'application/pdf'), ('Content-Length', len(pdf)), ]
         return request.make_response(pdf, headers=pdfhttpheaders)

l10n_ru_act_rev/report/general_ledger.xml

@@ -1,15 +1,15 @@
 <?xml version="1.0" encoding="utf-8" ?>
 <odoo>
-    <template id="act_revise.general_ledger">
+    <template id="l10n_ru_act_rev.general_ledger">
-        <t t-call="act_revise.html_container">
+        <t t-call="l10n_ru_act_rev.html_container">
             <t t-foreach="docs" t-as="o">
-                <t t-call="act_revise.internal_layout">
+                <t t-call="l10n_ru_act_rev.internal_layout">
-                    <t t-call="act_revise.report_general_ledger_base" />
+                    <t t-call="l10n_ru_act_rev.report_general_ledger_base" />
                 </t>
             </t>
         </t>
     </template>
-    <template id="act_revise.report_general_ledger_base">
+    <template id="l10n_ru_act_rev.report_general_ledger_base">
         <t t-set="foreign_currency" t-value="foreign_currency" />
         <t t-set="filter_partner_ids" t-value="filter_partner_ids" />
         <div class="page">
@@ -259,8 +259,8 @@
         <field name="name">Акт сверки</field>
         <field name="model">general.ledger.act_revise.wizard</field>
         <field name="report_type">qweb-pdf</field>
-        <field name="report_name">act_revise.general_ledger</field>
+        <field name="report_name">l10n_ru_act_rev.general_ledger</field>
-        <field name="report_file">act_revise.general_ledger</field>
+        <field name="report_file">l10n_ru_act_rev.general_ledger</field>
         <field name="print_report_name">'Акт сверки - %s' % (object.get_report_filename() or '')</field>
         <field name="binding_model_id" ref="model_general_ledger_act_revise_wizard"/>
     </record>

l10n_ru_act_rev/report/layouts.xml

@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="utf-8" ?>
 <odoo>
-    <template id="act_revise.html_container">
+    <template id="l10n_ru_act_rev.html_container">
         <t t-set="body_classname" t-value="'container'" />
         <t t-call="web.report_layout">
             <t t-out="0" />
         </t>
     </template>
-    <template id="act_revise.internal_layout">
+    <template id="l10n_ru_act_rev.internal_layout">
         <div class="article o_account_financial_reports_page">
             <t t-out="0" />
         </div>

l10n_ru_act_rev/views/report_general_ledger.xml

@@ -2,8 +2,8 @@
 <odoo>
     <template id="report_general_ledger">
         <div class="o_act_revise_page">
-            <t t-call="act_revise.report_buttons" />
+            <t t-call="l10n_ru_act_rev.report_buttons" />
-            <t t-call="act_revise.report_general_ledger_base" />
+            <t t-call="l10n_ru_act_rev.report_general_ledger_base" />
         </div>
     </template>
 </odoo>

l10n_ru_act_rev/wizard/general_ledger_wizard.py

@@ -293,7 +293,7 @@ class GeneralLedgerReportWizard(models.TransientModel):
         self.ensure_one()
         data = self._prepare_report_general_ledger()
         report = self.env["ir.actions.report"].search(
-            [("report_name", "=", "act_revise.general_ledger"), ("report_type", "=", report_type)], limit=1, )
+            [("report_name", "=", "l10n_ru_act_rev.general_ledger"), ("report_type", "=", report_type)], limit=1, )
 
         if self.partner_ids[0].parent_id:
             partner = int(self.partner_ids[0].parent_id.id)

l10n_ru_attorney/README.md

@@ -0,0 +1,21 @@
+# Российская локализация - Доверенность
+name: l10n_ru_attorney
+
+## Описание
+Создание списка доверенностей на получение ТМЦ и их печать.
+
+###Создание доверенности:
+1. Меню Покупки - Доверенности - кнопка "Создать";
+2. На форме указываем: 
+
+    2.1. Контрагент - поставщик;
+
+    2.2. Заказ на закупку;
+
+    2.3. Даты действия доверенности ("дата выдачи" и "действительно по").
+
+  
+###Для печати:
+1. Меню Настройки - Техническое - Отчеты;
+2. Находим в списке l10n_ru_attorney и добавляем в меню "Печать";
+3. Открываем созданную запись доверенности - Действие - "Доверенность".  

l10n_ru_attorney/__manifest__.py

@@ -1,6 +1,6 @@
 # -*- coding: utf-8 -*-
 {
-    'name': "fehu_base_consent",
+    'name': "Российская локализация - Доверенность",
 
     'summary': """
         Печать доверенности на получение ТМЦ
@@ -18,23 +18,23 @@
         
         Для печати:
         1. Меню Настройки - Техническое - Отчеты;
-        2. Находим в списке fehu_base_consent и добавляем в меню "Печать";
+        2. Находим в списке l10n_ru_attorney и добавляем в меню "Печать";
         3. Открываем созданную запись доверенности - Действие - "Доверенность".         
     """,
 
-    'author': "Odoo Community Association (OCA), MK Lab",
+    'author': "MK.Lab",
     'website': "https://www.inf-centre.ru/",
 
     'category': 'Uncategorized',
     'version': '0.1',
 
     # any module necessary for this one to work correctly
-    'depends': ['base','account','sale', 'purchase','hr',],
+    'depends': ['base', 'account', 'sale', 'purchase', 'hr', 'l10n_ru_base'],
 
     # always loaded
     'data': [
         'security/ir.model.access.csv',
-        'views/fehy_base_consent_views.xml',
+        'views/base_consent_views.xml',
         'views/hr_employee_views.xml',
         'views/purchase_order_views.xml',
         'report/consent_report.xml',

l10n_ru_attorney/models/__init__.py

@@ -1,5 +1,5 @@
 # -*- coding: utf-8 -*-
 
-from . import fehu_base_consent
+from . import base_consent
 from . import hr_employee
 from . import purchase_order

l10n_ru_attorney/models/base_consent.py

@@ -4,8 +4,8 @@ from odoo import api, fields, models, _
 from datetime import datetime, timedelta
 
 
-class FehuBaseConsent(models.Model):
+class BaseConsent(models.Model):
-    _name = 'fehu.base.consent'
+    _name = 'base.consent'
     _inherit = ['mail.thread', 'utm.mixin']
     _description = 'Consent'
     _order = 'date_from desc'
@@ -18,12 +18,12 @@ class FehuBaseConsent(models.Model):
     purchaseorder_id = fields.Many2one('purchase.order', _('Заказ на закупку'), domain="[('partner_id','=',partner_id)]",
                                        required=1)
     company_id = fields.Many2one('res.company', string=_('Компания'),
-                                 default=lambda self: self.env['res.company']._company_default_get('fehu.consent'),
+                                 default=lambda self: self.env['res.company']._company_default_get('base.consent'),
                                  required=1)
 
     @api.model
     def create(self, val):
-        name = self.env['ir.sequence'].next_by_code('fehu.base.consent')
+        name = self.env['ir.sequence'].next_by_code('base.consent')
         if name:
             if 'name' in val:
                 if val['name'] == False:
@@ -31,7 +31,7 @@ class FehuBaseConsent(models.Model):
                         'name': name,
                     })
 
-        result = super(FehuBaseConsent, self).create(val)
+        result = super(BaseConsent, self).create(val)
         return result
 
     @api.onchange('purchaseorder_id')

l10n_ru_attorney/models/purchase_order.py

@@ -6,4 +6,4 @@ from odoo import fields, models, _
 class PurchaseOrder(models.Model):
     _inherit = 'purchase.order'
 
-    consent_id = fields.Many2one('fehu.base.consent', string=_('Доверенность'))
+    consent_id = fields.Many2one('base.consent', string=_('Доверенность'))

l10n_ru_attorney/report/consent_report.xml

@@ -4,18 +4,18 @@
         <report
             string="Доверенность"
             id="action_report_consent"
-            model="fehu.base.consent"
+            model="base.consent"
-            report_type="qweb-pdf"
+            report_type="qweb-html"
-            name="fehu_base_consent.report_consent"
+            name="l10n_ru_attorney.report_consent"
-            file="fehu_base_consent.report_consent"
+            file="l10n_ru_attorney.report_consent"
         />
 
-        <record model="ir.actions.report" id="fehu_base_consent.action_report_consent">
+        <record model="ir.actions.report" id="l10n_ru_attorney.action_report_consent">
             <field name="name">Доверенность</field>
-            <field name="model">fehu.base.consent</field>
+            <field name="model">base.consent</field>
             <field name="print_report_name">(u'Доверенность - %s.pdf' % (object.name))</field>
-            <field name="report_type">qweb-pdf</field>
+            <field name="report_type">qweb-html</field>
-            <field name="report_name">fehu_base_consent.report_consent</field>
+            <field name="report_name">l10n_ru_attorney.report_consent</field>
         </record>
 
         <record id="paperformat_a4new" model="report.paperformat">
@@ -34,7 +34,7 @@
             <field name="dpi">90</field>
         </record>
 
-        <template id="fehu_base_consent.report_consent">
+        <template id="l10n_ru_attorney.report_consent">
             <t t-call="web.html_container">
                 <t t-foreach="docs" t-as="o">
                     <div class="page">

l10n_ru_attorney/security/ir.model.access.csv

@@ -0,0 +1,2 @@
+id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink
+access_base_consent,base.consent,model_base_consent,base.group_user,1,1,1,1

l10n_ru_attorney/views/base_consent_views.xml

@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="utf-8"?>
 <odoo>
     <data>
-        <record id="fehu.base.consent.tree" model="ir.ui.view">
+        <record id="base_consent_tree" model="ir.ui.view">
             <field name="name">Consents</field>
-            <field name="model">fehu_base_consent</field>
+            <field name="model">base.consent</field>
             <field name="arch" type="xml">
                 <tree>
                     <field name="name"/>
@@ -15,9 +15,9 @@
             </field>
         </record>
 
-        <record id="fehu.base.consent.form" model="ir.ui.view">
+        <record id="base_consent_form" model="ir.ui.view">
             <field name="name">consent.form</field>
-            <field name="model">fehu.base.consent</field>
+            <field name="model">base.consent</field>
             <field name="arch" type="xml">
                 <form>
                     <header></header>
@@ -44,18 +44,18 @@
             </field>
         </record>
 
-        <record id="fehu_base_consent.action_consent" model="ir.actions.act_window">
+        <record id="l10n_ru_attorney.action_consent" model="ir.actions.act_window">
             <field name="name">Доверенности</field>
-            <field name="res_model">fehu.base.consent</field>
+            <field name="res_model">base.consent</field>
             <field name="view_mode">tree,form</field>
         </record>
 
-        <menuitem id="fehu_base_consent.menu_1" name="Consents" parent="purchase.menu_purchase_root"
+        <menuitem id="l10n_ru_attorney.menu_1" name="Consents" parent="purchase.menu_purchase_root"
-                  action="fehu_base_consent.action_consent"/>
+                  action="l10n_ru_attorney.action_consent"/>
 
         <record id="seq_consent" model="ir.sequence">
             <field name="name">Consents</field>
-            <field name="code">fehu.consent</field>
+            <field name="code">base.consent</field>
             <field name="prefix">CON</field>
             <field name="padding">5</field>
             <field name="company_id" eval="False"/>

l10n_ru_base/README.md

@@ -0,0 +1,16 @@
+# Российская локализация - Базовый
+name: l10n_ru_base
+
+## Описание
+Российская локализация: основные отчеты и печатные формы. Это базовый модуль для работы с модулями локализации.
+
+###Для включения модулей:
+1. Меню Настройки - в боковом меню "Российская локализация";
+2. Выбирается нужный блок для подключения дополнительных возможностей по локализации.
+
+###Перечень модулей локализации:
+1. Российская локализация - Акт сверки (l10n_ru_act_rev)
+2. Российская локализация - Доверенность (l10n_ru_attorney)
+3. Российская локализация - Договоры (l10n_ru_contract)
+4. Российская локализация - Документы (l10n_ru_doc)
+5. Российская локализация - УПД в xml-формате (l10n_ru_upd_xml)

l10n_ru_base/__manifest__.py

@@ -1,6 +1,6 @@
 # -*- coding: utf-8 -*-
 {
-    'name': "base_russian_localization",
+    'name': "Российская локализация - Базовый>",
     'summary': """
        Российская локализация: основные отчеты и печатные формы.
     """,
@@ -13,7 +13,7 @@
         2. Выбирается нужный блок.
     """,
 
-    'author': "Odoo Community Association (OCA), MK Lab",
+    'author': "MK.Lab",
     'website': "https://www.inf-centre.ru/",
 
     'version': '17.0.1.0.0',

l10n_ru_base/models/res_config_settings.py

@@ -0,0 +1,41 @@
+# -*- coding: utf-8 -*-
+# Part of Odoo. See LICENSE file for full copyright and licensing details.
+
+from odoo import _, api, fields, models
+from odoo.exceptions import UserError
+
+_FIELDS_MODUL = [
+    'module_l10n_ru_act_rev',
+    'module_l10n_ru_contract',
+    'module_l10n_ru_upd_xml',
+    'module_l10n_ru_doc',
+    'module_l10n_ru_attorney'
+]
+
+class ResConfigSettings(models.TransientModel):
+    _inherit = 'res.config.settings'
+
+    module_l10n_ru_act_rev = fields.Boolean(_("Act revise"))
+    module_l10n_ru_contract = fields.Boolean(_("Contract"))
+    module_l10n_ru_upd_xml = fields.Boolean(_("Report_xml"))
+    module_l10n_ru_doc = fields.Boolean(_("Print forms"))
+    module_l10n_ru_attorney = fields.Boolean(_("Consent"))
+
+    @api.model
+    def write(self, values):
+        company = self.env.company
+        if company.country_id.code != 'RU':
+            raise UserError("Признак Российской компании не обнаружен!")
+        if _FIELDS_MODUL:
+            missing_modules = set()
+            for field in _FIELDS_MODUL:
+                if self.mapped(field)[0]:
+                    module_name = field[7:]
+                    module_installed = self.env['ir.module.module'].search([('name', '=', module_name)], limit=1)
+                    if not module_installed:
+                        missing_modules.add(module_name)
+            if missing_modules:
+                message = "Обратитесь в тех.поддержку для получения лицензии для следующих модулей:\n" + \
+                      "\n".join(missing_modules)
+                raise UserError(message)
+        return super(ResConfigSettings, self).write(values)

l10n_ru_base/views/res_config_settings_views.xml

@@ -8,17 +8,22 @@
         <field name="inherit_id" ref="base.res_config_settings_view_form"/>
         <field name="arch" type="xml">
             <xpath expr="//form" position="inside">
-                <app data-string="Russian Localization" string="Russian Localization" name="base_russian_localization" img="">
+                <app data-string="Russian Localization" string="Russian Localization" name="base_russian_localization" img="l10n_ru_base/static/description/icon.png">
                     <block title="Act revise" name="act_revise_setting_container">
-                        <setting id="act_revise" string="Act revise" help="Report act revise"><field name="module_act_revise"/></setting>
+                        <setting id="act_revise" string="Act revise" help="Report act revise">
+                            <field name="module_l10n_ru_act_rev"/>
+                        </setting>
                     </block>
                     <block title="Contracts" name="contract_setting_container">
-                        <setting id="contract" string="Contracts" help="Report contract"><field name="module_contract"/></setting>
+                        <setting id="contract" string="Contracts" help="Report contract">
+                            <field name="module_l10n_ru_contract"/>
+                        </setting>
                     </block>
                     <block title="UPD xml" name="upd_xml_setting_container">
-                         <setting id="report_xml" string="UPD xml" help="Report report_xml"><field name="module_report_xml"/></setting>
+                        <setting id="report_xml" string="UPD xml" help="Report report_xml">
+                            <field name="module_l10n_ru_upd_xml"/>
+                        </setting>
                     </block>
-
                     <block title="Print forms" name="print_forms_setting_container">
                         <setting id="print_forms" string="Print forms" help="print_forms">
                             <field name="module_l10n_ru_doc"/>
@@ -26,7 +31,7 @@
                     </block>
                     <block title="Consent" name="powers_attorney_setting_container">
                         <setting id="powers_attorney" string="Consent" help="Powers of attorney">
-                            <field name="module_fehu_base_consent"/>
+                            <field name="module_l10n_ru_attorney"/>
                         </setting>
                     </block>
                 </app>