See, I've made a search for the module l10n_es_toponyms and these are the results:

As you can see, the most important result appears last. This is something that keeps bugging me around. It seems like the search also matches when a module depends on the one you're searching on any version, which could help or could just clutter the results without need when you know what you're searching. When there are several pages of results, it's fastidious.

For example, the module l10n_es_location_nuts appears there because in v8 it depended on l10n_es_toponyms, but it's unrelated in higher versions. Also that relation is not clear when you see the module page.

The situation for l10n_es_partner is pretty similar.

So, my suggestion is that we should reorder modules like this:

1. Module that matches exactly the query (l10n_es_toponyms).
2. Modules that match partially the query (l10n_es_toponyms_region).
3. Modules where some dependency matches the query.

The 3rd one could even be a checkbox "search dependencies", which could be enabled or disabled by default. It could add a GET param to the URL, so bookmark users can just choose to (dis/en)able it directly.

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-13.0

Modules to migrate

• apps_download - By @Tardo - #75
• apps_product_creator - By @CarlosRoca13 - #74
• website_apps_store - By @Tardo - #76

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Example here: https://odoo-community.org/shop/product/mis-builder-1636?search=mis+builder

The acsone icon should not be there. It is not obvious where it comes from, as it is used nowhere in that module in github.

This is how account_banking_payment_export looks for version 8.0:

For lower versions, it looks good.

Link: https://odoo-community.org/shop/product/account-banking-payments-export-infrastructure-121

I got this when trying to download from https://odoo-community.org/shop/product/mis-builder-budget-1639

Traceback (most recent call last):
  File "/home/openerp/instance/odoo-community-prod/src/odoo/odoo/addons/base/models/ir_http.py", line 234, in _dispatch
    result = request.dispatch()
  File "/home/openerp/instance/odoo-community-prod/src/odoo/odoo/http.py", line 809, in dispatch
    r = self._call_function(**self.params)
  File "/home/openerp/instance/odoo-community-prod/src/odoo/odoo/http.py", line 350, in _call_function
    return checked_call(self.db, *args, **kwargs)
  File "/home/openerp/instance/odoo-community-prod/src/odoo/odoo/service/model.py", line 94, in wrapper
    return f(dbname, *args, **kwargs)
  File "/home/openerp/instance/odoo-community-prod/src/odoo/odoo/http.py", line 339, in checked_call
    result = self.endpoint(*a, **kw)
  File "/home/openerp/instance/odoo-community-prod/src/odoo/odoo/http.py", line 915, in __call__
    return self.method(*args, **kw)
  File "/home/openerp/instance/odoo-community-prod/src/odoo/odoo/http.py", line 515, in response_wrap
    response = f(*args, **kw)
  File "/home/openerp/instance/odoo-community-prod/src/apps-store/website_apps_store/controllers/main.py", line 236, in download_product_zip
    disposition = 'attachment; filename="%s"' % attachment.datas_fname
AttributeError: 'ir.attachment' object has no attribute 'datas_fname'

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-17.0

Modules to migrate

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Although the current code is performing a search on all the relevant fields, including technical name, name and descriptions, my experience in the App store is that it is not working as expected.

Specific example:

• there is a auth_topt module, "MFA Support". The "topt" text is both in the technical name and in the module description.
• searching the App store for "topt" returns no results!

Any ideas on why this might be?

We can list the features to be developed during the OCA code sprint (India) on 24th Nov.

It seems that Odoo modules categories are inconsistent through versions.

• 14.0:
  https://github.com/odoo/odoo/blob/14.0/addons/stock/__manifest__.py#L11

• 12.0:
  https://github.com/odoo/odoo/blob/12.0/addons/stock/__manifest__.py#L11

I'm wondering what should we do with OCA apps site helping people filtering modules per categories.

Either staying with original ones ?

Or breaking with Odoo ones and maybe creating OCA ones in order to fulfill our specific needs?

@OCA/core-maintainers

available in v8 and v10 in https://github.com/OCA/account-invoicing

All front page logos should be displayed with the same size.

Record the download numbers in the variant
Add the possibility to sort by:

• download number
• Most rated

Currently a lot of developers are referring to the modules via their technical names.
I suggest to add the technical name in the kanban view (first line).

cc @OCA/board

Some images shows insecure connection.

Hi All,

First off, really appreciate all the hard work you all do!!

Not sure to call this an issue, perhaps more of my probably just not sure I am using the addons correctly. With my use case, Its not to provide download for odoo modules, but to mobile applications I have I have built.

I create the product, I then add the android files, I then add my own variants, I then update the variant information. How this is where I then come into the issue.

No matter what I have tried, I keep getting

This product has no valid combination.

Just not sure what I am doing wrong to be honest. Would really appreciate the help.

Thanks in advance.

Error while trying to download an app (base_import_async)

In products:

In variants

Besides the field "Odoo Module" appears 2 times in the list of fields in the product variant filter interface

Module

website_apps_store

Describe the bug

The search bar, when the pager is displayed, is very small.

To Reproduce

Go to: https://odoo-community.org/shop

Expected behavior
A spacious search bar, where I can see the term I type without problems.

Additional context

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-15.0

Modules to migrate

• apps_download
• apps_product_creator
• website_apps_store

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Currently when we search it is searching directly on the name, desc, rst/html desc, author and everything.
The result is we have a lot of modules in search and the real meaningful module will be pointed out.

IMO we should have smart sorting (or maybe a proper name) option for sort, which will search include the apps in below orders

1. match with the technical name "=" operator
2. match with the name "=" operator.
3. match with technical name and name with ilike operator.
4. author "=" and "ilike" operator
5. rest current conditions.

Not clear the reason why: are modules in v12 or is it the filter itself

Steps to reproduce issue:

1. Go to Github menu → Repositories → Click on Branches sync.
2. Click on “Branches” button.
3. Select any branch. For example v9.
4. Click on “Download Source Code”.
5. Click on “Analyze Source Code”.
6. Go to settings → Automation → Scheduled Actions and run scheduler of “Create product variants for each module version“.
7. It will create product template and variants for v9.
8. Fetch module for v10 or for any version by following above steps.
9. Run scheduler again to create product variant for newer version.

Now, It is not creating product variant for newer version. Have I missed something?

"False" should be removed
missing information from the manifest: is it logical?

• technical name
• License
• Author
• Website
• Repository

Example:

https://odoo-community.org/shop/product/mis-builder-budget-1639

These render correctly in the backend or on pypi or on apps.odoo.com.

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0

Modules to migrate

• apps_download - By @ernestotejeda - #85
• apps_product_creator - By @ernestotejeda - #83
• website_apps_store - By @ernestotejeda - #86

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

during some discussions at the code sprint I got the impression most unrest about reviews, conventions and merging stems from the fact that stuff has to be merged to be visible, and that's what people care for much more than the actual merge.

So why don't we approach the maturity slightly differently: We scan open PRs for the ones that add a module, that should be simple to detect. If the PR is done by an OCA member (in order to avoid people being able to spam the webshop), we add it to the shop with maturity alpha. So we get early releases, but don't have to merge subpar code. The advantage I see is that this way, a module can mature without creating possible problems in a branch by being merged prematurely (unprotected imports, wrong monkey patching and the like). This can also be a selling point for the OCA membership, and can inform us about which modules users like most, thus allowing us to direct the review efforts to the ones that are most wide-spread. Plus there's no interaction needed by anyone to get something published, which probably would stay a bottleneck.

cc @OCA/board

Introduction

The modules on this repository aim to build an apps store based on:

• Standard Odoo v10 ecommerce
• Github Connector

Currently 2 modules are available apps_product_creator and apps_download linked to github-connector modules which information is used to create one product per module:

• apps_product_creator will check the new modules in the repositories and create or update the products (one per module and version) in the database. Additionally important information from the manifest are populated in specific fields
• apps_download is responsible to create and update one zip file per module based on the content of Github repository and link it to the product in Odoo.

A third module is needed to complete the other 2 and display the module specific information in a standard Odoo e-commerce website (front-end).

This document aims to specify the views, data and process to be done via this third module.

Module information

• Module name: website_apps_store
• Version: v10.0 (compatible Community and Enterprise Edition)
• Dependency: ecommerce, apps_download, apps_product_creator
• License: AGPL-3

Front-end view

E-commerce catalogue page

Here is the mock up suggested for the product catalogue page:

Changes expected to the standard e-commerce page:

• Add Author
• Hide the price
• Add Versions supported by the module

Search function should allow:

• Fuzzy search
• Content in module name, author and summary

3 filters widget to be added:

• Author
• Version
• Category

Product Detailed page

Here is the mock up suggested for the product detailed page:

NB: Current design is based on one page for all versions of the module, displaying the module description of the highest version.

Standard Odoo Fields:

• Image
• Product name

Add following fields (based on the manifest of the higher version)

• Module summary
• Radio button with the versions available for the module (From higher to lower, default = higher)
• Button "Download"
• Miscellaneous fields:
  • Technical Name
  • Author
  • Maintainer (Link to Contributor Page - static page in odoo-community.org)
  • License (Link to the license on the OSI website)
  • Website (URL)
  • Repository (URL)
• HTML description of the product

NB:

• all link should open in new tab
• Module details (summary, name, description...) should be dynamic depending on the selected version.
• Update Process: Pages are rebuilt every night via cron job after the module information have been update from Github. Only pages from updated modules are to be rebuilt.

checkout process

1. The visitor will select a module from the catalogue page
2. The visitor select the version he wants to download for the module
3. Visitor clicks on Download button and the download of the zip file linked to the selected product starts in the browser

NB:

• no login is required for download
• All other checkout buttons should be hidden

Roadmap:

• add an extensive search based on the content of RST
• Add multiple images if the modules contains multiple screenshots/images/icon.
• Add a donation button

Hello !
We have used
Odoo Version attribute in Py file for creating Product's variants
https://github.com/OCA/apps-store/blob/10.0/apps_product_creator/models/odoo_module.py#L90
But it has been added from the demo data.
https://github.com/OCA/apps-store/blob/10.0/apps_product_creator/__manifest__.py#L22
https://github.com/OCA/apps-store/blob/10.0/apps_product_creator/demo/product_attribute.xml#L6
IMO the place of product_attribute.xml will be in Data tag and folder and not in demo data.
I can change it while working on the website. but just wanted to confirm that Am I right or not.

Currently arriving on firs page are displayed modules from v6.1, starting with W. The sorting is not clear.
I suggest sorting by latest version then alphabetical order or commit date.

cc @OCA/board @bizzappdev @StephanRozendaal @RoelAdriaans

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-12.0

Modules to migrate

• apps_download - By @victormmtorres - #60
• apps_product_creator - By @victormmtorres - #59
• website_apps_store - By @victormmtorres - #61

When select an Odoo version from the top right drop down, it should reflected in the facets. Otherwise there is no visual feedback that a filter is active.

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0

Modules to migrate

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-11.0

Modules to migrate

• apps_download - By @bizzappdev - #12
• apps_product_creator - By @tarteo - #9

To make the shop a pleasant experience, we should be able to tell users that some module doesn't work in their specific situation. Might be view incompatibilities, incompatible overrides or the like.

I've put a breaks key in the roadmap of https://github.com/OCA/server-tools/tree/10.0/base_manifest_extension, I think it would be useful to implement that for the shop. Then we can add this information to our ecosystem, making stuff more stable for everyone. We can also go crazy and add more debianish keys, like recommends or suggests. Versioned dependencies also could be helpful in the shop context.

I would tend to keep the top button to give more space to the modules list.

cc @OCA/board @bizzappdev @StephanRozendaal @RoelAdriaans

If I change the version in the module page, the text of the link changes, but not the target:

1. input a text for search "account currency"
2. Click on page 2 button
   Expected result: see page 2 of the search result
   Current result: the search text is remove and page 2 is irrelevant

Module

website_apps_store

Describe the bug

The search domain is so open that it generates a lot of noise.

To Reproduce

Affected versions: 14.0

Steps to reproduce the behavior:

1. Search 'web_responsive'

Expected behavior
Be clear about why the results are shown as they are shown. Perhaps a new filter would be helpful or give more importance to matches by technical name.

Additional context