Skip to content

Technical Plugin Customize

Daniel Neto edited this page Oct 29, 2026 · 1 revision

Technical: Customize plugin

Customizes About content, the footer and descriptive site metadata.

Audience: developers, advanced administrators and AI-assisted diagnosis. Plugin catalog.

Source baseline

  • Review date: 2026-10-29. Method: static source analysis; runtime/provider behavior was not exercised.
  • Code ownership: independently versioned plugin repository.
  • Reported version: 2.0.
  • Source revision: 4c71b23e758e402ef8e44d5fdad3624c4fb52afa.
  • Entry class file: Customize.php.

Confirm the installed plugin version independently of the Streamer version. Configuration defaults below are not a dump of this installation's saved settings.

Dependencies

No literal dependency declaration was extracted. This does not prove the plugin is standalone.

Hook integration

Override Implementation
getTags() Customize.php:10
getPluginMenu() Customize.php:44
getStart() Customize.php:50

Configuration assignments

These are direct assignments inside getEmptyDataObject(), not evaluated effective defaults. Stored plugins.object_data, globals, structured values and conditional branches may alter runtime behavior. Private/default credential values are omitted.

Field Literal default or expression type Literal source label/help Evidence
colorsVariables Computed/structured; inspect source — source
showCustomCSS true — source

Files and request surface

This inventory distinguishes implementation files from an API specification. Includes, templates, callbacks and CLI workers are not interchangeable HTTP endpoints. Request-field names below are direct source references, not a complete schema or permission declaration.

File Source role Direct request fields observed
Customize.php plugin entry class —
Objects/ExtraConfig.php class/helper implementation —
install/install.sql schema/migration SQL —
page/colors.php PHP page/include/worker; inspect caller —
page/colorsReset.json.php JSON entry point; inspect caller and guard —
page/colorsSave.json.php JSON entry point; inspect caller and guard —
page/editor.php PHP page/include/worker; inspect caller —
page/editorSave.php PHP page/include/worker; inspect caller about, description, footer
page/imageDelete.json.php JSON entry point; inspect caller and guard name
page/imageSave.json.php JSON entry point; inspect caller and guard name
page/images.php PHP page/include/worker; inspect caller —
page/text.php PHP page/include/worker; inspect caller —
sass/assets/javascripts/bootstrap-sprockets.js browser/worker JavaScript; verify loader —
sass/assets/javascripts/bootstrap.js browser/worker JavaScript; verify loader —
sass/compile.php PHP page/include/worker; inspect caller —
sass/spectrum-dist/dist/spectrum.js browser/worker JavaScript; verify loader —

Data and migrations

Tables named in available CREATE TABLE statements: extraConfig. Apply installation/update behavior through the owning plugin; this reference is not a script for running historical migrations manually.

Main-file named symbols

Visibility and implementation semantics must be checked in source. Nonempty string defaults are represented as . This is a symbol reference, not a stable public API promise.

Function or method Source
getTags() 10
getPluginVersion() 15
getDescription() 19
getName() 23
getUUID() 27
getEmptyDataObject() 31
getPluginMenu() 44
getStart() 50
loadDefaultCustomImages() 63
getCustomImageDir() 73
cleanFileName($name) 79
getRelativeImagePath($name) 83
getAbsoluteImagePath($name) 88
saveCustomImage($name, $postIndex) 94
deleteCustomImage($name) 100

Supporting PHP declarations

These symbols are grouped by source file; inspect the class declaration and visibility before calling them.

Objects/ExtraConfig.php

Declared classes: ExtraConfig.

Named symbol Source
__construct() 11
getSearchFieldsNames() 16
getTableName() 20
getAbout() 24
getDescription() 28
getFooter() 32
setAbout($about) 36
setDescription($description) 40
setFooter($footer) 45

Diagnostics and validation

  1. Check the installed/enabled version and the dependencies/settings above.
  2. Identify the actual failing page, request, callback or worker and correlate its timestamp with the AVideo log.
  3. Follow the linked method and caller. Check business-state changes and output artifacts as well as HTTP status.
  4. Reproduce the relevant workflow in a test environment. External provider, Encoder, live-server, storage, payment and authenticated flows require their real integrations.

Shared diagnostic workflow. This page is not a security audit or a claim of end-to-end validation.

Clone this wiki locally