Easy Folder Listing Pro - Joomla Extension

A Guide to Using Easy Folder Listing Pro in Joomla

This guide walks you through building a managed file library from a site folder in Joomla: prepare the directory, enable the parts of Easy Folder Listing Pro you need, choose a profile and list format, then test standard downloads, previews, search, and ZIP downloads. We’ll also cover an important limitation: displaying a file list and download links does not turn a public folder into secure storage. This setup is best understood as a public file library: the site displays the allowed contents of a folder according to the extension’s rules.

The focus here is a working setup, not a promotional overview: where the files are stored, which rule determines what appears in the list, how the list is added to an article or template position, and how an administrator can tell whether it’s working correctly. We’ll also look at large directories, filenames in Cyrillic, ZIP archives, and activity logs.

Field names and available values may differ between extension branches. In Easy Folder Listing Pro 3+, the component includes built-in Help that explains profile settings and the corresponding keys for specific shortcode overrides. The steps below focus on what each setting does and how to test it safely on your own site, rather than assuming the current admin panel has a particular layout.

When a folder-based list is better than maintaining links by hand

A standard Joomla article has text and links that an editor maintains manually. That works when there are only a few documents and they change rarely. But if the site regularly adds journal issues, instructions, price lists, forms, or reports, maintaining a manual list becomes a task of its own: upload a file, update its name, add a link, change the date, and check that the article no longer contains an old URL. Easy Folder Listing Pro takes a different approach: an administrator specifies a folder and display rules, and visitors get a list of the files in that folder.

The extension is useful when the files already fit naturally into a folder structure. For example, a nonprofit publication might keep issues in a shared folder organized by year, with separate PDFs inside each year. An educational project might organize its folders by course, topic, and assignment. A company might sort public instructions by department so that a new file appears in the list as soon as it’s uploaded to the right folder, without adding the same link to several articles.

The main time savings come from avoiding manual duplication of a folder’s contents, not from automatically publishing documents. Editors are still responsible for the files themselves, clear filenames, the correct folder, and the site’s access rules. The extension doesn’t make editorial decisions, write descriptions, or turn unstructured uploads into a categorized library. It displays files and subfolders according to the settings for each instance.

A public library, not a document management system

Easy Folder Listing Pro works well for materials visitors are allowed to view or download: published forms, catalogs, instructions, press kits, reports, and learning materials. The files are already stored on the same server as Joomla, and regular subfolders make them easy to organize. You can add a list to an article or display it as a module. Choose the columns and format based on your audience: a list of filenames may be enough for a short reference page, an archive of issues may benefit from a table with file sizes and dates, and a deep hierarchy may call for an expandable tree.

The extension can also reduce the number of steps visitors need to take. Search helps them find a row, sorting helps them scan the directory by name or date, and batch downloads collect selected items into an archive. These features are especially useful in folders where staff regularly add documents. Still, test the visitor experience on a page before rolling it out: make sure filenames are self-explanatory, files open as expected, and subfolders don’t reveal internal structure that shouldn’t be public.

When another type of extension is a better fit

If each document needs its own title, summary, author, publication date, categories, tags, image, page, and managed permissions, a folder-based list may not be enough. A folder catalog knows about filenames, types, sizes, and file timestamps, but it doesn’t provide the same features as a full document record. Similarly, if private documents must be available only to specific user groups and the files themselves must not be directly accessible, look for a document manager with a clearly defined ACL model and private storage.

The product isn’t intended to use an external storage location on another domain or subdomain. The developer’s Help for this extension family states that files must be on the same domain as the site. Don’t use it as a cloud drive mirror, a remote FTP index, or a catalog of files on a third-party server unless another supported storage method has been confirmed. If your documents are currently in cloud storage, first decide whether they really need to be copied to the site server, then consider how those copies will be updated and backed up.

Who benefits from a dynamic list, and who doesn’t

The extension suits editors who can maintain a clear file structure but don’t want to rewrite a list of links every time a file changes. It works for small and medium-sized public archives, materials in a consistent format, or pages where files are added rather than turned into dozens of separate records. It’s also useful when you want to show folders and subfolders as a single tree instead of creating a separate menu item for every directory.

Consider an alternative if you need document records with fields and categories, visitor authentication for each action, upload approval, editorial review, scheduled publication, document versioning, expiration controls, full-text search inside PDFs, or detailed analytics. Some of these needs may be met by other Joomla extensions, but don’t assume Easy Folder Listing Pro provides them just because both products display files.

Use the extension with a folder only when its contents are already the right set of files to publish. A list filter can control which filenames appear, but it doesn’t replace access controls for sensitive files.

How Easy Folder Listing Pro builds a file list

The product’s key feature isn’t a single shortcode field; it’s the combination of the Joomla component and several supporting extensions. The developer’s package includes a component, a content plugin, an editor extension, and a module. This explains a common issue after installation: the component appears in the admin panel, but there’s no list in the article yet. The component stores and edits the rules, but the Companion Content Plugin renders lists embedded in articles. The developer states that without it, the list won’t render, including inside the Companion Module.

To visitors, the process looks like one action: open a page, find a file, and select it or download it. Behind the page are several separate decisions. A profile sets the list’s main configuration; a shortcode marks a specific location in the text and can override some profile settings; the content plugin processes that shortcode; and the extension gets files from the specified folder and displays them in the selected format. If you use a module, the same mechanism places the list in a template position, and the module itself must also be published and assigned to the relevant menu items.

The profile sets the default rules for a list

Profiles let you avoid repeating every setting in each article. You can create a basic profile for public PDFs, for example, and choose the display method, visible file details, subfolder behavior, filtering, and status messages. Another page might use a separate profile for documents with dates and a deeper folder tree. The Companion Content Plugin’s built-in Help describes a default profile that applies to all lists, while the module page says the Default profile appears in the dropdown after installation. Additional profiles become available after you create them.

Don’t start by creating dozens of options. Set up one profile you can test, try it with a document in an article, and adjust the list before creating reusable profiles for genuinely different needs. Add the profile’s purpose, root folder, audience, and editor owner to its name or an internal note. This is a site management practice, not a special product field, but it helps prevent people from guessing which of several similar profiles to use.

The extension can also create a profile automatically when a shortcode specifies a new folder, and you can turn off that behavior. This is convenient for a quick first setup, but on a production site, decide in advance which profile should serve as the default and what it should be called. If a new shortcode unexpectedly creates a separate record, check the automatic creation setting and the profile list before copying the shortcode into other content. Compare the result with the Default profile on a test page. If the new profile shouldn’t have been created, disable the option and choose a profile explicitly.

A shortcode in an article can override profile settings

The product page provides a short example that sets the display method, folder, and whether to collapse subfolders:

{easyfolderlistingpro method='list' folder='images' collapse='1'}

In your article, replace images with a folder containing files that are approved for publication. The example shows the syntax; it doesn’t mean every additional key or value is the same in every extension branch. First, find the key you need in the built-in Attribute Override List on the component’s Help tab. It maps each profile setting to the key you can use to override it in a shortcode. Don’t copy old examples that use a vertical bar as a separator. For version 3+, the keys are listed in built-in Help, and the current example uses spaces between attributes.

Overrides let you use one shared profile while giving an individual list its own location or display method. For example, standard site sections might use a table, while the same file collection appears as a simple list beside a short course description. To set this up, first confirm that the right profile is selected, then change one confirmed key and compare the result. If the entire set of settings changes unexpectedly, check whether you edited the shared profile instead of adding a local value to the shortcode.

Editor Extender and Companion Module serve different locations

The editor extension adds an Easy Listing button that helps build a shortcode so editors don’t have to type a long line by hand. It’s useful for choosing a profile and settings, but read the generated shortcode before using it: check the folder, display method, and any unnecessary overrides. Place the shortcode in the article’s regular content, not in an editor mode that automatically replaces braces or formats code. If it disappears after you save, open the article in source mode and check that the editor hasn’t removed or changed it.

Companion Module is for a template position. In the module manager, create an instance, choose a profile and position, publish it, and assign it to menu items. It isn’t a workaround for adding a list to an article body. The developer specifically warns against using the Joomla Load Position plugin when you want the list inside article text; use the Content Plugin directly. This distinction helps with page layout: an article places content in context, while a module occupies a consistent location on selected pages. If the two methods are applied to the same spot by mistake, you may see two lists, an unprocessed shortcode, or inconsistent behavior.

What to prepare before installation

Since the extension displays files from a folder, start by defining what belongs in that folder, not by choosing a design. Pick a test directory that definitely contains no private materials, and add a few harmless sample files: a PDF, an image, and a subfolder containing another file. Give the files clear names, including one sample with Cyrillic characters. This small set will show whether the path is correct, links work, nested files appear, and the encoding looks right. To test ZIP downloads, add two sample files and confirm that PHP has ZipArchive available.

Choose the extension branch based on your Joomla version, not simply because one branch has a higher number. The developer identifies 4.5.3+ as the build for Joomla 5.x and 6.x and warns that it isn’t fully compatible with Joomla 4.x. The product page mentions branch 3.8 for Joomla 3.10 and earlier, but that isn’t a recommendation to keep an outdated version of Joomla on a production site. Before installation, check your CMS branch and PHP version. The product page’s minimum of PHP 7.2+ doesn’t override Joomla’s own, stricter requirements. For example, Joomla 6 has its own minimum requirement of PHP 8.3.

Decide who owns the files and how often they’ll be updated. If staff will copy PDFs through the hosting control panel or another method, agree on the exact folder and filename rules in advance. Don’t put backups, logs, source files, temporary uploads, or internal work materials there. Excluding a file extension from the list isn’t a reliable way to hide a document if its URL is directly accessible.

Map the folders and define the audience

Before publishing, trace the folder tree from the root to its deepest file. Which folders should every visitor be able to see? Do you need an “Archive” subfolder? Are there folders that shouldn’t be exposed? Will visitors understand the names of year or topic folders? Your answers will determine the maximum nesting depth, whether the tree starts expanded or collapsed, and what to say when a folder is empty. An organized structure helps administrators as well as visitors: the path in a shortcode tells you which set of files the article controls.

Don’t rely on a folder appearing in Joomla’s file manager or your hosting control panel. That only confirms that the administrator can see it on the server. You still need to confirm the path relative to the site and how the installed extension expects you to specify it. Check each folder name, its capitalization, and any spaces. On a Linux server, names that differ only in capitalization can refer to different files or folders, even if they looked the same during a test on a local Windows computer.

Plan for file volume, performance, and recovery

How many files are in the root folder? How many levels of subfolders are there? How many list instances will appear on one page? A list creates HTML for the files it displays. The developer’s Help describes a case where an overly long table hit PHP’s memory_limit while the article shortcode was being replaced. There’s no need to guess at a universal limit before you start. First test with a copy of your content, then monitor the server log and response with the directory at its expected size. Pagination may make the list easier to browse, but don’t assume it will automatically avoid server limits.

Before installing or changing versions, create a backup you can restore and repeat the procedure on a test site first. Save the original shortcode, selected profile, and list of supporting extensions. That way, if there’s a conflict, you can identify what changed and restore the previous configuration. Don’t rewrite every shortcode during an update. Test one instance on a copy first, especially if it uses older keys, an attribute separator, or a preview mode.

Your minimum test set should cover the whole flow: a file is in the selected folder, the list appears, a click does what you expect, and unrelated documents don’t show up.

Install and enable the extension so you can diagnose issues clearly

For Joomla 5 or 6, choose the Easy Folder Listing Pro package from the branch compatible with your CMS. Before uploading it, make sure you have the installation ZIP, not an internal folder from one of its components. On a test site, use the standard Joomla path System → Install → Extensions, then open Upload Package File. Seeing the component in the menu after installation confirms that Joomla recognized the package, but it doesn’t prove that the Content Plugin is enabled.

The package includes several parts, and some may be installed but disabled. Open the plugin list, filter it by listing or the extension name, and check the Companion Content Plugin’s status. You need it to display lists in articles. If you plan to use a template position, check Companion Module as well. Editor Extender is needed for the helper button in the editor, but the missing button won’t prevent a shortcode that you entered manually from working.

First, open Dashboard in the component and check the status notices for its supporting parts. Then enable Content Plugin in the plugin manager and return to the dashboard. The notice should show that the required part is enabled. If there’s a separate notice for the module, enable it only if you need it. This makes it easier to tell which component is responsible for a particular symptom than enabling everything at once and testing several changes together.

Install in an order that makes testing easier

1. Back up the test site or create a separate restore point.
2. Check the Joomla and PHP branches and confirm the server has ZIP support.
3. Install the compatible package through System → Install → Extensions.
4. In Plugins, enable Companion Content Plugin. Enable Companion Module and Editor Extender only if they’re needed for your chosen placement.
5. In the component, open Dashboard, check the system notices, and confirm that built-in Help is available.
6. Create one short test article with one shortcode and one safe sample file.

If the installer reports a database error or part of the interface remains unavailable, don’t delete and reinstall the package repeatedly. First record the exact error message, check the Joomla log, and compare the extension branch with your Joomla version. In particular, trying to use branch 4.5.3 with an unsupported Joomla 4 version won’t be fixed by renaming the ZIP or changing the site’s design. Roll back the test installation and choose a compatible version before making changes to the production system.

Check that the plugin is enabled and the basic shortcode works

Add a short test shortcode to an article and keep it in its original form. It should be in the article content handled by the Content Plugin. If the editor button helps you create it, use the button, but don’t treat it as essential. Publish the article under a restricted test menu item and open the public-facing site: seeing the shortcode in the admin editor doesn’t mean the plugin processed it when the page was displayed.

The initial test passes when you see the expected list from the test folder instead of curly braces, the filename isn’t cut off, and the link points to the same document that’s in the directory. If the list is empty, don’t change the field name, profile, and folder permissions all at once. Confirm the exact path first, then that the file exists and has an allowed extension, and then check the plugin status. This sequence helps isolate the problem instead of introducing more variables.

Once the basic setup works, add a subfolder, view the page again, and test collapsing or expanding it. Add a pair of files for the ZIP test last. If you test a full archive, search, preview, and several profiles on a large directory all at once, it’s hard to tell which feature caused an error. The first test should confirm just the basic chain: the component is configured, Content Plugin is active, the folder can be read, and the shortcode becomes a list.

Configure a profile for a specific directory

Profile configuration is central to working with Easy Folder Listing Pro. In branch 3+, the component’s profiles hold the main features and settings, and the content plugin lets you choose a profile to use as the default for the list. Built-in Help does more than describe each field: it maps profile settings to shortcode override keys. Start with a real use case, then open the corresponding page under Profiles. If you’re unsure about a setting, select its Help icon and compare the field description with the version of the package you installed.

Don’t start with every available toggle. Decide what visitors should see and adjust only the settings that affect that experience. For a public folder of documents, the main settings are usually the root folder, whether to include subfolders, maximum depth, sorting, visible file details, list format, and link actions. Enable or configure ZIP downloads, previews, extended logging, and search only when you have a clear reason for each feature.

Start with the right folder

The folder path defines the input for the entire list. One extra directory in the path can produce an empty list; a path that’s too broad can expose files that an editor never meant to publish. For each list, record a short relative path within the site’s folder structure, add one test file to it, and confirm the result from a public page. Don’t start by experimenting with Joomla’s main images directory. It may contain technical files, old uploads, or unsuitable materials.

If the same folder appears in two articles, decide whether both lists should look the same. If so, use one shared profile. If one article needs a compact list and another needs a tree with dates and a specific depth, create separate profiles or use confirmed local overrides. An override works well for a one-off difference. A new profile is better when you’ll reuse different settings across multiple pages.

Set the subfolder depth and visibility

A nested tree is useful only if the folder names help visitors find their way. Show subfolders when they represent stable categories, years, topics, or departments. If folders contain only technical working files, a flat list or a limited depth will be clearer. A long tree that opens fully pushes useful documents down the page and makes visitors scroll through the structure even when they need just one file.

Choose the tree’s initial state based on how visitors first arrive at the page. If the directory is shallow, expanded folders may reveal the materials right away. If it spans several years or departments, leave branches collapsed and make it clear how to open the one they need. Don’t choose a maximum depth by habit. Test the value with a sample directory so the needed document is visible but irrelevant lower levels don’t open automatically. Also test controls for expanding and collapsing all branches, if your chosen display method includes them.

Filter file types and exclude items

The product description confirms that you can set allowed and disallowed extensions and exclude specific files and folders. Use these options to hide system items and irrelevant formats. A page of guides might list the document types its audience expects; a media library might include images, while an instructions page might include PDFs and office documents. If a folder contains several kinds of files, limit the allowed types to those relevant to that page.

Filtering the list doesn’t secure access to the files. Excluding secret.pdf from the displayed list doesn’t prove its direct URL is inaccessible. Similarly, hiding files with a particular extension helps manage the public list but doesn’t turn the folder into secure storage. The safest rule is not to store anything that visitors shouldn’t access in a folder used for public listings.

Check the Help for Profiles in your version for the exact separator and current field names. The older v2.8.5 table uses semicolons to separate extensions, but that doesn’t mean you should copy its values into the current build. Confirm the field and test one file of an allowed type and another that should be excluded. After testing, restore the intended list of allowed types. Don’t leave a broad default in place if it doesn’t match the contents.

Choose how much detail to show with each filename

The filename is the most important part of the list because that’s how visitors identify a document. Remove the extension only if the file type is still clear from the name or a nearby icon. Otherwise, guide-final.pdf and guide-final.docx would both appear with the same name. For the same reason, don’t add icons just for decoration. They can make file types easier to scan, but they don’t replace a readable title.

File size is useful for large downloads when visitors need to know what they’re getting before they click. The modification date can help distinguish a current guide from an old version if files are updated regularly. The time can add clutter without helping, so include it only when updates within a day matter. Choose a familiar date format and use it consistently. Also confirm that the date reflects the file timestamp you care about. The product describes options for using the creation, modification, or access time, but check the profile field in your version to see which one is available.

Sort files to make them easier to scan

Sorting by name works well for alphabetical directories or numbered sections. For journal issues or documents replaced by newer versions, sorting by modification date may make the most recently updated item easier to find. Sorting by size is less common, but it can help visitors locate a large package or gauge a download’s size. Before choosing a sort order, test the list with ten files that have different names and dates. A short test shows whether the order matches what visitors expect.

Files and folders may be sorted separately, so don’t judge by one column alone. Check how the top-level folders are sorted and how items are ordered inside an expanded branch. For filenames with natural numeric order, confirm that “2” comes before “10” if visitors read the numbers numerically rather than as text. The developer’s product history mentions both standard and natural sorting. Check the exact setting and value in Help before relying on a particular order.

Set up empty-state messages and action labels

An empty list doesn’t always mean there’s a technical problem. The folder may not have any files yet, the allowed file types may exclude everything, or the root path may be wrong. An empty-state message should be short and accurate. If it’s expected, say that there are currently no published materials in the folder, without promising a file will be added soon. If the empty state is unexpected, use it as a diagnostic signal rather than hiding the list before you find out why it’s empty.

Column headings and action labels should match the language of the page. You can leave filenames as they are, but controls, filters, empty-state messages, size labels, and archive prompts are part of the extension’s interface and should make sense to your audience. Built-in Help can help you find where to edit these labels in the current profile. Don’t use the same word for separate actions if the list offers both a preview and a ZIP download. Visitors should know whether they’re opening one file, previewing it in the browser, or collecting several items.

After each group of related settings, return to the public test page. A value that looks right in the form doesn’t prove that the list is clear or safe to use.

Choose a list format: table, paginated table, simple list, or Explorer

Easy Folder Listing Pro supports four main formats: a standard table, a bulleted list, a paginated table, and Explorer View. These aren’t just four styles for the same layout. Each one directs attention differently: a table compares files by column, a simple list emphasizes names, pagination breaks a long table into smaller pages, and Explorer shows a browsable folder hierarchy. Choose the format based on how visitors look for a document, not on which mode appears to have the most features.

Use a table to compare files by several details

A table works well when visitors compare documents by several details, such as name, size, date, type, or available action. Column headings make each detail clear, and sorting makes it easier to scan the list again. For a small report archive, a table is often clearer than a nested tree: every file appears at once, so visitors can compare rows side by side.

Adding columns doesn’t always make a list clearer. If filenames are squeezed on a phone, the time is rarely useful, or icons repeat the file extension, the table stops doing its main job. Start with the name and only the details that help visitors make a decision. Then check the table in a narrow browser window, see how long names wrap, and confirm that links are accessible from the keyboard. If the template doesn’t display the table well, try a simple list instead of adding lots of abbreviations.

Use a simple list when names and actions matter most

A bulleted list works well on a page where filenames and actions matter more than sizes and dates. It looks lighter, fits naturally alongside article text, and suits a list of forms, course materials, or a short set of PDFs. When filenames are descriptive, such as “Application Instructions” or “Participant Guide,” visitors don’t have to work through dry metadata to find what they need.

Don’t hide useful distinctions when you choose a simple list. If documents are versioned regularly, include a date or name files so the current version is easy to identify. If several file types share the same name, keep the extension or a file-type icon. Otherwise, the simpler format may look neater but make it harder to choose the right file.

Use a paginated table for a long list

Pagination helps when a large list would otherwise turn into a long, scrollable table. It divides the list into pages, gives visitors a clear way to move between them, and keeps each set of results shorter. This can help people browsing an archive by date or name when they don’t need to see every document at once.

Test search and navigation on the published page. If a visitor enters a filter, confirm that the matching row is available and doesn’t disappear when they move between pages. If they change the sort order, check that it applies to the full set they expect, not just the visible rows. Pagination can make a list easier to read, but it doesn’t guarantee lower server load. The developer’s FAQ describes a case where generating a large amount of HTML exhausted memory. Measure performance separately for a large archive, and don’t assume that adding pages makes the list scalable.

Use Explorer for a meaningful folder hierarchy

Explorer View makes sense when the folder structure helps visitors understand the content. For example, folders named “Preparation,” “Practice,” and “Materials” can help visitors choose a topic before opening its files. That’s clearer than a flat list that mixes every path together. Visitors can see the hierarchy and work within one branch without scanning the entire structure.

Explorer won’t fix confusing filenames or replace information architecture. Folders named new, final, old, or misc don’t explain what visitors will find. Rename folders to reflect their contents, limit unnecessary depth, and test every expand-and-collapse action before publishing. If the tree is long, start with its branches collapsed and use the text beside the heading to explain what kinds of documents it contains.

Choose a format with a short test

Use one folder containing a few files and a subfolder to compare all four formats. Focus on three visitor questions, not the administrator’s personal preference: Can they find a document quickly? Can they understand its size and date? Can they see how the files are organized without excessive scrolling? For a short list, start with a simple list or table. For a large, consistent collection, try pagination. For a meaningful folder structure, test Explorer.

Don’t leave all four formats on the same production page just to compare them. You can create a separate restricted test article, but remove the extra instances before publishing and keep one format. Otherwise, search controls, tree toggles, and several sets of headings will compete for attention. The best choice is usually the simplest one that answers a specific question. Another article can explain the rest of the archive structure if needed.

Use search, sorting, and nesting to help visitors navigate

In a large list, the problem usually isn’t just the number of files. Visitors need to know how to search, whether folders can be opened, how to compare similar names, and where each action leads. Easy Folder Listing Pro combines sorting, subfolders, expand-and-collapse controls, and AJAX search. These features work best as one navigation system, not as separate decorations. The tree separates files by topic, search narrows the visible results, sorting organizes what remains, and clear filenames connect a result to its document.

Make sure AJAX search finds the right filenames

The product describes a full-featured AJAX search. For visitors, that means they can filter the list as they type, without manually reloading the page. On a test page, try an exact part of a filename, a different part of the name, a match in one subfolder, and a search term with no match. Check what stays visible, how to clear the search, and what happens when the filter is reset. Don’t judge by one search term; try both a file and a folder.

Search in a file list doesn’t necessarily mean full-text search inside PDFs. The product would need to index file contents to provide that feature, and the available Easy Folder Listing Pro materials don’t confirm that it does. If visitors can search by the displayed filename in your version, explain that near the search field. Don’t promise that they can find text inside a PDF until you’ve tested it on the installed extension.

If a search unexpectedly shows a blank area or hides every row, clear the field first and confirm that the basic list appears. Then try a full and partial filename. If the list returns after the filter is cleared, the issue is with the filter or expectations about what it searches, not the folder. If the basic list is empty, go back to the path, file-type rules, and Content Plugin status.

Subfolders should clarify the list, not add an extra step

Compare the folder tree with the words your audience uses for its sections. If visitors know a category by name, use a folder name that matches it. If the folders reflect an internal department structure the public won’t understand, rename them before displaying them or use separate folders for public materials. The extension can show and expand subfolders, but it can’t tell which names will make sense to outside readers.

Limiting the maximum depth can keep a deeply nested structure from opening too far. Use it to simplify navigation, not as an arbitrary safeguard: if a needed document is below the limit, visitors may assume it isn’t there. During testing, follow the path to the deepest file that should be available and count how many actions it takes to open the right branch. If visitors must open several folders in succession, move frequently used files closer to the root or simplify the folder structure.

Match sorting to the filenames

For filenames based on years, issue numbers, or lesson order, alphabetical sorting may not match the expected numeric order. Use clear prefixes like 2025-02 or 03-lesson if they’re easy to explain to visitors, and test them against your actual filenames. Don’t rely on just the first two rows. Folders may be sorted separately from files, so check that an expanded folder still shows files in the expected order.

If several editors add files, include a few simple naming rules in your workflow: use a consistent date format, avoid unhelpful words like “new” and “final,” keep the document type clear, and add a number if needed. This isn’t an Easy Folder Listing Pro feature, but these naming choices affect the list more than the number of columns does. Good sorting makes a vague filename easier to spot; it doesn’t fix the name.

Downloads, previews, and ZIP archives serve different needs

The same file can offer several ways to interact with it. A visitor can open a file link, preview a document in the browser, or select several items for a batch ZIP download. The product’s features include obfuscated links, time-limited links, ZIP downloads, and logs of downloads and previews. Each mode has its own purpose and requirements, so don’t enable them all without testing the visitor flow and server configuration.

Standard file links

First decide whether clicking a filename should open the file, download it, or show a preview. The product description confirms that you can associate a file’s name with a target action. Test this on the public site with the types of files you actually store. PDFs, images, and archives behave differently in browsers and may depend on server headers. Don’t assume the same link will preview every file type.

Obfuscation changes how a link looks, but it doesn’t restrict access to the file and shouldn’t be treated as user access control. If a file isn’t intended for every visitor, don’t put it in a public folder or rely on its link being hard to read. For materials that are public, obfuscation and time-limited links may be useful parts of the download setup. Test both a fresh link and an expired one so you know what to expect.

Preview depends on the document type and server

A preview can prevent unnecessary downloads when visitors want to check whether a document is relevant first. The developer notes that the current branch supports a native preview option by default, but actual behavior depends on the file type, browser, and previewer settings. Test each format separately. A PDF is a useful first test; a file the browser can’t display may open differently or have no compatible preview at all.

If the preview appears in a modal instead of a new tab, check the modal’s width and height too. Visitors need to be able to close it without losing focus. If the preview won’t open, try the standard file link. If the file downloads but the embedded preview doesn’t work, check that the selected viewer supports the file type and MIME type rather than changing the list’s root folder.

ZIP downloads require ZipArchive

A batch archive is useful when visitors need to download several materials at once. Easy Folder Listing Pro requires the PHP ZipArchive extension for ZIP downloads. Missing ZIP support shouldn’t affect tests of standard file links; it’s a separate server dependency. If an individual file downloads but the archive button doesn’t work, check that ZipArchive is available and test with a small set of files.

Give the batch download a clear action label and keep the selection easy to review. Before publishing, test three cases: nothing selected, one file selected, and several files selected. Confirm that the archive name is clear and that it contains only the selected documents. Don’t use ZIP to give visitors files they aren’t allowed to access. An archive should contain only files that the visitor is permitted to receive.

Logs of downloads and previews

Logs can help answer operational questions: whether materials are being used, which file someone requested, and when it was previewed or downloaded. The product description says the log can show what was viewed or downloaded, when it happened, and the IP address. Before enabling collection, decide whether editors need these details and who will review them. For a site with public documents, the extension’s activity log may be enough to gauge general interest. For sensitive use cases, consider in advance how these records will be stored and how long they’ll be kept.

Depending on applicable data rules, IP addresses may be considered personal or sensitive information. Set administrator roles and retention periods according to your site’s policies. Don’t publish the log to visitors or use it to identify someone without additional information. In recent notes, the developer mentioned fixes to log filters. If the log is unexpectedly empty, filters the wrong way, or shows too much, first check the filters and the installed build rather than changing the file folder.

For search indexing, it’s useful to distinguish pages with file lists from the files themselves. The product includes X-Robots-Tag settings for downloads, previews, and archives. These let you control how search crawlers handle individual responses; they don’t guarantee that a page will rank. Before changing headers, check which tag is sent for each action and make sure it fits your site’s indexing policy. If the goal is to have a public article indexed, don’t block the article just because you’ve enabled a no-index setting for a file.

Publish documents safely

Store only approved materials in a folder used for a public list. If a document contains personal information, signatures, internal notes, or anything else that shouldn’t be public, remove it from the public folder before publishing. Don’t upload Joomla backups, credential sheets, customer exports, or unreviewed files there. A file-type filter can hide a format from the list, but it doesn’t replace the server’s access controls.

After making major changes to a directory, check both the list page and the direct file paths you expect to work. Joomla guidance on disabling directory listings explains that a server-generated directory listing and an extension’s intentional file list are different mechanisms. Disabling server-side directory listings remains a separate part of a proper server configuration. Don’t enable directory listings on the server to “help” Easy Folder Listing Pro. The extension generates a controlled interface, while the server setting protects the root and other folders from accidental exposure.

Clicking a hidden or disguised link doesn’t test whether access is restricted. Check who is allowed to view the file and whether it’s actually accessible separately.

Practical example: a monthly archive of journal issues

Imagine a small journal that publishes a new PDF issue each month. The editors want to keep past issues on the site without asking a web editor to manually update a long article every time. Easy Folder Listing Pro fits this use case: the folder structure already reflects the archive, the files are on the same server, and all published PDFs are public. The list should show the issues, include their dates and sizes, sort them by date, open an issue when clicked, and let visitors find one by name.

Prepare the folders and filename rules

Create a separate folder for public issues. You can organize its contents by year and give the files a consistent name with the date or issue number first, followed by a short title. Don’t keep working layouts or proof copies in the same folder. If some issues should be available only to subscribers, this is no longer a public archive. Store those documents separately and choose a solution with a proven access control model.

For testing, place three small PDFs with different dates in a test folder, plus one document in a subfolder. Give one file a Cyrillic name. This will show how sorting, Cyrillic filenames, and nesting behave. Record the exact relative path that will go in the profile field or the folder key.

Create a profile and add it to an article

In Components, open Easy Folder Listing Pro, go to the profiles section, and create a base profile such as “Public Issue Archive.” Choose the table format, show the filename, size, and modification date, set a clear date sort order, and decide whether to show subfolders. If the archive spans many years, compare pagination and tree view with a short test before choosing one. Check the fields against the Help tab for the profile you’re using, not labels from another branch.

Open the “Issue Archive” article and use the Easy Listing button to create a shortcode with that profile. Don’t add local overrides for the first test. Save the article and open the public page. Confirm that the list opens the right folder, not the entire uploads directory; contains exactly the three test issues; and displays the selected columns clearly.

Test the visitor’s path from search to file

Enter part of an issue title in the filter and confirm that the matching row remains. Clear the search and test sorting with the sample dates. Then open a PDF with the standard link, return to the list, and try the preview separately if it’s enabled. For ZIP, select two documents, create an archive, and check its contents. Afterward, check the download or preview logs if the project needs activity tracking.

If the links work but the table feels cramped, remove nonessential columns before changing the site layout. If the dates look identical, check which file timestamp is displayed and whether the test files were changed on different days. If search can’t find an issue, check whether the displayed filename contains the term. Don’t promise search within the document’s text. If ZIP creation fails, check ZipArchive separately.

Add the next issue without changing the article

After the test succeeds, editors upload the new PDF to the agreed folder and check its filename, date, and approval status. A visitor then refreshes the archive page and sees the new file in the position determined by the sort order. That’s the point of a dynamic catalog: the article remains a stable entry point, while the files are updated through the folder structure. Changing the folder, filter, or profile requires a new test. Make sure the editor uploaded the final document, not a temporary file with a similar name.

An option for course materials

The same approach can work for a course if its materials are public and easy to organize by topic. For example, an article can introduce the course while a module in the sidebar displays materials for the current section. Give each module its own profile and check its menu assignment so that one course’s materials don’t appear on unrelated pages. If the content grows into a catalog with detailed descriptions, authors, and complex permissions, consider a full document manager. A folder tree may no longer be the best model for the people and workflows involved.

Display a catalog in an article or Joomla template position

In Joomla, content can appear in different parts of a page. Easy Folder Listing Pro provides a Content Plugin shortcode and a module for a template position. Choose between them based on context, not just appearance: a list inside an article should complement the document description, while a module can provide navigation or a reusable block in a sidebar. These are different ways to place a list, though they share the profile settings.

Add a list to an article body

Use the Content Plugin when a catalog belongs in an article. Create the article, add a shortcode where the list should appear using Easy Listing or the documented syntax, and assign the article to a clear menu item. Add a short explanation of what the list contains, especially if filenames include numbers, abbreviations, or dates. Visitors should know which folder they’re browsing before they see the list.

Don’t try to place Companion Module in an article with Joomla’s Load Position plugin. The developer recommends using the Content Plugin itself instead. If the public page shows a blank area, a literal shortcode, or a separate empty module, check whether two methods are being used in the same location.

Place a list with Companion Module

To add a catalog to a sidebar or a block that should appear on several related pages, create a Companion Module instance in Module Manager. Set its template position, choose a base profile, publish it, and assign it to menu items. The module includes a Configure Features link to the component’s profile settings. The profile holds the main list settings, while the module manager controls where the list appears.

After saving, check the page assigned to the module, not just the module list in the admin area. A template position may have a different name or be hard to recognize visually. On a test page, temporarily choose a position you can identify, confirm that the module appears, and then move it to its permanent location. If it’s missing, check the status of Companion Module and Content Plugin, the module instance’s status, its selected profile, and its menu assignments.

Choose which menu items display the module

Menu assignments determine which routes display the module. For the initial test, assign it to one page, confirm that the right catalog appears, and then add the other menu items you need. If the same module appears where it shouldn’t, the issue is more likely to be a menu assignment or duplicate instance than the folder path. Give each instance a descriptive admin name, such as “File Archive in Sidebar,” to distinguish it from other catalogs.

Joomla displays the module in the template context, but hiding a module on a page doesn’t control access to the file. Hiding it from a menu item removes the block from that page; it doesn’t prove that a direct file URL is restricted. For confidential materials, use separate storage and access controls rather than relying only on the module’s publishing conditions.

Check the setup from the visitor’s and editor’s perspectives

A successful installation isn’t just a green status in the admin panel. It means the page behaves predictably. Check the setup from two perspectives. Visitors should understand what they’re looking at, find a document quickly, and get the action they expect. Editors should know where each file is stored, which profile controls the list, and how to confirm that an updated file appears.

Walk through the page as a visitor

Open the page in a new window without an administrator session and read from the top down. Check that the introductory text explains the archive, the list has a clear heading, and the column labels make sense. Find a document by name, clear the search, and expand and collapse the relevant folder if the list is a tree. Test links with both the keyboard and mouse. Their labels should be clear, and they shouldn’t be available only through a tiny icon.

Confirm that each filename matches the file opened by its link. Check whether the document opens in a new tab or downloads, and whether that behavior fits the page. If a link opens an unwanted file, remove that file from the public folder instead of shrinking the text or hiding the row with styles. For a preview, make sure visitors can return to the list. For ZIP, check that empty and nonempty selections are handled clearly.

Walk through the update as an editor

Place a new test file where it belongs and refresh the public page. If it doesn’t appear, check the path and filter, then the filename and profile settings. After a change, editors should know whether they’re updating the shared profile or an individual shortcode. Keep a short procedure that lists the root folder, filename rules, allowed extensions, who approves the content, and whom to contact if the list is empty. This is especially useful when people who don’t manage profiles add files.

Test sorting with two or three new items, not just the original set. Confirm that the subfolder appears at the agreed depth and doesn’t show up in unrelated modules. If you’ve changed settings, repeat the full check on at least one page and one file. To roll back, restore the original profile, remove the specific override, or disable the module while keeping the article’s basic list in place.

Check accessibility and indexing

Check text and table contrast, long-name wrapping, keyboard focus, button labels, and the empty-state message. Don’t rely on a single color or icon to identify a file type. In a table, column headings should clearly relate to the values below them. In a tree, the expanded or collapsed state should be obvious. If the template breaks the spacing or makes a row clickable only across a tiny area, reduce the number of columns or choose a list format.

Decide separately how search engines should handle the catalog page and the files themselves. The X-Robots-Tag setting for downloads, previews, and archives can change how server responses are indexed, so check the headers for each action after changing the setting. Don’t promise an SEO benefit just because the page lists PDFs. Depending on their content, availability, and headers, search engines may index the page, an individual document, or neither.

Check performance safely on a test site

If the folder contains dozens or hundreds of items, measure the initial page load and the response after a search on a test copy. Use a realistic number of files; a directory with three files tells you little about a long page. Check PHP memory and error logs, not just whether the top of the page appears. If the page fails to render, review the folder size, tree depth, number of list instances, and display format. Change one setting at a time and keep a copy of the original configuration so you can restore it.

Pagination and search can make the interface easier to use, but don’t assume they replace server-side optimization. Actual load depends on the number of files, the amount of HTML, hosting settings, and other extensions. For a very large public archive, consider moving to a managed document catalog that stores and searches individual records instead of displaying files from a single folder.

Maintain the archive after it goes live

A dynamic list eliminates the need to update links by hand, but editors still have work to do. Someone must decide where a new document belongs, whether its filename makes sense, whether it contains restricted information, whether an older version is obsolete, and whether that version should stay available. If nobody owns these decisions, even a simple list will eventually fill up with duplicate files named “new,” “revised,” and “final.”

Make the folder structure clear to staff

Set a few simple rules for filenames and folders. Start a document’s filename with the year and month if it’s tied to a time period, a lesson number if it’s for a course, or a topic if it belongs to a department. Use words visitors will recognize, not just internal codes. Keep file extensions consistent and don’t leave two files with the same name that differ only in capitalization. This makes sorting easier and reduces the chance that a new issue will look just like an old one.

Specify who reviews a file before upload, who confirms the folder, and how to remove an outdated version. These rules matter especially when staff work with files through a hosting control panel rather than Joomla’s article manager. Easy Folder Listing Pro reflects the actual contents of the folder, so removing an incorrect copy changes the public list without editing the article. That’s why checking the published list after every major upload should be part of the editorial workflow.

Name profiles by purpose

If the site has different use cases, give profiles clear names like “Public PDFs,” “Course Materials,” or “Dated Catalog.” Avoid names like “Profile 2” or “New List.” An internal note can list the folder, articles that use the list, the person responsible for the archive, and any file-type exclusions. This makes the profile a reusable configuration instead of a set of unknown settings chosen by a previous administrator.

Before changing a shared profile, check which shortcodes use it. If several pages share the profile, changes to sorting or file extensions may affect the whole archive. For one page, start with a confirmed local override; for several similar pages, create a new profile. After any change, open all related articles and confirm that their lists aren’t empty and their links still work as expected.

Separate technical updates from editorial changes

Updating the package and changing the folder structure are different tasks. First, test the new version on a Joomla copy and note what happens to the component, profiles, plugins, modules, and existing shortcodes. Then test one page of each type. Only after that should you change the archive’s editorial rules. If you move folders, rename all files, and update components at once, it will be hard to tell which change broke a link.

Before moving between supported branches, confirm compatibility with Joomla and PHP, then back up the files and database. Test a small set of pages: a simple list in an article, a list with an override, and a module. Save the original shortcodes and profile settings, especially if the site has used older keys for years. After the test on a copy succeeds, update the production site during a window when you can check the catalogs and quickly restore the previous build.

Account for Joomla caching when testing changes

If an editor uploads a new file but the page still shows the old list, first confirm that the file is on the server and the path is correct. Then open the page in a new private window or clear the standard page cache if one is in use. This is a general diagnostic step for a Joomla site, not a specific Easy Folder Listing Pro setting. Don’t disable caching across the site because of one stale page. Compare a new request with the server log, then restore the cache setting if it isn’t related to the issue.

Keep page caching separate from the folder’s contents. Caching can delay a visible update, but it doesn’t create a file or fix an incorrect path. If the list is still empty after you clear the cache, continue checking the profile and folder instead of clearing the cache again. If your site has several cache layers, check only the one actually in use so you don’t reset unrelated site data.

Turn off features you don’t use

If visitors don’t use previews or ZIP downloads, disabling those actions reduces the number of features editors need to maintain. If you don’t need activity logs, consider turning off that collection. For a short directory, search and pagination may only clutter the top of the page. Manageability isn’t measured by how many features are enabled. Each additional button should answer a visitor’s question and have a test that an editor can repeat.

After each change, define one clear expected state and one way to check it. For a profile, use a specific page and known file; for ZIP, check the expected archive contents; for a log, generate a test event that an administrator can see. If nobody can explain why a feature is enabled or who checks its output, it may be safer to turn it off and revisit it when there’s a real need.

Easy Folder Listing Pro troubleshooting: symptoms, checks, and safe fixes

When troubleshooting, don’t change the folder, profile, and template all at once. First record what the visitor sees, repeat the same request with a test file, and check one part of the setup at a time: plugin status, path, file filters, profile, module, and server response. This order matters because the same blank space could mean a disabled handler, an empty folder, an overly restrictive filter, or a PHP limit.

The article shows curly braces instead of a list

Symptom: Visitors see {easyfolderlistingpro ...} as plain text. Possible cause: Companion Content Plugin is disabled, a visual editor changed the shortcode, or the shortcode is in a field the plugin doesn’t process. Check: Find Content Plugin in the plugin manager and check its status. Then open the article in source mode and compare its contents with the saved shortcode. Fix: Enable the plugin and add the shortcode without extra HTML markup. Test it on one article. If enabling the plugin conflicts with another content handler, roll back the change and check the plugin order on a copy instead of deleting the article’s original text.

The list shows an empty state instead of files

Symptom: The page renders, but the list says there are no files. Possible cause: The path is wrong, the folder is empty, the extension rules exclude everything, the nesting limit doesn’t reach the file, or the selected profile isn’t the one you expected. Check: Confirm the path on the server, add one test document directly to the root folder, temporarily select a profile with minimal filters, and check it on the public page. Then restore the filter, subfolder, and other rules one at a time. Fix: Correct the relative path or adjust the allowed file types according to the current profile’s Help. Don’t turn off every exclusion on a production folder just to make rows appear. First use a copy containing test files. When testing is complete, restore the original rules and confirm that unrelated files aren’t displayed.

The list appears in an article but not in the module

Symptom: An article using Content Plugin works, but the sidebar module is empty or missing. Possible cause: Companion Module is disabled, its instance isn’t published, no profile is selected, the template doesn’t have the chosen position, or the menu assignment excludes the current page. Also check that Content Plugin is enabled. According to the developer, the module also requires it. Check: Open the plugin list, Module Manager, and the settings for the specific instance, then check the page on the public site. Fix: Enable the module, select a base profile, and assign it to a test menu item and a known template position. If the list belongs in an article body, don’t wrap the module in Load Position; use Content Plugin. Roll back the menu assignment if the module starts appearing on unrelated pages.

A module or component reports a class error after moving to Linux

Symptom: The error names a class or helper, and the failure starts after a migration from a local Windows server to Linux. Possible cause: A historical case of case sensitivity in directory names or autoloading. The developer discussed a similar issue in an early Joomla 4 branch and later published a fix. That report doesn’t prove the current version has the same issue. Check: Record the exact Joomla, PHP, and Easy Folder Listing Pro versions, the complete error, and where it appears. Check whether the extension version supports your Joomla version. Fix: First update to a compatible, supported build or restore the previous version on a test site. Don’t rename Joomla core files or edit extension files manually. If restoring the last working version makes the error disappear, save the details for the developer. If you’ve made manual changes, restore the whole package first so you don’t leave behind a mixed build.

A ZIP archive won’t download, but individual files do

Symptom: An individual file link works, but selecting multiple files or downloading a ZIP doesn’t complete. Possible cause: PHP ZipArchive isn’t enabled, the archive is too large, or one of the selected items is unavailable. Check: Check PHP modules using Joomla or your hosting tools, then create a small archive from two harmless files. Fix: If the server configuration allows it, ask the server administrator to enable ZIP support. Reduce the test set and try again. If the site doesn’t need ZIP downloads, disable the option and keep standard downloads available. Don’t fix the issue by enabling every PHP module without checking Joomla’s requirements.

A large folder leaves a blank page or cuts off the output

Symptom: A small directory displays, but a large one cuts off the output or produces a blank page. Possible cause: PHP ran out of memory_limit while generating a large HTML view. The developer describes this behavior in the FAQ. Check: On a test site, check the PHP log and memory limit, compare the number of files and folder depth, and temporarily reduce the number of items. Fix: Remove outdated items from the list, split a large folder into meaningful categories, limit the depth, and test pagination. Increase PHP memory only with approval from the person responsible for hosting and after checking overall usage. If changing the limit doesn’t help, restore its previous value and move the large archive to a dedicated document catalog.

Cyrillic filenames, dates, or sort order look wrong

Symptom: A filename is unreadable, the date is unexpected, or numbers appear in a strange order. Possible cause: The server’s filename encoding, a different file timestamp, the date format, or standard text sorting. Check: Compare the test filename on the server with the one in the list, check the page’s locale, and then review the current profile settings in Help. Try several filenames, including ones with 2 and 10, and files with different modification dates. Fix: Standardize filenames and choose a confirmed encoding, date, or natural sort setting if your installed branch provides one. Don’t enable several old encoding options at once. If other filenames break after a change, undo it and first check the server’s original encoding on a test copy.

The preview won’t open, but the standard download works

Symptom: The file downloads from its link, but the preview action opens a blank window, shows a format error, or does nothing. Possible cause: The browser can’t preview that format, the MIME type isn’t recognized, or the selected preview mode isn’t available. Check: Compare a PDF with another supported file type, and check the exact link and the state of the new tab or modal. Fix: Keep downloads available and enable previews only where they work. If the file is private, don’t open it with a third-party viewer without considering the implications separately. If you change the mode and the test file works less reliably, or data goes to an unintended third party, restore the original behavior.

The site still uses a branch affected by CVE-2024-11145

Symptom: Easy Folder Listing Pro 4.4 or 3.7 is installed on Joomla. Cause: These versions were affected by a deserialization vulnerability that could let a remote, unauthenticated attacker execute code with Joomla application privileges. The developer identifies fixes in 4.5 and 3.8; the current 4.5.3 branch includes further fixes and Joomla 6 compatibility. Check: Confirm the version in the extension manager and compare it with your Joomla branch. Fix: Back up the site, choose a supported branch, and update a test site first. Then check the files, profile, article, module, preview, and log. If there’s no compatible new version for your platform, disable the extension and plan a migration. Don’t leave a vulnerable build enabled on the assumption that confusing links or a hidden module will protect it.

If the current version still behaves suspiciously after the update, don’t consider the site secure based on its version number alone. Check the logs and backups, restore a clean copy if there are signs of compromise, and follow your hosting provider’s incident response procedure. This goes beyond ordinary list configuration because an update fixes a specific known issue but doesn’t audit the whole site.

When Easy Folder Listing Pro is a good fit

Easy Folder Listing Pro suits a site that needs to display files from an existing Joomla folder and maintain the list by updating the folder’s contents. Its strengths include several display formats, nested folders, search, profiles, local overrides, links, and ZIP downloads. Start by choosing a compatible branch, enabling Content Plugin, creating a safe profile, and testing the path with a small sample folder. Then walk through the public experience, decide who maintains the archive, and confirm that no confidential materials have ended up in the public directory.

If the test succeeds, the path and output make sense to editors, and the folder size doesn’t cause performance problems, you can download Easy Folder Listing Pro and continue testing on a copy of your site. If strict permissions, document records, lifecycle management, and private files are your main concerns, compare document managers first and migrate the archive only after that review.