2. Capability Comparison
For most extensions that store recognizable media paths in their database, the Custom Analyzer Builder is the fastest place to start. It can provide complete Media Discovery without writing code and can optionally add Asset Intelligence.
A coded Analyzer is appropriate when the extension requires logic the Builder cannot describe — such as combining related tables, constructing media paths dynamically, or performing custom processing before a media file can be identified.
| Capability | Custom Analyzer Builder | Coded Analyzer Plugin |
|---|---|---|
| Media Discovery | ✅ | ✅ |
| Asset Intelligence | ✅ Optional |
✅ |
| Multiple media fields in one database table | ✅ | ✅ |
| Media paths stored in JSON | ✅ | ✅ |
| Media embedded in HTML or complex field content | ✅ | ✅ |
| Multiple related database tables |
⛔️ |
✅ |
| Dynamically constructed media paths | ⛔️ | ✅ |
| Custom processing or business logic | ⛔️ | ✅ |
| Live record testing and configuration feedback | ✅ | Manual testing |
| Programming required | ⛔️ | PHP + Joomla plugin development |
| Export as a standalone Joomla plugin | ✅ | Already a plugin |
What "Export as Plugin" gives you
Every Custom Analyzer can be exported as a real, installable Joomla plugin. The exported plugin preserves the Analyzer you built — including its Media Discovery configuration and any Asset Intelligence you've added — and can be installed and enabled like any other Joomla plugin.
Exporting is also the bridge between the no-code Builder and custom development. If you eventually encounter something the Builder cannot describe, you don't have to start over. Export the working Analyzer and extend the plugin with PHP to handle the additional logic.