Details: Category: Documentation

ES Login Redirect Manager

Setup and Usage Guide

ES Login Redirect Manager lets you control where Joomla users are sent after:

Login
Logout
First Login

You can create redirect rules based on the user, Joomla user group, language, site area, source URL and rule priority.

This guide explains how to install the extension, configure it and create your first redirect rules.

1. Requirements

ES Login Redirect Manager supports:

Joomla 5.x
Joomla 6.x

The extension is installed as a Joomla package and includes all required parts.

2. Installation

Download the ES Login Redirect Manager ZIP package from your ExtensionSpot account.
Log in to your Joomla Administrator.
Go to:

System → Install → Extensions

Upload the package:

pkg_esloginredirect_x.x.x.zip

Wait for Joomla to confirm that the package was installed successfully.

After installation, the extension is available from:

Components → ES Login Redirect Manager

3. Configure your ExtensionSpot Download Key

ES Login Redirect Manager uses Joomla's native Update System.

Your ExtensionSpot order reference is used as the Download Key.

Example:

AFRDDAHCN

To add your Download Key:

Go to:

System → Update Sites

Find:

ES Login Redirect Manager Updates

Enter your ExtensionSpot order reference in the Download Key field.
Save.

A valid subscription gives access to updates for 12 months from the order date.

The extension continues to work after the update subscription expires. Only access to new updates is affected.

4. Open ES Login Redirect Manager

Go to:

Components → ES Login Redirect Manager

The main areas are:

Rules
Simulator
Import / Export
Settings / Fallback options

The Rules page is where you create and manage redirect behavior.

5. How redirect rules work

ES Login Redirect Manager evaluates enabled rules in priority order.

The first matching rule wins.

Example:

Priority 5
Special Login Page

Priority 20
Authors

Priority 100
Registered Users

If the first rule matches, the remaining rules are not used.

Lower priority numbers are evaluated first.

6. Create your first rule

Go to:

Components → ES Login Redirect Manager → Rules

Click:

New

A rule contains:

a name;
an event;
optional conditions;
a destination;
priority and ordering.

7. Rule fields explained

Title

Give the rule a clear name.

Examples:

Registered Users
Partners Login
Customer Dashboard
Special Login Page
Authors
Logout to Homepage

The title is only used in the Administrator interface.

Status

Choose whether the rule is active.

Published
Unpublished

Only published rules are evaluated.

Event

Defines when the rule runs.

After Login

Runs after a successful Joomla login.

Example:

Registered users
→ Customer Dashboard

After Logout

Runs after a successful logout.

Example:

Logout
→ Homepage

First Login

Runs only on the first successful login in the lifetime of the Joomla user account.

Example:

First Login
→ Welcome / Onboarding page

After the first successful login, the First Login rule will not run again for that user.

Priority

Controls the order in which rules are evaluated.

Lower numbers run first.

Example:

Priority 5
Source URL = /partner-login

Priority 100
Group = Registered

If the user logs in from /partner-login, the priority 5 rule wins before the general Registered rule.

Recommended approach:

1–20     very specific rules
20–50    role/group rules
100+     general fallback rules

You can use any priority values you prefer.

Ordering

Ordering is used when multiple rules have the same priority.

If two rules have the same priority, the rule with the earlier ordering position is evaluated first.

8. Conditions

Conditions are optional.

If you leave a condition empty, that condition is ignored.

If a rule contains several conditions, all configured conditions must match.

In other words, conditions inside one rule use AND logic.

Example:

User Group = Author
AND
Language = en-GB
AND
Source URL = /author-login

All three conditions must match.

9. Exact User

Use Exact User when a redirect should apply to one specific Joomla user.

Example:

Exact User:
This email address is being protected from spambots. You need JavaScript enabled to view it.

Destination:
/private-downloads

This rule applies only to that user.

Useful for:

dedicated client areas;
special download pages;
temporary project areas;
custom dashboards.

Leave empty to allow all users.

10. User Group

User Group lets you select one or more Joomla User Groups.

Example:

Registered
Author

If multiple groups are selected, the condition uses OR logic.

That means the user only needs to match one selected group.

Example:

Selected groups:
Registered
Author
Editor

A user belonging to any one of these groups can match the condition.

11. Preferred Group

Joomla users can belong to more than one User Group.

For example:

Registered
Author

By default, ES Login Redirect Manager evaluates all real group memberships.

If needed, you can assign an optional Preferred Group to a specific user.

Go to:

Users → Manage

Edit the user.

You will see:

Preferred Group

Available values are:

Default
+
only the Joomla groups that this user currently belongs to

Example:

Groups:
Registered
Author

Preferred Group:
Author

For ES Login Redirect Manager group matching, this user is treated as Author.

Important:

Preferred Group:

affects only ES Login Redirect Manager Group conditions;
does not change Joomla User Groups;
does not change Joomla ACL;
does not change Viewing Access Levels;
does not change permissions.

If Preferred Group is:

Default

all actual Joomla groups are evaluated normally.

12. Language

Use Language if a redirect should apply only to a specific Joomla language.

Example:

Language:
en-GB

or:

ro-RO

Leave empty to allow any language.

Example use case:

English users
→ /en/member-area

Romanian users
→ /ro/zona-client

13. Site Area

Site Area limits the rule to a Joomla application area.

Options may include:

Any
Frontend (Site)
Administrator

Frontend (Site)

Use when the redirect should apply only to normal website logins.

Administrator

Use when the rule is specifically intended for Joomla Administrator login context.

Any

The rule is not restricted by site area.

For most normal website redirects, use:

Frontend (Site)

14. Source URL

Source URL lets you apply a rule only when login or logout occurs from a particular frontend page.

Example:

https://example.com/customer-login

You can paste the complete URL.

ES Login Redirect Manager automatically normalizes the URL internally.

For example:

https://example.com/customer-login/

and:

https://example.com/customer-login?return=123

are treated as the same source path:

/customer-login

The query string is ignored for source matching.

Example:

Source URL:
/partner-login

Destination:
/partner-dashboard

A login from /partner-login can use this rule.

A login from /login will not match it.

Source URL is useful when you have several login pages that should lead to different destinations.

15. Active From / Active Until

If enabled in your version, these fields allow a rule to work only during a specified time period.

Example:

Active From:
2026-09-01

Active Until:
2026-09-30

Useful for:

campaigns;
temporary portals;
seasonal landing pages;
limited onboarding periods.

Leave empty if the rule should always be available.

16. Destination Type

A matching rule must have a destination.

Depending on the selected Destination Type, you can redirect to:

Joomla Menu Item
Internal URL
External URL

17. Joomla Menu Item destination

Choose a Joomla Menu Item from the selector.

This is usually the safest and easiest option when the destination already exists in a Joomla menu.

Examples:

Customer Dashboard
Member Area
Partner Portal
Homepage

ES Login Redirect Manager uses Joomla routing for the selected menu item.

18. Internal URL destination

Use this when you want to redirect to a page on the same website.

You may enter:

/member-area

or paste the full URL:

https://example.com/member-area

The extension normalizes same-site URLs automatically.

19. External URL destination

External redirects are controlled by the extension's external URL policy.

For security reasons, unrestricted external redirects are not enabled by default.

Available modes:

Disabled
Whitelist
Blacklist

20. External Redirect Policy

Disabled

External redirects are not allowed.

Use this if all redirects should remain inside your Joomla website.

Whitelist

Only domains explicitly added to the whitelist are allowed.

Example:

portal.company.com
crm.company.com

Blacklist

External redirects are generally allowed except for domains listed in the blacklist.

Example:

blocked-domain.com
tracking.example.net

21. Domain matching

Domain matching is exact by default.

Example:

company.com

matches:

company.com

but does not automatically match:

portal.company.com

To include subdomains, use:

*.company.com

22. Safe fallback

A redirect should never make your Joomla site unusable.

ES Login Redirect Manager includes safe fallback behavior.

A fallback may be used if:

the destination is invalid;
the destination is inaccessible;
the destination could create a redirect loop;
a redirect cannot be safely completed.

Authentication itself is not blocked.

If a redirect fails, Joomla login should still succeed and navigation falls back safely.

23. Redirect loop protection

The extension checks redirect destinations to reduce the risk of loops.

Example of a problematic flow:

Login
→ Login page
→ Login
→ Login page

A destination that would send the user back into an unsafe login redirect loop should not be used.

24. Super User protection

ES Login Redirect Manager is designed to avoid locking Joomla Super Users out of the Administrator area.

Do not use the extension as an ACL or access-denial system.

The extension controls navigation after authentication.

Joomla remains responsible for authentication and permissions.

25. The Simulator

Before testing by repeatedly logging in and out, use the built-in Simulator.

Go to:

Components → ES Login Redirect Manager → Simulator

Select or enter:

User
Event
Site Area
Language
Source URL

Then click:

Run Simulator

The Simulator uses the same redirect rule engine as the live system.

26. Understanding Simulator results

The result shows:

Matched Rule
Target
Preferred Group
Evaluation Trace

The Evaluation Trace helps explain what happened.

Example:

Rule:
Special Login Page

Result:
MATCH

Why:
All configured conditions matched.

A rejected rule may show why it did not match.

27. Example: Registered users to Member Area

Create a rule:

Title:
Registered Users

Event:
After Login

User Group:
Registered

Site Area:
Frontend

Priority:
100

Destination:
Member Area

Expected result:

Registered user logs in
→ Member Area

28. Example: Authors to Author Area

Create:

Title:
Authors

Event:
After Login

User Group:
Author

Site Area:
Frontend

Priority:
20

Destination:
/author-area

Expected result:

Author logs in
→ /author-area

If the user belongs to both Registered and Author, use rule priority or Preferred Group if necessary.

29. Example: Different login pages

Create:

Title:
Partner Login Page

Event:
After Login

Source URL:
/partner-login

Priority:
5

Destination:
/partner-dashboard

Then keep a general rule:

Title:
Registered Users

Event:
After Login

User Group:
Registered

Priority:
100

Destination:
/member-area

Result:

Login from /partner-login
→ /partner-dashboard

while:

Login from /login
→ /member-area

30. Example: First Login onboarding

Create:

Title:
First Login Welcome

Event:
First Login

User Group:
Registered

Destination:
/welcome

Expected result:

First successful login
→ /welcome

Future logins will use normal After Login rules.

31. Example: Logout redirect

Create:

Title:
Logout to Homepage

Event:
After Logout

Destination:
Homepage

Expected result:

User logs out
→ Homepage

32. Import and Export Rules

Go to:

Components → ES Login Redirect Manager → Import / Export

Use:

Download JSON

to download a backup of your rules.

The JSON file can be used to:

back up configuration;
move rules between websites;
reuse a setup on another client site.

Before importing rules into a production website, export the current configuration as a backup.

Always verify imported rules in the Simulator before relying on them.

33. Recommended rule design

Keep rules simple.

Good:

Group = Partner
→ Partner Dashboard

Good:

Source URL = /customer-login
→ Customer Dashboard

Good:

Exact User = John
→ John Private Area

Recommended structure:

Specific users / source URLs
        ↓
Specific groups
        ↓
General groups
        ↓
Fallback

34. Troubleshooting

A rule does not run

Check:

Is the rule Published?
Is the Event correct?
Is another rule using a lower priority number?
Does the user match the selected User Group?
Is Preferred Group affecting Group matching?
Does the Source URL match?
Is Site Area correct?
Is Language restricted?
Is the destination valid?

Then use the Simulator.

The wrong rule runs

Remember:

Lower priority number = evaluated first

Use the Simulator Evaluation Trace to see which rule matched first.

Preferred Group appears to change matching

This is expected.

Example:

User groups:
Registered
Author

Preferred Group:
Author

A rule that only selects:

Registered

will not match the Preferred Group condition.

Set:

Preferred Group:
Default

if you want ES Login Redirect Manager to evaluate all actual Joomla groups.

Source URL does not match

Paste the real frontend page URL where the login form is used.

Example:

https://example.com/contact

Do not use Joomla's technical login processing URL.

Use the Simulator with the same Source URL to confirm the expected rule.

External URL is rejected

Check the External Redirect Policy.

If set to Disabled, external redirects are intentionally blocked.

If using Whitelist mode, make sure the destination domain is allowed.

Remember:

domain.com

is an exact domain.

Use:

*.domain.com

when subdomains should be included.

35. Update troubleshooting

If an update is not detected:

Go to:

System → Update Sites

Verify that ES Login Redirect Manager Updates is enabled.
Verify that your Download Key is entered.
Clear the Joomla update cache.
Run Check for Updates again.

If your update subscription has expired, the installed extension continues to work. Renew your ExtensionSpot subscription to receive newer versions.

36. Best practices

Create specific rules before general rules.
Use clear rule names.
Keep priority numbers spaced apart.
Test changes in Simulator.
Keep at least one exported JSON backup.
Avoid unnecessary external redirects.
Use Whitelist mode when only a few external domains are required.
Do not use redirect rules as a replacement for Joomla ACL.
Test Administrator-related redirects carefully.

37. Quick Start Example

For a basic Joomla membership site:

Rule 1

Title:
Authors

Event:
After Login

Group:
Author

Priority:
20

Destination:
/author-area

Rule 2

Title:
Registered Users

Event:
After Login

Group:
Registered

Priority:
100

Destination:
/member-area

Rule 3

Title:
Logout

Event:
After Logout

Priority:
100

Destination:
Homepage

Then test all three rules in Simulator.

38. Live Demo

You can see ES Login Redirect Manager working on a live Joomla website:

https://j6.extensionspot.com/es-login-redirect-manager

The demo includes examples of:

group redirects;
Source URL redirects;
Preferred Group;
rule priority;
Simulator behavior.

39. Summary

The normal workflow is:

Install extension
        ↓
Add Download Key
        ↓
Create Rules
        ↓
Set conditions
        ↓
Choose destination
        ↓
Set priority
        ↓
Run Simulator
        ↓
Publish / Test Login

For most websites, start with simple group-based rules and only add Source URL, language or user-specific conditions when required.

ES Login Redirect Manager is designed to keep Joomla login routing predictable, testable and safe.

Extension Docs

ES Login Redirect Manager - Setup Guide