Better Preview Pro - Joomla Extension

Guide to Setting Up and Validating Previews in Better Preview Pro

Better Preview Pro is not meant to decorate the Joomla admin panel. It solves a specific editorial problem: quickly seeing how an article will look on the public-facing site without manually going to the homepage and guessing the right menu item. In this guide, we will look at how to use the extension as a practical tool for editors, webmasters, and administrators of older Joomla sites: what to check before installation, which settings to enable first, how to verify the result, and what to do if the preview points to the wrong page.

This article is written with an important limitation from the official Regular Labs documentation in mind: Better Preview belongs to the Joomla 3 line, and for newer sites the developer recommends Better Frontend Link. Because of that, this guide does not promise universal compatibility. We will look separately at when Better Preview Pro still makes sense on a supported copy of an older site, and when it is safer to plan a replacement, a migration, or a different workflow.

The core workflow here is simple: an editor opens an article in the admin panel, clicks the preview button or the enhanced public-side link, lands on a page with the correct template, modules, and active menu item, and then checks whether the text, images, fields, and page context match expectations. The main value of Better Preview Pro is reducing manual checks before publication, but that value only appears after careful setup of menus, cache, and exclusions.

What Problem the Extension Solves for Joomla Editors

In Joomla, an article's appearance depends on more than just the text itself. The final page is shaped by the menu item, template, assigned modules, category, component parameters, SEF URL settings, access permissions, and cache. That is why the standard "go to site" button often does not answer the editor's main question: how exactly will this article look in its real context. Better Preview Pro tries to close that gap between the editing screen and the live page.

The official documentation describes two core mechanisms. The first is an article preview button that opens a modal window showing the article before saving or publishing. The second is an enhancement of the standard View Site link in the admin panel: instead of taking you to the homepage, it can lead to the public equivalent of the item you are editing and show a dropdown with parent pages, such as categories, along with the homepage.

For editors, this means more than just a more convenient button. The extension changes the content review habit itself: instead of the chain of "save draft, open the site, find the section, go to the article, refresh the page," you get a much shorter path from the editing form to the page a visitor will actually read. This is especially noticeable on sites with long menus, hidden utility items, multiple categories, and different module positions.

Where the Impact Is Most Noticeable

Better Preview Pro is especially useful in editorial workflows where an article goes through several rounds of revisions before publication. For example, a content manager checks the lead, images, tables, links, and headings, then passes the page to an administrator for final review. If the public URL has to be found manually every time, the process becomes slow and unpredictable.

Another common case is a site where an article looks different without a menu item than it does inside the correct category. Joomla uses the active menu item to choose output settings, the template, and the module context. If the preview does not understand that context, the editor may see a page without the required sidebar modules, with different layout markup, or with a URL that does not match the eventual public route.

What the Extension Should Not Replace

Better Preview Pro is not a publication approval system, a visual builder, or a migration tool. It does not fix template errors, it does not make an older Joomla branch secure on its own, and it does not guarantee that a third-party component will support preview correctly. Its role is narrower: to provide a convenient link or modal window for checking content in the context of the site. If your project needs a full editorial workflow with roles, statuses, and a revision log, Better Preview Pro can be part of that process, but it should not be the center of it.

Current Product Status and Compatibility You Cannot Ignore

The most important part of evaluating Better Preview Pro is not the button list, but compatibility. In the official Regular Labs documentation for Better Preview, it is clearly stated that this documentation is for Joomla 3, and there is no Better Preview version for Joomla 4 or later. The same source recommends Better Frontend Link for newer Joomla branches. This is not a minor footnote. It is a practical limitation that should drive the adoption decision.

If the site is still running on an older Joomla branch and cannot be migrated quickly for technical reasons, Better Preview Pro can be considered a tool for careful editorial checks. But before installing it, you need to assess the environment honestly: who maintains the site, how backups are handled, where the extension is tested, whether there is a migration plan, and whether the team understands the risks of working on an outdated platform.

Do not install Better Preview Pro as a way to postpone migration. If the site can be moved to a current Joomla branch, it makes more sense to look at Better Frontend Link or the built-in tools of the newer version, and keep Better Preview only for an older working copy where the environment actually supports it.

How to Interpret Information About the Pro Version

Older materials about Better Preview often mention both free and paid editions. A third-party Joomlashack tutorial notes that the copy-to-clipboard link feature belonged to the paid version, while an official Regular Labs video shows the Pro version being installed through Regular Labs Extension Manager when access to Pro packages is available. You should not build a critical workflow around a single paid feature unless you have confirmed that it is included in your package. Structure the process so it still works without link copying: the real priority is correct preview behavior and the correct public route.

What Conclusion to Reach Before You Start

Before installation, answer one simple question: are you maintaining an existing Joomla 3 site, or are you trying to improve a modern site running Joomla 4, 5, or 6? In the first case, Better Preview Pro can be useful as a supporting tool. In the second, it is better not to waste time trying to force an unsuitable extension into place. Go straight to Better Frontend Link and check whether it covers your workflow for moving from the admin panel to the public page.

Who Better Preview Pro Fits, and Who Should Take a Different Route

The extension is a good fit for teams that regularly edit content in Joomla and spend time manually checking the public-facing view. That can include information sites, corporate portals, article catalogs, educational sites, and older client projects where the menu structure is more complex than a homepage plus a few articles.

Better Preview Pro is useful for the editor who wants to see the article inside the site's template, the webmaster who checks the active menu item and module context, and the administrator who wants to give the team a clearer review path. But the product may not be a good fit if the whole team already works on a current Joomla branch, if the site relies mostly on a third-party component without preview support, or if the real problem is not finding the page, but an outdated template, PHP errors, or an insecure environment.

This may seem like a strict filter, but it saves time. A convenient preview button should not hide the project's technical debt. If the extension is being installed on an older site, security and rollback options should be checked first, and editor convenience second.

What to Check Before Installing on a Live Site

Preparation matters because of the nature of the product: Better Preview Pro affects the admin-side preview workflow and the link that leads to the public-facing page. This is not just a simple text plugin that you can enable and forget. A poor configuration may not break the entire site, but it can easily confuse editors: the button will appear, the link will point to the wrong place, the modal window will show an outdated version of the page, and the team will decide that the content is formatted incorrectly.

Backup and Staging Copy

Before installation, create a backup of both files and the database. If the project is maintained regularly, it is better to test the extension on a staging copy. This matters especially on older sites, where you may have template customizations, old editors, non-standard content plugins, or modified core files. In its general FAQ, Regular Labs explicitly notes that support assumes a clean environment without modified core or extension files.

Joomla Version and Replacement Plan

Make sure the site actually belongs to the Joomla branch Better Preview was built for. If the project is already on a newer branch, do not try to force an old extension to work against the documentation. Newer branches have Better Frontend Link, which addresses a similar need: jumping to the public equivalent of a page.

Menus, Categories, and Hidden Items

The main source of strange preview behavior in Joomla is usually not the button itself, but the relationship between the article and the menu item. In Joomla, the menu item determines not only the URL, but also the page output parameters. So before enabling Better Preview Pro, it is worth opening the menu structure and understanding which categories have their own menu item, which articles are displayed through Category Blog or Single Article, and which are not attached to any menu at all.

If an article has no obvious menu path, preview may use a route without an active menu item or rely on the Default Menu ID parameter. That is not a product bug. It is a consequence of Joomla's logic. It is better to create a hidden utility menu item for the category or choose a default item in the settings ahead of time than to explain later why the page opened without the expected modules.

Access Permissions and Editorial Roles

Check who will see the preview button and who will be able to change the system plugin settings. Editors usually only need to use the button. Settings should remain in the administrator's hands, because excluded components, the default menu selection, or cache purging can affect the entire team's workflow.

Installation and the First Check Without Unnecessary Risk

The official Regular Labs video describes several installation methods: uploading the package through the Joomla installer, installing through Install from Web, and using Regular Labs Extension Manager. For an older Joomla site, choose the method your project already uses and the team can control most reliably. If you already run several Regular Labs extensions, Extension Manager is convenient for updates and package visibility. If this is a one-time installation, a standard ZIP upload through the extension manager is enough.

Basic Installation Order

1. Create a backup and confirm that you can restore the site.
2. Download the Better Preview Pro installation package from a trusted source connected to Regular Labs or your legitimate project archive.
3. In the Joomla admin panel, open the extension installer and use the package upload tab.
4. After installation, find the Better Preview system plugin and make sure it is published.
5. Open a test article and confirm that the preview button and the enhanced public-side link are present.
6. Open the preview in editor mode and compare the result with the expected page on the site.

Do not start with fine-tuning. First confirm that the extension installed correctly, the plugin is enabled, the button appears, and the preview opens at all. If that basic check fails, additional parameters such as Default Menu ID or Purge Component Cache will only make diagnosis harder.

What Counts as a Successful First Check

A successful check is not just a modal window opening. Verify four things: the preview shows the current article, the page uses the expected template, the module context resembles the real public page, and the link does not send you to the homepage for no clear reason. If even one of these points is off, document the symptom and move to configuration, rather than publishing blindly.

Quick takeaway: after installation, you should have a testable chain of "editing form - preview button - public-facing result." Until that chain works on a test article, do not roll the process out to the full editorial team.

Better Preview Pro Settings Map After Installation

Better Preview settings are located in the system plugin parameters. The official documentation groups them into three areas: View Site link settings, preview button settings, and advanced settings. The most practical approach is to configure them in that order: first decide where links should appear, then how the button should behave, then how the extension should handle routing and cache.

View Site Link Options

In the View Site Options section, check where the extension should replace the standard link to the site. Display Title Link and Display Status Link control whether the link is transformed in the title area or the status area of the admin panel. If editors are already used to one specific location, do not enable everything at once. It is better to leave one clear entry point and train the team around it.

Reverse Status Link changes the order of items in the dropdown list. This is not a critical feature, but it affects team habits. If editors more often jump to the current article, let that item stay near the top. If they more often check the parent category, reversing the order may make more sense.

Show Type and Show URL Details help clarify where the link is going. On a simple site, you can leave them off to avoid cluttering the interface. On a site with a more complex structure, it is better to enable at least the URL details for administrators, so it is easier to see why one article routes through a category while another uses the default menu item.

Preview Button Options

The Preview Button Options section controls the button in the editorial workflow. Display Editor Button adds a button near the editor, while Display Toolbar Button places it in the toolbar. For a content team, it usually makes sense to enable both during testing, observe where editors actually click, and then keep the location that feels more natural.

Button Text should be set so the team does not confuse preview with saving. If the site interface is in Russian, you can assign a clear label such as "Preview." Technical wording is not helpful here: the editor cares about the action, not the routing mechanism.

Primary Button makes the button stand out visually. Only enable it if preview really is a required step before publication. If the button is too prominent on every page, it starts competing with save and close actions. Preview Window Width controls the modal width. For long articles, it is usually better to keep the maximum width or choose a value that does not break the site's template.

Advanced Options

The Advanced Options section contains the settings most likely to affect strange symptoms. SEF Index Timeout (hrs) is tied to the SEF address index. The documentation explicitly advises increasing the value if admin pages become slow. This is a good example of a setting you should not touch in advance: measure behavior first, then adjust it.

Purge SEF Index is useful when the URL structure has changed and preview still relies on old data. For example, if you moved a category, changed a menu item, or updated aliases in bulk. After purging the index, check several articles across different categories, not just a single page.

Purge Component Cache can clear the cache of the relevant component before previewing. This is helpful if editors keep seeing an old version of the page, but it may be unnecessary on a large site with aggressive caching. Enable it only after testing on a copy of the site, and check whether it slows down working admin pages.

Default Menu ID is one of the most important settings for sites with hidden or incomplete menus. It defines the active menu item for a URL when the extension cannot find a better match. Disable on Components lets you exclude components where preview is unnecessary or unreliable. It is better to exclude an unsupported component than to let an editor land on the wrong page every time.

The Preview Button and Enhanced View Site Link in Real Workflows

Better Preview Pro is useful because it gives you two different entry points into the review process. The preview button is for editors working inside an article who want to quickly see the current page. The enhanced View Site link has a broader role: it helps you jump to the public equivalent of the current admin page and to related parent pages.

When to Use the Preview Button

The preview button is useful before saving a draft, after inserting images, and when checking tables, quotes, lists, and embedded modules. Its job is to show the content in something close to its real presentation. If the modal window is too narrow or does not show the expected context, go back to the width setting and verify the relationship between the article and its menu item.

It is helpful to establish a simple editorial rule: before publishing, open the preview and check at least the title, the first screen, images, links, code blocks, tables, and sidebar modules. If the site uses different templates for different sections, the review should include at least one article from each important section.

When to Use the Enhanced View Site Link

The enhanced View Site gives you more navigational context. It can lead to the current article, the parent category, and the homepage. That is useful when an administrator is not just checking the text itself, but also the user's path: how a visitor reaches the section, which modules display at the category level, how the article list looks, and whether the route matches the intended site structure.

If an editor complains that "the button goes to the wrong place," first clarify which entry point they are using. Previewing an article and jumping to the parent category are two different workflows. Those two actions are often mistaken for each other and perceived as a bug, even when the extension is working correctly.

How Not to Confuse the Editorial Team

Do not enable every possible interface element without explanation. Create a short internal instruction: where to click for preview, when to check the parent category, what to do if the link leads to the homepage, and who to notify about an incorrect route. Better Preview Pro only becomes useful when the team knows what the correct result is supposed to look like.

Default Menu ID, SEF URLs, and the Logic of the Active Menu Item

The most product-specific part of configuring Better Preview Pro is its handling of the active menu item. The Regular Labs documentation explains that when previewing articles and categories, the extension tries to choose the most suitable menu item based on the object type and parent categories. If no suitable item exists, it may proceed without an active menu item, and if necessary you can specify a Default Menu ID.

To understand why this matters, you need to remember how Joomla works. A menu item is not just a navigation link. It defines the page type, output settings, part of the SEO configuration, the active template, and the module context. That is why two links to the same article can look different when they route through different menu items.

When You Need Default Menu ID

This setting is worth configuring when some content has no public menu item of its own, but still needs to be checked in a specific context. For example, all news items may be displayed through a hidden "News" menu item, while individual articles are not placed in the main navigation. In that case, the default item helps Better Preview Pro choose a predictable context.

Do not use a random homepage as the default. It is better to create a utility menu item that matches the content type: Category Blog for a section, Single Article for a specific utility page, or another type that truly reflects the site structure. Even if the item is hidden from menus, as long as it is published, it can still define the correct route.

How to Verify That the Correct Route Was Chosen

1. Open an article from a category that has an explicit menu item.
2. Click preview and check whether the URL matches the expected structure.
3. Open an article from a category without a separate menu item.
4. Check whether Default Menu ID was used and whether the correct modules appeared.
5. Change the default item only on a test copy and repeat the check.

If the preview still shows the old route after you change the menu setup, clear the SEF index in Better Preview settings and then clear Joomla's system cache. Do not make several changes at once: first the menu, then the index, then the cache. That makes it much easier to see what actually fixed the issue.

Why the Preview May Differ From the Published Page

A difference can be normal if the article is not published yet, is available only to a specific user group, or uses plugins that behave differently inside a modal window. But if the difference affects the template, modules, menu, or URL, you almost always need to inspect the active menu item and the cache. Better Preview Pro helps you spot the problem faster, but it does not override Joomla's standard routing logic.

Practical Example: Checking an Article Before Publication

Let us walk through a realistic scenario. On an older corporate site, there is a "News" section displayed through a Category Blog menu item. The editor has prepared a new article, added an image, a table with parameters, and an internal link. The goal is to check the visual result before publishing and confirm that the page will open in the section context, rather than as an isolated article without modules.

Goal

You need to see the article inside the site template, check the sidebar modules, make sure the table does not break the width, and confirm that the image is displayed at the correct size. The article is not published yet because it is still under review.

Preparation

Before you begin, make sure Better Preview Pro is installed, the system plugin is published, the "News" category has a menu item, and the editor has permission to edit the article. If the category is not tied to a menu, choose an appropriate Default Menu ID in advance or create a utility menu item.

Steps

1. Open the article in the Joomla admin panel and make your edits.
2. Check the category, publication status, access level, and article alias.
3. Click the Better Preview preview button.
4. In the modal window, check the first screen, the title, the image, the table, and the links.
5. Using the enhanced View Site link, open the parent category and confirm that the article fits the list, or will fit once published.
6. If you see an old version of the page, clear the relevant cache and repeat the check.

Result Check

The result is considered correct if the preview shows the article in the right visual context and the parent page opens through the expected category. The table should not break horizontally, the image should not overflow the content area, and internal links should point to existing pages.

One Important Detail

If the preview opens the homepage, do not assume right away that the extension is broken. Check whether a suitable menu item exists, whether the component is excluded in Disable on Components, whether the SEF index is outdated, and whether cache is interfering. If the problem is reproducible only in one third-party component, it is more sensible to exclude that component from Better Preview and keep manual checks for it.

Practical Ways to Use It in an Editorial Workflow

Better Preview Pro may look like a small extension, but it can fit into several real working scenarios. The key is not to invent extra capabilities, but to use the confirmed ones: the preview button, the enhanced link to the public equivalent, parent pages, the default menu item, URL details, and the ability to exclude unsuitable components.

For the News Editor

The editor uses the preview button before every publication. An internal instruction can require checking the first screen, image, caption, tables, links, and the view inside the parent category. This kind of workflow reduces the number of small errors that are usually discovered only after publication.

For the Administrator Managing a Complex Menu Structure

The administrator enables Show URL Details and uses the enhanced View Site link as a diagnostic tool. If an article opens in the wrong context, they can see which route was selected, whether a suitable menu item exists, and whether a Default Menu ID is needed. In this role, the extension helps not only the editor, but also the person maintaining the site's structure.

For Checking Hidden Sections

Many Joomla sites have hidden menu items for utility pages, news sections, landing pages, or archives. Better Preview Pro helps check content through such an item if the structure is configured correctly. This is especially useful when the section should not appear in the main menu, but still needs its own output settings.

For Supporting an Older Site Before Migration

If the site has not yet been moved to a newer Joomla branch, Better Preview Pro can temporarily improve editorial work. But in that scenario, it is useful to add not just the preview button to the checklist, but also a migration note: which sections depend on the old logic, which extensions need replacement, and where Better Frontend Link can take over after the upgrade.

Validating the Result, Cache, and Safe Publication

After setup, it is important to verify not only that the button works, but that the preview shows the current and correct page. Joomla may cache components, modules, and full pages. The official Joomla caching guide explains that changing content does not always automatically clear the page cache, so the editor may see an outdated result.

Better Preview includes a Purge Component Cache setting that can clear the cache of the relevant component before rendering the preview. But this is not a universal fix. Some sites also have template cache, server-side cache, CDN layers, or third-party optimizers. That is why validation has to happen at multiple levels.

Mini Checklist After Setup

• Open a test article and check the preview before saving.
• Save the article as a draft and see whether the result changes.
• Open the parent category through the enhanced View Site.
• Check the article as a regular user if access permissions affect output.
• Clear Joomla cache through System and Clear Cache if you see stale data.
• Check whether server-side or external cache is hiding the fresh result.

How to Tell Cache Problems From a Wrong Route

If you see outdated text but the template, menu, and modules are correct, the problem is most likely cache. If the text is current but the page opens without the expected modules or with a different template, the problem is most likely the active menu item. If the homepage opens instead of the article, check excluded components, the default menu item, and support for the current content type.

The right order for result validation: first confirm that the correct route is being used, then verify data freshness, and only after that look for a conflict with the template or a third-party component.

Editorial Policy: How to Build Preview Into Publication

Better Preview Pro becomes much more useful when the team treats it not as a random button, but as part of a working policy. Without that policy, editors may click preview only occasionally, administrators will receive vague complaints like "the page looks wrong," and mistakes will still reach the live site. A good policy is short: it does not turn publishing into bureaucracy, but it creates a shared language for review.

Split the process into three roles. The editor is responsible for the content itself: text, images, tables, links, captions, quotes, and the appearance of the first screen. The administrator is responsible for the technical context: the menu item, template, modules, cache, and Better Preview exclusions. The person responsible for publication makes the final decision: the article can go live, the route needs adjustment, or publication should be delayed until the template is checked.

Minimum Checklist for the Editor

The editor does not need to understand all the logic behind Itemid and the SEF index. They need a list of visible signs they can check with their own eyes. After clicking the preview button, they should confirm that the title is not cut off, the opening paragraph is readable, the image is not stretched, the table fits inside the content area, links work, and sidebar blocks do not overlap the main text. If something looks wrong, the editor should report a concrete symptom rather than simply saying "it broke."

A useful internal wording is: "The article opens in preview, but the table extends beyond the right edge" or "Preview shows the updated text, but the right-side news module is missing." Messages like that save administrators time because they immediately separate a content problem from a routing problem.

Minimum Checklist for the Administrator

The administrator checks the parts the editor is not expected to know. First, they open the same article and see which menu item is selected for preview. Then they verify whether the category has its own menu item, whether Default Menu ID is appropriate, whether the component is excluded, and whether the SEF index is outdated. If the editor sees an older page version, the administrator checks Joomla cache and any outside caching layers.

This order matters: if you start by changing template CSS and only later discover that preview was opening the wrong page, you will waste time fixing a problem that never existed. Better Preview Pro helps expose the symptom, but correct diagnosis still begins with the route.

How to Handle Edge Cases

Sometimes preview shows a result that is technically correct, but the editor does not like it. For example, the article may open in the correct category, but a sidebar module feels unnecessary. That is no longer a Better Preview Pro issue, but a site structure issue: the module assignment, menu item parameters, or section template needs to change. It is useful for the policy to state this directly: the extension is not a design tool. It shows the site's current logic, not the desired one.

If the disagreement concerns an older Joomla branch, record it in the migration task list. For example: "After moving to the newer branch, check replacement of Better Preview Pro with Better Frontend Link," "Review the hidden news menu item," or "Remove preview's dependency on an outdated template override." That way, the extension becomes not just a convenient button, but a source of facts about how the older site actually works.

When It Is Better to Stop Publication

Pause publication if preview leads to the homepage without a clear reason, shows a different template, hides important modules, returns an outdated version after cache clearing, or consistently breaks on a specific component. That does not mean the content is poor. It means the team cannot reliably confirm the public-facing result. On a site running an older platform, that kind of caution matters more than publishing speed.

If the issue is not critical for the current article, you can use a temporary workaround: open the public URL manually, check the page as a normal user, and create a follow-up task for the administrator. But do not let that workaround become the permanent process. If Better Preview Pro is installed, it should reduce manual review, not become yet another source of exceptions.

It is useful to revisit this policy every few months. Menus change, editors get used to new sections, some content moves into archives, and older hidden menu items lose their purpose. A short review helps you see which routes are no longer needed, where preview works reliably, and where it is time to replace a temporary workaround with a proper site-structure fix. Mark the sections where preview always requires manual checking, because those are often the first candidates for cleanup during the next technical update.

Safe Improvements Without Editing the Extension Files

There is no reason to invent PHP hooks or edit Better Preview Pro files: the sources reviewed for this guide do not document public extension points for that kind of customization, and changing extension core files makes updates harder. But there are safe external improvements that do not interfere with the product's code.

Language Overrides for a Clearer Label

If the button label or tooltips are unclear to editors, use Joomla's built-in language overrides instead of editing extension files. That is the safer route: the override can be removed, it survives normal updates, and it does not change plugin logic. First, check which language constant the specific version of the extension uses, then create the override in the Joomla admin panel.

Utility Hidden Menu Item

For content without an obvious route, create a utility menu item that does not appear in the main navigation but defines the correct page type. This is a standard Joomla practice for controlling routing and module context. After creating the item, set it as the Default Menu ID or check whether Better Preview starts selecting it automatically through the category structure.

Careful CSS Only for the Public-Facing Result

If preview shows that tables or images break the public page, fix the site template, not Better Preview itself. For small visual corrections, use the template CSS file or custom CSS if the template supports it. Do not inject styles into the article just to make a single preview look better. For example, for tables inside the content area, you can add a wrapper or a template rule, but only after testing on real pages.

.article-content table {
  max-width: 100%;
  overflow-wrap: anywhere;
}

.article-content img {
  max-width: 100%;
  height: auto;
}

This snippet is not part of the Better Preview Pro API. It is a safe external template adjustment that helps the preview result match a stable public-facing layout. Test it on a site copy, then open several articles with tables and images. Rolling it back is simple: remove the added lines from your custom CSS.

Why Preview May Behave Incorrectly and How to Diagnose It

Better Preview Pro issues are usually not tied to a single button. They are more often related to Joomla routing, cache, access permissions, and components that do not support the expected preview workflow. That is why diagnosis should move from simple to complex: button presence, plugin publication, route, menu, cache, exclusions, and third-party components.

The Preview Button Does Not Appear

The symptom is simple: the editor opens an article but cannot see the button in the editor area or toolbar. Possible causes include the system plugin not being published, Display Editor Button and Display Toolbar Button being disabled, the user viewing the wrong content type, or the admin template hiding the button area.

What to Check

• Find the Better Preview system plugin and make sure it is published.
• Open the button settings and check both display toggles.
• Test the button on a standard Joomla article instead of jumping straight to a third-party component.
• Clear admin cache and refresh the edit page.

If the button appears on a standard article but not inside a third-party component, do not try to fix it with general settings. Most likely, the component does not provide the right context for the button or is excluded in the parameters.

Preview Opens the Homepage

This symptom usually points to a routing issue. Better Preview tries to find an appropriate public path but cannot find a related menu item, or the component is excluded. Another possibility is that the current content type does not support preview.

How to Fix It

1. Check whether the category or article has a published menu item.
2. Create a utility hidden menu item if no public item is needed in navigation.
3. Set a correct Default Menu ID.
4. Clear the Better Preview SEF index and Joomla system cache.
5. Check whether the component was added to Disable on Components.

You should roll a setting back if a new default item improves one section but breaks preview for other categories. In that case, it is better to refine the menu structure than to force one universal route for the whole site.

The Correct Page Opens, but the Text Is Outdated

If the route is correct but the content is stale, start with cache. Joomla may be serving a saved version of the page, and third-party optimizers or server-side cache may add yet another layer. Enabling Purge Component Cache only helps within the relevant component and does not replace checking outside caches.

Check the page after clearing Joomla cache, then in a private browser window, then as a regular user. If the updated text is visible to the administrator but not to guests, look at page cache, CDN behavior, or access rules.

Modules and Template Differ From the Real Site

This symptom is almost always tied to the active menu item. Joomla selects modules and template parameters by Itemid, so the wrong route produces a different context. Check which menu item is being used for preview and compare it with the one a visitor would actually use to reach the page.

The Admin Panel Became Slower After Enabling Advanced Options

If the slowdown appeared after working with the SEF index or cache settings, return the configuration to more cautious values. Better Preview documentation directly recommends increasing SEF Index Timeout (hrs) if admin pages become slow. Adjust that setting gradually and test several typical editing screens.

Preview of a Third-Party Component Looks Unpredictable

Not every component can be shown correctly through a general preview mechanism. If the issue repeats only in one component, add it to Disable on Components and keep a separate manual review process for it. That is better than giving editors a button that repeatedly creates a false sense of what the result will be.

When Better Preview Pro Is the Right Choice

Better Preview Pro is worth using if you maintain an older Joomla site where editors regularly need to see content in its real context before publication, and the menu structure makes manual checking too slow. Its strongest use case is articles and categories where the template, modules, hidden menu items, and fresh post-edit results all matter.

Before adopting it, check compatibility, create a backup, configure button visibility, choose a clear Default Menu ID, test cache behavior, and exclude components that do not produce reliable results. If the site has already been upgraded to a newer Joomla branch, it is better to move to Better Frontend Link instead of trying to use this product outside its current context.

If the extension fits your project after testing, you can download the latest version of Better Preview Pro and test it on a site copy first. The new publication workflow should only go live after the editor, the administrator, and the person responsible for the site all agree on what counts as a correct preview and how to roll back a disputed setting.