You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This module will provide ratings for products by using the rating module provided by Odoo (v10) core. It will add rating to product.product, with another computed rating on the product.template containing an aggregate rating for the variants.
It will add a new model product.rating will be created that will allow for the abstract scheduling of product rating requests. This will allow for the module to be used in all contexts of a product (sales, purchases, etc), without requiring glue modules. The model will allow for the choice of:
Model to act on
Domain filter for matching records that should have a rating requested (similar to the way server actions work)
Email template used for ratings requests
product_field_id - This is the field on the record for the product that is being rated
rater_field_id - This will set the rating.rating.partner_id to the value of this field. The rating request email will be sent to this partner's email.
rated_partner_field_id - if defined, this will set the rating.rating.rated_partner_id to the value of this field
A scheduled task will be added that will iterate the active product.rating records, search the model for the defined domain, then send the defined email to the rater.
If a partner has already rated the product variant, they will be ignored from this task. On that same note, a partner should not be able to rate the same product variant twice. They should, however, be able to rate two different product variants of the same template - because they are technically different products.
Plan seems simple enough IMO. Anyone know of some pre-existing code/strategies, or see a hole in the plan?
The text was updated successfully, but these errors were encountered:
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.
This module will provide ratings for products by using the
rating
module provided by Odoo (v10) core. It will add rating toproduct.product
, with another computed rating on theproduct.template
containing an aggregate rating for the variants.It will add a new model
product.rating
will be created that will allow for the abstract scheduling of product rating requests. This will allow for the module to be used in all contexts of a product (sales, purchases, etc), without requiring glue modules. The model will allow for the choice of:rating.rating.partner_id
to the value of this field. The rating request email will be sent to this partner's email.rating.rating.rated_partner_id
to the value of this fieldA scheduled task will be added that will iterate the active
product.rating
records, search the model for the defined domain, then send the defined email to the rater.If a partner has already rated the product variant, they will be ignored from this task. On that same note, a partner should not be able to rate the same product variant twice. They should, however, be able to rate two different product variants of the same template - because they are technically different products.
Plan seems simple enough IMO. Anyone know of some pre-existing code/strategies, or see a hole in the plan?
The text was updated successfully, but these errors were encountered: