Issue: XenForo tags wiki

As of 4.0.7, a new integration-type has been added for "Content Tags" that can be enabled in the same way as previously existing types. The familiar "header" will then appear at the top of the results page for a given tag. Since there are no separate permissions for tags on their own, only moderators or admins are able to create the integration.

Of course, the positioning and the permissions can be overridden via plugins, but this change should provide basic tag-header functionality to both vBulletin 4 and XenForo 1.5.

Could you please post instructions on how to enable this?

It seems to me that this was not really implemented. Probably because I did not describe the functionality well. What is needed:
On each tag page, have a block or a tab that displays the first x characters of the wiki with the same name.
If there is no wiki with the same name, then display a function so users can start a wiki on the topic.

At the top of any tag page, you should see the standard wiki-integration block:
If this does not appear, check your Settings > VaultWiki: Miscellaneous:
- Allow Wiki Content Integration, must be checked
- Wiki Content Integration Locations, must have "Content Tags" selected

The user must have permission to manage the tag.

I have it on the demo wiki, so I can tell that it was really implemented: https://www.vaultwiki.org/xf/index.php?tags/ps4/
There is an issue with the CSS of wiki integrations in the current version, due to this change which affected the timing of CSS externals: https://www.vaultwiki.org/issues/5341/
The integration-CSS issue is resolved in the next release.

Thank you for the information. Some comments:
1. This bug gets in the way: https://www.vaultwiki.org/issues/5387/

2. Managing tags is a moderator permission in XenForo. It would make more sense to base this on a separate permission or on can edit wiki articles.

3. The function does not recognize if there is a wiki article for the tag. According to statistics I have 2200 wiki articles (not sure if that's correct) but there is no way to manually attribute those to the matching tags.

4. If I understand it correctly it will display an entire article, which basically makes the main function of the page unusable. The block should only display an article preview. Wiki articles are long. Some of our wiki articles can go over 100K characters. Tags are pushed to the bottom. So we need a short preview of an article. See my article system for an example of what would be nice.

For number 1, disable debug mode.

For number 2, we can consider making separate permissions for integrations in the future. Historically you always had to have a management-related permission (for forums, threads, etc) in order to make the forumpage-wikipage connection and manage the connection options. Anyone with permission to edit the original wiki page is still able to edit the page's content.

For number 3, we have never had automatic connecting of integration locations to wiki pages. In general, it can cause a mess. The closest we can do without creating a mess is attempting to pre-fill the integration form with a list of similarly-named wiki pages to choose from. Otherwise a separate tool would be needed in the Mass Management Tools.

For number 4, yes it displays an entire wiki page. You can show it collapsed in the integration settings when you connect the content to a wiki page. Check the box "Show an expandable preview of long content."

2. We have 35k tags. Its not possible for staff to manage that amount of pages. It needs to be a simple function that the end user can use.

3. Tag Essentials for XF does this. It will automatically use the Wikipedia page that has the exact same name. My suggestion is to do the same for VW. If a wiki article with the exact same title exists then display this. If there is no match then make it manual.

4. As there are 35k tags, it will be a technically challenged end user who will connect the tag page to a wiki article. We can be sure that they will not check any box. The things we can ask end users to do or understand are severely limited. In other words: add a 'preview snippet length' admincp setting that applies globally. There is no need for settings per tag page.

Lastly: I dont think it makes sense to show an empty block when there is no article. It would be better to have a 'Add Wiki Article' button. Its clearer and more compelling to have a call to action button. And it doesn't waste space. Some tags will never or cannot get a wiki article.