maz_the_man's profile

3 Messages

 • 

112 Points

Sun, Oct 22, 2017 2:51 PM

Sleepwalking in Suburbia listing contained a review with a "without warning spoiler"

http://www.imdb.com/title/tt6829222/?ref_=nv_sr_2 for Sleepwalking in Suburbia contained a review which had a spoiler. There was no warning about this and obviously, this ruined the film.

Champion

 • 

3.7K Messages

 • 

77.7K Points

Il y a 5 y

Hi Maz the Man,

I'm sorry to hear this, please go to the review in question and use the "report this" feature to submit a report to our data editors.

Regards,
Will

3 Messages

 • 

112 Points

Il y a 5 y

Hi there, I've already done that but I assumed that I would be reporting the poster for violating the rules when it wouldn't have been their fault. This is why I emailed you as well.

Kind regards, Maz

3 Messages

 • 

112 Points

Il y a 5 y

Hi Will, sorry but I think I might not have been clear in my query. The situation is as follows;
When I view the details of the film in IMDB in URL http://www.imdb.com/title/tt6829222/?ref_=nv_sr_2 when you scroll down to look at reviews, it has a review that includes a spoiler even though the original poster of that review marked it has "contains spoiler". So the problem is that the procedure needs to be changed so that any reviews that contain spoilers are not including in the 'head' listing of the film, or any film really. Hope this makes it clearer.

Many thanks, Maz

Employee

 • 

14.4K Messages

 • 

281.7K Points

Il y a 5 y

Hi Maz -

Thanks for clarifying further.  Unfortunately, all the reviews for this title include Spoiler Warning tags, normally we will filter out reviews with spoilers as the default review on the title page, but in this case we don't have any available reviews that are spoiler-free. Rest assured that once a review has been added for the title that is spoiler-free, it will replace the default.

With that being said, there is still the issue of the Spoiler Warning not being displayed on the title page for the existing default review.  This is likely due to limitations in our system and I have now filed a ticket for the appropriate team for visibility and to review a resolution.  Thanks again for your report!