Technical Plugin AD_Overlay

Technical: AD_Overlay plugin

Displays timed advertising overlays during video playback.

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: AVideo Streamer repository.
• Reported version: 2.1.
• Source revision: 7d48f2dfc0289236718a3f9fba7c5ffecff4a37f.
• Entry class file: AD_Overlay.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

Plugin	Required by declaration	Source reason
ADs	Required	Reuses the ADs image upload/library to attach overlay images

Literal runtime plugin references: ADs. These calls do not mean every referenced plugin is mandatory.

Hook integration

Override	Implementation
getTags()	AD_Overlay.php:15
getHeadCode()	AD_Overlay.php:107
getFooterCode()	AD_Overlay.php:145
profileTabName($users_id)	AD_Overlay.php:229
profileTabContent($users_id)	AD_Overlay.php:238
getUsersManagerListButton()	AD_Overlay.php:247

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
adText	Computed/structured; inspect source	—	source
mobileAdText	Computed/structured; inspect source	—	source
align	"bottom-left"	—	source
showBackground	true	—	source
attachToControlBar	false	—	source
debug	false	—	source
allowUserAds	true	—	source
AdminMustApproveUserAds	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
AD_Overlay.php	plugin entry class	c, link, u, videoName
Objects/AD_Overlay_Code.php	class/helper implementation	—
footer.php	PHP page/include/worker; inspect caller	—
getCode.json.php	JSON entry point; inspect caller and guard	users_id
install/install.sql	schema/migration SQL	—
profileTabContent.php	PHP page/include/worker; inspect caller	—
profileTabName.php	PHP page/include/worker; inspect caller	—
saveCode.json.php	JSON entry point; inspect caller and guard	addOverlayCode, approveAd, deleteAd, users_id

Data and migrations

Tables named in available CREATE TABLE statements: ad_overlay_codes. 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
getPluginDependencies()	9
getTags()	15
getDescription()	25
getName()	33
getUUID()	38
getPluginVersion()	43
getEmptyDataObject()	48
getHeadCode()	107
showAdsOverlay()	139
getFooterCode()	145
profileTabName($users_id)	229
profileTabContent($users_id)	238
getUsersManagerListButton()	247
getAdsFromUserIfActive($users_id)	257

Supporting PHP declarations

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

Objects/AD_Overlay_Code.php

Declared classes: AD_Overlay_Code.

Named symbol	Source
loadFromUser($users_id)	11
getFromDbFromUser($users_id)	23
getSearchFieldsNames()	39
getTableName()	43
getUsers_id()	47
getCode()	51
setUsers_id($users_id)	55
setCode($code)	59
getStatus()	63
setStatus($status)	67
filterCode($data)	71
get_magic_quotes_gpc()	77

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.