not sure what you need - the issue is scheduled for 7.3.4 (check the "fix version") which means that we will fix it if we have sufficient time - if we don't it will get rolled over to 7.4.0. It was also raised by an Evoq customer (hence the trouble ticket id), so it is more likely to be looked at sooner rather than later (that said 7.3.4 is almost done and no one is assigned to it yet, so I suspect it will be a 7.4.0 fix)

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

I already answered this - it was on the list for 7.3.4 but we did not have time to fix it, so it's now "rolled-forward" to 7.4.0 - as that is a larger release with a longer time frame I would expect it to be fixed in that version

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Version numbers are how we have always worked. When bugs/enhancements are logged at support.dnnsoftware.com we (DNN Corp) triage them to ensure they are valid (and not already fixed/duplicate). At that time they're assigned a priority and severity. When a new release is being planned then we estimate the resources we will have (both developers and QA) and assign a number of jira items to that release - the intent is that we will fix those items in that release (in reality more items are fixed, as we get pull requests from community members). If we do not get a chance to fix an issue in a release e.g. if we run out of time, we usually move the issue forward to the next release i.e. if it was important enough to be assigned to this release it should get assigned to the next as it was not fixed in time. When the next release is planned we can see the items already assigned to that and ensure that we do not add too many to that release. This has been the process we have used for 10+ years. 

In this case the issue was deemed as "high" and assigned to 7.3.4 on October 6th. Unfortunately we did not have time to fix this in the 7.3.4 release as it is now code-frozen, so the issue will move to 7.4.0 and get fixed in that release

As to why the feature doesn't work, it's a relatively rarely used feature so hasn't been logged before. The breaking change was introduced in 7.1.0 which came out on July 9th 2013, but the bug was not logged until Aug 27th 2014, more than a year later.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US