Reports Broken due to BBCode

[ShannonA]

Ever since we upgraded to vB5, our post reports have been broken because they're inexplicably being sent in bbcode, which of course mail readers don't understand.

Why did this change, and how do we get back to correctly formatted text?

Thanks.

[kimtan]

Do You have an example screenshot for this issue? Do you mean its not bbcode for the previous version?

[ShannonA]

The email reports are all in BBcode, like this:

USER has reported a post.
Reason:

REASON

ETC.

(You'd have to click EDIT to see the actual BBcode since it's being converted by the forums.)

Obviously, BBcode isn't a standard for email so every single one is a mess that's hard to parse. Email reports under vB4 used to be plain text, as on this site that we fortunately haven't upgraded to vB5:

USER ( USER EMAIL ) has reported this post: Re: [Britpack] Brexit III: Brexit Stupider

[Wayne Luke]

Hmmm... I am surprised this hasn't been reported before. It is an issue in the phrase of the system.

Go to Languages & Phrases -> Phrase Manager.
On the next page where it has a drop down for phrase type choose Email Body Text.
Go to Page 3.
Edit the reportitem_ newpost_ gemailbody phrase at the bottom of the page.
Enter something like below into the translation box:

{1}, ({2}) has also reported this item.

Reason: {3}

If that doesn't work then I will need to see an actual email that gets sent from your site.

[ShannonA]

That looks like it. Thanks much, I would never have thought to look there.

[Kevin Sours]

I think the phrase you are looking for is actually reportpost_newthread_gemailbody, which is similar.

[ url={1}]{2}[/url ] has reported a post.

Reason:[ quote]{3}[/quote]
Post: [ url={4}]{5}[/url ]
Forum: {6}
Assigned Moderators:{7}

Posted by: [ url={8}]{9}[/url]
Original Content: [ quote]{10}[/quote]

(added some spaces so that the board doesn't try to parse it)

[Kevin Sours]

FYI, issue in JIRA for tracking http://tracker.vbulletin.com/browse/VBV-17224

[ShannonA]

Thanks Kevin. We are indeed working again.