All Video Share Pro - Joomla Extension

Guide to Setting Up and Using All Video Share Pro on a Joomla Site

All Video Share Pro is a Joomla extension for cases where a site needs more than the occasional video embedded in an article. It is built for a managed video library: categories, individual video pages, modules, menu-based output, player embedding inside articles, user video submissions, and player settings. This guide focuses on the practical workflow rather than marketing copy: what to check before installation, which admin sections to open after setup, how to add your first video, how to publish a gallery on the site, and how to confirm everything is working properly.

This article is written for webmasters, Joomla administrators, content editors, and site owners who have already decided to evaluate All Video Share Pro and want to avoid common mistakes. Special attention is given to the component + module + plugin + menu item combination, because that is what sets a Joomla video gallery apart from simply pasting iframe code into an article.

Below you will find a practical scenario for a training video page, a checklist for validating the public-facing result, a troubleshooting section, and a comparison with similar solutions. Any feature that can vary has been described carefully: capabilities such as dynamic YouTube Gallery, VAST/VPAID, user uploads, private videos, and comments depend on the edition of the extension, the Joomla version, and the specific site configuration.

What a Video Library Solves That a Standard Video Embed Does Not

Joomla lets you insert video in several ways: through hosting code, through the editor, through a module, or through a dedicated extension. All Video Share Pro becomes useful when videos turn into a distinct content type rather than an occasional illustration inside an article. Once that happens, the videos need structure: categories, pages, thumbnails, access control, sorting, search, modules, separate player settings, and in some cases user submissions.

The official page and the JED listing describe All Video Share as both a video player and a video gallery for Joomla. Based on the available sources, the extension supports local video files, YouTube, Vimeo, HLS and DASH streams, third-party embed code, categories, modules, menu items, and a content plugin. In practical terms, that means the site gets a single video management system instead of relying on manually copied HTML fragments scattered across pages.

The difference becomes especially clear on sites where video is updated regularly. A training center may publish webinar recordings, a sports club may post match recaps, a church or conference may maintain an archive of talks, and a marketing team may build a library of demo videos. In those cases, the editor needs more than a way to "attach a video." They need a fast way to choose a category, assign a preview image, apply the right player profile, publish a block in a module position, and verify that visitors land on the correct page.

When the Extension Is More Useful Than a Manual iframe

A manual iframe works well for a single video, but it does not scale well. It can easily get buried inside an article, depends on editor settings, may be stripped by Joomla filters, and makes repeated videos harder to find and maintain. All Video Share Pro solves a different problem: centralized video management and repeatable output through Joomla's built-in mechanisms.

• If you need to store dozens or hundreds of videos, categories help prevent the content from turning into one long unstructured list.
• If the same player needs to appear in an article, a module, and a standalone page, a player profile keeps you from styling it manually each time.
• If some videos should only be available to registered users, Joomla access fields and permissions become important.
• If the site uses ad inserts, cover images, SD/HD quality options, or HLS streams, a dedicated component is more convenient than a plain iframe.

That said, the extension does not replace common sense. If the site only has two articles with YouTube videos and no gallery is needed, a separate component may be unnecessary. But if the project revolves around video content, the component starts saving time after just a few publications.

Where All Video Share Pro May Be More Than You Need

There are also cases where keeping the site simple is the better choice. A landing page with one promotional video only needs a standard embed block or a lightweight plugin. A large paid video platform with subscriptions, lessons, progress tracking, quizzes, and protected video delivery may require an LMS or a dedicated access platform. All Video Share Pro is closer to a video gallery and player than to a full learning platform.

It is also worth deciding in advance who will maintain the videos. The component offers more flexibility, but it also requires discipline: filling out categories, avoiding duplicate videos, keeping thumbnails consistent, checking access permissions, and not enabling questionable options without testing them first. The larger the video library becomes, the more important it is to have clear publishing rules.

Who All Video Share Pro Is For and What Limitations to Consider Up Front

All Video Share Pro works best on Joomla sites where video content is part of the site's navigation, not just an add-on. That includes more than video portals. The extension fits event sites, training projects, review blogs, online magazines, nonprofit organizations, companies with demo videos, and any site where visitors need to browse, watch, and share videos.

Based on the JED listing and the documentation, the extension works as a set of Joomla building blocks: the component manages videos and categories, modules display the player, gallery, and search, the plugin inserts the player into content through a shortcode-like syntax, and menu items create public pages. Because of that, the product is not just for developers. A content manager can work with it too, as long as the structure is explained clearly in advance.

Good-Fit Scenarios

• A video catalog with categories and subcategories where visitors choose a topic and open an individual video.
• A "Videos" section in the main Joomla menu that leads to a gallery rather than a regular article.
• A block of recent or featured videos in a sidebar, on the homepage, or inside the template.
• Joomla articles, K2, VirtueMart, Kunena, or another component where a single player needs to be embedded through the content plugin.
• A private library for registered users, if access rights are configured through Joomla permissions.
• A dynamic gallery for a YouTube channel or playlist, if that feature is available in your edition and the API key is configured.

Scenarios Where You Should Think Twice

The extension should not be treated as a universal solution for every media task. The official migration documentation includes important notes: after moving from an older Joomla branch to a newer one, some features may behave differently, and certain integrations for comments and advertising have limitations. That is normal for a complex Joomla component, but it should be factored in before migrating a live site.

If your project depends on a specific feature, test it on a staging copy first. For example, if you need comments through a third-party extension, ad inserts for Vimeo, automatic approval of user-submitted videos, or a dynamic YouTube Gallery, do not stop at reading the product page. Build a small test setup: one video, one category, one menu item, one module, and one article embed. That will show you not only whether the option exists, but how it behaves in your template, editor, and caching setup.

The main decision point: use the component if video needs to become a managed library. If you only need to place a few videos inside articles, start with a simpler solution and move to All Video Share Pro when categories, modules, access control, or ongoing publishing become necessary.

What to Check Before Installing on a Live Site

Before installing any Joomla extension, it is important to understand not only whether your CMS version is supported, but also how the product will interact with the template, editor, cache, user permissions, and video sources. The documentation for the current branch of All Video Share lists the Joomla and PHP requirements and explains that installation is done through a single package that installs the component, modules, and plugins together. That is convenient, but it also means you need to verify several parts of the system after installation, not just one menu item.

Minimum Technical Prep

Start with a safe environment. It is best to install the extension on a site copy or a staging environment. If that is not possible, create a backup of both files and database, and perform the installation during a low-traffic window. A video extension can affect routing, menus, module positions, access permissions, article editing, and front-end script output.

• Check that your Joomla and PHP versions meet the requirements listed in the extension documentation.
• Make sure the admin user has permission to install extensions, create menu items, manage modules, and change the component's global settings.
• Prepare one short test video or a YouTube/Vimeo link, along with a separate thumbnail and poster image if you plan to test cover images.
• Note which editors are being used on the site: TinyMCE, JCE, or another editor. This matters for shortcode insertion and embed code handling.
• If the site uses aggressive caching, minification, or JavaScript optimization, prepare a test mode with optimization disabled.

Check the Site Structure Before Installing

Think through where the video library will live. All Video Share supports several output methods: a component menu item, a module, a plugin inside an article, separate layout modes, and a dynamic YouTube Gallery. If you start adding videos without a structure, you may later have to move categories, rebuild menus, and explain to editors why similar videos are scattered across different sections.

For a simple starting point, three decisions are enough. First, create one top-level category such as "Training Videos" or "Event Recordings." Second, choose one main player profile with safe settings: no autoplay with sound, a clear control bar, responsive width, and privacy consent enabled for external services if your site requires it. Third, decide what the primary public entry point will be: a "Videos" menu item or a module on an existing page.

What to Check for Video Sources

All Video Share supports multiple sources, but they do not all behave the same way. Local MP4/WebM/OGV files require proper storage and correct server delivery. YouTube and Vimeo depend on external services, video privacy status, thumbnail availability, and browser policies. HLS and DASH are useful for streaming delivery, but they require a correctly prepared stream. Third-party embed code may not use the extension's player profile, which the documentation explicitly notes for videos added through Third Party EmbedCode.

Do not mix every source type in your first test. Start with one clear source, verify the player and the gallery, and only then add a second type. That makes it much easier to tell whether the issue is in Joomla, the component, the video URL, the external service, the template, or the browser.

Installation and Initial Validation After Enabling the Extension

The official instructions for the current branch describe installation through Joomla Administrator: download the package, sign in to the admin panel, open System, go to extension installation, and upload the package through the Upload Package File tab. The documentation emphasizes that the package installs as a complete set: the component, modules, and plugins are installed together. After installation, do not close the tab immediately. First confirm that all parts are available.

Basic Installation Sequence

1. Open the Joomla admin panel using a user account with permission to install extensions.
2. Go to System and open the extension installation section.
3. Make sure the Upload Package File tab is selected, then upload the extension ZIP package.
4. Wait for the success message. If Joomla reports an upload error, check PHP limits, temporary folder permissions, and the package size.
5. Open Components and confirm that the All Video Share menu is present.
6. Open the Joomla module list and make sure the player, gallery, and search modules are available if they are included in your build.
7. Open the plugin list and find Player - All Video Share. This plugin must be enabled if you want to embed the player inside articles.

If the component appears but the plugin is disabled, the shortcode in an article will not be replaced with a player. If the module exists but is not assigned to a position or menu items, visitors will never see it. If no menu item is created, the component may work in the admin panel while the video library still has no clear public entry point.

Initial Check Without Complex Settings

Do not enable every feature right after installation. Create a minimal test loop first: one category, one video, one player profile, one menu item. That may feel slower, but in practice it is faster than chasing a conflict across a dozen settings.

• Open Components -> All Video Share -> Categories and create a test category.
• Add one video to that category through Videos -> New.
• Review the player profile and save baseline settings without autoplay with sound.
• Create a menu item using the category or video layout.
• Open the page as both a guest and a logged-in user if access depends on roles.

Quick summary: installation is only truly validated when the video is visible on a public page, the player launches, the thumbnail displays correctly, the menu item opens without errors, and the access permissions match the intended audience.

Categories, Videos, and Metadata: The Foundation of a Manageable Gallery

The All Video Share documentation is explicit that a category should be created before adding videos. That is not just a formality. A category defines the structure of the library, helps build public galleries, simplifies filtering, affects navigation, and can be used for access control. If category planning is skipped, the video library quickly starts to resemble a file folder with no system behind it.

How to Design Categories

Start with the visitor journey, not the labels. When someone lands on the video page, they should immediately understand what they can choose from: lessons, reviews, webinars, news, event recordings, tutorials, interviews. A category should reflect the visitor's task, not just the internal logic of the editorial team.

In the category form, the documentation lists fields such as title, alias, parent, image, access, status, meta keywords, and meta description. For SEO and navigation, title, alias, parent, and meta description matter most. The image field helps visually distinguish categories, and access can restrict who sees a section. One important detail from the documentation is that after a category is created, its name may not be renameable under certain conditions, so do not rush final naming decisions on a live site.

Practical Naming Principle

Choose names that will still make sense as the project grows. "Video 1" and "Misc" turn into clutter very quickly. Better choices are stable groups such as "Training," "Webinar Recordings," "Testimonials," "Product Demos," or "Broadcast Archive." If the site is multilingual, check from the start how category names will be translated and how they will appear in the URL.

Adding Videos Without Avoidable Mistakes

The video form in All Video Share has more fields than a standard article. According to the documentation, it includes title, alias, category, source type, video input, HD video, image, preview, user, views, access, featured, date added, status, description, and metadata. Not every field is needed every time, but it is important to understand which ones affect the final result.

If you use third-party embed code, the documentation warns that the player profile will not control that video in the same way it controls standard sources. For consistent design and management, it is usually better to use the extension's native source types whenever possible.

Player Profile: Safe Settings Worth Configuring First

The player profile defines how visitors interact with video. The player settings documentation lists size, autoplay, loop, initial volume, muted, privacy consent, controlbar, current time, duration, fullscreen, quality switcher, embed button, share button, and advertising parameters. This is one of the most important screens after installation because it affects user experience, support overhead, and the way the site feels overall.

Size and Responsiveness

Start with the player width and height. The documentation refers to the Player Width and Player Height (Ratio) fields. On a modern site, it is not enough to pick a nice-looking number. You also need to verify how the player renders in your template. If the player sits in a narrow module position, a fixed width can break the grid. If the video appears in the main content area, a very short height can make it feel like an accidental widget.

For a typical site, it is safer to choose a width that does not exceed the template container and then test the result on both desktop and mobile. If you use vertical videos, such as YouTube Shorts, pay close attention to the ratio setting. In the support forum, the developer provided an example ratio for short vertical videos. But that should not become a global setting without testing, because standard horizontal videos will render differently.

Autoplay, Sound, and Browser Restrictions

Autoplay often looks convenient, but autoplay support depends on browsers and platforms. In an All Video Share support thread, the administrator explained that autoplay is not guaranteed, especially on mobile devices and in modern browsers. A more reliable approach is to use autoplay only for carefully designed scenarios and enable muted playback if the video must start automatically without sound.

Do not make autoplay with sound your default setting. It hurts the user experience, may fail technically, and often creates the false impression that something is broken: the editor enabled the option, but the visitor still sees a static player. If autoplay is essential, test it separately in Chrome, Safari, Firefox, and on a mobile device.

Control Bar and Buttons

The controlbar, current time, duration, fullscreen, quality switcher, embed, and share fields determine how self-sufficient the visitor experience will be. For training videos, duration, fullscreen, and quality controls are usually helpful. For a marketing video on a landing page, a minimal control bar may be enough. For a public video library, it often makes sense to keep share enabled if you want the videos to spread across social platforms.

Enable the embed button deliberately. It is useful if you allow other sites to embed your player, but it is not always appropriate for a private library, an internal corporate section, or restricted-access materials. Do not just check whether the button appears. Also verify what code the user actually receives.

GDPR Privacy Consent for External Services

The player settings and global configuration mention GDPR Privacy Consent, which asks the viewer for consent before loading YouTube or Vimeo content. This is especially important when the site serves an audience that cares about privacy and external tracking. Even if you do not frame it as a legal setting, technically it changes when the external player is allowed to load.

After enabling consent, open the public page in a private browsing window. The video should not call the external service immediately before the user acts, and after consent it should start without forcing a full page reload, assuming that is how the current version behaves. If the player stays empty, check for conflicts with cache, JavaScript optimization, and the template.

Gallery, Menus, and Modules: How to Publish Video on the Front End

All Video Share Pro can be displayed in several ways. The documentation separately covers the component menu item, modules, and the content plugin. These are not duplicates. They serve different scenarios. A menu item creates a full video library page. A module outputs a player, gallery, or search box in a template position. The plugin inserts a specific player into a Joomla article or another component that supports content plugins.

A Menu Item for a Full Video Library

If the video section should be part of the site's main navigation, start with a menu item. The documentation describes the path Menus -> Main Menu -> New, followed by choosing an AllVideoShare menu type. The documented layout options include Add New Video, Categories Layout, Manage Videos, and Videos Layout. For a public catalog, it usually makes sense to start with categories or a video list.

When creating the menu item, use a clear title, verify the alias, and review the component options on the right. If you are showing all categories, make sure empty test categories are not visible to visitors. If you are showing one specific category, make sure editors add new videos to that exact place.

Player, Gallery, and Search Modules

The module documentation lists three roles: Player - All Video Share for the player, Gallery - All Video Share for the gallery, and Search - All Video Share for search. This is especially useful in Joomla because a module can be assigned to template positions and to specific menu items.

For the player module, the most important settings are player profile and video selection, as well as whether the title and description should be visible. For the gallery module, key settings include gallery type, category, number of rows and columns, ordering, featured videos, popup mode, and the "More" button. For the search module, the critical point is where users are sent after searching: if the wrong menu item is selected, visitors may land somewhere that does not contain the expected player.

How to Avoid Breaking Module Positions

Before publishing a module, inspect the actual template positions. Do not assign a video gallery to a very narrow column if the thumbnails are meant to be large. Do not place an autoplay player next to a text-heavy article if the visitor came there to read. Do not place video search on pages without video content: users will expect a local search within the section, not a confusing redirect.

Using the Plugin to Embed a Player in an Article

The plugin is useful when a video needs to appear inside an article. The documentation explains that you need to enable Player - All Video Share in System -> Manage -> Plugins, and then use syntax such as {avsplayer id=1} or {avsplayer src="https://www.youtube.com/watch?v=twYp6W6vt2U"}. Supported parameters include autoplay, loop, volume, muted, controlbar, currenttime, duration, fullscreen, quality, embed, share, and advertising options.

For editors, this is a good workflow: they do not have to paste a large block of HTML, only a short tag. But this approach requires two checks. First, the content plugin must be enabled and must execute in the place where the tag is inserted. Second, the editor must not break the syntax of the quotes or curly braces. If the site shows the raw text {avsplayer id=1} after saving, the plugin did not run or the content is not being processed through Joomla plugin handling.

Dynamic YouTube Gallery and API Cache: When You Actually Need It

One of the most product-specific capabilities in All Video Share Pro is the dynamic YouTube gallery. The documentation describes it for the Joomla 4 branch and the Pro edition: the user adds a YouTube Playlist, Channel, Username, Search Keyword, or a list of URLs, and the component builds the gallery. That is not the same as embedding a single video. The gallery can update from its source and depends on the YouTube Data API.

If you run a YouTube channel and want new videos to appear on the site without manually adding each one, this mode can be very useful. But it also adds a separate dependency: the API key, quota limits, cache, and a correctly defined source. For that reason, it is better to configure the dynamic gallery only after standard categories and videos have already been verified.

How the Playlist Scenario Works

The documentation describes inserting it through the Joomla editor: open an article, choose YouTube Gallery from the CMS Content dropdown, complete the form, and insert the generated shortcode. The form includes the Source, Gallery, and Player tabs. On the Source tab, you define the source, such as a playlist, along with cache settings. On the gallery and player tabs, you control the visual presentation and behavior.

For your first test, use a small public playlist. Do not begin with a channel that has hundreds of videos and multiple source types. That makes it much easier to confirm that the API key works, the gallery is being built, the cache does not interfere with updates, and the front end looks the way you expect.

Why Cache Time Matters More Than It Seems

The All Video Share documentation explains Cache Time separately for a reason. The YouTube Data API has a daily quota, and every request has a cost. Google's official documentation confirms that even invalid requests consume at least one quota unit, and projects with the YouTube Data API enabled receive a default daily limit. That means cache in a dynamic gallery is not a cosmetic setting. It protects you from unnecessary requests.

If a playlist updates once a day, there is no reason to request YouTube data on every page load. Set a sensible cache period and then verify that a new video appears after the cache expires. If the gallery does not show fresh videos, the official FAQ in the documentation suggests checking the cache and using Clear API Cache under System -> Global Configuration -> All Video Share -> Advanced.

Common YouTube Gallery Mistakes

• The API key was not entered in the YouTube API Key field or was created in the wrong Google Cloud project.
• The source was entered as a regular channel page, while the form expects a specific source type.
• The cache duration is too long, so the editor assumes the gallery "is not updating."
• The quota has been exhausted because of too many requests, multiple galleries, or repeated tests without cache.
• JavaScript optimization or the site's privacy policy is blocking external data from loading before the visitor gives consent.

For dynamic galleries, it helps to keep a simple log: which source is connected, which API key is in use, what Cache Time is set, and where the cache-clearing button is located. That reduces the number of "random" edits made by editors.

Practical Example: A Training Video Section With a Sidebar Gallery

The example below is not tied to a single demo site. It shows a typical working Joomla scenario: create a video catalog with a main page, add several training videos, display a sidebar gallery, and insert one key video into an article. This setup helps validate almost all of the core All Video Share Pro mechanics without the risk of immediately restructuring the entire site.

Goal

The goal is to create a "Video Training" section with a public category page, an individual video page, a sidebar module with recent videos, and one embedded player in an article called "How to Get Started." A visitor should be able to open the menu item, choose a category, play a video, move to another video through the module, and see an embedded player inside the article.

Preparation

• The extension is installed and visible in the Components menu.
• The Player - All Video Share plugin is enabled.
• There is one player profile with safe settings: no forced autoplay, plus fullscreen, duration, and controlbar enabled.
• Three videos are ready: an intro video, a hands-on lesson, and a webinar recording.
• The site template has a suitable module position for a sidebar or footer gallery.

Steps

1. Create a category called "Video Training" through Components -> All Video Share -> Categories -> New. Use a clear alias and public access.
2. Add three videos through Videos -> New. For each one, choose the category, source, thumbnail, publish status, and description.
3. Open the component settings through Options and review Gallery Settings: number of rows and columns, popup mode, and the menu id used when opening a video.
4. Create a menu item called Videos or Video Training and choose the category layout or video list layout, depending on your site structure.
5. Create a Gallery - All Video Share module. Set the type to Videos, choose the "Video Training" category, configure the number of rows and columns and display order, and assign the module only to pages in the training section.
6. Open the article "How to Get Started" and insert the player shortcode, for example {avsplayer id=1}, where the ID matches the desired video.
7. Clear the Joomla cache and the optimizer cache if it is enabled, then open the public site in a private browsing window.

How to Verify the Result

The validation should be specific. Open the menu item and confirm that the categories or videos appear in the correct grid. Click a thumbnail: the video should open on the expected page or in popup mode if that mode is enabled. Check that the title, description, view counter, and search are shown or hidden according to the single video page settings. Then open the article containing the shortcode and confirm that the player appears instead of raw text.

After that, check the module. It should display videos from the intended category, keep thumbnails from stretching, stay off pages where it is not needed, and link to the correct item id. If clicking the module opens the video on an unexpected page, go back to the menu id setting or the custom player page URL.

A Common Detail That Gets in the Way

If an editor inserted a shortcode into an article but the site still shows the text {avsplayer id=1}, the issue is usually not the video itself. Check whether the content plugin is enabled, whether that article is processed through plugin handling, and whether the code was inserted into a field where Joomla content plugins actually run. If you see an empty block instead of a player, investigate the video source, access permissions, browser console, and any JavaScript optimization conflict.

Checking the Result, Performance, and SEO After Setup

Once the video library is configured, you should verify more than just whether the video is visible. A video player loads scripts, iframes, or streams, thumbnails take up space, and external services may connect before the user gives consent. A strong video page has three layers: the user-facing result, technical stability, and search-engine clarity.

User-Facing Validation

• Open the page as both a guest and a logged-in user if the videos or categories are access-restricted.
• Test desktop, tablet width, and mobile. The player should not overflow the template container.
• Click play, pause, fullscreen, quality, share, and embed if those buttons are enabled.
• Check the gallery thumbnails: consistent proportions, no stretched images, and clear titles.
• If popup or lightbox mode is enabled, make sure closing works properly and keyboard focus is not lost.

Technical Validation

Open the browser console and network tab. For YouTube and Vimeo, confirm that external requests are only made when that matches your privacy settings. For HLS and DASH, make sure the stream is available over HTTPS and is not blocked by mixed-content policy. For local videos, verify that the server returns the correct MIME type and does not require authorization if the video is supposed to be public.

If the site uses caching, check the page twice: once after clearing the cache and once after reopening it normally. Some issues only appear after JavaScript is combined or deferred. If the player stops working after optimization is enabled, temporarily exclude the component scripts or the video library page from aggressive optimization. Do not permanently disable site-wide caching without a reason. It is better to narrow the exception.

SEO and Metadata

The category and video forms include metadata fields. Do not treat them as a dumping ground for keywords. A category page benefits more from a short explanation of what videos are collected there, who they are for, and how often they are updated. For an individual video, use a clear title, description, preview image, and readable URL. If the gallery is built from a YouTube playlist, make sure the page still has its own text context instead of consisting only of external video cards.

Video does not replace written explanation. Search engines and users understand a page better when the player is accompanied by a brief explanation, a clear section structure, headings, and related content. All Video Share helps you publish video, but the editorial value of the page is still your responsibility.

Safe Visual Improvements Without Editing Core Files

The official All Video Share global configuration includes a Custom CSS field, and the module documentation mentions support for Joomla module styling through the module class suffix. That gives you a safe way to fine-tune the gallery's appearance so it fits your template without editing the extension files. The rule is simple: do not modify the component, module, or template core just to solve a minor visual issue.

When a CSS Tweak Makes Sense

CSS is useful when the gallery works functionally, but the thumbnails have inconsistent sizing, the blocks feel cramped, the titles wrap awkwardly, or the module does not sit well in a sidebar position. CSS should not be used to mask a broken video source, a permission issue, or a JavaScript problem. If the video does not play, diagnose the player first instead of hiding the symptom with styling.

A safe approach is to assign the module its own class suffix, for example video-gallery-compact, and write CSS only for that area. If you are styling a component page, add a page class in the menu item or scope the CSS to the template's parent container. Below is a simple example for keeping thumbnails aligned in a compact gallery. The classes in the extension output may differ in your template, so use this as a principle and verify the actual result in the browser inspector.

.video-gallery-compact img {
  aspect-ratio: 16 / 9;
  object-fit: cover;
}

.video-gallery-compact a {
  text-decoration: none;
}

.video-gallery-compact h3,
.video-gallery-compact h4 {
  line-height: 1.25;
  margin-top: 0.5rem;
}

Where to place it: in the extension's Custom CSS field if you are styling the component, or in your template's custom CSS if you are styling a module. How to validate it: open the gallery page, reduce the browser width, and check the thumbnails, titles, and clickable areas. How to roll it back: remove the CSS block or remove the class suffix from the module.

Language Overrides Instead of File Edits

If you need to change interface labels, use Joomla's built-in language overrides instead of editing extension files. This becomes especially important after updates: a direct file edit can disappear, while an override stays manageable. Do not invent specific language constants in an article if you cannot see them in your own installation. Open System -> Language Overrides, search for the string by its visible text, and create an override for the appropriate language.

ACL and User Video Submission

If you allow visitors to add videos from the front end, do not rely on a single form setting. The All Video Share migration documentation notes that Joomla group permissions should be used to control who can create, edit, and delete videos. That is safer than giving every registered user full access.

Create a separate group, for example "Video Editors," assign only the permissions it actually needs, and test the workflow under a dedicated test account. Check auto approve separately as well: if videos should not appear without review, configure permissions so that an editor must confirm publication. After changing ACL, always test both the allowed path and the blocked path. A user without permissions should not see actions they are not supposed to have.

Why the Video or Gallery Is Not Working: Troubleshooting by Symptom

Video component issues often look the same: an empty block, a video that will not start, a gallery that does not update, a module showing the wrong videos, or a shortcode that does not render into a player. But the underlying causes differ. Below is a practical troubleshooting map for All Video Share Pro and the Joomla mechanisms it typically depends on.

The Page Shows the Shortcode Instead of the Player

Symptom: the visitor sees {avsplayer id=1} or similar text. A likely cause is that the Player - All Video Share plugin is disabled, the article is not being processed through content plugins, or the code was inserted into a field where Joomla does not trigger plugin events.

What to check: the plugin status, the insertion location, the curly brace syntax, the quotes around the URL, and the permissions of the user who edited the article. If the code was inserted through a visual editor, switch to HTML mode and make sure the editor did not add extra characters.

How to fix it: enable the plugin, insert the code into a standard content field, save the article, and clear the cache. If the component where you inserted the code does not support content plugins, use a module or a menu item instead of a shortcode.

The Player Is Empty or Will Not Play the Video

Symptom: the player area is present, but the video does not play. The cause may be an incorrect source type, an unavailable URL, mixed HTTP/HTTPS content, a private video, a blocked external service, or a JavaScript conflict.

What to check: open the video URL directly, confirm the source type in the video record, temporarily disable JavaScript optimization, and inspect the browser console for errors. For HLS and DASH, verify stream availability. For Vimeo, check privacy settings and any required token, especially if it is needed for automatic thumbnails or private content.

How to fix it: choose the correct source type, replace the URL with a publicly accessible one, use HTTPS, disable conflicting optimization for the video page, or adjust the privacy settings of the external service. If you are using third-party embed code, remember that the player profile may not control it.

The YouTube Gallery Does Not Show New Videos

Symptom: a new video appears on YouTube, but the gallery on the site remains unchanged. According to the official documentation, the most likely cause is API cache. API key issues, quota exhaustion, or an incorrect source definition are also possible.

What to check: the Cache Time value, the Clear API Cache button, the correctness of the API key, the source type, and any console messages. If a YouTube Data API quota message appears, check the request frequency and the number of galleries.

How to fix it: clear the API cache, set Cache Time based on the real update frequency of the playlist, and avoid an overly short cache window on a busy site. If the quota is being exhausted, reduce the number of dynamic sources or rethink the refresh strategy.

The Module Shows the Video but Opens the Wrong Page

Symptom: the thumbnail in the module is clickable, but the visitor lands on the wrong layout, an empty page, or a page with a different template context. This is usually related to the menu item id, a custom player page URL, or module assignment.

What to check: whether there is a stable main menu item for the video library, which item id is configured in the gallery or search settings, and whether the module is assigned only to the intended pages. If you are using a custom player page URL, make sure that page actually contains the player or component output.

How to fix it: create a stable menu item for video, assign it in the component or module settings, and clear route-related cache. Do not use temporary test pages as a public target.

Autoplay Works on Desktop but Not on a Phone

Symptom: the editor enabled autoplay, but the video does not start automatically on mobile. That is not necessarily an All Video Share problem. In the support forum, the developer noted that browsers and mobile operating systems restrict autoplay, while muted autoplay is supported more reliably.

What to check: whether Muted is enabled, how different browsers behave, and whether the site is waiting for a user interaction. Also check whether the user has data saver or autoplay-blocking settings enabled.

How to fix it: do not build a critical workflow around autoplay with sound. If autoplay is needed, enable muted playback and provide a clear sound control. For a standard video library, click-to-play is usually the better choice.

Comments Disappeared or Ad Behavior Changed After Joomla Migration

Symptom: after moving from an older Joomla branch, some integrations behave differently. The All Video Share migration documentation mentions limitations for JComments and Komento, as well as for pre-roll and post-roll advertising in Vimeo-related scenarios, and it also notes changes in the way auto approval for user-submitted videos is handled.

What to check: the developer's migration instructions, the current extension version, the video source types, the comment settings, and Joomla permissions. Do not assume behavior from the old branch will carry over unchanged.

How to fix it: first update the old installation using the recommended path, then test every critical feature on a site copy. For auto approval, use Joomla group permissions as described in the documentation rather than relying on the old familiar setting.

Limitations You Should Know Before Launching a Video Library

A good guide should explain not only what a product can do, but also where its boundaries are. All Video Share Pro is a capable extension, but it lives inside Joomla and depends on browsers, video hosting platforms, the template, cache, access permissions, and editorial workflows. If those dependencies are ignored, the product may get blamed for problems that actually live elsewhere.

Browser Rules Override Autoplay Settings

Even if autoplay is available in the player profile, the browser may block automatic playback with sound. This matters on homepages, promo sections, and background-video scenarios. Do not promise a client that a video will "definitely start automatically for everyone." Frame the requirement differently: the video should be noticeable, have a clear play button, and if autoplay is needed, it should be muted and tested on the relevant devices.

Third-Party Sources Are Not Always Controlled Like Native Ones

YouTube, Vimeo, third-party embed code, HLS, and local files all come with different limitations. For example, embed code may not obey the All Video Share player profile. Private Vimeo videos may require a token for certain operations. YouTube Gallery requires an API key and sensible cache settings. Local files require proper server delivery. The more source types you mix, the stricter your test matrix needs to be.

Access Permissions Need to Be Verified as Real Users

The Access field in a category or video and Joomla group permissions may look straightforward in the admin panel, but the actual result needs to be checked under different user accounts. A registered user should not see an edit button if editing is not allowed. A guest should not be able to open a private video by direct URL if access is restricted. An editor should not be able to publish a user-submitted video without review if moderation is required.

Cache and Optimization Can Change Behavior

Video players are often sensitive to JavaScript bundling, deferred loading, iframe lazy loading, cookie-consent behavior, and page caching. If everything works on a clean page but the player disappears after optimization is enabled, do not immediately conclude that the extension is broken. First check your exclusions, script load order, and the cache mode applied to the video library page.

When All Video Share Pro Is a Good Choice

All Video Share Pro is worth using when video on a Joomla site needs to become a managed section rather than an occasional embed. Its strengths are the component-based structure, categories, standalone videos, modules, content plugin, player settings, menu-based output, and support for dynamic YouTube galleries. That gives the webmaster a system and the editor a clear, repeatable publishing workflow.

Before rolling it out on a live site, walk through a short control path: install the package, create a category, add a video, configure the player profile, create a menu item, enable a module, insert a shortcode into an article, and then verify the public view, access permissions, mobile layout, cache behavior, and browser console. If that path works cleanly, you can expand the video library with more categories, dynamic sources, user submissions, comments, ads, or custom CSS.

If the workflow in this guide matches your use case, start with a test installation and only then move to the production site. Near the download section, you can get the All Video Share Pro package, create a backup, and test the extension with one category and one video. That approach is far more useful than trying to enable every feature of the component all at once.