BUG: When authenticated (logged in) the body is showing base template.

Problem: When authenticated (logged in) the body is showing base template.

Encountered: During early testing (ET), while performing crafting allauth.

Can it be Reproduced: Yes it is reproducable, one just perform the Log in precedure.

Impact:

The issue leads to a lack of contextual relevance in the content presented to authenticated users. Instead of displaying user-specific data or interfaces (like dashboards or personalized content), logged-in users are seeing the base template, which is typically intended for first-time or non-authenticated visitors. This can confuse users about their login status and reduce the usability of the application.
Since the expected authenticated user interface (UI) elements such as links to user profiles, dashboards, or logout options do not appear, users might find it difficult to navigate or utilize the application effectively. This disruption can hinder user engagement and productivity, especially in applications where logged-in functionality is central to user activities.
Displaying incorrect templates might lead to potential issues with access control, where users do not see or cannot access features meant for their use levels. Although this does not directly imply a security breach, it does raise concerns about the application's ability to present content appropriately based on user roles and permissions.
If foundational elements like template rendering based on authentication states are not reliable, scaling the application can introduce more complexities and worsen existing issues. This could complicate the integration of more sophisticated features and functionalities in the future.

Possible Testing and Validation:

In this case ands at this point correct the issue and thest the login feature manually

JaqiKal / ScrollStack