WP Manifestindependent plugin directory
manifest / updates / affi-brain-wp-plugin

Affi-Brain Connector self-updates

WordPress plugin for affi-brain integration (owner verification HTML deployment + auto-update via GitHub Releases)

by gesukiwafukase · github.com/gesukiwafukase510-bot/affi-brain-wp-plugin · website

★ 0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/gesukiwafukase510-bot/affi-brain-wp-plugin/archive/refs/heads/master.zip

Ships its own WordPress updater (Plugin Update Checker), so new versions show up under Dashboard → Updates.

Readme github.com/gesukiwafukase510-bot/affi-brain-wp-plugin ↗

WordPress plugin that connects to affi-brain for site verification HTML deployment and automated content management.

Features

  • Owner verification HTML deployment (Google Search Console, Twitter, Pinterest, Yandex, Bing)
  • Token-based authentication (X-Affi-Token header)
  • Auto-update via GitHub Releases (Plugin Update Checker)
  • File whitelist + path traversal prevention

Installation

  1. Download latest release zip from Releases
  2. WordPress admin → Plugins → Add New → Upload Plugin
  3. Activate
  4. Settings → Affi-Brain → Enter site token (generated in affi-brain UI)

Auto-update

This plugin uses Plugin Update Checker to check GitHub Releases for new versions. WordPress's standard update notification will appear when new releases are published.

REST API

Base URL: https://<your-site>/wp-json/affi-brain/v1/

Method Endpoint Description
GET /info Plugin / WP version, site info, post counts
GET /verify-html List configured verification files
POST /verify-html Deploy a verification HTML to site root

All endpoints require X-Affi-Token: <token> header.

Security

  • Token stored in WP DB (never in plugin code or repo)
  • File writes restricted to owner verification patterns (google*.html, twitter*.txt, etc.)
  • Path traversal prevention (no .., /, \, \0 in filenames)
  • Whitelist-based filename validation (regex patterns)
  • Content size limit (1000 bytes per file)

License

Private use only.