Skip to content

Technical Plugin LoginWordPress

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

Technical: LoginWordPress plugin

Integrates account login with a configured WordPress site.

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: LoginWordPress.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() LoginWordPress.php:7
getLogin() LoginWordPress.php:70

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
customWordPressSite '' My Custom WP Site: This will use your personal WP API to login with your users, this option does not require the ID and Key, this option must be your site URL, I.E. https://mywordpresssite.com/ source
customWordPressSiteSavePassword Private setting; value omitted Save the password on AVideo the database: This will use your personal WP API to login with your users, this option does not require the ID and Key, this option must be your site URL, I.E. https://mywordpresssite.com/ source
customWordPressSiteIfLoginFailTryDatabase false Check the database if the wordpress login fail: This will use your personal WP API to login with your users, this option does not require the ID and Key, this option must be your site URL, I.E. https://mywordpresssite.com/ source
customWordPressSiteForgotMyPasswordURL Private setting; value omitted — source
customWordPressSiteSignUpURL '' — source
autoAddNewUsersOnUserGroup Computed/structured; inspect source Auto add new users on UserGroup: When a new user is created with the your WordPress site, this user will be auto added on the selected user group source
globalWordpressLogin true Use the global Wordpress login: This will use the global WordPress OAUTH2 to login, this option requires the ID and Key source
id "" — source
key Private setting; value omitted — source
buttonLabel "" — 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
LoginWordPress.php plugin entry class —
view/login.json.php JSON entry point; inspect caller and guard WPpass, WPuser
view/loginForm.php PHP page/include/worker; inspect caller cancelUri

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() 7
getDescription() 14
getName() 25
getUUID() 29
getPluginVersion() 33
getEmptyDataObject() 37
getLogin() 70
auth($user, $pass) 92
login($user, $pass) 136

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