Technical Plugin PedagoFlix

Technical: PedagoFlix plugin

Provides an installation-specific frontend integration.

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: installation-specific local extension; no canonical repository identified.
• Reported version: 1.0.
• Entry class file: PedagoFlix.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: PayPerView, TopMenu, Wix, YPTWallet. These calls do not mean every referenced plugin is mandatory.

Hook integration

Override	Implementation
updateScript()	PedagoFlix.php:32
getPluginMenu()	PedagoFlix.php:46
onNewVideo($videos_id)	PedagoFlix.php:52
getMyAccount($users_id)	PedagoFlix.php:66

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
LinkLoja	Computed/structured; inspect source	—	source
LinkLojaMenuItemId	8	—	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
MercadoPago/get.json.php	JSON entry point; inspect caller and guard	—
MercadoPago/ipn.json.php	JSON entry point; inspect caller and guard	—
MercadoPago/linkPagamento.php	PHP page/include/worker; inspect caller	—
MercadoPago/list.json.php	JSON entry point; inspect caller and guard	—
MercadoPago/tmp_webhook_logs/index.php	PHP page/include/worker; inspect caller	—
MercadoPago/webhook.json.php	JSON entry point; inspect caller and guard	type
PayPal/webhook.json.php	JSON entry point; inspect caller and guard	—
PedagoFlix.php	plugin entry class	—
cpfForm.php	PHP page/include/worker; inspect caller	—
saveCPF.json.php	JSON entry point; inspect caller and guard	cpf
setAllLinkLojas.json.php	JSON entry point; inspect caller and guard	—

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
getDescription()	10
getName()	17
getUUID()	22
getPluginVersion()	27
updateScript()	32
getEmptyDataObject()	38
getPluginMenu()	46
onNewVideo($videos_id)	52
getMyAccount($users_id)	66
setCPF($users_id, $cpf)	74
getCPF($users_id)	81
processWebhookInfoToPPV($sku, $email, $paid_amount, $store, $itemName = '')	88

Supporting PHP declarations

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

MercadoPago/get.json.php

Named symbol	Source
getMerchantOrderDetails($accessToken, $merchantOrderId)	4

MercadoPago/list.json.php

Named symbol	Source
getPayments($accessToken)	4
getMerchantOrder($accessToken, $merchantOrderId)	26

MercadoPago/webhook.json.php

Named symbol	Source
getMercadoPagoResource($url, $accessToken)	131

PayPal/webhook.json.php

Named symbol	Source
getPayPalAccessToken($clientId, $secret)	35
getOrderDetails($orderId, $accessToken)	61

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.