Set a configurable delay before a resource review can be posted

[MarkElf]

Pretty much a means of ensuring that users actually attempt to reach out to a resource author before opening a chargeback and/or leaving a negative review because the user failed to understand something that might have been important or a misunderstanding. This can be applied to both free and premium resources.

Copy/Pasted from RoboMWM from Spigot but is just as applicable: At the current moment, reviews are permitted only after downloading the resource. Delaying users from immediately making a review forces them to find other, and more appropriate, methods to communicate their distress/question.

Additionally, this will also help prevent the far more minor issue of "fake" reviews by developers who maliciously incentivize others to rate their plugin highly.

 

[MarkElf]

Bump.

 

[R3XET]

Good idea

 

[MarkElf]

Bump.

 

[Larjd]

What about positive reviews? Would the delay also apply?

 

[MarkElf]

What about positive reviews? Would the delay also apply?

I don't see why this wouldn't apply to positive reviews as well. Buyers should obviously use the resource for a period of time before leaving a review - for the first 2 years or so I left a message on my resource page asking to use the resource for 24 hours before leaving a review but that was ignored the majority of the time so I just removed it. Having that delay should help with the other side of the coin as well, referring to people constantly leaving 5-star reviews to artificially promote a resource. I personally don't notice it as I don't use other resources on here but it is apparently a trending issue based on my last suggestion thread which was aimed toward a similar goal related to reviews and posting multiple. Returning to the point, setting a double standard of making it impossible to get 1-star reviews by setting a super long delay while letting it be easy to get 5-star reviews shouldn't be permitted so whatever delay you set would apply to all reviews.

 

[Mick]

This seems like a really intuitive way to go about resolving a lot of the issues you have brought up. We won't be doing any more custom development while on XF1, but I'll move this to pending for us to remember to implement eventually within our XF2 installation of the site.

Pending, thanks for the suggestion