Advanced Custom Fields Pro - Joomla Extension

Advanced Custom Fields Pro for Joomla Guide: Fields, Display Conditions, and Practical Setup

Advanced Custom Fields Pro is not meant to replace Joomla as a content management system. Its real value is in extending Joomla's standard fields in a clean, structured way when plain text, lists, and images are no longer enough. In this guide, we will look at the extension as a practical working tool: what to check before installation, how to create your first fields, which settings to enable right away, how to build a real-world setup for listing pages, how to verify the result on the site, and where to look if a field does not appear or a file fails to upload.

This guide is written for site owners, content editors, and Joomla developers who need to store clear, structured data instead of dropping random bits into the article body: addresses, maps, files, galleries, related articles, videos, download buttons, filter values, and content blocks controlled by display conditions. We are not going to repeat the short product summary from the top of the page. Instead, we will show how to turn Advanced Custom Fields Pro into a stable part of your content workflow.

One important idea from the start: the extension is built on top of Joomla Fields. That means much of the work still happens through familiar Joomla areas like Content, Users, field groups, access permissions, automatic display, and template overrides. The Pro features add new field types, display conditions, advanced file upload scenarios, maps, galleries, article relationships, and integrations, but the underlying discipline is still pure Joomla: structure the data first, then style the output.

Where Advanced Custom Fields Pro Is Actually Useful

The best way to understand this extension is to picture a site where every article includes repeated structured data. For example, a directory of specialists may store the city, a map, a portfolio, a PDF certificate, and a profile link. An events section may store the date, venue, address, directions, video, and related content. A knowledge base may store the difficulty level, an instruction file, a Q&A block, related articles, and rules that make a specific block appear only on the full article page rather than in a category listing.

If all of that is entered directly into the article editor, a site quickly runs into three problems. First, editors start formatting the same kind of block in different ways. Second, it becomes harder for a developer to output that data in filters, listing cards, and template blocks. Third, any redesign or migration turns into manual HTML cleanup. Advanced Custom Fields Pro helps separate that information into fields and gives editors a clear, structured form to work with.

The extension is especially useful for sites that need a structured editorial form without a full CCK component. It expands Joomla's standard fields with specialized field types such as file upload, gallery, map, address autocomplete, related articles, video, audio, FAQ, progress, QR code, telephone, URL, country, currency, module as field, chained fields, and other options. That does not mean you should use everything at once. In practice, the best results usually come from a small set of fields chosen for a specific type of content.

When the extension is better than plain HTML inside an article

Use fields when a value repeats across dozens of articles, needs to be displayed in a consistent format, participates in filtering, or depends on access permissions. For example, an ACF - File Upload field for a product datasheet is better than a PDF link pasted into the article text because you can restrict the file type, define the upload folder, force download, and keep a clear label. An ACF - Map field is better than a random embedded map because the editor works with markers, providers, and dimensions instead of copying third-party code.

If a block is unique to a single article, does not need to be reused anywhere else, and is not part of the site's logic, a separate field may be unnecessary. You do not need to turn every sentence into a field just for the sake of order. A good rule of thumb is this: a field should reduce future work, not create another admin form with no clear benefit.

Who this extension may not be right for

Advanced Custom Fields Pro does not replace a dedicated directory component if you need complex entities, user dashboards, multi-step submissions, separate database tables, imports of thousands of records with business logic, or a custom admin panel. It also does not solve the visual page builder problem on its own. With YOOtheme Pro, the extension can pass values into Dynamic Content, but the design of sections, grids, and cards still has to be built with the template or the builder itself.

Another important boundary is security and permissions. A file upload field can be very convenient, but it requires careful checks for allowed extensions, file size, upload folder, and the Edit Custom Field Value permission. A map may be straightforward with OpenStreetMap, but Google Maps or Bing Maps require API keys in the system plugin. If the site does not have a responsible administrator who keeps extensions updated and reviews permissions, Pro features should be enabled carefully.

What to Check Before Installation and First Use

Before installing the extension, it helps არა just to confirm that the package matches your Joomla version, but also to understand in advance which contexts the fields will live in. Advanced Custom Fields Pro works on top of Joomla Fields, so a field may belong to articles, users, contacts, and third-party extensions if they support Joomla's standard field mechanism. That is one of the product's strengths, but it also requires careful preparation.

Site and environment compatibility

On the current Tassos product page, the latest branch is listed as compatible with Joomla 4, Joomla 5, and Joomla 6, along with PHP and MySQL requirements. On older Joomla 3 projects, you need to choose a legacy release and verify its requirements in the release notes. This guide does not tie the workflow to a specific version, but before installation you should check three things: the Joomla version, the PHP version, and any server extensions required by the specific field types you plan to use.

Standard text and link fields usually do not need additional PHP modules, but file upload and gallery fields are a different story. The documentation for ACF - File Upload requires fileinfo for MIME type detection and gd for image resizing. The documentation for ACF - Gallery also mentions exif and gd for image processing and watermarking. If those modules are missing, the interface may still load, but some features may behave inconsistently or fail entirely.

Contexts: articles, users, contacts, and third-party components

Before creating your first field, answer one simple question: where will the editor enter the value? For articles, the usual path starts at Content -> Fields. For user profiles, it is Users -> Fields. For contacts and third-party components, the location may be different. If the field is created in the wrong context, it will not appear in the form where you need it, even if the extension itself is installed correctly.

Joomla also supports field groups. If a field is not assigned to a group, it appears under the standard Fields tab in the edit form. If you have many fields, it is better to create groups such as "Location," "Files," "Gallery," and "Related Content." That is not only easier for editors, but it also reduces the chance that an important field will be left empty in a long list of settings.

Access permissions and editorial roles

One of the most common reasons custom fields behave strangely is not the field type itself, but permissions. In Joomla, every field has an Edit Custom Field Value permission. If a public user needs to fill in a field in a contact or registration form, that permission must be checked for the relevant user group. If an editor can see the field but cannot change the value, start with the field's own Permissions tab and the component settings.

Practical pre-installation check: write down one content type, the list of planned fields, the Joomla context, who fills in the field, who sees the result, whether file uploads are required, and which permissions are needed to save the value.

Installation and Initial Verification in Joomla

Installing Advanced Custom Fields Pro is broadly similar to installing any other Joomla extension: the administrator uploads the package through the standard installer, confirms that the plugins are enabled, and then creates a field in the appropriate section. You do not need to implement separate authentication inside the site project or connect any external API for content generation. For this extension, a correct Joomla environment and enabled field plugins matter much more.

After installation, do not start with the most complex field. Create a simple test article and one field that is easy to verify visually. For example, ACF - URL, ACF - Telephone, ACF - Country, or ACF - Articles in manual mode. That will quickly answer the main question: does the Fields tab appear in the edit form, and does the value show up on the front end?

Quick post-installation test

1. Open the Joomla admin panel and go to the section where you plan to use the field, for example Content -> Fields.
2. Click New and give the field a clear title, such as "Instruction File" or "Office Address."
3. In the Type field, select one of the options with the ACF - prefix. The documentation notes that this prefix makes it easy to distinguish extension fields from Joomla's built-in fields.
4. Save the field and open a test article. If the field is not assigned to a group, look for it under the Fields tab.
5. Enter a value, save the article, and open the public page. If the value does not appear, check Automatic Display, the field category, access permissions, and the article template override.

This test may look simple, but it quickly separates an installation problem from a field configuration problem. If a basic field displays correctly, you can move on to file uploads, maps, galleries, and display conditions. If even a simple field does not show up, do not waste time on Pro settings until you verify the basic Joomla Fields behavior.

What counts as a successful installation

A successful installation is more than just a Joomla message saying the package was uploaded. A solid minimum result looks like this: ACF - ... field types appear in the type list, a field can be created and saved, it shows up in the edit form for the right entity, its value is saved, the front-end page displays it in the expected place, and there are no warnings in the admin panel related to Tassos Framework system plugins.

If multiple Tassos extensions are installed on the site, check updates for the shared framework plugin separately. In an official Tassos security update, a vulnerability in Tassos Framework was described, and it was noted that updating one extension can also update the shared framework plugin. In practice, that leads to one simple rule for administrators: do not treat Advanced Custom Fields Pro as separate from your overall Tassos extension update strategy.

Field Configuration: From Data Type to Front-End Output

After installation, the real work begins not when you pick a nice-looking field type, but earlier, when you design the value itself. A field should have a clear purpose: does the editor enter one value or several, is it required or optional, can guests see it, should it display automatically, does it participate in filtering, can it be safely reused in a template? The more precisely you answer those questions before creating the field, the fewer rebuilds you will need later.

Field title, name, and group

The title is for the editor, while the system name is for the developer, the template, Smart Tags, and any integrations. Do not use generic names like "File," "Link," or "Photo." A few months later, no one will remember what they belong to. Use names such as "Instruction PDF," "Office Map," "Related Case Studies," or "Property Gallery" instead. The system name should be stable, short, and meaningful.

The field group controls the order and structure in the form. If you have only one or two fields, the default Fields tab may be enough, but for a real project grouping is a better approach. For example, a listing page might use groups like "Main Details," "Media," "Location," "Documents," and "Related Content." That way, the editor understands what to fill in first and what to review before publishing.

Automatic display and template-level control

Joomla can display fields automatically after the title, before the content, after the content, or not display them automatically at all. For simple projects, automatic display is convenient. But if you are building a clean, structured listing layout, it is better to choose Do not automatically display and output the values through a template, YOOtheme Dynamic Content, or an alternative layout. That helps you avoid situations where a field appears in an unexpected place, such as a category listing or next to the intro text.

Tassos documentation specifically describes alternative layouts for widget-based fields such as ACF - Address Autocomplete, ACF - Countdown, ACF - FAQ, ACF - Gallery, and ACF - Map. For those fields, Advanced Custom Fields gives you a more convenient override path than working only with the final HTML output. If you need to change the structure of a gallery or map, start with the documented layout override instead of editing the extension core.

Display Conditions: when a field appears on the site

Display Conditions are one of the most useful Pro features. On the Tassos product page, the available rules include page-based, user-based, geographic, time-based, device-based, e-commerce, and other signals. In practice, the most common conditions are based on content view, menu item, category, user, access group, and device type.

It is important not to confuse Display Conditions with edit-form logic. The Getting Started documentation notes that publishing assignments work on pages where the field is rendered for the user, but they are ignored on edit pages because that is how Joomla Core Fields behave. So if an editor can see the field in the article form, that is not necessarily an error. Conditions should be tested on the public page where the field is actually displayed.

How to choose between ALL and ANY

If a field should appear only when several conditions are all true at the same time, choose ALL logic. For example, only on a single article page, only in the "Properties" category, and only on desktop. If any one of several conditions is enough, use ANY. For example, display the block for two different menu items or for several user groups. Mistakes with ALL and ANY often look like "the field disappeared," when the real issue is that the rules became too strict.

Custom CSS and safe styling

Tassos documentation includes a Custom CSS setting in ACF - Options that is applied when the field appears on the site. It is a convenient way to make targeted visual fixes without editing template files. But the CSS should stay small and tied to a specific field or container class. Otherwise, one change can start affecting every similar element across the site.

.acf-resource-card {
  display: grid;
  gap: 0.75rem;
  padding: 1rem;
  border: 1px solid rgba(0, 0, 0, 0.12);
  border-radius: 8px;
}

.acf-resource-card__download {
  font-weight: 600;
}

That kind of CSS makes sense if you are using a custom layout for a file or article field and you control the HTML classes. The check is simple: open the article, make sure only the intended block changed, then open the category listing and a neighboring article. If the CSS affected extra elements, narrow the selector or move the styling into the template file.

How to Choose a Field Type Based on the Job, Not the Name

Advanced Custom Fields Pro includes many field types, and that can easily become a trap. An administrator sees a long list and starts choosing by label alone: need a link, pick URL; need an address, pick Address; need files, pick File Upload. In simple cases, that works. But on a production site, it is better to start from the behavior of the data: who enters the value, how often it changes, whether there are multiple values, whether it needs to appear in a filter, and whether it will be used in a template or a builder element.

For example, "address" can mean three different things. If the visitor only needs a plain text line such as "123 Main St, New York, NY," a regular text field or Address Autocomplete with unnecessary output disabled may be enough. If you need a map with one or more markers, ACF - Map is a better fit. If the address must become a filter by country or city, it is better to store separate values that JFilters or the template can read directly without parsing a long string. The same human meaning may call for different technical field types.

Content fields

Content fields are values that simply enrich an article: telephone, link, country, currency, video, audio, QR code, progress, download button. Their job is to give the editor a convenient input form and the visitor a clean result on the front end. For these fields, the key concerns are the label, placeholder, automatic display, and styling. They are easy to test: enter a value, save the article, open the page, and make sure the visitor clearly understands what is being shown.

If a value may legitimately be empty, do not turn it into a required content block. For example, not every listing has a video. In the template, it is better to hide an empty video block than to show a "Video" heading with no content under it. If the value is critical, such as a phone number on a branch page, then the field should be obvious to the editor, and your editorial publishing checklist should explicitly say that the article is not complete without it.

Media fields

Media fields such as File Upload, Gallery, Video, Audio, and Map have a much stronger effect on page speed and visual presentation. They need to be designed as part of the public interface. How many files are allowed? What happens if the editor uploads a very large image? Does the visitor need a lightbox? Should the map appear in category listings or only on the full article page? Those questions matter more than the simple fact that the field is a Pro field.

For media fields, it helps to define a "minimum good" value in advance. For example, for a property gallery: no more than 12 images, 3 columns on desktop, lightbox enabled, original images resized, thumbnails with a practical size. For an instruction file: one PDF, a clear link label, and forced download only if that actually improves the user experience. For a map: a height that does not dominate the page and centering based on markers.

Logical and relational fields

Articles, Chained Fields, True/False, FAQ, and display conditions all belong to page logic. They do more than add a value. They control relationships, choices, or visibility. These fields should be tested across multiple scenarios. A related article may later be unpublished. A chained list may receive incomplete data. A display condition may depend on Joomla routing. An FAQ block may be useful on a single article page but unnecessary in a category view.

For logical fields, create one simple maintenance rule: if a field affects what the visitor sees, it should have a test article where the administrator knows exactly what result to expect. That kind of "reference article" becomes especially useful after updates. Open the test content, check the fields, check the conditions, check the builder bindings, and you can immediately see whether the logic still works.

Files, Galleries, and Maps: The Three Most Practical Pro Field Groups

Advanced Custom Fields Pro is often chosen not because it offers "more fields" in the abstract, but because it handles several specific scenarios that are hard to build comfortably with standard Joomla tools. The most practical groups are file uploads, galleries, and maps. Each group has its own limitations, checks, and failure points, so they should not be configured the same way.

File Upload: documents, images, and security rules

ACF - File Upload lets the editor upload a file directly in an article or user form, and lets the visitor see it as a link, image, or custom layout. The settings include the upload folder, file limit, maximum size, allowed extensions, random filename prefix, download link display, interface preview, image resizing, and public output settings.

For a typical site, start with a strict ruleset. If this is a PDF manual, allow only .pdf, set the limit to 1 file, restrict the file size, and use a clear link label. If this is a profile image, allow only the needed formats, enable resize, and choose Image as the output layout. If you need custom captions, use title and description, which are supported in link/custom layouts through Smart Tags.

Be especially careful with the Allow Unsafe Files option. The documentation explains which files are considered unsafe: blocked extensions, PHP tags, null bytes, and other warning signs. For public or editor-facing forms, this option should not be enabled without a very strong reason. A safer approach is to allow only the required extensions, store files in a predictable folder, enable a random prefix if filename collisions are possible, and verify write permissions.

Gallery: when you need a photo gallery inside an article

ACF - Gallery is useful for real estate listings, portfolios, case studies, events, products, and tutorials with visual steps. The documentation describes Grid, Masonry, Slideshow, and Justified styles, along with settings for columns, spacing, sorting, lightbox, original image optimization, thumbnails, and watermarks. At that point, you are no longer just "attaching a few images." You are building a full front-end output block.

For the first rollout, choose the safest option: Grid or Masonry, a clear number of columns, moderate thumbnail sizes, lightbox enabled, original image resize enabled, and a fixed folder. Do not keep full-size original photos unoptimized if editors are uploading directly from a camera. Otherwise, a single gallery can hurt page speed more than the extension itself.

Map and Address Autocomplete: location data without chaotic embed codes

ACF - Map supports OpenStreetMap, Google Maps, and Bing Maps, along with markers, map dimensions, centering, zoom, info windows, maximum marker count, and an editor sidebar. Google Maps and Bing Maps require keys in the system plugin, and some OpenStreetMap scenarios may require a separate ArcGIS key. So before choosing a provider, check not just the look of the map, but also key availability, usage limits, and your site's policy.

ACF - Address Autocomplete solves a related problem, but its focus is the address itself: the editor selects a point on the map or enters an address or coordinates, and the field stores details such as country, city, ZIP code, latitude, longitude, street, and street number. This is especially useful for branch directories, event pages, and location profiles. If the visitor mainly needs a map with multiple markers, choose ACF - Map. If structured address data and separate values matter more, choose Address Autocomplete.

Related Articles, Chained Fields, and Display Conditions

The second major group of Advanced Custom Fields Pro features is useful where data does more than display on the page and instead connects content or changes page behavior. The key tools here are ACF - Articles, ACF - Chained Fields, and Display Conditions. They help build directories and reference pages without a heavy standalone component, but they require a clean structure.

Articles: manual and automatic relationships between articles

ACF - Articles lets you choose related articles manually or use automatic discovery, where an article becomes related through other fields of the same type. The settings include filters by category, tags, authors, and status, minimum and maximum article counts, ordering, and layouts. For output, you can use list layouts, grid variants, or a custom layout with Smart Tags such as {acf.article.title}, {acf.article.link}, {acf.article.introtext}, and {acf.article.field.KEY}.

A typical scenario is a knowledge base or directory. On a product page, the editor manually selects 3 related tutorials. The visitor sees more than a generic "Read also" block. They get cards with a title, intro text, and, if needed, the value of another field from the related article. Automatic discovery is useful if relationships should be mutual or built from already selected links, but before enabling it, test the output on a small set of articles.

Chained Fields: cascading lists without a complex form

ACF - Chained Fields creates dependent dropdown lists where each next selection depends on the previous one. The data can be entered manually in a CSV-like format or imported from a CSV file. The first row defines the labels of the lists, and the remaining rows define the values. This approach works well for choosing country, region, and city, equipment type and model, or service category and subcategory.

The key risk here is the quality of the source data. If the CSV contains inconsistent spellings for the same value, the editor will get a fragmented list. If the delimiter is wrong, the import will produce strange options. Before going live, run a test with 10 rows, verify the order, and only then import the full dataset. For front-end output, you can use a custom layout and Smart Tags such as {field.1.value}, {field.2.label}, and similar markers.

Display Conditions as an editorial tool

Display Conditions are often seen as a marketing feature, but in a content project they are really a tool for editorial order. For example, a "Directions" field should appear only on the single article page, not in category listings. An "Internal File" field may need to appear only for logged-in users. A contact button block may need to appear only for a specific menu item or a specific category.

Do not overcomplicate conditions without a clear reason. The more rules you add, the harder it becomes to understand why a field disappeared. A good practice is to keep one clear condition group per field and add a short note in the Note field explaining why it exists. If a rule depends on a category or menu item, test the article through multiple Joomla routes, because the active menu item can affect the output context.

Integrations with YOOtheme Pro, JFilters, and Third-Party Components

One of the extension's strongest advantages is not just its own fields, but the ability to pass their values into other Joomla tools. The Tassos product page specifically highlights compatibility with YOOtheme Pro Dynamic Content, and the documentation describes integration with JFilters. At the same time, it is important to remember that integration does not replace the field's basic setup. If the value is not saved correctly or does not display on a standard page, the builder and the filter will not fix it for you.

YOOtheme Pro Dynamic Content

Tassos documentation shows several scenarios: ACF - Video passes a URL into a video element, ACF - Gallery can serve as a multiple item source for a gallery element, ACF - File Upload passes File URL, Title, Description, and File Size into a list element, and ACF - Map passes coordinates, address, latitude, longitude, label, and description into a map element. This is especially useful when the page design is built in YOOtheme, while the editorial data stays in Joomla Fields.

After updates, there may be cases where a YOOtheme element needs to be reconnected. In the Tassos integration FAQ, it is explained that when the set of available properties expands, the configuration between a specific ACF field and a YOOtheme element may need to be reset. So before a large site update, make a list of pages where the builder uses ACF values and verify them on a staging copy.

JFilters: when fields become filters

Integration with JFilters makes the values of some ACF fields easier to read inside filters. The documentation gives examples such as Address, Articles, and Country, where the visitor sees a readable address, article title, or country name instead of a technical value or ID. This matters on directory-style sites where the user needs to narrow down a list of content using structured attributes.

But not every field is a good candidate for filtering. Tassos notes that fields with multiple or complex values such as Gallery, Map, File Upload, FAQ, Countdown, and PHP should be excluded from JFilters because they provide no practical filter benefit. That is a good example of why the extension should not be used mechanically. If a value cannot be represented as a simple filter, it is usually better to display it in the card than to force it into the filter sidebar.

Third-party components and Joomla Fields limitations

Advanced Custom Fields Pro can work with components that use Joomla Fields. But if a third-party component does not support Joomla fields, the extension will not magically add them. In a Tassos FAQ entry about J2Store, it is specifically noted that J2Store does not support Joomla custom fields out of the box, and support is possible through a separate Content custom fields app. That means that before planning any integration, you need to verify not only ACF itself, but also the receiving component.

Practical Example: a Listing Page with Address, PDF, Gallery, and Related Content

Let us walk through a concrete scenario. Suppose a Joomla site has a section called "Locations" with articles about branches, showrooms, or training centers. The goal is to let the editor fill in the address, map, PDF instructions, gallery, and related articles. The visitor should see a clean structured block on the page, not a collection of random links inside the article text.

Goal and preparation

The goal is a repeatable listing card: a normal article description at the top, followed by a structured block with "How to Get There," an instruction file, a photo gallery, and related content. Before configuration, you need to create a "Locations" category, plan a field group called "Location Data," confirm that Advanced Custom Fields Pro is installed, and make sure the required PHP extensions for file uploads and galleries are available on the server.

Setup steps

1. Create a field group called "Location Data" so all values appear to the editor in one tab.
2. Create an "Address" field using ACF - Address Autocomplete, or a map field using ACF - Map if you need multiple markers.
3. Create a "PDF Instructions" field using ACF - File Upload. In the settings, define a folder such as media/acf/object-files, set the limit to 1 file, add a size restriction, and allow only the .pdf type.
4. For public output of the file, choose the Link layout, set a clear Link Text, and enable Force Download if the user should download the file rather than open it in the browser.
5. Create a "Location Photos" field using ACF - Gallery. Start with Grid or Masonry, choose the number of columns, and enable lightbox.
6. Create a "Related Guides" field using ACF - Articles. Limit the selection to the "Guides" category and set a maximum of 3 to 5 articles.
7. For each field, verify the category, access level, and automatic display settings. If you are building your own layout, disable automatic display and output the values through a template or builder.

Result verification

Create a test article in the "Locations" category and fill in all fields. Then check four states: the article in the admin panel, the single article page, the category listing, and the page under a different menu item if the site has multiple routes to the same article. This matters because display conditions can depend on the view, category, menu item, and access level.

The expected result is this: the editor sees the fields in a separate tab, the file uploads without a red indicator, the gallery shows thumbnails, the map or address is saved correctly, the related articles appear as a list or cards, and the public page does not show empty blocks. If a field is empty, the template should either hide it or show a clear fallback without leaving broken spacing behind.

A detail people often miss

Do not make every field required if the editor will not always have the data. For example, a new branch may not yet have a PDF guide or a complete gallery. It is better to make only the critical fields required and hide empty values in the template. Joomla does not display empty fields in its standard output, but a custom layout or builder element may still need its own empty-state check.

Workflow for Editors and the Administrator

After the technical setup is complete, the extension should become part of the editorial workflow. Otherwise, fields quickly become inconsistent. One editor uploads the PDF into one folder, another leaves the gallery without captions, and a third chooses related articles from the wrong category. Advanced Custom Fields Pro gives you the form, but it does not replace content rules. That is why every field set needs a short internal standard.

Instructions for the editor

The editor does not need to know how layouts work or how the Joomla Fields API is structured. They just need to know what to fill in and how to verify the result. For a listing page, the instructions might be: first fill in the title and main text, then open the "Location Data" tab, choose the address, upload one PDF, add 5 to 10 photos, select related guides, and save the article. After saving, open the public page and confirm that the map, file, gallery, and related content are visible.

It is especially important to explain the difference between an empty field and an actual error. If a field is optional and the data is not available yet, it can stay empty. If a file does not upload, a red indicator in the uploader is not something to ignore. It means the format, file size, or permissions need to be checked. If the map does not show the point, the fix is to check whether the marker was saved, not to paste a map manually into the article body.

Administrator checklist after updates

It helps for the administrator to keep a separate test article where all important field types are filled in. After updating Joomla, the template, YOOtheme, JFilters, or Advanced Custom Fields Pro, open that article and walk through the same route every time. First the edit form: the fields display correctly, the values are still saved, and File Upload shows the existing files. Then the public page: the blocks are still in place, the conditions still work, the gallery still opens, and the map is still visible. Then the integrations: the builder still receives the values, and the filter still shows readable options.

This checklist is especially important on sites with multiple administrators. If everyone tests only "by eye," some problems will not be caught until visitors complain. If you have a reference article and a clear review process, maintenance becomes much more predictable.

When it is better to roll back a configuration

Rolling back is not only for obvious failures. If a new field makes the form more complicated and editors regularly leave it empty, it may not be needed at all, or it may belong in another group. If Display Conditions have become so complex that no one can explain why a block is visible or hidden, simplify the logic. If a gallery makes the page too heavy, temporarily reduce the number of images and their dimensions instead of trying to compensate only with caching.

A good Advanced Custom Fields Pro setup should survive a normal editorial day. The editor opens the article, fills in the fields, saves it, and checks the result. If every article still requires an administrator to manually fix the layout, conditions, and styles, the field architecture needs another pass.

Checking the Result After Configuration

Result verification should not happen only at the end of the project. It should happen after each new field type is introduced. Advanced Custom Fields Pro touches several layers at once: the field in the admin panel, value storage, permissions, display, display conditions, the template, cache, builder, or filter. If you wait until ten fields are configured before testing, finding the cause of a problem becomes much harder.

Mini checklist for every field

• The field is created in the correct Joomla context and assigned to the right category or group.
• The field's system name is clear and does not conflict with existing fields in other contexts.
• An editor with the correct role can enter the value and save the article.
• An empty value does not break the public page.
• A filled value appears where expected and does not appear where it should not.
• For files, verify the type, size, folder, write permissions, preview, and public link.
• For galleries, verify image sizes, lightbox, mobile display, and loading speed.
• For maps, verify the provider, keys, block height, centering, and behavior with multiple markers.
• For YOOtheme or JFilters, verify that the integration is using the actual ACF value rather than static text.

How to test cache and template overrides

If the field is configured correctly but nothing changes on the site, clear the Joomla cache and the template or page builder cache if one is being used. Then temporarily switch Automatic Display to a standard output position and check whether the value appears without your custom layout. If it does, the problem is almost certainly in the template override, builder binding, or CSS that is hiding the block.

If the standard output still does not appear, go back to the field itself: category, access, language, published state, display conditions, value edit permissions, whether the field is actually filled in on the article. That order saves time: first check the data, then the display, then cache and styling.

Common Problems and Diagnostics

Most Advanced Custom Fields Pro issues do not live in one single place. They usually show up at the boundary between Joomla Fields, the specific field type settings, access permissions, and public output. Below is a practical diagnostic guide based on the kinds of problems that actually appear when configuring Joomla extensions like this.

The field exists but is not visible in the edit form

Symptom: the administrator created the field, but the editor cannot see it in an article, user profile, or contact. Possible causes include the wrong context, category, access level, language, unpublished status, the field group being somewhere unexpected, or a third-party component that does not support Joomla Fields.

Check the creation path first. For articles, it is Content -> Fields; for users, Users -> Fields. Then open the field itself and verify the category, access, language, and published state. If the field belongs to a third-party component, confirm in that component's documentation that Joomla custom fields are supported.

The field is visible in the admin panel but does not display on the site

Symptom: the value is filled in and saved, but the visitor cannot see it. Start with Automatic Display. If Do not automatically display is selected, the field must be rendered by the template, a builder element, or a layout. If automatic display is enabled, check the Display Conditions: ALL logic may be requiring too many matches.

Also check whether the field is being hidden by a template override. On sites with custom templates, the custom fields output block is sometimes missing from an overridden article layout. A quick test is to temporarily switch the article to the default template or enable a standard display position.

Display Conditions do not work as expected

Symptom: the field appears on the wrong page or disappears everywhere. Possible causes include incorrect ALL/ANY logic, a condition tied to the active menu item, confusion between Include and Exclude, or testing conditions in the edit form instead of on the public page.

The safest fix is to leave only one condition, test the result, and then add the remaining rules one by one. If the field should appear only on a single article page, use a view-based condition, not just a category-based one. If the rule depends on a menu item, verify the actual URL route used to open the article.

File Upload shows an error or a red indicator

Symptom: the file does not upload, or the uploaded files list shows a red status. The File Upload documentation points to common causes: the file exceeds the size limit, its extension is not in Allowed File Types, or the file count limit has been reached. Also check the upload folder, write permissions, and whether the fileinfo PHP extension is available.

If the error involves images, verify gd, the resize settings, and the actual file format. For public forms, do not enable unsafe file types just to work around the error. It is better to expand the allowed list only for the required format and verify the MIME type.

The upload field is visible, but the user cannot attach a file

Symptom: the field appears disabled or the value is not saved. The File Upload documentation directly points to Edit Custom Field Value permissions in both the field settings and the component settings. For registration and contact forms, check the Public group. For editors, check the relevant editorial group.

The safe fix is simple: allow value editing only for the groups that actually need to fill in the field. Do not open broader component permissions if it is enough to configure a specific field.

The gallery hurts page speed

Symptom: after adding galleries, the page becomes heavy. The likely cause is that editors are uploading large originals and the optimize original image and thumbnail settings are not restricting size. Check width, height, resize method, image count, and whether lightbox is enabled.

The fix is to define sensible sizes for originals and thumbnails, limit the number of files, choose a layout that does not display too many images at once, and review the mobile view. If the site uses a separate image optimization system, make sure it also processes the gallery folder.

A YOOtheme element broke after an update

Symptom: after updating ACF or YOOtheme, an element no longer receives the field value. The Tassos integration FAQ warns that when ACF properties are expanded, some YOOtheme bindings may need to be reconfigured. Check the Dynamic Content source, the multiple item source, and the exact field property being used.

The fix is to open the page in YOOtheme, select the source again as Page -> Article, then choose the specific ACF field and the required property. After that, clear the cache and test the page on the front end.

There is a post-update risk related to Tassos Framework

Symptom: the site has not been updated in a long time, or multiple Tassos extensions are installed. The official Tassos Framework security update notes that the affected extensions include those that bundle the shared system plugin, including Advanced Custom Fields. Check the extension version and the Tassos Framework version under System -> Plugins.

If the framework version is below the patched branch, update the extension using the standard Joomla process and test again. If Tassos Framework remains after uninstalling Tassos extensions and is no longer needed, the official recommendation is to remove the leftover plugin manually through the admin panel.

SEO, Performance, Security, and Maintenance

Advanced Custom Fields Pro does not guarantee better search rankings, and it does not make a site fast automatically. What it does do is help you store data cleanly, and clean data is much easier to output in clear markup, cards, lists, filters, and template blocks. In that sense, the extension improves page quality indirectly through structure, repeatability, and output control.

SEO practice without over-optimization

Use fields for facts that actually help the visitor: address, specifications, documents, related guides, gallery, and answers to real questions. Do not create separate fields just to repeat keywords. It is better to output one useful block with a file, map, or related content than to repeat the product name five times in different places.

If a field outputs a document link, give it meaningful link text. If a field outputs a gallery, make sure captions and image alt text are covered in your editorial workflow. If a field is tied to an FAQ block, make sure the questions do not simply repeat the page's promotional copy. Structured data is useful only when it reflects real content.

Performance and heavy fields

The most performance-sensitive fields are galleries, maps, videos, and external embeds. For galleries, use resize and thumbnails. For maps, use a reasonable height and marker count. For video, do not embed several heavy players without a real reason. If a field is displayed in a category listing, it may repeat many times on the same page. That is why complex fields are usually better on the single article page, while category views should use short text or a lighter indicator.

Upload security

For File Upload, follow the principle of minimum necessary access. Allow only specific extensions, set limits for size and file count, verify the upload folder, and do not enable unsafe files unless there is no other reasonable option. If files are uploaded by public users, the Edit Custom Field Value permission should be open only for the required form and the required field.

For updates, keep your attention not only on the extension itself but also on Tassos Framework. After major updates, verify field creation, value saving, front-end output, file upload behavior, builder integrations, and filters. That takes less time than diagnosing problems after editors start reporting them.

When Advanced Custom Fields Pro Is the Right Choice

Advanced Custom Fields Pro is worth using if your Joomla site needs structured data, but you do not want to build a separate component for every listing or content block. The extension works especially well in directories, knowledge bases, user profiles, event pages, portfolios, reference sections, and any content where the editor needs a clear form and the visitor needs a clean, predictable result.

Before rolling it out, verify the environment, choose 5 to 8 fields you actually need, configure groups and permissions, create a test article, check the public output, and only then connect the builder, filters, and template overrides. Do not start with dozens of fields and complex conditions. Start with one well-tested scenario, like the listing page example above, and expand the structure only when the editorial workflow has clearly become easier.

If you already understand which fields your site needs, go to the download section and download Advanced Custom Fields Pro, then test it on a staging copy of the site. That order is safer than installing it directly on the live project: you will see the interface, evaluate which Pro fields you really need, and understand in advance which permissions, folders, conditions, and template blocks will be required.

The core decision criterion is simple: the extension should reduce content chaos. If it helps the editor enter data through a clear form, helps the developer output that data predictably, and helps the visitor understand the content faster, then Advanced Custom Fields Pro is a good fit for the project. If the need comes down to one rare block or one highly specific page, start with standard Joomla tools and avoid adding complexity without a clear reason.