Bug Description
When I open add-ons published by other creators, I cannot find any option to rate them.
I tested several different add-ons from different creators, but the Rate button or any other rating control does not appear on the add-on page.
I am reporting this because I was recently informed that add-on scores are based on ratings submitted by actual users. However, I currently cannot find a way to submit a rating for an add-on.
Steps to reproduce
- Open BlenderKit.
- Browse or search for an add-on published by another creator.
- Open the add-on details/page.
- Look for the option to rate the add-on.
Actual behavior
There is no Rate button, star-rating control, or other visible option that allows the user to submit a rating for the add-on.
I tested this with multiple add-ons from other creators and observed the same behavior.
Expected behavior
If add-ons support user ratings, a rating control should be available so users can submit their rating, similar to other asset types that support ratings.
Alternatively, if add-on ratings are intentionally not currently available, clarification would be useful because add-on scores are described as being based on real user ratings.
I have attached screenshots showing examples where the rating option is not present.
Additional Information
Environment Information - Bug happens on:
- BlenderKit version: v3.21.0.260628
- Blender version: v5.2.0 LTS
- Python version: 3.13.13
- Operating system & architecture: Windows 11 (AMD64)
- Proxy setting: SYSTEM
- BlenderKit type: Legacy (User)
Additional observations
- The issue has been reproduced with multiple add-ons from different creators.
- The rating control appears to be completely absent rather than disabled.
- No error message is displayed.
- The problem is specifically related to rating add-ons.
- Screenshots showing the missing rating option are attached.
Error Logs
No Blender error or crash is produced when reproducing the missing add-on rating issue.
This appears to be a UI/feature availability issue: the rating control is not displayed for add-ons, and no related error message is shown.
Additionally, I encountered a separate issue with the GitHub bug report form itself:
- The Bug Description field does not allow me to enter text normally.
- As soon as I start typing, the field resets and the entered text disappears.
- I reproduced this behavior in multiple web browsers with the same result.
- Because of this, I had to place the complete bug description and reproduction details in the Additional Information section instead.
No browser error message was displayed when this occurred.
Bug Description
When I open add-ons published by other creators, I cannot find any option to rate them.
I tested several different add-ons from different creators, but the Rate button or any other rating control does not appear on the add-on page.
I am reporting this because I was recently informed that add-on scores are based on ratings submitted by actual users. However, I currently cannot find a way to submit a rating for an add-on.
Steps to reproduce
Actual behavior
There is no Rate button, star-rating control, or other visible option that allows the user to submit a rating for the add-on.
I tested this with multiple add-ons from other creators and observed the same behavior.
Expected behavior
If add-ons support user ratings, a rating control should be available so users can submit their rating, similar to other asset types that support ratings.
Alternatively, if add-on ratings are intentionally not currently available, clarification would be useful because add-on scores are described as being based on real user ratings.
I have attached screenshots showing examples where the rating option is not present.
Additional Information
Environment Information - Bug happens on:
Additional observations
Error Logs
No Blender error or crash is produced when reproducing the missing add-on rating issue.
This appears to be a UI/feature availability issue: the rating control is not displayed for add-ons, and no related error message is shown.
Additionally, I encountered a separate issue with the GitHub bug report form itself:
No browser error message was displayed when this occurred.