Advanced Template Manager Pro - Joomla Extension

Advanced Template Manager Pro Setup Guide for Joomla

Advanced Template Manager Pro is not meant to replace your site's design with a single click. Its purpose is to give you more precise control over Joomla template styles. In this guide, we will walk through how to prepare your site, install the extension, configure assignment rules, choose the right Include, Exclude, ALL, and ANY logic, verify the result on the front end, and avoid the usual pitfalls involving cache, menu items, and template frameworks.

This article is aimed at Joomla administrators, webmasters, and developers who already understand the difference between a template and a template style, but want to assign different visual variants based on more than just menu items. If the short product description above answers the question "what is it," the goal here is different - to show how to use the extension safely in a real production scenario and how to confirm that a rule behaves exactly as intended.

There is also one important limitation to keep in mind: the official Regular Labs documentation for Advanced Template Manager applies to the Joomla 3 branch and explicitly states that there is no version for Joomla 4+. So before installing it, do not just download the archive - verify your actual site version, template state, framework type, and migration plan. For new sites running modern Joomla versions, other approaches will usually make more sense. For supported Joomla 3 projects, however, the extension can still be a useful tool for fine-grained control over site appearance.

What Problem an Advanced Template Manager Actually Solves

In standard Joomla, a template style is usually assigned through the template manager or through a specific menu item. That approach is clear and reliable, but it quickly becomes limiting when the same section needs to change appearance based on more specific criteria such as article category, language, user group, component, tag, device type, URL, or a time-based condition. Advanced Template Manager Pro extends that exact layer of control - it lets you assign template styles based on a set of conditions rather than only on a direct "menu item - style" relationship.

The key idea is simple: the extension does not create a new template or design your layout. It controls which already installed template style should be applied in a specific situation. That means you need the styles themselves in place before you begin configuring rules: for example, a main style, a catalog section style, a members-only section style, a seasonal landing page style, or a style for a specific component.

Its practical value is especially clear on older but still active Joomla 3 sites that have grown over time. Those projects often accumulate hidden menu items, duplicate categories, separate store or catalog components, multiple languages, and different user audiences. If you try to manage design only through the menu system, administrators end up creating workaround menu items, getting lost in Itemid values, and manually checking dozens of URLs. Advanced Template Manager Pro moves control closer to the actual display conditions and makes the rules easier to understand.

At the same time, the product does not override Joomla's core logic. If a page does not match any special assignment, it will continue using the default style. That fallback behavior is important: a misconfigured rule usually should not "break the entire site," but it can still cause the expected style not to appear where you intended it to.

Where the Extension Really Helps

Advanced Template Manager Pro is useful when a site has several visual variants and those variants need to be activated by rules. For example, the blog may use one color accent, the product catalog another, the private area a third, and a temporary promo page may need a separate style enabled only during a specific period. The standard template manager handles simple menu assignments well, but it is much less flexible when conditions depend on content, users, or components.

Another strong use case is maintaining large sites where you cannot justify rewriting a template for one group of pages. Instead of editing files, you can create a copy of a style, change the template parameters inside that copy, and assign it only where needed. That approach is easier to roll back: you disable the assignment or switch it back to Ignore instead of hunting down modified code inside template files.

Where the Product Does Not Replace Other Tools

The extension is not a page builder, layout editor, module output system, or migration tool for moving to a newer Joomla version. If you need to control modules by condition, Advanced Module Manager is closer to the task. If you need to show or hide a piece of text inside an article, Conditional Content is a better fit. If the site is already built on a modern template framework that overrides Joomla's template logic, Advanced Template Manager Pro may be incompatible or simply unnecessary.

The right way to frame the task: first identify which template styles already exist and under what conditions they should be applied. If you start by installing the extension instead, it is easy to end up with a pile of rules and no clear result.

Compatibility, Limitations, and the Installation Decision

Before installing Advanced Template Manager Pro, the most important thing to check is not the feature list but the site context. Official Regular Labs materials refer to Joomla 3, the minimum requirements for that branch, and the lack of a Joomla 4+ version. That means the extension makes the most sense for a supported Joomla 3 project where style control matters more than an immediate migration. For a new site on Joomla 4, 5, or 6, this product should not be your first choice.

The second critical question is the template framework. Regular Labs documentation states that Advanced Template Manager relies on Joomla's core template functionality, while some frameworks completely override how templates and template management work. The incompatible frameworks listed in the documentation include Astroid Framework, Gantry, JoomlaXTC, RSJoomla, T3, and Warp. If the site is built on one of those solutions, start by evaluating an alternative path rather than installing the extension.

Who the Extension Is a Good Fit For

The extension works well for sites that already have several styles for one or more templates and need precise assignments for when those styles should be used. That could be an editorial site with distinct content sections, a catalog with a dedicated style for item pages, a multilingual project, a user-only area, a seasonal promo page, or an agency site where the client often asks to "make this section look a little different" without rebuilding the whole template.

A strong candidate is a site where the administrator knows how to verify the style on the front end, understands the difference between a template style and a template file, has a backup, and can test rules on a site copy. In that environment, Advanced Template Manager Pro helps bring order: color labels, descriptions, and notes make a long style list easier to manage, while the assignments view shows why a style is being applied to a particular page.

Who Should Choose Another Path

The extension may not be a good fit if the site already runs on a modern Joomla branch, if migration is planned soon, if design is controlled entirely inside the template framework, if there is no access to a staging copy, or if the real issue is module output rather than template styles. In those cases, adding another component will not solve the root problem and may make maintenance harder.

You also should not use Advanced Template Manager Pro as a way to "fix" a chaotic menu structure. If the site has duplicated content, incorrectly configured menu items, wrong category assignments, or the same URL opening under different Itemid values, fix the Joomla structure first. The extension works best when it strengthens a clear architecture rather than compensating for disorder.

What to Check Technically

• The Joomla version matches the product's official documentation and the actual archive you plan to install.
• The PHP version and database meet Regular Labs requirements for that extension branch.
• The site is not using an incompatible template framework, or compatibility has already been confirmed on a staging copy.
• You have a backup of both files and database, along with a clear rollback path.
• There are at least two template styles that genuinely need to be switched between.
• Joomla cache and third-party caching extensions can be temporarily disabled or cleared to verify results.
• The user configuring the product has permission to work with templates and component settings.

The takeaway from this stage is straightforward: if the site is on a suitable Joomla branch, the template does not override assignment logic, and the task really is about template styles, you can move on to installation. If any of those points raise doubts, it is better to test on a site copy first and write down the expected outcome.

Installation and the Initial Check in the Joomla Admin Panel

The official Regular Labs instructions describe several installation methods: through the standard Joomla installer, by uploading a ZIP archive, and through the Regular Labs Extension Manager. For the Pro archive, the usual options are uploading the package directly or using the Regular Labs manager if it is already set up. This article does not cover purchasing, license keys, or obtaining the paid version - the focus here is configuring an installation file you already have.

Before installing, open a staging copy of the site or at least prepare a fresh backup. The extension affects the template manager and adds a system plugin, so testing it on a live site without a rollback option is poor practice. The installation process itself is similar to installing any Joomla extension: the administrator opens the installer, uploads the ZIP package, waits for the success message, and then checks whether Advanced Template Manager now appears in place of the standard template manager.

Basic Installation Steps

1. Log in to the Joomla admin panel with a user who has permission to install extensions and configure templates.
2. Open the extension installation section. In Joomla 3, the path is typically Extensions - Manage - Install.
3. If you are using a ZIP archive, select the Upload Package File tab, choose the file, and start the installation.
4. After installation, open the template manager through Extensions - Templates.
5. Check that the link opens the Advanced Template Manager interface rather than the standard com_templates.
6. Open the site style list and confirm that you can see existing front-end styles, not only administrator templates.

If the interface does not change after installation, do not rush into creating rules. First check whether the extension's system plugin is enabled, whether the installation completed correctly, and whether there is a conflict with the template or an outdated Regular Labs Library version. The official changelog includes fixes related to installing over an older Pro version and updating the library, so on older sites it is important not to mix random packages from different periods.

What Should Change After Installation

According to the official documentation, once the extension is installed, the Templates link under Extensions no longer opens the standard template component and instead opens Advanced Template Manager. In the styles list, you get additional conveniences such as color labels, descriptions, notes, and an expanded assignments tab. That does not mean every style automatically starts working under new rules. As long as assignments remain set to Ignore, the site should behave much as it did before.

The initial check should be very boring: open the homepage, a category page, an article, and a component page, and make sure the appearance did not change on its own. If you see changes before you configure any rules, there is likely a conflict, an old assignment, or a cached result. Fix that before adding new conditions.

How to Update or Remove the Extension Safely

Regular Labs states that a standard update can be installed over the existing version without uninstalling it, and settings should be preserved. But for major changes and removal, you should expect some configuration loss. In practice, that means documenting important assignments before updating, taking screenshots of styles, and noting where each rule is used. After the update, verify not just the extension list but the actual result on front-end pages.

If you need to remove the extension, first disable the special assignments or return key styles to a simple standard configuration. Then remove the component and plugins through the extension manager. After removal, confirm that the site is using Joomla's default template logic again and that important menu items have the correct styles assigned.

Post-Install Setup: What to Enable and What to Hide

After installation, do not open every style and enable dozens of conditions right away. Start with the global Advanced Template Manager settings. The tool panel includes an Options button that opens the component parameters. These settings do not choose a style for a specific page, but they do determine how usable and efficient the admin interface will be.

The official configuration includes options for showing the heading, thumbnails, the color column, descriptions, the notes tab, a switch to the standard template manager, update notifications, the user actions log, and permissions. For most sites, it makes sense to enable only what actually helps manage a large list of styles. The fewer unnecessary elements you have on the editing screen, the lower the risk of making assignment mistakes.

Style List Settings

The color column and color list are useful when a site has many styles. For example, you can mark the main production style with a neutral color, experimental styles with another, and temporary campaign styles with a more visible accent. Color does not affect the front end at all - it exists only for the admin panel. That makes it a safe setting that is easy to enable and just as easy to disable.

The description field and notes tab help you remember why a style exists. On large projects, that matters more than it seems. Six months later, an administrator sees a similarly named style and has no idea whether it is safe to remove. A short description such as "News category, Russian version only" or a note explaining the reason for the rule saves time and reduces the risk of accidental cleanup.

Show Assignments and Admin Performance

The Show Assignments tab lets you disable assignment types you do not use. The official documentation explicitly recommends turning off unnecessary assignment types so style editing screens show only the options you actually need and the page is easier to work with. This is not a front-end "site speed booster" - it is a way to reduce noise and make configuration safer.

For a typical site, you can keep Menu Items, Home Page, Languages, Joomla Content, Categories, Articles, Tags, User Group Levels, Components, URL, and Templates. Conditions based on browsers, operating systems, devices, IP, or geolocation should only be enabled for real use cases. Device detection and IP geolocation are not perfectly accurate, so they are a weak foundation for critical design logic unless you also have a fallback.

Activity Log and Permissions

Advanced Template Manager can keep a more detailed user action log than the basic template manager. That is useful for teams where multiple administrators change styles. If a section suddenly looks different, the log can help identify who changed the style, assignment, or file. On a single-admin site, you can leave the log disabled if you do not need it and are not reviewing editor actions.

The extension inherits permissions from Joomla's template manager rules. So do not create a separate, confusing access model. If an editor does not need to manage styles, do not give them access to the component. If you need a dedicated user for template maintenance, configure the rights through Joomla ACL and test login with that user. It is better to start with fewer permissions and expand them after verification than to give every content administrator control over the site's design.

Recommended Safe Starter Configuration

After saving the global settings, open one test style and make sure the assignments tab is shorter and easier to read. If you hid an assignment type you still need, restore it in Options. That is a safe rollback: you are not changing style rules, only the visibility of condition types in the interface.

Assignment Logic: Ignore, Include, Exclude, ALL, and ANY

The most common mistake with Advanced Template Manager Pro is thinking of assignments as a simple list of checkboxes. In reality, each assignment type has a state, and several active conditions are connected through a matching method. As long as all conditions remain set to Ignore, the style has no special restrictions. The moment at least one condition is switched to Include or Exclude, the style begins applying only to situations that pass the rule logic.

Regular Labs documentation describes three states: Ignore, Include, and Exclude. Ignore means that assignment type does not participate in the decision. Include means the style applies to pages that match the selected condition. Exclude means the style applies to pages that do not match the selected condition. In practice, Exclude is useful for exceptions, but it becomes risky when combined with the wrong ALL or ANY method.

How to Read Include and Exclude

Imagine a style called "Catalog." If you select the "Catalog" category under Joomla Content and set it to Include, the style should apply to pages in that category. If you select the same category and set it to Exclude, the style should apply everywhere except that category, assuming the other conditions also allow it. That is why Exclude is rarely a good sole condition for a new style. More often, it is used as a supplement: apply the style to a section, but exclude one page or one subgroup.

The Ignore state is especially important for keeping rules clean. Do not leave an active condition enabled "just in case." If an assignment type is not part of the logic, it should stay on Ignore. That makes the rule easier to read and speeds up troubleshooting because you can see only the conditions that actually affect style selection.

Why the ANY Method Can Unexpectedly Broaden Display

The ALL method means every active condition must match. The ANY method means a match on just one condition is enough. For simple inclusion rules, ANY can be convenient - for example, a style applies either to a category or to a specific URL. But once Exclude enters the picture, ANY often produces results that are far too broad. The official documentation warns that when one or more Exclude conditions are present, ALL is usually the safer choice because a single excluding condition may end up matching almost everywhere.

A reliable working rule is this: if you are unsure, start with ALL and a small set of Include conditions. Add Exclude only after the base display has been confirmed. After every change, clear the cache and test two groups of pages: those where the style should appear and those where it definitely should not.

How the Default Style Behaves

Pages that do not match any special assignment use the default style. That is not an error - it is Joomla's built-in safety net. Because of that, when configuring a new style, it helps to keep a simple expectation table nearby: URL, expected style, reason, and verification method. If a page remains on the default style, then it failed the condition, the rule was not saved, the style is disabled, cache is interfering, or another style has a more appropriate assignment.

Do not verify only the positive result. If the style should appear on three pages, also find three pages where it should not appear. Without that negative check, the rule may turn out to be too broad.

Practical Ways to Use It on Real Joomla Sites

Advanced Template Manager Pro shows its value not in an abstract feature list but in concrete scenarios. Below are ideas based on documented assignment types: Joomla content, categories, articles, tags, languages, users, components, URL, devices, and time-based conditions. This is not a call to enable everything at once. Pick one scenario, configure it on a site copy, and only then bring that approach into a production project.

Different Styles for Editorial Sections

If a site includes news, a knowledge base, and a catalog, each section can use its own style based on the same template. Inside the style, you change template parameters such as accent color, container width, position set, or header and footer appearance, assuming the template itself supports those changes. Advanced Template Manager Pro handles only the assignment: the "News" category gets one style, the "Catalog" category another, and the rest of the site stays on the default style.

Verifying the result is straightforward: open an article from the target category, an article from a neighboring category, and a page with no relevant category condition. If the first gets the intended style, the second stays unchanged, and the third is unaffected, the rule is configured cleanly. If the style appears on too many pages, check the Include/Exclude state and the handling of child categories.

Separate Design for Users or Groups

On membership or restricted sites, you may want logged-in users to see a different visual context: fewer promo blocks, a different header, separate navigation, or a more compact interface. In that case, you create a template style with those parameters and assign it by user group or user state. This scenario is especially sensitive to caching: guest and logged-in pages may be cached differently, so verify the result in two browsers or in a private window.

If the task is really just about showing or hiding a module, do not use a template style as a heavy workaround. For modules, Advanced Module Manager or standard Joomla module settings are a better fit. Change the template style only when the overall layout, template parameters, or visual system of a section actually changes.

Multilingual Sites with Different Template Accents

Language-based conditions are useful when site versions differ not only in text but also in presentation: a different logo, a different set of positions, a local banner, or a separate footer structure. In that case, you can create a style for each language version and assign it to the corresponding language. But remember that Joomla language settings, menu items, and article associations still need to be configured correctly. The extension will not fix a poorly configured multilingual site.

Temporary Campaigns or Seasonal Sections

Date and time conditions let you prepare a style for a promo section or a temporary visual variation. The important detail is that these conditions rely on server time, not the visitor's clock. So before launch, verify the Joomla time zone, server time, and cache behavior. If a page is heavily cached, a time-based condition may not appear immediately for all users.

Pages from a Specific Component

Component-based assignment helps when a third-party component outputs pages with a distinct structure. A catalog, forum, form, store, or documentation section may require a different container and a different set of module positions. In this scenario, do not test only the component homepage - also test nested pages such as list views, detail pages, forms, search pages, error pages, or empty results. Some components use multiple views, and a single rule may not cover everything you expect.

Practical Example: A Separate Style for a Knowledge Base Section

Let us walk through a scenario that often appears on real Joomla sites. The site has a main company section and a knowledge base section. The knowledge base needs a narrower container, a different heading color, fewer distracting blocks, and a different set of module positions. The template already supports those differences through a style. Our task is to assign that special style only to knowledge base articles and make sure everything else stays unchanged.

Goal

Apply the "Knowledge Base" style to articles in the knowledge base category, including child categories, but not to news, the homepage, contacts, or store pages. This is a useful example because it relies on content structure rather than just a menu item.

Preparation

• The staging copy already has a knowledge base category and several published articles.
• A template style has been created or duplicated with the required appearance changes.
• Joomla cache is temporarily disabled or a cache-clearing routine is ready after each change.
• The administrator has a control list of URLs: a knowledge base article, a child category page, a regular news article, the homepage, and a component page.

Configuration Steps

1. Open Advanced Template Manager and go to the site styles list.
2. Open the style that should apply to the knowledge base.
3. Enable a color label and description so the purpose of the style stays obvious later.
4. In the assignments tab, find the block related to Joomla Content or categories.
5. Select the knowledge base category and set the state to Include.
6. If child categories should be included, enable the corresponding child-item option if your assignment type provides it.
7. Leave all other condition types on Ignore until the base rule has been confirmed.
8. Set Matching Method to ALL if more than one condition is active or if you plan to use Exclude.
9. Save the style, clear the cache, and open the control URLs.

Verification

On a knowledge base article, the new style should appear. On an article from a regular news category, the style should not appear. The homepage and contacts page should keep the default style or any previously assigned style. If the knowledge base has child categories, test an article from a child category separately. Do not trust only what the admin panel shows: the truth is on the front end after cache has been cleared.

What Can Go Wrong

If the style does not apply, check whether the article is being opened through a menu item that creates a different context, whether the child-category option was missed, whether the condition type was accidentally left on Ignore, and whether cache is interfering. If the style appears on extra pages, check whether the selected page type is too broad or whether ANY is being used with multiple conditions.

How to Roll Back This Example

Do not delete the style immediately when rolling back. First switch the active assignment back to Ignore, save the style, and clear the cache. If the front end returns to its previous appearance, the rule was the source of the change. After that, you can remove the test style or keep it with a clear note if it may be useful later.

Verifying the Result, Cache, and the Right Investigation Order

After configuring a rule, you need to prove that it works consistently. Opening one page in the same browser session you just used in the admin panel is not enough. Joomla, the browser, server-side cache, third-party optimization extensions, and the template framework may all show outdated results. That is why verification should look more like a small test plan.

Create a table of URLs and expected styles. Include at least two pages where the style should apply and two pages where it should not. If the rule depends on user state, test both a guest and a logged-in user. If it depends on language, test each language version. If it depends on date or device, write down the test conditions, otherwise it will be hard to understand a changed result later.

Verification Order After Every Change

1. Save the style and confirm that Joomla does not show a save error.
2. Clear Joomla cache and any third-party optimizer cache in use.
3. Open the page in a private window or a different browser.
4. Check the visual markers of the style: color, width, module positions, header, footer, or another parameter you defined in advance.
5. Check a negative example where the style should not appear.
6. Record the result in the style notes or in the project's internal checklist.

If the site uses aggressive caching, you can temporarily add a small safe visual marker to the template style that is easy to remove, such as changing the color of a secondary bar or enabling a visible but harmless setting on a staging copy. Do not edit core files or inject temporary code into a production template unless there is no other option.

How to Tell an Assignment Problem from a Template Problem

Sometimes an administrator thinks the rule is not working even though the style is being applied, but the template itself is not changing any visible parameter. That is why you should create an obvious difference between styles before testing assignments. For example, in the test style, change the color scheme, logo, or container setting in a way that definitely affects the front end. If the styles look identical, you will not be able to verify the assignment visually.

If the correct style is selected for the URL but the appearance is still wrong, the issue may be in the template, module positions, CSS, overrides, or cache. If the style is not being selected at all, the problem is more likely related to assignments: category, language, user, component, Matching Method, or a framework conflict.

How to Maintain Rules So the Site Does Not Turn into a Pile of Exceptions

Advanced Template Manager Pro is easy to start using as a quick answer to every new request: "make this section look different," "change the layout for these users," "the promo page needs a different header." In the short term, that is convenient. In the long term, the site can end up with dozens of similar styles that nobody fully understands - which one is active, which one was temporary, and which one was just a test. That is why rule maintenance should be planned early, while the number of assignments is still small.

The first maintenance rule is naming. Do not name styles based on mood. A name like "Blue copy 2" explains nothing. A name like "Knowledge Base - Narrow Container" or "Catalog - Product Cards" gives real context. If the template and interface allow descriptions, use them to answer three short questions: where the style is used, why it exists, and who is responsible for changes. The Notes tab is the right place for longer context: a task reference, a list of control URLs, the date of the internal review, or the reason a temporary rule exists.

The second rule is not to mix permanent and temporary assignments. A permanent knowledge base style may stay in place for years. A temporary campaign style should have a clear deactivation date in the internal note. Even if you do not write dates in the public article, dates in the project admin help prevent forgotten rules. If a temporary assignment relies on Date & Time, still verify it after the campaign ends: the condition may stop matching, but the style and note will remain in the list.

The third rule is to keep the assignment map outside the administrator's head. For a small site, a simple table in a working document is enough: style, condition, pages, exceptions, verification, owner. For a larger project, it helps to keep that map next to the site's documentation. If one administrator leaves the project, the next specialist should be able to understand the style logic without investigating every menu item and category from scratch.

How to Review Existing Styles

Every few months, open the style list and check which styles are actually still in use. Start with classification rather than deletion. Permanent styles get a clear description and a color label. Test styles are moved into a separate color group or renamed with an obvious marker. Questionable styles should first be disabled on a staging copy and checked against control URLs. Only after that should they be removed or merged.

Pay special attention to styles with many Exclude conditions. That is often a sign that a rule grew out of a series of urgent fixes. If a style applies to almost the entire site except for ten exclusions, it may make more sense to make that style the default or rebuild the logic around clearer Include conditions. That is not always necessary, but it is a question worth asking before the exclusion list becomes unmanageable.

What to Consider Before a Site Migration

For Advanced Template Manager Pro, migration risk matters especially because the official documentation is tied to Joomla 3 and does not promise a version for Joomla 4+. If the site is going to be moved to a modern Joomla branch, do not create new complex rules unless there is a strong reason. First document what each rule is actually solving: assignment by category, language, user group, component, URL, or a temporary campaign. Then identify the future path for each case: standard Template Styles, capabilities of the new template, YOOtheme Pro templates, Advanced Module Manager for modules, Conditional Content for text fragments, or custom development.

Good migration preparation means you do not copy the old set of rules blindly - you migrate the intent. For example, if an old rule changed the style for knowledge base articles, on the new site that may become a separate page template in a builder, a distinct style within the template, or a different menu structure. If the old rule changed appearance only for the sake of a single module, the better migration path is to move that logic into module handling rather than creating a full-page style again.

Before a major site rebuild, preserve not just the extension list but also the Advanced Template Manager rule map. Without it, the team will see "lots of styles" but will not understand which business problems those styles were actually solving.

Using Custom PHP Assignments Safely

Advanced Template Manager includes a Custom PHP Assignments option. The official documentation describes it as a way to return true or false based on available Joomla data. It is a powerful tool, but it should be your last option, not your first. Start with built-in assignments: menus, categories, articles, languages, user groups, components, and URL. PHP should be used only when a built-in condition truly cannot express what you need.

The main risk with Custom PHP is not syntax - it is maintainability. A few months later, another administrator may have no idea why a style is being triggered, and one coding mistake can break template selection. That is why every PHP snippet should be short, readable, tested on a site copy, and documented in the style Notes. Do not use this mode to bypass access rules, payment logic, authentication, or to hide errors.

Minimal Safe Example

The example below shows the basic principle: the condition returns true only for a logged-in user. In a real project, a built-in user group assignment is often the better option, but this example is a safe way to verify how Custom PHP works. It relies on the $user variable, which the Regular Labs documentation lists among the available objects for PHP assignment.

// Custom PHP assignment in Advanced Template Manager
// The style applies only to logged-in users.
// Test this on a staging copy first.
return isset($user) && !$user->guest;

Verification: save the condition on a test style, clear the cache, and open the page as a guest and as a logged-in user. Rollback: switch Custom PHP back to Ignore or remove the code from the condition, then clear the cache again. If you cannot explain the code in a one-line note, it is too complex for this location.

When a PHP Condition Is Justified

Custom PHP may make sense if the condition depends on a specific template parameter, a non-standard user characteristic, or an unusual component state that cannot be expressed through standard assignments. But even in those cases, first check whether there is a more conventional solution through category, tag, URL, user group, language, or component. The closer the rule is to standard Joomla data, the easier it will be to maintain.

Do not paste large PHP fragments into a style assignment. If the logic has grown into multiple branches and database queries, that is no longer template configuration - it is a separate development task that belongs in controlled code and should be tested independently.

Troubleshooting Common Template Style Assignment Problems

Advanced Template Manager Pro issues almost always come down to one of five areas: an unsuitable Joomla version, an incompatible framework, incorrect condition logic, cache, or the expectation that a style will change something controlled by another tool. Below is a practical troubleshooting order with no unnecessary panic and no core edits.

The Style Does Not Apply to the Intended Page

Symptom: the style is saved, but the public page still shows the old design. Possible causes include the condition still being set to Ignore, the wrong category being selected, child items not being enabled, the page opening through a different menu item, the rule failing under the Matching Method, or the result being served from cache.

Check this by temporarily simplifying the rule to a single Include condition, clearing the cache, and opening the page in a private window. If the style appears, add the other conditions back one at a time. If it does not, verify that the page really belongs to the selected category, language, component, or URL.

The Style Appears Where It Should Not

Symptom: the new style shows up in neighboring sections or across nearly the whole site. A common cause is a condition that is too broad or the use of ANY together with Exclude. Switch the matching method back to ALL, disable unnecessary conditions, and test negative URLs.

Fix: start with the narrowest possible Include logic and add Exclude only for specific exceptions. If the rule is complex, write a note inside the style describing which pages should match, which should not, and why.

Nothing Changes Visually After Configuration

Symptom: it looks like the rule is not working, but everything in the list appears to be configured correctly. A possible reason is that the selected style is almost identical to the main style, the template parameters do not affect that page type, or the result is being overridden by CSS or a module position.

Check this by temporarily changing an obvious parameter in the test style on a site copy. If the change becomes visible, the assignment works and the problem is in the specific template settings. If not, go back to diagnosing the rule itself.

The Site Uses an Incompatible Template Framework

Symptom: the rules behave unpredictably or are ignored, while the template is controlled by its own framework. The official Regular Labs documentation notes that some frameworks override Joomla's core template logic, and Advanced Template Manager depends on that core logic.

Fix: do not try to force the extension to work on that kind of project. Check the framework's own settings, the capabilities of its built-in template manager, YOOtheme Pro templates, module assignments, or separate CSS-based solutions. If the real need is only module output, use a module-oriented tool instead of a template style.

Problems After an Update or Removal

Symptom: part of the configuration disappears after an update, the interface changes, or the site falls back to the standard template manager. Possible causes include a major version change, an older Pro branch, package removal, or a mismatch in the Regular Labs library.

Check this by restoring a backup in a test environment, comparing the styles and assignments list, reviewing the activity log, and checking enabled plugins. If the extension must be removed, first return key pages to standard Joomla assignments and only then uninstall the component.

Cache Gets in the Way of Verification

Symptom: one user sees the new style, another sees the old one, or the result changes only after several refreshes. Check Joomla system cache, template cache, third-party optimizers, browser cache, and server-side cache.

Fix: while troubleshooting, disable or clear cache, test the page in a private window, and record the result. If the rule depends on user state, language, device, or time, configure caching so it does not mix those different states together.

When Advanced Template Manager Pro Is the Right Choice

Advanced Template Manager Pro makes sense on a Joomla 3 project that already has multiple template styles and has outgrown standard menu-item-based assignments. It is especially useful for scenarios involving content sections, user groups, languages, components, time-based conditions, and a clear need to manage design without editing template files.

Before rolling it out in production, verify compatibility, create a backup, enable only the assignment types you actually need, build one test scenario, and confirm it on both positive and negative URLs. If everything works consistently, you can download the ZIP archive and repeat the setup on your own project carefully, starting from a staging copy and with a clear rollback plan.

If the site already runs on a modern Joomla version, is built on a framework that manages templates on its own, or if the real task is about modules and individual content blocks, choose a different tool. The best solution here is not the most powerful one, but the most direct one: change a template style only when what you truly need to change is the template style itself.