1. Builder or Coded Analyzer?
There are two ways to add Analyzer support for an extension: build one with the Custom Analyzer Builder, or create a coded Analyzer plugin. Both provide Media Audit with the information it needs to understand how an extension uses your media.
For most extensions, start with the Builder. It requires no programming and is designed to handle the way typical Joomla extensions store their media references.
- Custom Analyzer Builder — tell Media Audit where an extension stores its media references, test the configuration against live data, and create a working Analyzer without writing code.
- Coded Analyzer — a Joomla plugin written in PHP for extensions that require more complex logic than the Builder can provide.
When does code become necessary?
Some extensions don't store their media in a way the Builder can fully describe. For example, an extension might construct file paths dynamically, combine information from related database tables, or require other custom logic before a media reference can be identified.
That's when a coded Analyzer becomes useful. A developer has complete control over how the extension's data is interpreted and reported to Media Audit.
You don't have to make that decision before you begin. Start with the Builder. If you eventually reach something it can't handle, you can export your working Custom Analyzer as a Joomla plugin and use it as the starting point for custom development.
{jd_file file==10}