AMPZ Extended - Joomla Extension

A Guide to Configuring and Using AMPZ Extended on a Joomla Site

AMPZ Extended is a Joomla extension for displaying social media buttons, share blocks, follow buttons, and click statistics. In current official sources, the product is more often called AMPZ Social Sharing, so in this guide those names refer to the same extension family from roosterz.nl. This guide focuses on practical use rather than marketing claims: where to enable positions, how to choose networks, how to avoid overcrowding the mobile screen, how to use shortcodes, and how to verify that the buttons actually help users share your content.

This material is intended for a Joomla administrator who already has access to the installation ZIP archive and wants to roll out AMPZ Extended safely on a live site. We will go from pre-installation checks to test publishing, configure behavior across different pages, troubleshoot cache conflicts, and review comparable alternatives. Special attention is given to what matters most for social buttons in particular: privacy, unnecessary external requests, mobile behavior, negative social proof, and choosing the right output locations.

This guide does not replace the official documentation. Its purpose is to show how to turn scattered settings into a working setup: which parameters to touch first, which ones to leave for later, where mistakes happen most often, and what signs indicate that the extension is configured cleanly. If you are moving a site between Joomla versions, using a third-party content component, or enabling aggressive caching, do not skip the compatibility and troubleshooting sections.

What Problem the Extension Solves on a Real Joomla Site

The main purpose of AMPZ Extended is to give visitors a convenient way to share a specific page of your site through the right social network, messenger, or communication channel. That sounds simple, but in practice social buttons often break a page in one of two ways: either they are so subtle that nobody uses them, or they are so intrusive that they hurt performance and get in the way of reading. AMPZ aims for the middle ground: you can place buttons in multiple positions, limit them by components and categories, adapt them for mobile screens, and collect click statistics.

This is especially useful in Joomla because of the variety of components. On one site, content may appear as regular articles, store product pages, blog posts, event pages, forms, catalog pages, or content from a third-party builder. The official AMPZ listing emphasizes that the extension is not limited to native Joomla articles alone: the administrator selects which components should display the buttons. That does not mean you can enable everything on every site without checking first, but it does provide the right starting point: identify the page types first, then assign positions.

Good social button configuration starts not with choosing icons, but with asking which pages actually make sense for visitors to share. For a news article, tutorial, product review, recipe, or charity campaign, a share button may be useful. For a login page, cart, contact form, private account area, or utility page, it is often unnecessary. In AMPZ, this is handled through component selection, category and article exclusions, separate position settings, and shortcodes.

The second important layer is mobile behavior. WhatsApp, Telegram, and phone actions usually make the most sense on smaller screens. The official documentation notes that some mobile buttons are shown only when mobile mode is active and the screen is below a defined width threshold. That means desktop testing is not enough: you need to open the page on a phone or in responsive browser mode and make sure the bottom bar, popup combination, and fly-in do not cover the content.

The third layer is statistics. AMPZ tracks button clicks and shows which networks and positions are actually used. It is not a full analytics platform, but that level of data is enough to choose between inline, sidebar, fly-in, and shortcode placement. If the statistics show that visitors almost never click the fly-in while the inline block under the article performs better, you can remove the more intrusive block and keep a clear button close to the content.

Who AMPZ Extended Is Good For, and When Another Approach May Be Better

The extension is a good fit for sites where content is genuinely shared through social channels: editorial magazines, blogs, educational sites, content libraries, deal pages, event pages, campaigns, and communities. It is especially useful when you need more than just a row of icons and want to manage multiple positions while comparing how well they perform.

AMPZ Extended is worth considering if your site has different page types and you need control at the Joomla component level. For example, maybe the buttons should appear in articles and K2 items, but not on contact pages or category listings. Or maybe the inline block should sit below the content, the sidebar should appear only on long-form articles, and a separate shortcode should go in a custom module next to a call to share. In cases like these, a basic module with one fixed position quickly becomes too limiting.

The product may be excessive for a small brochure-style site with three static pages and no ongoing content. If the site does not have a real scenario where visitors share specific pages, social buttons become decorative noise. In that case, simple links to the company’s social profiles in the template are often enough, rather than a dedicated sharing extension. Another questionable scenario is a site with strict privacy requirements and a very low tolerance for external requests. AMPZ claims to minimize external requests and cache counters intelligently, but the site owner still needs to verify which buttons are enabled, which networks are used, and what requests are actually leaving the browser.

It is also worth evaluating the design. AMPZ offers several built-in button styles, sizes, corner radius options, labels, counters, and hover effects. If the site has a strict corporate design, it is not a good idea to enable every effect and dozens of networks. It is better to start with a smaller set: Facebook, LinkedIn, X or Bluesky, Email, Print, plus WhatsApp and Telegram for the mobile scenario. Then expand based on actual statistics rather than on the idea that everything should be available just in case.

A practical selection criterion: if you need positions, mobile mode, shortcodes, and click stats inside Joomla, AMPZ Extended looks like a strong fit. If all you need is a single row of simple share links with no counters and no settings panel, look at lighter free alternatives.

What to Check Before Installation

You do not need to run a full site audit before installation, but a few checks can save hours of troubleshooting. AMPZ Extended works as a Joomla extension with a component and a plugin, which means it depends on the condition of the CMS itself, access permissions, caching, and any third-party components where the buttons should appear.

Joomla Compatibility and Site Health

The JED listing for AMPZ Social Sharing shows compatibility with several current Joomla branches, including modern CMS versions. The official product page also states support for Joomla 3, 4, 5, and 6, while one of the developer’s FAQs includes a note about using the backward compatibility plugin for Joomla 5. Because of that mismatch, the safest approach is simple: before installing, cross-check the JED listing, the developer’s page, and your own admin update panel. If the site was updated recently or is preparing for a migration, check both the backup and the staging copy first.

Minimum pre-installation checklist:

• A fresh backup of both files and the database is available.
• The site works without errors in the Joomla admin panel.
• You have administrator rights to install extensions.
• You know which components should display the buttons: Joomla articles, a blog, a catalog, a store, or another component.
• You know whether page cache, system cache, template cache, or server-level external caching is enabled.
• You have a test page where you can verify the buttons without risking changes to the homepage.

A Map of Pages Where Sharing Makes Sense

The most common mistake is enabling social buttons on every page and then wondering why they show up in unexpected places. AMPZ can display positions across the entire site, but the documentation explicitly warns that if you enable global output, the more flexible rules below may no longer apply. For any serious site, it is better to map the output in advance.

Write down three groups of pages. The first group is where buttons belong: articles, news posts, tutorials, case studies, product reviews, and event pages. The second is where buttons are undesirable: cart, checkout, user account, login form, search, contacts, and technical landing pages. The third group is the gray area: categories, content lists, catalog items, and tag pages. For those disputed pages, make the decision only after reviewing the actual result.

Privacy and External Requests

Social buttons are often criticized for generating unnecessary requests to external services. AMPZ is positioned as a privacy-conscious solution with minimal external requests and cached counters, but the administrator is still responsible for the actual configuration. Do not enable networks your audience does not use. Do not show share counts if they are unnecessary or if retrieving them adds extra delay. If the site serves an audience with strict privacy requirements, inspect the page with browser developer tools and verify which domains load before the click and after the click.

A useful habit: before enabling AMPZ across all content, open one test article, record the number of external requests without the extension, enable one minimal set of buttons, and compare the result. That makes it much easier to separate extension-related issues from scripts that were already there in the template, analytics stack, or advertising widgets.

Installation and the First Check After Enabling It

The official AMPZ documentation describes the standard Joomla installation flow through the Extension Manager: sign in to the admin panel, open the extension install area, select the ZIP archive, and start the upload. In modern Joomla versions, the exact interface path may differ slightly by label, but the logic stays the same: install from package, then open the AMPZ Social Sharing component and verify that the extension is enabled.

An Installation Sequence With Minimal Risk

1. Create a backup and make sure it can actually be restored, at least on a staging environment.
2. Open the Joomla admin panel and go to the extension installation section.
3. Select the AMPZ Extended installation ZIP archive and start the installation through Upload Package File or the equivalent interface option.
4. After the success message appears, open Components - AMPZ Social Sharing.
5. Verify that the component opens without errors and that the related plugins are enabled in the extension manager.
6. Do not enable every position at once. Start with one test position and one test page.

If the installation fails, do not keep retrying the upload over and over. At this stage, errors are usually related to file permissions, archive upload size, the Joomla temporary folder, an incompatible CMS version, or a damaged archive. Save the exact error message first, then check the Joomla system log, the state of the tmp folder, and your hosting file upload limits. If the error looks like a package or compatibility issue, it is better to consult the documentation and the developer’s support rather than manually unpacking the archive on a live site.

A Safe Initial Configuration

After installation, open the AMPZ settings and enable a minimal configuration. For testing, one inline position below the article, two or three networks, and one category are enough. Do not enable fly-in, sidebar, mobile mode, all counters, and dozens of networks at the same time. If something goes wrong after that kind of maximum-start setup, it becomes hard to tell which option actually caused the problem.

Recommended first test:

• Position: inline below the article.
• Component: native Joomla Articles or the component where you definitely want the buttons to appear.
• Category: one test category or one test item.
• Networks: Email, Print, Facebook, or LinkedIn, with WhatsApp/Telegram added only after mobile mode is verified.
• Counters: disabled at first, then enabled separately if needed.

After saving, clear the Joomla cache and browser cache if applicable. Open the test page in a private window, verify that the buttons appear only where expected, and make one safe test click on a network like Email or Print. For external networks, you do not need to publish a real post. It is enough to confirm that the correct share window opens with the current page URL.

Position Map: Inline, Sidebar, Fly-In, and the Mobile Bar

One of AMPZ Extended’s strongest features is its support for multiple placement types. Each one solves a different problem and should not be enabled mechanically on every page at once. Inline works next to the content, sidebar keeps the buttons visible, fly-in draws attention at a chosen moment, and mobile mode adapts the panel to the phone screen.

Inline: The Calmest Starting Point

The inline position displays a horizontal panel above the article, below the article, or in both places. For most sites, this is the best first option because the buttons appear in the reading context and do not cover the interface. In the inline settings, it is worth paying attention to Display on, Display above title, button width, entry animation, hover effect, Combine after, labels, and counters.

A practical setup is to show the inline block below the article, leave the width on auto, combine extra buttons after four, and hide labels if the buttons sit inside a narrow container. If the site has long-form content and users usually share after reading, the bottom position makes more sense than the top. If the content behaves more like a news feed and users may share right after reading the headline, the top position can also work, but it should be tested next to article metadata, ads, and the lead image.

Sidebar: Visibility Without Intruding on the Text

The sidebar is a floating vertical panel on the left or right side. It is useful on long articles where a visitor scrolls through the content and may want to share before reaching the end. Important settings include screen side, button spacing, animation, visibility condition, and Combine after. If the sidebar is always visible while inline is enabled too, the page may start to feel overloaded. A softer approach is to show the sidebar only when the inline block is no longer in the visible area.

Before enabling the sidebar, test the template. On narrow containers and sites with fixed side panels, a floating block may conflict with navigation, a back-to-top button, a chat widget, or a consent banner. If the buttons overlap the text, reduce the number of networks, move the panel to the other side, or disable the sidebar for problematic components.

Fly-In: Use It as a Targeted Trigger

The fly-in is a popup-style panel that appears from the bottom or side based on a trigger. In AMPZ, it can work as either a share button block or a follow button block. It is a powerful tool, which is exactly why it should never be enabled without a clear scenario. An appropriate example would be showing a gentle “share this guide” block after a user finishes reading a long tutorial, or inviting them to follow the project’s social page. An inappropriate example would be showing the fly-in immediately after every page load.

Key fly-in parameters include the title, text, screen side, animation, share/follow mode, homepage visibility, component override, trigger by scroll-to-bottom or delay, and the amount of time the panel stays hidden after a user closes it. If the user closes the fly-in, respect that choice: set a hide period so the panel does not come back on every page.

Mobile Mode: A Separate Logic, Not a Shrunken Desktop Version

Mobile mode should not be a copy of the desktop panel. A phone offers less space, users are more likely to share through messengers, and the lower part of the screen may already be occupied by the browser’s own navigation. The network documentation notes that WhatsApp, Telegram, and Phone are displayed only when mobile mode is active and the screen is below the configured threshold. That is why mobile mode must be tested separately: which buttons are visible, how many appear before combining, whether the cookie banner gets in the way, and whether the panel is easy to close.

For a typical site, start with three or four mobile buttons plus a “more” button. On a mobile screen, counters often take up more space than the value they provide. If your audience actively uses WhatsApp and Telegram, those buttons should move higher in the list, but only after you confirm that the links actually open correctly on a real device.

Networks, Follow Buttons, and Output Order

The Networks section controls which social networks are enabled and in what order they appear. The official documentation describes an interface that uses green and red states for enabling and disabling, along with drag-and-drop sorting. The order in the settings becomes the order on the site, so this is not just a cosmetic detail - it is part of the user flow.

Do not start with the longest possible list. Start with the network where your audience has a real reason to share. For B2B content, LinkedIn and Email are often the most important. For a news site, Facebook, X, or Bluesky may matter more. For recipes, images, and product pages, Pinterest can make sense. For local services, WhatsApp and Telegram are often relevant on phones. Print can be useful for tutorials, checklists, and reference pages. Reddit, Tumblr, VK, OK.ru, Pocket, Buffer, Flipboard, and other networks should be added only where the audience actually uses them.

Share and Follow Do Not Solve the Same Problem

A share button shares the current page. A follow button leads to the site’s or brand’s profile. AMPZ lets you use follow buttons in fly-ins and other specific scenarios. Do not mix them without making the distinction clear to the user. If the panel headline asks the user to share the article but some of the buttons lead to a profile instead, the result is confusing. If the goal is subscription, the fly-in text should say that directly and should not imply that the current page will be shared.

Counters and Social Proof

Counters can help when a piece of content already has visible engagement. But zeroes or very low numbers create the opposite effect: visitors see that almost nobody has shared the content. AMPZ includes settings for share counts and total shares, and the product page specifically mentions the ability to control when the total share count becomes visible so you do not create negative social proof. The practical approach is simple: on a new site, keep counters off at first, collect some data, and then enable them only where they build trust.

If counters are enabled, check both load speed and external requests. AMPZ claims asynchronous retrieval and caching, but the real result depends on the selected networks, hosting environment, and site cache. Do not enable counters everywhere just for decoration. In some cases, one total counter below the article is enough, while the sidebar works better without numbers.

Handling Many Networks With Combine after

The Combine after setting helps keep the panel from turning into a long strip of buttons. The documentation gives a default value where, after several visible buttons, the rest are grouped under a single popup button. That is useful on sites with a broad audience: the most important networks remain immediately visible, while less common ones stay available without breaking the design.

For a desktop panel, four or five visible networks are usually enough. For a mobile panel, fewer is better. If the popup feels too crowded during testing, it is better to cut the list than to force users to choose among twenty options. The “more” button should simplify the interface, not hide chaos inside it.

Design, Speed, and Privacy: Settings You Should Not Skip

AMPZ’s visual settings matter for more than appearance alone. Button size, labels, hover effects, corner radius, counters, and animations affect visibility, accessibility, and how quickly the interface is understood. On an overloaded site, a bright floating panel may distract users from reading or buying; on a quieter blog, icons that are too subtle may go unnoticed.

Labels, Sizes, and Hover Effects

Labels are helpful when an icon may be unclear or when the site targets a less technical audience. But labels also take up space, especially in the inline position and on mobile screens. If the buttons sit inside a narrow container, start with icons only, and show text labels only on hover if that fits the design. For accessibility, also verify contrast and readability, because a nice brand color does not always provide enough separation from the background.

Hover effects and animations should be restrained. They help signal interactivity, but they should not make the buttons jump around every time the mouse moves. For a business site, a subtle background change or slight lift is usually enough. For a media site, a more noticeable effect may be acceptable, but only after testing on real devices.

Caching and External Counters

Social counters may require requests to external sources. AMPZ describes smart caching as a way to reduce those requests while preserving functionality. But caching is not a magic speed boost - it is a tradeoff between data freshness and system load. If counters refresh too often, the page may slow down. If they refresh too rarely, the numbers drift away from reality. For most content pages, minute-level precision is unnecessary, so a calmer refresh frequency is usually the better choice.

After changing cache settings, check three things: the speed of the first page load, the speed of the second load, and whether the output still renders correctly after clearing the Joomla cache. If the buttons disappear only when page cache is enabled, the issue may not be AMPZ itself but the way the full page or module position is being cached. In that case, disable the problematic cache layer in testing first, then re-enable layers one at a time.

Privacy and a Minimal Set of Networks

The official AMPZ listing emphasizes privacy and the absence of data transfer without user action. That is a meaningful advantage for a social sharing extension, but the administrator still needs to think practically. The more networks you enable, the greater the chance of unnecessary scripts, extra windows, blocked domains, or odd behavior in browsers with tracking protection. Start with the networks you can justify clearly: “users share through WhatsApp here,” “people read business content here and send it to LinkedIn,” or “this is a page people print.”

If your site policy requires a separate mention of social buttons, add it to the privacy page. Do not promise that no external service will ever be involved: after a click, the user still goes to the selected network or opens its sharing window. It is more accurate to say that the buttons support voluntary user actions and that the set of enabled networks is limited to practical necessity.

Shortcodes and Joomla Modules: How to Place Buttons Exactly Where You Need Them

Shortcodes are one of AMPZ Extended’s most useful features because they let you go beyond the standard positions. In the documentation, the example appears as a tag like {ampz: module_right}, which you can insert into an article or a custom HTML module. The result is that the buttons appear exactly where the tag is placed and where Joomla processes the content.

When a Shortcode Is Better Than a Standard Position

Standard positions work well for repeatable page layouts. A shortcode is the better choice when context matters more than a global rule. For example, in a tutorial you might place a small “share this checklist” block after the practical section. In a catalog, you might display buttons only in a dedicated module position next to a product description. On a campaign page, you might place follow buttons beside the community block while keeping share buttons below the main text.

A shortcode is especially helpful if the template does not provide a clean place for the inline position, or if a third-party component renders content with complex markup. Instead of trying to “catch” the right container through component settings, you can create a custom module, assign it to the appropriate menu items, and place the AMPZ Shortcode there.

The Shortcode Creation Workflow

1. Open Components - AMPZ Social Sharing.
2. Go to the Shortcodes tab and create a new shortcode.
3. Give it a clear name, such as article_bottom or campaign_share.
4. Select the networks and sort them in the desired order.
5. Configure the button type: share, follow, or a combination if the scenario truly calls for it.
6. Save the shortcode and confirm that it appears in the list.
7. Insert the tag into an article or a custom module using the AMPZ Shortcode button if that option is available in the editor.

The documentation recommends using the shortcode insertion button because manual typing is easy to break with an extra space or a typo. If you do type the tag by hand, save the page, open the public view, and make sure the tag turns into buttons rather than remaining visible as plain text.

Custom HTML Module Details That Matter

In Joomla, a custom module is displayed based on its template position and menu assignment. For AMPZ, that means the shortcode may be created correctly but still not appear on the site because of the module itself: it may be unpublished, assigned to the wrong position, limited to the wrong menu items, or stripped by the editor. If the shortcode is inserted into a module, check Status, the template position, the Menu Assignment tab, and any content preparation setting required for plugin processing.

The safest workflow is this: first create a module with simple text such as “test,” assign it to the target page, and verify that it appears. Then replace that text with the AMPZ shortcode and test again. If the module disappears after the replacement or displays the raw tag, the problem is no longer the module position - it is content processing, editor behavior, or the shortcode itself.

Practical Scenario: Buttons for an Article Section and a Separate Block in a Module

Let’s look at a realistic setup. A Joomla site has a section called “Helpful Resources.” You want to show buttons below each article, avoid displaying them in the category listing, add mobile WhatsApp and Telegram buttons, and place a separate compact shortcode in the right column of one campaign page. We are not enabling the fly-in yet, because the goal is to validate the calmer positions and the statistics first.

Goal and Preparation

The goal is to get a clean share button block at the bottom of articles plus a separate module block on a campaign page. Before starting, AMPZ Extended should already be installed, a test article should be published, the article category should be known, and a template position should be available for the module. You will also need either a phone or responsive browser mode to test the mobile panel.

Configuration Steps

1. Open the AMPZ settings and enable the inline position.
2. In Display in Components, choose the Joomla Articles component or the third-party component you want.
3. Disable global output on all pages if you plan to use exclusions and categories.
4. Enable output only in the desired category, or exclude the categories where buttons should not appear.
5. In the inline settings, choose display below the article and set extra button grouping with Combine after.
6. In the networks section, enable a few primary desktop networks, then add mobile WhatsApp and Telegram.
7. Configure mobile mode so the phone shows a short set of buttons and the lower content is not covered.
8. Save the settings, clear the cache, and test the article.
9. Create a shortcode for the campaign page with only the networks that make sense in that context.
10. Create a Joomla custom HTML module, insert the shortcode, publish the module in the proper position, and assign it only to the campaign page.

Verifying the Result

On the desktop page, the article should show the inline block below the content. In the category listing, the buttons should not appear if you excluded the category view. On a phone, mobile buttons or a compact panel should be visible, and WhatsApp and Telegram should open the correct sharing flow. In the campaign module, the shortcode should render as a separate button set rather than duplicating the main inline block.

Quick verification summary: the buttons appear only on the selected pages, do not cover the text, open the correct URL of the current page, and do not duplicate inside the category view. Only after that does it make sense to enable the sidebar, fly-in, or counters.

What Can Go Wrong

If the buttons show up on the homepage or in the category listing, check the global all-pages output setting and the category view exclusion. If the shortcode appears as text, verify its name, the insertion method, content preparation in the module, and editor settings. If mobile buttons are not visible on desktop, that may be expected behavior: the documentation states that some mobile networks appear only when mobile mode is active and the width threshold is met. If the buttons open the wrong link, check the SEF settings, the canonical URL, and the cache.

AMPZ Statistics and Improving the Configuration After the First Data Comes In

The statistics in AMPZ are not there to make the dashboard look impressive - they are there to support decisions. The product page and documentation describe a dashboard that shows clicks by network and by position. That helps answer questions you cannot resolve by intuition alone: which networks people actually click, which position performs better, whether the fly-in is worth using, whether counters should stay enabled, and which buttons can be removed.

First, let the setup run on real traffic for a while. Do not move positions around every day, or the data will stop being comparable. Once clicks start accumulating, review the distribution by network. If Email and Print account for a meaningful share while rare social networks go unused, trim the panel with confidence. If mobile messengers are active, move them higher in the output order. If the sidebar gets almost no clicks and users complain that it covers content, disable it or show it only on long-form pages.

How to Read the Stats Without Fooling Yourself

A click on a button is not the same as a successful social post. A user may open the window and close it. For that reason, AMPZ statistics are better treated as a measure of intent to share rather than as an exact count of external shares. Even so, they are far more useful than guessing. If a position receives no clicks at all, it is wasting space. If one network consistently leads the others, it should become more prominent.

Compare like with like. You should not directly compare a homepage news item, a long-form guide, and a utility page. It is better to choose one category, one position, and one date range. For a test, you can leave inline at the bottom of articles for a few weeks, then add the sidebar only on longer articles and see whether the overall click rate changes without hurting user behavior.

What to Improve After Reviewing the Statistics

• Remove networks that receive no clicks and only take up space.
• Move popular networks higher in the output order.
• Disable counters where they show low values or slow down the page.
• Review mobile mode separately if mobile clicks are lower than expected.
• Create a separate shortcode for campaigns where the standard panel is too generic.
• Configure the fly-in only after you understand the baseline performance of inline and sidebar.

If you also use external analytics, you can compare AMPZ data with events in your analytics system, but there is no need to do that at the first stage. Start with the basics: are clicks visible, which networks perform, and which positions are unnecessary. That alone already makes the page cleaner and faster.

Common AMPZ Extended Issues and Troubleshooting

Most social button issues do not come from one single “broken” setting. They usually result from the interaction between the Joomla component, the template, cache, the editor, mobile mode, and third-party scripts. Below is a practical symptom-based troubleshooting guide. Start with the narrowest possible test: one article, one position, two networks, and a cleared cache.

The Buttons Do Not Appear on the Page

Symptom: the settings are saved, but no buttons appear on the front end. Possible causes include the position not being enabled, the component not being selected in Display in Components, the page falling into an excluded category, output being enabled in the wrong position, the cache serving an older page version, or the plugin not being published.

Check the component and category first. If the all-pages option is enabled, disable it temporarily and configure targeted output instead. Then clear the Joomla cache through the admin panel, reload the page in a private window, and inspect the page source for AMPZ markup. If the markup is missing, the issue is in the output rules. If the markup is present but the block is invisible, inspect the template CSS.

The Buttons Appear in the Wrong Places

Symptom: the buttons are visible on the homepage, in a category view, on contacts pages, or on utility pages. In most cases, global all-pages output is enabled, the category view exclusion is missing, or the position has a component override. Go back to your page map and configure the rules from general to specific: components first, then categories and articles, then position-level overrides.

If the problem shows up only inside a third-party component, check how that component builds its pages. Some components use their own views, and the buttons may end up on a list page instead of a detail page. In that case, use exclusions, a separate shortcode, or module placement instead of relying on universal output.

The Shortcode Is Displayed as Plain Text

Symptom: the site shows {ampz:module_right} or a similar tag, but the buttons do not render. Possible causes include a typo in the shortcode name, the editor changing the syntax, the module not preparing content, the processing plugin being disabled, or the tag being inserted into a place where content plugins do not run.

Start the fix by using the AMPZ Shortcode button in the editor if it is available. Then verify the shortcode name in the AMPZ list. If the tag is in a custom module, make sure the module is published, assigned to the correct page, and allowed to prepare content. For testing, insert the same shortcode into a normal test article. If it works in the article but not in the module, the problem is with the module or its position.

Mobile Buttons Are Missing or Cover the Content

Symptom: WhatsApp, Telegram, or Phone do not appear on desktop, while on a phone the panel makes the page hard to read. The first behavior may be normal, because those buttons depend on mobile mode and the width threshold. The second requires adjustment. Check the mobile mode activation threshold, the number of visible buttons, the grouping of extra buttons, and nearby template elements such as the cookie banner, chat widget, or floating feedback button.

If the panel covers the content, reduce the number of visible buttons, disable labels, move the panel, or disable the problematic position on mobile. After every change, test on a real phone rather than relying only on a desktop browser with a narrowed window.

The Page Became Slower After Enabling Counters

Symptom: the buttons work, but the page takes longer to load or developer tools show additional external requests. A likely cause is that share counts are enabled for networks that require external requests to fetch data, or the counter refresh interval is configured too aggressively. Disable the counters first and compare performance. Then enable them for only one position and test again.

Do not try to solve this only with site-wide caching. If unnecessary counters are the real issue, it is better to reduce functionality than to hide the delay behind cache. On a new site with low numbers, counters often add little value and can be disabled without losing anything important.

The Settings or Appearance Changed After an Update

Symptom: after updating AMPZ or Joomla, some settings reset, the buttons changed appearance, or the share windows stopped opening correctly. The documentation on automatic updates warns that direct modifications inside the extension copy can be overwritten by an update. That is why you should not customize the extension by editing its files directly. Use AMPZ settings, template CSS, or a child/custom template mechanism if one is available.

Before updating, export the AMPZ configuration if that option is available, and create a backup. After the update, test one page, mobile mode, shortcodes, and statistics. If the issue is related to the update server or download ID, follow the official automatic update documentation and do not expose secret identifiers in third-party tools.

Safe Improvements Without Editing Extension Files

There is no need to edit the Joomla core, AMPZ files, or the template directly just to refine social buttons. Safe improvements should be reversible: a setting in the AMPZ panel, CSS in the template’s custom stylesheet, a module assignment, or a shortcode. If something breaks after an update, you should be able to disable one setting instead of restoring files from an archive.

CSS for Spacing Around the Inline Block

If the inline buttons sit too close to the text, add a small amount of spacing in the template’s custom CSS. The AMPZ container class should be confirmed through your browser inspector because the exact markup may vary depending on the selected design. The example below shows the general idea, not a universal selector for every site:

/* Add this to the template's custom CSS, replacing the selector with the actual AMPZ container */
.ampz-inline,
.ampz-inline-wrapper {
  margin-top: 1.25rem;
  margin-bottom: 1.25rem;
}

Check the result on a test article, in the category view, and on a mobile screen. If the spacing appears on the wrong block, remove the rule and refine the selector with the inspector. Do not add !important unless you truly need it: it makes future maintenance harder and may interfere with AMPZ’s own design settings.

A Gentle Strategy for Uncertain Pages

If you are not sure whether buttons belong in category pages, store pages, or a third-party component, do not enable them globally. Create a separate shortcode, place it in a custom module, and assign the module to just one test page. That approach is safer than changing the component rules right away. If the statistics and user behavior show that it helps, you can expand the output later.

Exporting and Moving Settings

Official sources mention AMPZ configuration export and import. That is useful for moving settings between staging and production, and also for preserving the current state before larger changes. But import should not replace verification after migration: different sites may have different components, menu items, categories, template positions, and cache layers. After importing, always open the positions, components, shortcodes, and mobile mode settings and review them manually.

Post-Launch Maintenance: Updates, Monitoring, and Careful Expansion

After the initial successful setup, the work with AMPZ Extended does not end. Social networks change their rules, Joomla gets updated, the template may gain new floating elements, and the site’s audience gradually reveals which buttons are actually useful. That is why the extension should be treated as a small ongoing maintenance area, not as something you “install once and forget.”

Updates Without Losing Settings

AMPZ documentation describes automatic updates through Joomla’s update mechanism and a separate download identifier in the developer account. This article does not cover purchasing, entering payment details, or bypassing access restrictions for updates. For an administrator, the more important practical takeaway is this: before updating, save the configuration, make sure nobody has made direct edits inside the extension files, and run the update on a staging copy of the site first.

If someone previously changed CSS or templates directly inside the AMPZ files, the update may overwrite those changes. That is not a bug - it is normal extension package behavior. The fix is to move that customization into the template’s custom CSS, AMPZ settings, or another supported Joomla layer. The fewer direct changes you keep inside the installed extension, the less stressful updates become.

After updating, do not check only the settings page. Open several page types: a regular article, a category page, a third-party component page, a mobile screen, and a page with a shortcode. Verify that inline, sidebar, fly-in, and mobile mode behave the same way they did before the update. If the extension uses statistics, make sure the dashboard opens and the data does not look unexpectedly empty after an otherwise routine update.

Monitoring After Changing the Network Set

Adding a new network may seem harmless, but it changes button order, panel width, the combined popup, the mobile layout, and sometimes external requests. That is why new networks should be added in small groups and tested carefully. For example, first add Bluesky or Threads to the desktop set, then test WhatsApp and Telegram separately in mobile mode. Do not combine a new network, enabled counters, a design change, and a new fly-in in one single change.

If the number of buttons grows, revisit Combine after. A setting that worked well for four networks may look poor with eight. On desktop, you can leave more icons visible if the container is wide enough. On mobile, it is usually better to shorten the row and hide less common networks behind the “more” button. What matters is not the total number of available services, but how quickly the user can find the one they need.

Regular Result Checks

From time to time, open the AMPZ statistics and compare them with the actual site structure. If new sections have appeared, the buttons may not yet be assigned to the correct component or category. If an old section has been retired, buttons may still be rendering in places where they are no longer needed. If the site has moved to a new template, check whether the sidebar conflicts with new side navigation, a chat button, or a sticky header.

It is also helpful to keep a small change log: when you enabled a new position, which networks you added, when you disabled counters, and when you changed mobile mode. This can be as simple as a note in your task system or a comment in the site documentation. When someone asks a month later why buttons appear only in articles and not in the category view, you will have a clear reason instead of a guess.

How Not to Turn Social Buttons Into Visual Noise

Social buttons compete for attention with navigation, subscription forms, banners, recommendations, ads, breadcrumbs, and buy buttons. If you enable several positions at once, the page can start to feel loud even when nothing is technically broken. Every so often, look at the page the way a new visitor would: what is the first visible call to action, what distracts from reading, and whether there are simply too many floating elements.

If AMPZ is used on a commercial or lead-generation site, share buttons should not overpower the page’s main action. On a service page, quote form, or registration page, a modest inline block at the bottom is usually better than a fly-in layered over the primary conversion path. On an editorial site, the opposite may be true: visible sharing after a strong piece of content can make perfect sense because content distribution is one of the goals.

Checks When Switching the Template or Component

Changing the Joomla template can alter containers, module positions, sticky elements, content width, and CSS load order. After that kind of change, AMPZ should be checked as a separate item in the release checklist. The inline block may pick up different spacing, the sidebar may end up too close to the edge, the fly-in may conflict with a bottom menu, and a custom module with a shortcode may disappear because the position map changed.

Switching the content component also requires validation. If the site moves from regular Joomla Articles to a blog component, a catalog, or a page builder, the old output rules may no longer match the new views. Do not migrate the settings blindly. First create a test page in the new component, enable AMPZ only there, and verify the basics: does the block appear, is the correct URL passed into the share link, are there duplicates, and does the button show up on a detail page rather than in a list view.

Maintenance rule: every major site change - a Joomla update, a new template, a new component, a different cache layer, or a changed network set - should include a short AMPZ Extended check on both desktop and mobile.

When AMPZ Extended Is a Good Choice

AMPZ Extended is worth using when social buttons are part of your content strategy rather than visual decoration. The extension is useful if you want to control positions, show buttons only in the right Joomla components, adapt the mobile screen, create shortcodes for targeted blocks, and review click statistics. In that kind of setup, the product helps you do more than just “add icons” - it helps you build a clear working sharing flow for the visitor.

Before rolling it out broadly, go through a short cycle: one test page, one position, a limited set of networks, desktop and mobile verification, cache clearing, one test click, and a look at the statistics after the first visits. If that cycle goes smoothly, you can add the sidebar, fly-in, follow buttons, or separate shortcodes. If conflicts show up in the first cycle, do not expand the configuration until you understand the cause.

If, after reading this guide, you understand which pages should use the buttons, which networks matter to your audience, and how to verify the result, move on to installing it on a staging copy or go to the download section. For the next step, you can get the AMPZ Extended file, then follow the setup steps from this guide and enable the extension on the live site only after testing.

The core idea is simple: AMPZ Extended delivers value not through the number of buttons, but through accurate placement. The better you match the button to the page context, the less visual noise you create and the more likely visitors are to actually use the sharing option.