It seems crazy to me this feature has been asked since 2017 and does not seem to be something in place still?
A website or online solution which has a number of member only content for someone to have to always specify this is very tedious.
I think the way it should really work is that:
You can set a default login and error page in appsettings.
When you are in the "Restrict Public Access" pane you should only need to select member and groups.
Custom group level login and error pages should sit on the group in the back office which will overide any default configured in appsettings.
There is a whole display for member groups with nothing in it so this can easily sit in there.
It definitely sounds frustrating to deal with the lack of built-in support for default login and error pages in Umbraco, especially since this feature has been a notable request since 2017. It’s understandable that continuously specifying access restrictions can become tedious, and having a more streamlined approach would certainly improve the developer experience.
Given that this has been an ongoing issue, the most direct way to bring about change might be to engage more actively with the development process. Since you’re already involved in the forums, contributing to the Umbraco CMS on GitHub might be the next step. You could start by creating a feature request on the Umbraco CMS GitHub repository. Clearly outline the benefits of adding default login and error pages and how they could be configured and overridden at the group level.
Additionally, if you’re comfortable with coding, consider contributing a pull request with an initial implementation of this feature. Umbraco’s community and development team are very supportive of contributions that can enhance the platform. This proactive approach might not only solve your issue but could also benefit many others in the community facing the same challenge.
Lastly, participating in discussions during RFCs (Request for Comments) can also be a powerful way to influence new features. Although it's more of a long-term engagement, it helps shape the future of Umbraco.
I hope these suggestions help, and that you’ll find a receptive audience in the Umbraco community. It’s clear you’re looking to make Umbraco better for everyone, and that’s truly commendable.
2024 still no public access default login / error pages?
It seems crazy to me this feature has been asked since 2017 and does not seem to be something in place still?
A website or online solution which has a number of member only content for someone to have to always specify this is very tedious.
I think the way it should really work is that:
You can set a default login and error page in appsettings.
When you are in the "Restrict Public Access" pane you should only need to select member and groups.
Custom group level login and error pages should sit on the group in the back office which will overide any default configured in appsettings. There is a whole display for member groups with nothing in it so this can easily sit in there.
Hi Liam,
It definitely sounds frustrating to deal with the lack of built-in support for default login and error pages in Umbraco, especially since this feature has been a notable request since 2017. It’s understandable that continuously specifying access restrictions can become tedious, and having a more streamlined approach would certainly improve the developer experience.
Given that this has been an ongoing issue, the most direct way to bring about change might be to engage more actively with the development process. Since you’re already involved in the forums, contributing to the Umbraco CMS on GitHub might be the next step. You could start by creating a feature request on the Umbraco CMS GitHub repository. Clearly outline the benefits of adding default login and error pages and how they could be configured and overridden at the group level.
Additionally, if you’re comfortable with coding, consider contributing a pull request with an initial implementation of this feature. Umbraco’s community and development team are very supportive of contributions that can enhance the platform. This proactive approach might not only solve your issue but could also benefit many others in the community facing the same challenge.
Lastly, participating in discussions during RFCs (Request for Comments) can also be a powerful way to influence new features. Although it's more of a long-term engagement, it helps shape the future of Umbraco.
I hope these suggestions help, and that you’ll find a receptive audience in the Umbraco community. It’s clear you’re looking to make Umbraco better for everyone, and that’s truly commendable.
Warm regards, UCP
is working on a reply...