JP CE jDownloads List - Joomla Extension

A Practical Guide to JP CE jDownloads List for Joomla and YOOtheme Pro

JP CE jDownloads List is not meant for manually re-creating a list of PDFs, archives, or software on a page. Its purpose is different: it takes documents and categories already set up in jDownloads and displays them in a YOOtheme Pro layout, either as a managed list or as a source of dynamic data. That is why this guide focuses on the practical workflow rather than repeating the extension’s promotional description: how to prepare the catalog, enable the element, choose the right display method, check access, and keep each item on the site connected to the actual file.

This guide covers two ways to work with the extension. The first is useful when you need to add a few specific documents or one folder to a regular page. The second is for libraries that should be part of a template, with a grid, accordion, metadata, download counts, category pages, or individual document pages. In both cases, jDownloads remains the source of the information, while YOOtheme Pro controls how it is arranged and presented on the public site.

The example uses a realistic technical documentation library: some files are available to all visitors, while others are restricted to logged-in users. An editor also needs to add new materials without rebuilding the layout in the page builder. Along the way, we’ll cover installation, the Single Document and Folder options, sorting, dynamic fields, jDownloads permissions, result checks, and common troubleshooting steps.

How jDownloads, the element, and the page builder work together

To avoid looking for a setting in the wrong place, start by separating their roles. jDownloads stores the catalog data: categories, hierarchy, download records, files, descriptions, images, license information, and permissions. YOOtheme Pro builds the page and determines how visitors see that data. JP CE jDownloads List sits between them. It adds an element to the builder that can select a specific document or category, and it also makes jDownloads data available for more flexible layouts.

This separation is especially useful for an archive that grows over time. An editor creates a new download in jDownloads and assigns it to the right category. The designer does not have to revisit a dozen existing pages to add a new link manually: the category list can include the new item according to its display settings. That reduces the chance of leaving an outdated file link on the site while the label, icon, and description no longer match the record in the download manager.

Keep in mind that the extension does not replace jDownloads features. JP CE jDownloads List is not a file manager, does not set access permissions on behalf of the component, and does not protect a file just by displaying a polished button. It displays the data and download links provided by the source component. If a record is unpublished, has no file, or the visitor is not permitted to download it, the page builder should not be used to bypass that state.

Two display methods that serve different needs

The product’s official description highlights a simple list element and a custom dynamic data source. The simple element works well as an editorial tool. You can select an individual document, an entire category, or combine those items in one block, and choose a suitable icon for a file. This approach works well on a support page, in a “Helpful Resources” section, or alongside a product description when the list is short and you want to control its order.

The dynamic source solves a different problem. It makes jDownloads data available to standard YOOtheme Pro elements such as a grid, list, or accordion. Instead of building repeated cards by hand, you map fields such as the title, description, image, file link, download count, and other available information. When new records are added to the source, the template keeps its structure while the content changes. This is no longer a “list of files in the text,” but a presentation layer for the catalog.

A simple rule of thumb: if you need to control a few items on one page, start with the list element. If the same format needs to serve a category, archive, or detail page, plan the data source and template first. Moving a large archive into manually selected items later is usually more work than setting up dynamic output correctly from the start.

The extension is designed for Joomla and YOOtheme Pro. It is not a general-purpose widget for any Joomla template, and it does not replace standard jDownloads modules. If the site does not use YOOtheme Pro, or its builder is disabled in the part of the project you are editing, the extension’s main benefit will not be available. In that case, use jDownloads’ built-in views and modules or choose a solution designed for your template.

Who benefits from this approach to managing a file catalog

JP CE jDownloads List is a good fit for a site that already uses jDownloads and YOOtheme Pro, but needs to display files in a layout that matches the rest of the site rather than in the component’s standard view. Examples include a manual library, software update section, forms repository, partner media library, or course resource archive. The size of the archive matters less than the need to keep its presentation consistent as the catalog changes.

This setup gives a small team a clear workflow: one person manages the data in jDownloads, while another looks after page sections and templates. Even if the same person handles both roles, the sequence still helps: complete the download record first, check its permissions, and then display it through the builder. Start with an accurate record and the right access, then work on the presentation. That is the best way to avoid a polished but unusable file catalog.

The extension may not be a good fit if the site does not use YOOtheme Pro, if you only need to display one static file, or if all download handling must go through a different component. Do not choose it on the assumption that it will automatically restrict document access: access is controlled by jDownloads and Joomla settings. For a catalog with complex rules for departments, customers, or subscribers, test the user groups, view levels, and permissions with a test category first.

What visitors see on the page

Visitors see a clear block that fits the page, not an administrative list. For one document, it might be a row with a title, description, and file type icon. For a category, it might be a set of materials in an editor-defined order. In a dynamic template, the display could use cards or an accordion, with the file name, short description, download count, date, image, and link coming from the record’s fields. The fields visitors see depend on the selected layout and the data that has actually been entered.

So before you start designing, ask “What decision should the visitor be able to make?” rather than “Which element looks better?” For documentation, visitors usually need the title, a version in the record name, a short description, the language, and a clear download button. An update archive may also need a date and change log. For a restricted knowledge base, it may be more helpful to show that a resource exists and explain that visitors need to sign in than to leave them guessing why a button is unavailable.

Before you begin: check the source data and compatibility

Before installing the extension, prepare a small test set: one category, one published document with a real file, one record without a file, and a separate user account that is not a super user. This lets you test the successful path as well as empty states, link behavior, and permissions. Do not start with a production archive containing hundreds of records. It will be harder to tell whether an item disappeared because of a filter, permissions, its status, or an element setting.

Review the jDownloads catalog

Open jDownloads and make sure the category you plan to use is published and contains the right documents. For each test record, check its publication status, visitor-facing title, file or selected download method, and view level. If the list is meant to display a description, image, license, or download count, fill in those fields for at least two different documents. Otherwise, the template may work technically but look like a set of empty spaces.

Do not treat different data types as interchangeable. A jDownloads category is more than a decorative folder for a menu: access settings may be inherited by child categories and downloads. According to the jDownloads documentation, permissions set at a higher level can apply down the tree, while the view level must be checked separately. If you plan to create a restricted section, set up its category structure in advance. Hiding a block in the builder is not the same as denying access to a download.

Map out fields before building the first layout

Before creating a list, make a short data map for the test category. In the first column, note the jDownloads field; in the second, who fills it in; and in the third, where it will actually help visitors. For example, every document needs a title and file. A short description helps when two similar files serve different purposes. An image makes sense for a visual library, but it does not have to accompany every technical manual. This review helps prevent a common mistake: adding every available field to a card, then trying to hide the extras with styles.

Also decide which value is the source of truth for a document’s name. If an editor changes only the physical file name, visitors do not necessarily need to see that technical change. Usually, the readable title, description, and version details belong in the jDownloads record, while the file name is internal. If you use a custom title for a Single Document item, record why it is different. For example, a title on a support page might identify the equipment model. Otherwise, the same manual could end up with three different names in the catalog, on the page, and on the download button.

Check more than just a carefully completed record. One test download should have a long title, another should have a short description, and a third should have no optional image. Decide which fields are required by your editorial policy and which can be left blank without affecting the layout. That gives you a clear outcome to look for: once the source is connected, the cards should still hold together with real content, and editors should know what to fill in before publication.

Check the environment without assuming compatibility

The developer publishes test results for the current release with the Joomla, jDownloads, and YOOtheme Pro versions current at the time of release. This is a useful reference, but it does not guarantee compatibility with every combination of third-party extensions, template overrides, and server settings. Before updating a production site, compare your installed environment with the developer’s requirements, review the package changelog, and make a backup according to your project’s usual procedures.

Make sure jDownloads is installed and enabled. The JP CE jDownloads List changelog specifically mentions that the integration is disabled automatically if jDownloads is missing or disabled. This is sensible fallback behavior, but to an administrator it may look like “the element disappeared.” Also confirm that YOOtheme Pro opens the builder on a test page and that your account has permission to edit the content item or template you need.

• Back up the site and export or record the current settings of the test page.
• Create a test category with two published documents and one item with controlled access.
• Check that a regular user can see the categories and records intended for that user.
• Make sure the YOOtheme Pro builder is available on the page or in the template area where the list will appear.
• Record the page’s current state so you can distinguish an integration problem from an existing catalog issue after enabling the element.

You are ready for the next step when a permitted user can actually open and download a test file, not just when the page looks polished. This will save time during troubleshooting and prevent design settings from masking an access problem.

Install and enable the extension in Joomla

Install the extension using Joomla’s standard process. After obtaining the installation archive, go to System → Install → Extensions in the administrator area and upload the package through the installer. Joomla will recognize the extension package and run the installation routine. Do not unpack it into a random template folder or copy its files over other extensions. That can leave you with a partially installed component that is difficult to update or remove.

After Joomla confirms the installation, open plugin management at System → Manage → Plugins, or use the equivalent page in your Joomla version. Enter the product name in the search field and, if needed, filter by status. Find JP CE jDownloads List and enable it. JPro Studio’s official instructions include this step: the installed plugin must be active before the custom element appears in the builder.

First check without changing the design

Open a copy of a page, or a test page, in YOOtheme Pro Website Builder. Find JP CE jDownloads List in the element library. If it appears, add a temporary block without complex styling and save the layout. At this stage, the goal is not to make it look good. It is to confirm the sequence package installed → plugin enabled → builder recognizes the element.

If the element is missing, do not immediately reinstall the archive over the live site. First check three things: the plugin’s status, whether jDownloads is present and working, and whether you opened the Joomla version of the YOOtheme Pro builder. If all three are in order, review the changelog and any environment changes since the last known working state. Test updates on a copy of the site so you can safely disable the extension and compare behavior.

Once the element appears, add one item using the public test document you prepared, save the layout with Save layout, and close the builder. Then open the page in a separate session without administrator privileges. This short test checks that the configuration was saved, the item appears on the site, and an actual visitor can access it. Do not rely only on the preview inside the editor, which may be running under an administrator account.

Do not change the category, permissions, template, and styling all at once. Make one controlled change, save it, check the public page, and only then move to the next setting. This makes later adjustments repeatable instead of guesswork.

Choosing between Single Document and Folder

To add an item, start with the ADD ITEM button. Choose a jDownloads item type for each entry. The official instructions list two basic options: Single Document and Folder. The first displays one selected jDownloads document; the second displays all downloads in a selected category. The options may look similar, but they serve different editorial needs and behave differently as the catalog grows.

Use Single Document for a curated selection

Choose Single Document when the block should contain specific files and nothing else. This works well on a product page that needs a manual, driver, and request form; in an article that offers one sample file; or on a software update landing page. After choosing the type, select a document from jDownloads. You can then configure the item’s presentation, including its document icon. Recent releases also include a custom title setting for an individual document.

The benefit is deliberate ordering and the ability to combine different types of documents on one page. The tradeoff is that new materials will not appear automatically: an editor has to add another item or replace the selected document. That makes Single Document a good fit for a curated selection, but a poor fit for a fast-growing library where dozens of files are added every week.

Use Folder for a category that changes over time

Choose Folder when you need to display the contents of a jDownloads category. Select the category in the Select Folder field and configure ORDER BY. The block then uses the category’s data rather than a manually maintained list. A new published record added to that category and accessible to the current user can appear in the list according to the selected sorting rules.

Sorting is an editorial decision, not a minor styling detail. For a manual library, a clear order can help visitors find the newest or most important document. For a version list, recency may matter more. Before launch, add two test files with different titles or dates and check that the selected ORDER BY produces the expected order on the public page, not just in the builder.

Do not assume that Folder will always display “everything in the folder.” Publication status, view levels, permissions, the selected category, and sorting all affect what appears. If the category contains many older materials, decide in advance whether they all belong on one page or whether you need a separate archive and a shorter selection on the landing page. That helps prevent a long, hard-to-scan column from taking the place of a useful resource block.

Set a clear rule for category updates and curated lists

Make the difference between automatic updates and manual selection clear to the team. For a category displayed through Folder, the rule is: after publication, a document can appear if it is in the right category, passes access checks, and matches the current sorting settings. A Single Document block follows a different rule: the new record exists in the catalog but will not appear on the page until an editor adds it as a new item. Either outcome is correct if it was chosen deliberately.

For a test, create a document with an easy-to-recognize title, but do not attach a real internal file. First place the record in a neighboring test category and confirm that it does not appear in the public block. Then move it to the selected category, publish it, and refresh the page in a guest session. If it appears, move it back or unpublish it and check the reverse behavior. This test confirms both the expected case and the source boundary: the list should not pick up anything that merely has a similar name or sits nearby in the category tree.

Try not to change the category and sorting field at the same time. Otherwise, after saving, it will be hard to tell why a record moved to the top or bottom, or disappeared. First set the category and confirm which items are included; then choose ORDER BY and check the order as a separate step. If several editors maintain the archive, add this rule to an internal guide: publishing a file in the correct branch populates the list, while rearranging cards on the page is not how you control the order in Folder mode.

Configure the list after installation: from source data to a readable block

It is easier to configure the list in two passes. The first makes sure the data is right: item type, document or category, sort order, visible fields, and access. The second focuses on readability: headings, icons, spacing, contrast, and what visitors see on wide and narrow screens. If you style an empty or incorrect list first, it becomes harder to tell which changes affect the data and which only affect its appearance.

Build one item and check its meaning

Open the element in the builder, add an item with ADD ITEM, and choose Single Document. Find the test record you prepared in the document selector. If the selector is empty, do not enter the title manually or create a copy of the file somewhere else. Go back to jDownloads and check the publication status, whether the record was saved, and whether your administrator account can access it. The product changelog includes a fix for loading custom category or document selection fields in the builder. If you are using an older package, compare the symptom with the installed release instead of hiding it with a workaround layout.

Next, choose an icon that matches the file’s purpose. A PDF, archive, or software icon should not be the only clue to what a file contains: it still needs a clear title and short description. An icon helps people scan the list, but it cannot replace accessible text. If you enable a custom title for a single document, use it only when it adds context for the page. Do not replace the file’s name with marketing copy that leaves visitors unsure what they are downloading.

Configure Folder mode and sorting that will hold up as the catalog grows

Create a second test block, choose Folder, select a category in Select Folder, and try the available ORDER BY options one at a time. Save after changing each setting. The goal is to choose a rule that will make sense to a future editor, not a random order that happens to look good today. It can help to record a note such as “Materials in the Manuals category are sorted by [selected field].” That way, adding a new file does not depend on one administrator’s memory.

If the list needs to show items from several categories, do not try to turn one Folder item into an unclear aggregator. It is simpler to create separate, purpose-specific blocks or use the dynamic source in a template if it meets the need. Clear groupings are easier for visitors to understand and easier to test: you can open each category, check its access settings, and confirm that its items do not appear in the wrong section.

Style the block without changing the data

In YOOtheme Pro, adjust the grid, spacing, and typography so the main action is clear without extra explanation. For a document list, a short title, one line about the file’s purpose, and a noticeable download link are usually helpful. If you display a download count, do not use it as a measure of the document’s quality: it is informational, not an endorsement. If you show a description, make sure that overly long text does not obscure the title or disrupt the rhythm of the cards.

Pay special attention to the file link. A page can look right even if a document has been deleted or its URL is empty. The JP CE jDownloads List changelog includes a fix that returns an empty address when no file is present, preventing an empty download error. For editors, this is a reason to set a rule: every new record must be checked on the public page by clicking the actual link before the block is published. A visible item and a working file are two separate requirements.

Make safe improvements without editing core files

If the design needs a small adjustment, start with the element and section settings in YOOtheme Pro, such as spacing, classes, visibility, and the section’s custom CSS field. These are easier to undo than changes to Joomla, jDownloads, or extension core files. Avoid embedding an arbitrary script in a document description just to animate a button. That makes updates harder and may interfere with content filtering.

For a small design adjustment, create a test section first, give it a clear name in the builder, and apply CSS only to that section using the theme’s built-in tools. After checking the public page, keep a copy of the original code in the project’s internal documentation. You can then undo the change by removing the section rule instead of searching the extension for a modified file. If an adjustment would require editing product files, stop and consider a template override or help from the developer rather than making updates harder.

Dynamic data and templates: when a basic list is no longer enough

A simple list handles selected items. A dynamic source is useful when the catalog needs to become part of the site’s layout. The product’s official page describes a connection between jDownloads and YOOtheme Pro elements, including Grid, Accordion, and List, as well as the ability to display a name, link, download count, description, and metadata. This makes it possible to create category overviews, category detail pages, and individual download pages.

Start with a field map, not a decorative card. List the data in a real record and mark what visitors need. Usually that means a title, purpose, and file. Depending on the use case, you may also need an image, date, file size, license, download count, or change log. Do not display a field just because the source makes it available.

Map the source to a YOOtheme Pro element

In YOOtheme Pro, select a source in the element or item settings. A single source is displayed once; a multiple source repeats the element for each record. A grid should therefore receive multiple downloads, while a detail page heading should receive one current record. A source with no mapped fields may produce an empty or incorrect display.

For an archive, create a test Grid, connect the jDownloads source, and map the title, short description, and link. Add other fields one at a time, comparing two different records: one with an image and one without, one with a long text and one with a short text. Display conditions can handle empty secondary fields, but they do not replace jDownloads permissions.

jDownloads view templates

The extension advertises templates for category overviews, category pages, and individual downloads. Start by testing one template on a test category and confirm that it applies to the intended jDownloads view. Then expand its use. Do not combine the catalog, card, and instructions into one initial view: a grid helps visitors choose a document, while a detail page helps them decide whether a specific file is right for them.

Use a minimal card to verify the dynamic source

Start with a card containing three verifiable parts: a title, a short explanation, and an action that leads to the file. Do not add an image, counter, file type icons, size, date, and several nested buttons all at once. This minimal version is not meant to make the interface bare. It gives you a diagnostic checkpoint. It is easy to see whether the grid is receiving the correct record, whether it repeats a card for every download, and whether a field is being pulled from the wrong context.

Then add exactly one field that helps visitors choose, such as file size for software packages or revision number for technical manuals. Check it against two real records, save, and open the archive outside an administrator session. If a field is missing from some materials, decide in advance what visitors should see: a hidden row, a neutral label, or an editorial requirement to fill in the data. Do not guess at empty values or copy values from another record into the template by hand.

Display a download count only if it adds useful context. In a public library, it may indicate that a file is in demand, but it does not show whether it is up to date or accurate. For policies and manuals, a controlled title and brief description matter more. Treat dates with similar care: they help when the editorial policy keeps them accurate, but they should not make a file look newly updated just because the page layout changed.

A dynamic archive has a clear limitation: it reduces the repeated work of building cards, but it does not fix unstructured data. If ten records use different naming conventions, descriptions of different lengths, and missing files, the template will display those inconsistencies consistently. After the source is set up, document a short jDownloads record template: required title, clear description, category, file, permissions, and any image field you need. This helps keep the catalog consistent when editors change.

Example: a manual library with public and restricted categories

Consider a company that publishes equipment manuals. Its support page needs a block with the three most important PDFs, while a separate archive should contain all manuals by model. Service bulletins for partners should be visible only after they sign in. The goal is to show users only the materials they are allowed to access, while letting editors add new files in jDownloads without repeating the work on every YOOtheme Pro page.

Set the goal and prepare the data

Create two top-level categories in jDownloads: Public Manuals and Partner Bulletins. Add two published PDFs to the first category, each with a clear title and short description. Add one test bulletin to the second. Configure a user group and view level for the restricted category according to your site’s rules. jDownloads documents the difference between a view level and a permission: the former determines what a user can see, while the latter determines what they can do, such as download a file. Check both for restricted materials.

On a test site, do not leave the restricted category open to everyone “just for a minute.” Set up a test partner account and a separate guest session first. If a user group inherits permissions from another role, check the calculated permissions rather than relying on the group name alone. Permissions can pass down to child items in the jDownloads category tree, while an unintended Denied value on a public group can block more than expected.

Add a curated block to the support page

Open the support page in YOOtheme Pro and add JP CE jDownloads List. Create three Single Document items: an installation guide, a quick reference, and a service form. For each one, select an existing jDownloads record, add a custom title if needed, and choose a recognizable file icon. Place the block after an explanation of what the documents contain, not before it. Visitors should know what they will get before they download it.

Save with Save layout, open the page in a guest session, and click each download in turn. Then change the title of one test document in jDownloads and check that the editorial choice is clear: should the page title follow the record automatically, or should the element’s custom title intentionally replace it? Record the policy so editors do not start presenting the same documents in different ways a month later.

Use Folder mode for an archive that updates automatically

On the “All Manuals” page, add a new element, choose Folder, select Public Manuals in Select Folder, and set the appropriate ORDER BY. To test it, add another document to the same category and publish it. It should appear on the public page in the expected sort order. If it does not, check in this order, from the source to the page: record publication, selected category, view permissions, file, saved layout, and only then the presentation settings.

If the archive needs a richer presentation, create a dynamic grid using the jDownloads source. Add a title, short description, link, metadata that helps visitors choose, and a subtle fallback for missing images. Five clear cards are more useful than twenty half-empty ones. Use pagination, category structure, or separate views to handle larger archives rather than an endless page.

Test the restricted section with the right accounts

Open the archive in three states: as a guest, as a registered user without the partner role, and as a test partner. For each state, record what is visible, whether downloads work, and whether the outcome matches the site’s policy. Do not use a super user session as proof that access restrictions work: it shows the maximum level of access, not the experience of your intended audience.

If a guest can see the title of a restricted file but cannot download it, that is not necessarily an error. First decide what experience you want: hide the entire section or show that the resource exists with an explanation. Then align the category and record view levels, download permission, and builder block with that decision. A clear access policy matters more than an element of surprise.

Add a new document without manually editing the archive

Ask an editor to complete the full process for one test document. They create a jDownloads record, enter a clear title and short description, attach the real file, select Public Manuals, check the publication status, and save. Then they open the public archive in a separate window, not from the builder. If the new material appears in the right place in Folder mode, the day-to-day task does not require access to the YOOtheme Pro layout.

After a successful test, repeat the process with a restricted bulletin. The record should be placed only in Partner Bulletins, using the approved view and download permission settings. Test it first as a guest, then as a regular user, and finally as a partner. Do not change permissions on the public category to get the outcome you want quickly. That mixes two separate branches and makes future troubleshooting harder. If access does not match the policy, stop publication and review the category and assigned group.

This example also shows the tool’s limits. JP CE jDownloads List can display selected jDownloads data in a page layout, but it does not make the editorial decision about what belongs in the public library and what should be reserved for partners. Category names, record-entry rules, and checks with all three user roles remain part of the team’s workflow. The builder should display a well-organized catalog, not become the place where access and classification are corrected manually for every block.

Check the page after saving the layout

Your checks should follow the same path as a real visitor. After each significant change, log out of the administrator area or open the page in a separate browser profile. Do not check only the YOOtheme Pro preview: it is useful for reviewing the layout, but it does not replace testing as a guest or as a member of a particular group. For a dynamic page, also open two records with different sets of fields to see how empty values are handled.

A basic acceptance check

1. Open the page as a guest and confirm the order, titles, icons, and absence of restricted materials.
2. Click the download link for a real document and confirm that it opens or downloads the expected file.
3. Add a test record to the selected category and check how it appears in Folder mode or the dynamic grid.
4. Open the page with an account that has a restricted role and compare the list with the expected access policy.
5. Check the page at a narrow viewport width: a long title should not cover a button or cut off an important label.

Test the negative cases too. Create a temporary unpublished record and confirm that it is hidden. Make a copy of a document without a file and check that it does not create a meaningless empty download. Then remove the test records or restore their previous status. This gives you more confidence than opening a polished page with one working PDF a dozen times.

For a dynamic source, check what happens when a displayed field is missing. For example, open a record without an image if the card is meant to show one. If the layout breaks without it, configure a fallback using the element’s settings or make the field required under your editorial policy. Do not rely on a placeholder image indefinitely: visitors should understand that they are choosing a document, not an image.

A successful check has an observable outcome: the right user sees the right record, the link leads to the right file, and a new publication changes the catalog according to a known rule. “The block appears” is not enough.

Acceptance checks after changing a template

Run a separate check after any change to a shared YOOtheme Pro template, even if it seems purely visual. Start with one short record, one long record, and one record missing an optional field. Then repeat the test as a guest and as the intended user role. This helps distinguish a field-mapping problem from an access issue: the former usually affects everyone in the same way, while the latter changes with the user.

It helps to keep a short acceptance log with the internal check date, page, category, user role, expected items, and actual outcome. There is no need to turn this into paperwork. The next editor just needs to know which document was used for testing and why a restriction was applied intentionally. If only one old item disappears after a template update, compare its fields with a working record before changing the global setup.

Finish by returning the catalog to a clean state. Unpublish or remove temporary documents according to your usual process, and do not keep using test roles as permanent accounts. Check a set of real documents again after cleanup so the outcome reflects the normal workflow, not the accidental presence of a test record. This last step matters especially in Folder mode, where a test item could remain in a public category and make it look as though it belongs there.

View levels, permissions, and why they matter from the start

JP CE jDownloads List displays the catalog, but decisions about whether a user can access a category and download a file start in jDownloads and Joomla. The jDownloads documentation makes a clear distinction between two concepts. A view level determines whether a user can see a category or document. Permissions determine what the user can do, such as download a file. For a restricted catalog, configure both consistently. Otherwise, a visitor may see a record and get a denial message, or may not see the intended material at all.

For a simple public archive, the default behavior of a public category and its download permissions may be enough. If your site has restricted documents, though, do not set permissions file by file without a plan. Create a top-level category for the intended audience, assign a suitable view level, and grant only the necessary permissions. jDownloads permissions can be inherited by child categories and downloads, so the model is easier to maintain when it is defined at the top of the branch, with only a few documented exceptions.

Test the experience as a guest and a member

Suppose public manuals should be available to everyone, while service bulletins are reserved for registered partners. First, create or use a partner group in Joomla. Then configure the restricted category so it is visible to that audience and grant the corresponding download permission. After saving, test as a guest and as a partner. If guests should only know that the section exists, create a separate public page to explain it. Do not leave a direct list of restricted files on the page and hope it behaves as intended.

Do not rely on hiding a YOOtheme Pro section as your only access control. That changes the presentation; it does not replace jDownloads permission checks. Likewise, do not set a broad Denied value without understanding inheritance and calculated permissions. It is safer to start with the minimum required access, test as a member of the intended group, and expand access only if needed. If in doubt, create a test category branch instead of experimenting on the live library.

Practical ways to use the extension without duplicating content

The product’s main strength is that you can place a file within the page layout while keeping its jDownloads record as the source of truth. The examples below use the documented element modes rather than assumed integrations.

A product page with documents selected by an editor

Below the specifications on an equipment page, add three Single Document items: a manual, a drawing, and a spare parts list. Each file has its own jDownloads record, so it can be updated without editing the page. Check all three titles and decide in advance whether the custom title should follow the source record.

A support section that grows with its category

For a support center, create categories by product line and use Folder. The editor adds a manual to the right branch, and the list updates according to ORDER BY. A new test document should appear only on the page for its product line. If it does not, check the selected category and catalog structure.

Consistent cards in an archive template

For cards with descriptions, metadata, and download counts, use the jDownloads source in Grid or Accordion. Select only the fields that help visitors decide, create a category view template, and test it with records that have different amounts of data. A new record should update the archive without requiring anyone to copy a card manually.

Troubleshooting: the list is empty, a file will not open, or the wrong users can see it

Most problems with this integration are easier to find if you follow the data in order: jDownloads stores and publishes the record, JP CE jDownloads List receives it through the enabled plugin, YOOtheme Pro saves the element configuration, and the public user sees the result with their own permissions. Do not start by rebuilding the design. Identify the symptom first, then reproduce it in a separate session.

The element is missing from the builder library

Symptom: Installation completed without an obvious error, but JP CE jDownloads List is missing from YOOtheme Pro. Possible cause: The plugin is disabled, jDownloads is missing or turned off, or you opened the wrong editing context. What to check: Find the plugin under System → Manage → Plugins, confirm its status is Enabled, then make sure jDownloads is active and open the Joomla version of the YOOtheme Pro builder.

Fix: Enable the plugin you found, save its status, and reload the builder. If the issue appeared after updating the extensions, compare your versions with the configurations the developer tested and repeat the check on a copy of the site. When to roll back: If enabling the extension causes a critical error on a production page, disable it on the copy, save the error details, and do not continue updating the live site.

A document or category does not appear in the list

Symptom: The selector is empty, or an expected record is missing from the public list. Possible cause: The document is unpublished, belongs to another category, is unavailable to the current user, or the layout was not saved after a change. What to check: Open the record in jDownloads and check its status, category, view level, download permission, and attached file. Then open the element and make sure the right Single Document or Select Folder is selected.

Fix: Correct the data and access in jDownloads first, save the record, and then resave the element with Save layout. Add one new test document to the category to confirm that Folder is reading from the intended source. When to roll back: If a permissions change has made a restricted branch public, restore the previous settings immediately and continue testing with a copy of the category.

The page shows an item, but the download does not work

Symptom: The title and styling are visible, but clicking the file does not produce the expected result. Possible cause: The record has no file, its address has changed, the visitor lacks the Download permission, or the link has not updated after a record change. What to check: Open the jDownloads record, confirm that the file is present, and test it on the public page as a user in the intended role. Remember that seeing a title does not prove that the user can download the file.

Fix: Attach or restore the correct file, check the category and document permissions, clear only the caches covered by your site’s procedures, and test again in a new session. When to roll back: If a permissions change grants access to the wrong audience, undo it and rebuild the rules from the top-level category. Do not try to compensate by hiding the button in the design block.

Guests can see restricted details, or partners are denied access

Symptom: What users can see or download does not match the access policy. Possible cause: View levels and download permissions are out of sync, inherited permissions are unexpected, or testing is being done in an administrator session. What to check: Compare access for a guest, a regular registered user, and a user in the intended role, each in a separate session. Check the top-level category and all relevant child records.

Fix: Write down the intended “who can see it / who can download it” matrix, configure it at the top-level category, and save the changes. For a complex structure, use a separate test branch. When to roll back: If public documents disappear after a change, restore the known working configuration, then add the restricted branch gradually, one group and one category at a time.

The dynamic grid has empty cards or an uneven layout

Symptom: The grid appears, but some cards are empty or long descriptions disrupt the layout. Possible cause: The selected source fields are not mapped, real records are missing required data, or the template does not account for empty values. What to check: Compare two different jDownloads records and check their titles, descriptions, images, and links. In the builder, confirm that a source is selected and that specific fields are mapped to the element.

Fix: Return to a minimal working card with a title, short text, and link, then add fields one at a time. Use a display condition for optional information or set an editorial rule for filling it in. When to roll back: If a new template starts replacing content in other views, unassign it and restore the known working template while you isolate the cause.

Video walkthrough of the jDownloads and YOOtheme Pro integration

JPro Studio’s product video shows the JP CE jDownloads List custom element and the JP CS jDownloads data source working with YOOtheme Pro. It is useful after the sections on simple lists and dynamic sources because it illustrates that the two approaches serve different levels of the same task; they are not just two names for the same block.

As you watch, compare the demonstration with the test page you prepared: first find where the element is added in the builder, then compare selecting one document or a category with your own catalog, and finally compare the layout with the public page. Do not copy the demonstration settings without checking them. You still need to verify publication status, access, and the actual file on your own site.

When JP CE jDownloads List is a good choice

This extension makes sense if your site needs both jDownloads as a managed file catalog and YOOtheme Pro as a page and template design environment. Start with a small list where you can easily verify the connection between the record, file, and public page. Then decide where Single Document is enough, where Folder is useful, and where the catalog calls for a dynamic template.

The key to a reliable setup is to keep access, data, and presentation as separate steps. Let jDownloads manage records and permissions, JP CE jDownloads List connect them to the builder, and YOOtheme Pro present them clearly. Once you have checked the setup, you can download JP CE jDownloads List and add the integration to a test page first, then to the live catalog.