Issue: Can't convert thread to wiki page?

You are correct. The menu options to do this are missing in XenForo 2 (they exist in XenForo 1 which may be what you're remembering). If you manage to access the URL directly, there are also lots of errors in XenForo 2.

This is fixed in the next release. After fixing the menu and all the errors, I have successfully converted several threads into wiki pages.

I would really like to have this next release soon.. Any ETA for it? can you estimate anything at all?

We currently have 19 files that have "unexpected contents" (which makes that security feature useless since we now ignore it....) and many of the reported bugs can't be fixed until the next release is actually released.

I would point you to: https://www.vaultwiki.org/pages/Info...rsion-Releases

The typical sticking points are:
Specifically:
e.g. your example of XenForo search becoming unusable under XFES when certain VaultWiki settings are used.
Usually happens when we investigate an issue reported by a user that we come across other issues. This literally just happened while I was looking into the search issue. Even several days after the user's report was closed, we may still be sifting through those.
During this time, it is not uncommon for the first point to become undone again.

Seeing as there is now almost 6 months since the last release, would it make sense to add a "maximum X days since last release" to the release rules where you would freeze the things to be fixed and only bring in really critical fixes in to the next release?

Keeping some fixes that have been reported and fixed up to 6 months ago unavailable for you customers to get can't be in their (or your) best interest to be honest..

I'm not talking monthly releases here (we do that at the SW company I work for), but every 2-3 months would at least be a bit better than 6+ months..

tldr; the main purpose of this post is actually to document that I discovered a Permissions Escalation in the code for thread conversion. But I thought you also deserved some sort of acknowledgment to your previous reply...

Normally I would agree with you on the timing, but in this case there were 2 bug reports between June and September, making it very difficult to justify packaging a release in the first 3 months of the 6-month period in question (really, 5 months so far). Starting in September, we began to see some changes that could start to justify packaging a release (remember we're limited in the types of changes that we're allowed to put in certain releases), and around late September/early October we got to a point where we began considering packaging a release (in fact I see that the upgrade script started to be written on 9/27). So it has been on our todo list, and we are building toward it.

We basically do make a freeze on things to be fixed at a certain point, although I see that when that happens is not described in the release policy. It's somewhat based on achieving the earlier points in the release policy, the part about 10 resolved issues and 60 days since the last release, although there are other factors.

So at this point we basically say, that we're now focused on building the release, and we're only going to include new reports in the next release if they are critical or extremely easy/short to fix. I guess a problem is, that even after that point, all newly discovered issues still have to be triaged to determine the level of severity, before it can be said, yeah that can wait for a future release.

For example, perhaps this bug report may not necessarily fall under the "critical" description, because it otherwise relates to a minor, rarely used feature. But it was triaged to determine why the option was not appearing (first thought was a "permissions de-escalation", which is considered critical). In the process of determining this, I discovered that the thread conversion process, which actually works against other versions of forum software, does contain a "permissions escalation"... and that triggers a future security patch.

I do take your point that some elements of this could possibly be streamlined more, and perhaps we did kind of drag our feet on this upcoming release. But hopefully, it will be worth the wait.