Issue: bb codes do not work on XF demo

I don't see what you mean. Please be more specific.

bb code is not parsed in the comments of the XF wiki demo.
Please scroll down on the page I linked to.

BB-Code is parsing correctly on the comments:

- Non-existing BB-Codes (such as "h2") are displaying in plain-text, as expected.
- Users who don't have permission to post BB-Code (such as guest users) have their BB-Code displayed as plain-text.
- Users who have permission to post BB-Code (such as pegasus) have their BB-Code parsed.

This is all working as designed.

I am not following you. Because for any potential buyer of VW4 it looks like the bbcodes are not parsing.
h2 is wiki bbcode. Why does it not exist?
Xenforo user tagging should work in comments. But instead it displays as raw code.

h2 is not a wiki BB-Code. "H" is. H2 and H=2 are not the same BB-Code.

For user tagging, you have pointed out that there is an inconsistency in behavior between tagging in the latest XenForo vs the latest VaultWiki. In VaultWiki, user tagging only works when the comment is initially posted. If you try to mention users in a later edit, as was done in that example, it will not work. This was originally done to avoid a situation where the same user kept receiving an alert for being mentioned every time the comment was edited, but it has resulted in the inconsistency you see. We will have to look for an alternative solution to that issue. I have Confirmed this as a bug with respect to that.

I have just mentioned you in a comment to make sure that user tagging was working at all.

Unfortunately, with that being a demo site, we are going to test things on it, and other users are going to test things on it. In a lot of cases, test content is not going to be attractive to a potential buyer. Some tests are going to look like garbage in order to see if the wiki can handle garbage without breaking down. But I'm not sure if there's a way to resolve that -- the point of a demo is to allow the potential buyer to try things out for themselves. The only thing I can think of to improve that in the comments, without actively removing other users' tests, is to bring back the ability to reverse the order of comments to newest-first (an option that has regressed).

I see bold bbcode not working there.
The usertag should display as a normal usertag. I would not want it in plain code on my site, because it looks broken.
Old usertags should still work. If a user returns to the site after some time they should still see the alert. (if the admin has set it this way)

The bold BB-Code is not working in a post written by a guest. On our demo, that is expected. We have set guest permissions to not allow BB-Codes. I will have to see if a guest that tags a user has the user-tag converted to BB-Code at post time. The expected behavior would be to ignore the user-tag if it was done by a guest.

I was not talking about old user-tags. I was talking about:
1. I post a comment with no user-tag.
2. No user is alerted, because no one is tagged.
3. I edit that comment and add a user-tag.
4. The tagged user should be alerted.

1. I post another comment and I tag Alfa1.
2. Alfa1 receives an alert, because he was tagged.
3. I edit my comment that tagged Alfa1 before.
4. Alfa1 receives a duplicate alert about the same user-tag. This should not happen. If this were allowed, then I can edit my comment 100 times in order to spam Alfa1 with 100 alerts.

I missed that the users were guests.

So I guess what I have to do to avoid confusion with potential buyers is modify our demos to put a banner in every guest post "This comment was posted by a guest. BB-Codes and user-tags are not allowed in guest comments."

Possibly also edit some test comments to better explain what the comment is testing.

After investigating this, I see that there is actually no inconsistency in the XenForo vs VaultWiki behavior regarding tagged users in edited comments. If you edit a regular forum post and add a tag to it after it was already created, the newly tagged user will not receive an alert. This is also the current VaultWiki behavior.

However, I noticed the following issues:
- When approving a moderated wiki comment, users who were tagged in the original comment did not receive alerts upon approval. This is now fixed.
- When approving a moderated wiki comment, users who were quoted in the original comment did not receive alerts upon approval. This is now fixed.
- When a user who was not allowed to post BB-Code (such as guests) tagged a user in the original comment, the tag was converted to BB-Code. This is now fixed; the tag is ignored.

I have also edited the demo comments you referred to so that they fully explain what each comment is testing -- that way the comments are not considered bugs by potential customers.

Marking this issue as fixed in the next release.