Technical Plugin MobileYPT

Technical: MobileYPT plugin

Presents YPT mobile-app integration/download information.

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: 1.0.
• Source revision: 7d48f2dfc0289236718a3f9fba7c5ffecff4a37f.
• Entry class file: MobileYPT.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.

Literal runtime plugin references: API, Chat2, CustomizeAdvanced, CustomizeUser, Notifications, ReportVideo, YPTSocket. These calls do not mean every referenced plugin is mandatory.

Hook integration

Override	Implementation
getTags()	MobileYPT.php:9
getStart()	MobileYPT.php:70
onNewVideo($videos_id)	MobileYPT.php:117
getHTMLMenuLeft()	MobileYPT.php:133
getHeadCode()	MobileYPT.php:139
getFooterCode()	MobileYPT.php:145

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
doNotAllowAnonimusAccess	false	—	source
doNotAllowUpload	false	—	source
hideCreateAccount	false	—	source
approvalMode	false	—	source
EULA	Computed/structured; inspect source	—	source
enableLivePublisher	true	—	source
enableAudioPlayer	true	—	source
privacyPolicyURL	''	Privacy policy URL: Link shown in the mobile app (Settings > About). Leave it empty to hide the link	source
termsOfUseURL	''	Terms of use URL: Optional link shown in the mobile app next to the EULA text. Leave it empty to hide the link	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
HTMLMenuLeft.php	PHP page/include/worker; inspect caller	—
MobileYPT.php	plugin entry class	—
getConfiguration.json.php	JSON entry point; inspect caller and guard	sort
head.php	PHP page/include/worker; inspect caller	Chat, iframe, noNavbar, noNavbarClose
index.php	PHP page/include/worker; inspect caller	key, live_index, live_servers_id, logoff
loginPage.php	PHP page/include/worker; inspect caller	SignUp, logoff
open-in-app-button.php	PHP page/include/worker; inspect caller	—

Data and migrations

No CREATE TABLE names were extracted from available plugin SQL. The plugin can still use core tables, PHP-created schema or another component's data. 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()	9
getVersion()	17
getDescription()	22
getName()	30
getUUID()	35
getPluginVersion()	40
getEmptyDataObject()	45
getStart()	70
getFirstPageEndpoint()	79
getBlockedUsersIds()	102
onNewVideo($videos_id)	117
getCheckMP3($videos_id)	122
getHTMLMenuLeft()	133
getHeadCode()	139
getFooterCode()	145

Supporting PHP declarations

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

head.php

Named symbol	Source
getColorValue($requestKey)	8

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.