I understand that you do not perceive them as bugs, but, from an end-user's perspective, all I am trying to do is assign permissions to a page and redirect my users to a login page if they do not have permissions to see this page.
When a CMS product does not support this, it would seem very much like a bug, to a non-technical evaluator of your product.
You must understand the types of conversations I am trying to deal with, let me give you this example.
Non-Technical Business User: Can you show us how we can only allow access to certain pages based on a users role?
Me: Sure, all I have to do is assign permissions to the page like this.
Sitefinity: 404 error
Non-Technical Business User: Is it supposed to give an error screen like that.
Me: No, it seems like a bug.
Me: No, thats not a bug, thats how .NET implements the SiteMapProvider
Non-Techincal Business User: What is .NET, and what is a SiteMapProvider ?
Don't get me wrong, this is an exceptional product that we are complete sold on, and will probably buy lots of licenses of, but, I was really disappointed when this seemingly simple issue was not resolved in the last beta2 release. I was very excited that I would be able to show my business users that this core functionality of a CMS system is actually working.
I apologize to continue to belabor this topic, but, come-on guys, this should be a huge priority. I can't test out permissions at all.