Skip to Content

Contributors

  • E-Mail Tracking V16
    Hello,
    are there any plans to upgrade this app: https://apps.odoo.com/apps/modules/15.0/mail_tracking/ to V16?
    --

    Herzliche Grüße / Kind regards
    Tim Vollmer
    Software Consultant







    by Tim Vollmer - 10:36 - 21 Sep 2023
  • Re: multi company issue


    On Wed, Sep 20, 2023 at 12:04 PM Samir Hassan <samir2010ssf@gmail.com> wrote:
    Dear 
    i have that issue for multi company 
    image.png
    i solve this issue with add user group under record rule

    image.png
    when i add user group the user can issues the invoice but user now see all Customers for both companies 


    --
    Best Regards
    Samir Mahmoud
    00201062648111




    --
    Best Regards
    Samir Mahmoud
    00201062648111



    by Samir Mahmoud Hassan - 01:40 - 20 Sep 2023
  • Re: Branches for v17.0
    On 19/09/23 18:56, Luis Ernesto Torres [Vauxoo] wrote:
    
    > I have a question, We are working for a customer who wants to be in v17 
    
    > in October when Odoo 17 is done.
    
    Hi Luis,
    
    Don't forget that Odoo 17.0 is going to be released only in November, 
    not October (the Odoo Experiences are a bit later this year).
    
    Best,
    
    Martin
    

    by Martin Trigaux - 01:30 - 20 Sep 2023
  • Re: multi company issue
    They are on the archive: https://odoo-community.org/groups/contributors-15/contributors-878617

    But sure, it would be nice to fix this.

    Francesco

    Il giorno mer 20 set 2023 alle ore 12:42 Fernando La Chica <notifications@odoo-community.org> ha scritto:
    Images are not visible

    El mié, 20 sept 2023, 11:07, Samir Hassan <notifications@odoo-community.org> escribió:
    Dear 
    i have that issue for multi company 
    image.png
    i solve this issue with add user group under record rule

    image.png
    when i add user group the user can issues the invoice but user now see all Customers for both companies 


    --
    Best Regards
    Samir Mahmoud
    00201062648111


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

    by Francesco Foresti - 12:45 - 20 Sep 2023
  • Re: multi company issue
    Images are not visible

    El mié, 20 sept 2023, 11:07, Samir Hassan <notifications@odoo-community.org> escribió:
    Dear 
    i have that issue for multi company 
    image.png
    i solve this issue with add user group under record rule

    image.png
    when i add user group the user can issues the invoice but user now see all Customers for both companies 


    --
    Best Regards
    Samir Mahmoud
    00201062648111


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Fernando La Chica - 12:41 - 20 Sep 2023
  • multi company issue
    Dear 
    i have that issue for multi company 
    image.png
    i solve this issue with add user group under record rule

    image.png
    when i add user group the user can issues the invoice but user now see all Customers for both companies 


    --
    Best Regards
    Samir Mahmoud
    00201062648111



    by Samir Mahmoud Hassan - 11:06 - 20 Sep 2023
  • Re: OCA Functional Group - Project Modules Documentation
    El mar, 19-09-2023 a las 10:48 +0000, Pedro M. Baeza escribió:
    As we talked previously, do you already know GitHub's image retention policy for being sure they don't expire?



    by Jairo Llopis - 08:56 - 20 Sep 2023
  • Re: Branches for v17.0
    > Is it possible to create the OCA branches for v17 at this moment?  Or only
    
    > when the Odoo branch for v17 is ready?
    
    for what I assume you want to do (just now already develop stuff for v17), you 
    don't need OCA v17 branches anyways. Just start doing your things in an empty 
    branch using the usual migration steps (one branch per module), and you'll be 
    able to easily cherry-pick this to the upcoming OCA branches and then PR them 
    as your migration of whatever module(s) it's about.
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    by Holger Brunn - 10:10 - 19 Sep 2023
  • Re: Branches for v17.0
    > Is it possible to create the OCA branches for v17 at this moment?

    No, that is not possible. CI wouldn't work without the 17.0 branches from Odoo.

    For reference here is the checklist we had to prepare our tooling for v16: https://github.com/OCA/maintainer-tools/issues/537

    Best regards,

    -Stéphane

    On Tue, Sep 19, 2023 at 6:56 PM Luis Ernesto Torres [Vauxoo] <notifications@odoo-community.org> wrote:
    Hello,

    I have a question, We are working for a customer who wants to be in v17 in October when Odoo 17 is done.

    Is it possible to create the OCA branches for v17 at this moment?  Or only when the Odoo branch for v17 is ready?

    Regards

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Stéphane Bidoul - 09:59 - 19 Sep 2023
  • Branches for v17.0
    Hello,

    I have a question, We are working for a customer who wants to be in v17 in October when Odoo 17 is done.

    Is it possible to create the OCA branches for v17 at this moment?  Or only when the Odoo branch for v17 is ready?

    Regards

    by Luis Ernesto Torres - 06:55 - 19 Sep 2023
  • Re: OCA Functional Group - Project Modules Documentation
    Thank you for all the work done.

    As we talked previously, do you already know GitHub's image retention policy for being sure they don't expire?

    Regards.

    by Pedro M. Baeza - 12:46 - 19 Sep 2023
  • Re: OCA Functional Group - Project Modules Documentation
    Hello Yann,

    On Mon, Sep 18, 2023 at 4:43 PM Yann Papouin <notifications@odoo-community.org> wrote:
    Does the oca-gen-addon-readme tool will fetch these files, copying them into the static folder and re-edit the MD to make relative links ?

    That is not planned at this point. It could be interesting, to ensure that all source images are in the repository.

    But note that currently, the readme generator currently replaces relative image links by github urls, so the README renders correctly in Odoo and on PyPI.

    Best regards,

    -Stéphane


    by Stéphane Bidoul - 12:37 - 19 Sep 2023
  • multi company issue
    Dear 
    i have that issue for multi company 
    image.png
    i solve this issue with add user group under record rule

    image.png
    when i add user group the user can issues the invoice but user now see all Customers for both companies 

    --
    Best Regards
    Samir Mahmoud
    00201062648111



    by Samir Mahmoud Hassan - 10:11 - 19 Sep 2023
  • Re: tool: Odoo Modules Migration
    Take a look at this tool


    At first I thought it was the same tool. I understand that it is out of the scope of your tool but I think it can be useful for your final objective which is to migrate a large number of modules.

    El lun, 18 sept 2023, 9:37, Jan Suhr | Nitrokey <notifications@odoo-community.org> escribió:
    Hi!
    I wrote a simple tool which helps me keeping an overview of module 
    upgrades during ongoing upgrade projects, especially for a large amount 
    of modules. I hope someone finds it useful.
    
    https://github.com/Nitrokey/odoo-modules-migration
    
    Best regards
    Jan
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Fernando La Chica - 11:06 - 18 Sep 2023
  • Re: tool: Odoo Modules Migration
    Hi Daniel!
    The tool is pretty simple so all documentation is in the README.
    
    Best regards
    Jan
    
    Am 18.09.23 um 19:53 schrieb DANIEL CARRION HUACANI:
    
    > Hello Jan:
    
    > 
    
    > I think it's great. This is the first time I read about OMM, could you 
    
    > recommend additional sources or documentation so I can study it
    
    > 
    
    > Atte:
    
    > Daniel
    
    > 
    
    > El lun, 18 sept 2023 a las 2:37, Jan Suhr | Nitrokey 
    
    > (<notifications@odoo-community.org 
    
    > <mailto:notifications@odoo-community.org>>) escribió:
    
    > 
    
    >     Hi!
    
    >     I wrote a simple tool which helps me keeping an overview of module
    
    >     upgrades during ongoing upgrade projects, especially for a large amount
    
    >     of modules. I hope someone finds it useful.
    
    > 
    
    >     https://github.com/Nitrokey/odoo-modules-migration  <https://github.com/Nitrokey/odoo-modules-migration>
    
    > 
    
    >     Best regards
    
    >     Jan
    
    > 
    
    >     _______________________________________________
    
    >     Mailing-List: https://odoo-community.org/groups/contributors-15
    
    >     <https://odoo-community.org/groups/contributors-15>
    
    >     Post to: mailto:contributors@odoo-community.org
    
    >     <mailto:contributors@odoo-community.org>
    
    >     Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    >     <https://odoo-community.org/groups?unsubscribe>
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    > 
    

    by Jan Suhr - 10:27 - 18 Sep 2023
  • Re: tool: Odoo Modules Migration
    Hello Jan:

    I think it's great. This is the first time I read about OMM, could you recommend additional sources or documentation so I can study it

    Atte:
    Daniel

    El lun, 18 sept 2023 a las 2:37, Jan Suhr | Nitrokey (<notifications@odoo-community.org>) escribió:
    Hi!
    I wrote a simple tool which helps me keeping an overview of module 
    upgrades during ongoing upgrade projects, especially for a large amount 
    of modules. I hope someone finds it useful.
    
    https://github.com/Nitrokey/odoo-modules-migration
    
    Best regards
    Jan
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by DANIEL CARRION - 07:51 - 18 Sep 2023
  • Re: OCA Functional Group - Project Modules Documentation
    Hello,

    Ok, so there will be a syntax change but it looks like that the new thing is the need/possibility to use GitHub to edit these files ?
    Because Markdown is not magic and image pasting or drag&drop just upload it to Github.
    Does the oca-gen-addon-readme tool will fetch these files, copying them into the static folder and re-edit the MD to make relative links ?

    Yann.


    by Yann Papouin - 04:41 - 18 Sep 2023
  • OCA Functional Group - Project Modules Documentation

    After the last OCA Days in 2022, a group of functional people from different countries and companies decided to work together to improve functional contributions in OCA. 


    Documentation of OCA modules has been identified as one of the main areas where functionals’ expertise can be useful. 


    Our primary goals with this project are:

    • to make it easier for everyone to understand what is the purpose of a module and how to use it ;

    • to provide guidelines on how to write good and complete documentation ;

    • to improve access to editing and contribution of module’s documentation for functional people (eg: adding screenshots).


    What are the changes?

    • Implementing Markdown in place of RST for Read Me

      • A great module documentation has screenshots so the reader can understand better how to use the module. The problem is that it is difficult for a functional person to add screenshots into an RST file.  You must upload the image in a folder (and you have to know which one ;) ), then you need to know how to put the link to the image, and if you make a mistake, the image doesn't show…

      • Markdown files are supported by GitHub and this format allows you to insert a screenshot easily by Drag & Drop.

      • Markdown provides a simple and unified layout (as RST do) so we don’t lose this advantage.

      • GitHub provides a Markdown editor tool so you don’t even have to learn the syntax (but, we tell you, it is very easy to learn ;) ) 

    • Providing guidelines for documentation

      • We are still working on the Guidelines but we will have a first version ready for the OCA days!

    • Enhancing Readme template

      • Adding some information into the description of the fragments so anybody (functional or developer) can understand the usage of each fragment.

      • Adding a new CONTEXT fragment. This new fragment can then be used to explain the why (context, use cases) of the module.


    What are the impacts of those changes?

    • The Read Me’s template files have been converted to Markdown.

    • We will be converting, in the next weeks, all Read Me files to Markdown for all repositories in branch “16.0”. 

    • Read Me in RST will still be accepted but we strongly recommend to use Markdown for all the reasons enumerated previously.

    • For the branch “17.0”,  only Markdown files will be accepted.


    How to proceed in case of migration of a module?

    • You can convert existing readme fragments from RST to Markdown for a whole repo using a command such as:

    $ oca-gen-addon-readme --convert-fragments-to-markdown --org-name OCA --repo-name rest-framework --branch 16.0 --addons-dir . --gen-html


    • You can also convert an individual addon with --addon-dir (instead of --addons-dir) with a command like this:

    $ oca-gen-addon-readme --convert-fragments-to-markdown --org-name OCA --repo-name purchase-workflow --branch 16.0 --addon-dir purchase_request --gen-html



    How to proceed in case of pushing a new module into OCA?

    • Using the templates (which are now in Markdown)

    • And we recommend you follow the Guidelines!

      • We will be communicating about these Guidelines when they are ready!


    We hope you enjoy these improvements!!!


    The OCA Functional Group, Documentation Team

    Julie LeBrun, Numigi Solutions

    Francesco Foresti, ooops

    Lara Freeke, Therp

    Benedito Monteiro



    by Julie LeBrun - 04:12 - 18 Sep 2023
  • tool: Odoo Modules Migration
    Hi!
    I wrote a simple tool which helps me keeping an overview of module 
    upgrades during ongoing upgrade projects, especially for a large amount 
    of modules. I hope someone finds it useful.
    
    https://github.com/Nitrokey/odoo-modules-migration
    
    Best regards
    Jan
    

    by Jan Suhr - 09:35 - 18 Sep 2023
  • Re: Auto unsubscribe
    Probably some odoo flaw. Just ignore it.

    On Sat, 16 Sept 2023, 1:53 am Radovan Skolnik, <notifications@odoo-community.org> wrote:
    +1
    
    On piatok 15. septembra 2023 15:17:16 CEST Roussel, Denis wrote:
    
    
    > Hi,
    
    
    > 
    
    
    > 
    
    
    > Is there something done on OCA side that has triggered an unsubscribe action
    
    
    > to this mailing list as I've just received a 'Confirm unsubscription to
    
    
    > Contributors' email?
    
    
    > 
    
    
    > 
    
    
    > Thanks to the Board for the answer (as some colleagues received it too).
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > --
    
    
    > 
    
    
    > 
    
    
    > Denis Roussel
    
    
    > Software Engineer
    
    
    > T    : +32 2 888 31 49
    
    
    > M : +32 472 22 00 57
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    
    
    > 
    
    
    > Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    
    
    > Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    
    
    > 
    
    
    > 
    
    
    > _______________________________________________
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Graeme Gellatly - 06:51 - 16 Sep 2023