Issue: Forum headers display in random wiki articles

The default behavior is that a wiki area header will also display on any wiki pages within that area. The VW3 importer does not import any headers at the wiki page level -- only the area level. If the header was added by the importer, it was added to the article's area, not the article itself. So the area must be related to node 176 (such as it is the imported wiki version of node 176), and the article is within that area.

Please note that if a user added this header since the import, the header could be anything with any or no relation. Unlike VW3, VaultWiki 4 allows you to select any wiki page to be a header, and you can reuse the same page for as many headers as you want. If the header has the preview bit set, then it has definitely been modified by a user (although not having the preview bit does not mean that a user did not edit it), and cannot be trusted to be the same data that was imported.

At this point, the only way to know for sure if a header was created by the import or a user would be by looking at clues in the raw data. The vw_integrate.title field, which is not used on the front-end for these types of headers, would differ in the following ways:
- For imported headers, 'Header for [name of the header target]"
- For user-generated headers, 'Header for [ID1]:[ID2]'
This only holds true if vw_integrate.adminset = 0, which designates that the row was not added via the admin panel. If it is 1, there is no way to tell the difference. However, this still only tells you if the header record was created by the import; if it was edited by a user since the import (and the user could have changed the header content as part of the edit), there is no way to tell the difference.

I would only suspect there to be a bug if:
- The database shows no user-generated header records
- Every header record is either associated to the wrong target area or has the wrong wiki page associated as the header content

And this could only be confirmed with file access so that the incoming import data could be checked for errors at each part of that import conversion.

Please see the marquis wiki on my sites.

The Marquis article, which is an an area called "Wiki Articles" has a header whose title is "Forum Header-176". In VaultWiki 3, "Forum Header-176" would have been the automatically generated title for the page that contained the header content, with the "176" corresponding to the VW3 forum ID of the forum the header was used on. Since you preserved IDs during your forum import, I can see that forum 176 was a forum called "Wiki Articles." There is an old thread called "Marquis" in that forum.

This suggests that forum 176 "Wiki Articles" was imported as the wiki area "Wiki Articles". And that the header for the original forum has been imported to the area as well. The expected behavior in both VW3 and VW4 is for a wiki header on a forum/area to also appear on its child threads/pages.

It would appear to me that this header was correctly imported, and that this is Working as Designed.

Do you have a different header example, which was not imported correctly?

In VW3 the forum header only displayed in the forum and not in the threads. You can see this here on my old site:
Thread without header: /forum/showthread.php?t=297265
Parent Forum with header: /forum/forumdisplay.php?f=30

This forum header was indeed correctly imported. I do hope that we can still use forum headers without imposing them to other pages than originally intended. Similarly; I do hope when turning on forum headers for forum nodes that we can do so without affecting hundreds of thousands of threads. Nowadays 85% of our readers is on small mobile device and filling that screen with a forum header imposes problems.

In VaultWiki 3, the forum header displayed on all child threads of that forum and there was no built-in way to disable it. I reviewed your VW3 installation, and you used a custom plugin in order to remove the forum header from threads.

There is no inconsistency in behavior between VW3 and VW4 regarding this. However, VW4 does give you the option to disable the header on a thread-by-thread basis. If you wish, we can add a new feature to make it easier: a setting for each header instance that prevents it from appearing on child nodes. You can still use the VW3 method of using custom plugins to remove unwanted headers, although you would need to update it for compatibility with VW4.

I see there is the plugin: remove forum header from thread
IIRC you kindly added this for me and a few others. But it was many years ago. Do I remember this correctly?

In relation to the issue we see now: its not a bug and the headers just need to be disabled.

Moved this to a feature request. The desired feature is as follows:
A setting for each header instance that prevents the header from also appearing on child nodes (relevant to forums, areas, projects, cms sections, group categories, blog categories, and possibly others)

I'd much like a global setting.

The following has been implemented in 4.1.x:
- A new setting "Inheritable Wiki Content Integrations"
This is the global setting you were asking for. In this setting, you would un-check the "Forums" option, and forum-integrations would no longer appear on thread views.

Alternatively, you could also do the following, if it meets your needs, due to other changes to the integration system in 4.1.x.
- In the Wiki Admin Panel, under Content > Integration, you will now find a list of valid "Integration Positions". If you don't want any kind of integrations on thread views at all, you would locate the positions such as "header:thread" in the list and disable them.
As another example, most admins would probably want to disable "header:user" and only use "tab:user" (allowing only integrations as a profile tab vs as a header block on the profile).

There will be more information about these and other changes to integrations when we make a release announcement for 4.1.x.