Issue: XF Widgets placed in sidebar don't respect positions and go above wiki content sidebar

Sidebar widgets that are generated by BB-Code have no ordering as far as XF widgets are concerned. They are placed after all other XF widgets. Changing this ordering may be considered for a future release, depending on the effect:
- Placing all BB-Code-generated widgets first. Easy.
- Placing all BB-Code-generated widgets at the same (specifiable) display order. Difficult, would require significant code changes, maybe not even possible.
I hesitate to close this as "as designed" because this is unique to XenForo 2.1+. On other platforms, VaultWiki uses its own widget system, where it is possible to change the ordering of these widget groups.

I would be happy enough with having an option so that the BB-Code ones are placed first, and then after the XF Widgets come in whatever order they are defined

This is fixed in the next release.

AdminCP > Setup > Options > VaultWiki: Aesthetics > Display order for widgets created with BB code

This will allow you to rearrange BB-Code widgets before, after, or in between regular widgets, by specifying a number like you would for any widget's display order. However, the Display order applies to all BB-Code widgets. You still cannot specify a number for each BB-Code individually.

This change has been applied to XenForo 2.1 only, since other platforms already provided a similar type of reordering.

No support for XF 2.2 then? or is it XF2.1 and higher ?

XenForo 2.1 and higher.

Hmm I guess this was not included in vw 4.1.2 PL 2 ? (I just installed it and can't find this feature..)

If so, what is the ETA for next version release?

Patches only contain the changes listed in the patch notes. For 4.1.2 Patch Level 2, see: https://www.vaultwiki.org/articles/290/

Our policy is that new versions do not have any specific ETA but are instead every new version has a specific threshold:
- At least 3 weeks after the previous version release
- At least 10 changes in the changelog
- Fewer than 5 active bug reports on the web site, not counting: duplicates, cannot reproduce, or flagged for future.
- Any additional bugs that were found internally must be resolved

- If all of the above are okay, then a multi-day process begins:
-- Note that if at any point in this process, the above threshold is no longer met, the threshold must be met again before continuing.
-- New version notes (changelogs, style change info) must be posted to our documentation. If any additional bugs are encountered, they must be resolved before continuing.
-- We test upgrade in place on vBulletin 3, vBulletin 4, XenForo 1.x, and XenForo 2.x. If changes to the installer have been made, we additionally test install in place on vBulletin 4 and XenForo 2.x. If any additional bugs are encountered, they must be resolved before continuing.
-- We generate a package and upgrade from the package on vBulletin 4, XenForo 1.x, and XenForo 2.x. If any additional bugs are encountered, they must be resolved and new packages generated before continuing.
-- Wait 3 days. If any additional bugs are logged or reported, they must be resolved and new packages generated before continuing. There must be at least 3 days with no additional bugs logged, and 1 day with no additional bugs reported, before continuing.
-- Release the package and post an announcement.