Description
MEGA is an AI-powered growth platform that automates SEO and content management for your WordPress website. This plugin enables MEGA’s AI agent “Lindsay” to manage your content, optimize for search engines, and continuously improve your site’s performance – all without manual intervention.
Get started at gomega.ai
What MEGA Does
MEGA provides a fully managed SEO service that automates end-to-end SEO processes, delivering enterprise-level optimization at a fraction of the cost. Our AI agents work 24/7 to research, strategize, and execute SEO tasks that typically require a full marketing team.
Key Benefits
- AI-Powered Content Creation: Automatically generates and publishes SEO-optimized content
- Continuous Optimization: Real-time content updates based on Google Search Console data
- Technical SEO Automation: Automated audits, fixes, and performance improvements
- Keyword Research & Strategy: AI-driven keyword discovery and implementation
- Link Building: Automated backlink acquisition and management
- Conversion Rate Optimization: Improves user engagement and conversions
- Local SEO: Optimizes for local search visibility
- LLM Placement: Optimizes content for AI search engines and featured snippets
How It Works
- Install and activate the MEGA plugin
- Connect your WordPress site to MEGA’s platform
- Our AI agent Lindsay begins analyzing your site
- Content is automatically created, optimized, and published
- Continuous monitoring and optimization improve results over time
Features
- Secure Authentication: Military-grade encryption ensures only authorized MEGA agents can access your site
- Full Content Management: Create, update, and optimize posts automatically
- SEO Plugin Integration: Works seamlessly with Yoast SEO, Rank Math, and All in One SEO (AIOSEO)
- Autopilot Mode: 85% of users enable full automation for 2x faster results
- Multi-Platform Support: Integrates with 50+ platforms beyond WordPress
- Performance Tracking: Comprehensive analytics and reporting
- Human Oversight: Complex tasks reviewed by SEO experts when needed
Expected Results
Most users see organic traffic growth within 3 to 9 months. MEGA’s AI continuously learns and improves, providing ongoing optimization that adapts to search engine changes.
Learn more on our website.
External Services
This plugin connects to MEGA’s external service to provide AI-powered SEO optimization for your WordPress website.
MEGA SEO Platform
The plugin communicates with MEGA’s platform (gomega.ai) to enable automated SEO optimization and content management. This connection is essential for the core functionality of the plugin.
What data is sent: The plugin sends website content, metadata, and site configuration information to MEGA’s platform for analysis and optimization.
When data is sent: Data is transmitted when MEGA’s AI agents perform content creation, updates, or SEO optimization tasks on your behalf.
Purpose: This data exchange enables MEGA’s AI to analyze your site, generate SEO-optimized content, track performance, and continuously improve your website’s search engine rankings.
Service provider: MEGA (gomega.ai)
Terms of Service
Privacy Policy
WordPress.org core checksums
The file-integrity check calls api.wordpress.org (through WordPress core’s own get_core_checksums() function) to download the official checksums for your WordPress version and language. No site data is sent to WordPress.org beyond that request. The plugin compares the checksums with your core files locally, then reports the paths, sizes, modified times and md5 hashes of any differing or unexpected files (never file contents) to MEGA’s platform. Set MEGA_DISABLE_INTEGRITY in wp-config.php to disable this check.
Security activity reports
For administrator-level accounts, the plugin reports security-relevant activity to MEGA’s platform (api.gomega.ai) so a compromised account is noticed: logins, plugin installs, activations and deactivations, new administrator accounts and role changes, posts created through the REST API, changes to the default user role and to a few code-injection settings, and edits made in the plugin and theme file editors. Each event carries the account’s login name, a SHA-256 hash of its email address, the network part of the visitor’s address (the first three bytes of an IPv4 address or first six of an IPv6 address; never the full address), and a coarse browser type. File contents, option values and passwords are never sent. The last seven days of events are also kept in the site database and returned on MEGA’s daily file-integrity check.
The file-integrity check also reports which administrator accounts exist (ID, registration date, email domain and hash), hashes of the active theme’s PHP files, and hashes of a few code-injection settings and code-snippet entries, never their contents.
By using this plugin, you acknowledge that your website data will be processed by MEGA’s platform in accordance with their terms of service and privacy policy.
Configuration
After creating your MEGA account and installing this WordPress plugin, our agents will automatically be able to access your WordPress and optimize it.
No manual configuration required – just install the plugin and our AI agents handle the rest!
Installation
- Create your MEGA account at gomega.ai
- Upload the
mega-aifolder to the/wp-content/plugins/directory - Activate the plugin through the ‘Plugins’ menu in WordPress
- In your MEGA dashboard, add new feed from media accounts and select WordPress
- Our agents will automatically connect to your WordPress site and begin optimization
FAQ
What is MEGA?
MEGA is an AI-powered SEO platform that uses intelligent agents to automate your entire SEO strategy. Our AI agent “Lindsay” handles keyword research, content creation, technical SEO, link building, and continuous optimization – delivering results that typically require a full marketing team.
How much does MEGA cost?
MEGA’s SEO service starts at $999/month (or $799/month billed annually). This includes full SEO automation, unlimited content updates, and all features. Learn more at https://gomega.ai/pricing
Is this plugin secure?
Yes, the plugin uses military-grade RSA encryption with public/private key cryptography. Only MEGA’s authorized AI agents can access your site, and all communications are cryptographically signed and verified.
What can MEGA’s AI do with my WordPress site?
MEGA can:
– Create new SEO-optimized blog posts and pages
– Update existing content based on performance data
– Optimize meta titles and descriptions
– Fix technical SEO issues
– Manage internal linking
– Track and improve keyword rankings
– Monitor competitor strategies
– And much more, all automatically
Does it work with my SEO plugin?
Yes, MEGA seamlessly integrates with Yoast SEO, Rank Math, and All in One SEO (AIOSEO), enhancing rather than replacing their functionality.
How long until I see results?
Most users see organic traffic growth within 3 to 9 months. MEGA works continuously, and results compound over time as the AI learns your market and optimizes your content.
Can I review content before it’s published?
Yes! You can choose between full autopilot mode (85% of users) for fastest results, or review mode where you approve content before publication.
Will it affect my site’s performance?
No, the plugin is lightweight and only adds a small optimization script. All heavy processing happens on MEGA’s servers, not your WordPress site.
Can I use this with other CMS platforms?
Yes, MEGA supports 50+ platforms including Shopify, Webflow, Wix, HubSpot, and more. This plugin is specifically for WordPress integration.
Changelog
2.55.0
- Feature: a signed, read-only route shows one term of a public taxonomy (a WooCommerce product category, a post category or tag, a custom taxonomy): its name, slug, link, description and its text fields (the term’s ACF fields and public term meta), each with a hash a later edit must quote, and an optional search for a phrase. Values that look like credentials are never returned and SEO plugin data is not listed.
- Feature: a signed route changes ONE text field of such a term: its description, one ACF text, text-area or visual-editor field, or one existing term meta value holding a single string. It writes only while the stored value is still the one the caller read (judged under the term’s lock), only a value the field’s own sanitizer would store unchanged, and reads it back to say whether it landed. The description is set on its one column without running other plugins’ save filters, so no other part of the term changes. Names, slugs, parents, SEO data and new meta keys are never written.
- Feature: the guarded ACF field write also accepts a published entry of a public custom post type (for example a theme’s service or gallery type), not only pages and posts. Attachments, menu items, templates and other non-public types are still refused.
2.54.0
- Feature: the guarded custom-field write can change one text, textarea or wysiwyg subfield inside an ACF group, addressed as group.subfield; the custom-field read lists such subfields. Other subfields of the group, and every other field type, are untouched.
2.53.0
- Fix: a guarded page-unit write to an Elementor page stores the planned data byte for byte even when the site’s own save filters strip an html widget’s style or script tags (the one row is set by a hook-free update and still verified by an exact read-back).
2.52.0
- Elementor empty-id repair: when a site’s meta filters rewrite the stored Elementor data, the repaired bytes are set by a hook-free update of the one row and still verified by an exact read-back.
2.51.0
- Feature: a guarded page-unit update of an existing Elementor html widget may also swap one whole piece of its markup (for example one carousel slide, with its image and links) for one whole inert element, between two tags. The new element follows the same rules as an added one (plain text and basic tags, double-quoted attributes, no script, style, form, frame or event handler, links only relative or http, https, mailto or tel). The old piece may hold no script, style or comment, and nothing else in the widget may change.
2.50.0
- Fix: a guarded page-unit update of an Elementor section or widget no longer fails because it sends back, unchanged, parts the plugin would not accept on a new element (an html, template or third-party widget inside the section, a locked element, a dynamic-tag binding, custom CSS). Every part sent back exactly as stored is kept exactly as stored; only new or changed parts are checked, by the same rules as before. A changed html, template or third-party widget, and a new value for a setting bound to a dynamic tag (which Elementor would not show), are still refused.
2.49.0
- Elementor empty-id repair: a read-back mismatch now reports sizes, digests and the first differing offset (no content) so the cause can be found.
2.48.0
- Feature: a guarded page-unit update of an existing Elementor html widget may also add one whole inert element (for example one slide of a carousel) between two tags. The element may hold only plain text and basic tags (links, images, headings, lists) with double-quoted attributes, no script, style, form, frame or event handler, and links only relative or http, https, mailto or tel. Nothing else in the widget may change.
2.47.0
- Feature: a guarded page-unit update of an existing Elementor html widget may remove one whole piece of its markup (from < to >, occurring once), for example one slide of a carousel. Nothing can be added or changed, no other setting of the widget may change, and every other update of an html widget is still refused.
2.46.0
- Fix: hardening of the read-only operator session and the guarded menu edits, none of which any site uses yet. A session minted at the same moment as the cleanup of expired sessions is no longer lost, and the cleanup removes only expired sessions. A failed read of the operator user or of a page to land on is reported as unavailable instead of a missing user or an invalid landing. A write the operator session refuses now fails the same way on every WordPress version (old versions used to report success to code that tests for failure strictly, such as a draft being created when the editor opens a new post), and no longer fills the error log. Menu titles and descriptions with an unclosed or stray tag are refused before anything is written. Menu text an edit did not name is never stored in a filtered form, not even for an instant, and a plugin that saves another post while a menu item is being saved gets that post filtered as usual.
2.45.0
- Feature: a signed route changes the text of one ACF text, text-area or visual-editor field on a published page or post, only while the stored value is still the one the caller read, under the page’s edit lock, and only to a value the field’s own sanitizer would store unchanged. The value is read back after the write and the answer says whether it landed. Fields that look like credentials and every other field type are refused.
2.44.0
- Feature: a signed, read-only route lists where a page’s text is stored outside its page builder: the page’s ACF fields, its public custom fields, the active theme’s customizer values and ACF options-page fields, each with where it lives and the key a later edit would name, and an optional search for a phrase. Values that look like credentials are never returned. Nothing is changed.
2.43.0
- Fix: guarded menu edits no longer reorder a live menu whose stored item order is not exactly 1 to N (a first item stored at 0, gaps left by a removal, values written by the older menu sync): an edit that does not move an item leaves every item where it was, and an add, reorder or restore writes the whole order. A page, category or archive link whose title is empty or the same as its target now reads back as verified. Submitted menu text can no longer carry script (it is cleaned the same way for a preview and a write), backslashes are kept, values WordPress would silently change (such as a numeric character reference) are refused, an add to a menu that already has 500 items is refused before anything is written and a menu over the limit can be cut back, a menu that has an item WordPress does not list (a link to a trashed page, a draft item) is refused before any write, a custom link can no longer be edited to an empty title or address, text an edit did not name is left exactly as stored even on a site whose save filters would strip it (icon markup in a menu title, for example), and a restore is refused on a menu that is already over the limit.
2.42.0
- Feature: a read-only operator session. MEGA can open a short window (5 to 15 minutes) in which its automated operator signs in as a dedicated
mega-operatoruser to look at pages and the page editor. Nothing in it can change the site: the user’s role has no capabilities of its own, and while the window is open it is given only the ability to read and open pages and posts in the editor, every database write from its requests is refused, and it cannot manage users, plugins, themes or settings. The sign-in is a single-use, 60 second token that MEGA redeems with a secret only it holds; the session lasts five minutes at a time, is tied to the browser’s User-Agent, and ends when the window closes or expires. The operator cannot sign in with a password or an application password. Site administrators can switch it off at any time with a button on the MEGA settings page (orMEGA_OPERATOR_DISABLEDin wp-config.php), which ends any open session at once. Not supported on multisite. Nothing happens on a site until MEGA opens a window.
2.41.1
- Fix: a sandbox copy or page duplicate of an Elementor page keeps the page’s layout byte for byte even on a site that filters post meta as it is added (which could drop markup, such as a style block, from an HTML widget). When the stored copy differs from the source, the exact layout is written straight to the row.
2.41.0
- Feature: an Elementor page whose elements include an empty id (which Elementor and MEGA’s validator refuse) can be repaired by one explicit, guarded operation: each empty id gets a new unique 7-character id while the stored layout still hashes to the value the caller read, under the page lock and after a pre-write revision. Only the empty id values change, byte for byte; Elementor’s CSS for the page is rebuilt afterwards. Reading a page never changes an id.
2.40.0
- Feature: on a WooCommerce store, Mega can connect the store’s order feed: a signed route creates (or repairs) one webhook named “MEGA SEO purchases” that sends order updates to the store’s Mega webhook URL, owned by a store administrator, and sends WooCommerce’s test ping. It only ever points at Mega’s own WooCommerce webhook route, keeps the secret write-only, and a repeat call updates the same webhook instead of adding another.
2.39.0
- Fix: appending an item to an Elementor nested accordion also works when each item’s answer sits in a boxed container inside the item container (item container, one boxed container, one text editor). The new item copies that layout with fresh ids; any other layout is still refused and no existing item changes.
2.38.0
- Feature: page units can add the core and Pro Elementor widgets customers ask for: image carousel, slides, gallery, basic gallery, video, tabs, nested tabs, nested accordion, social icons, Google Maps, call to action, price table, price list, testimonial carousel, flip box, icon, alert, progress bar, reviews, media carousel and blockquote. Every submitted setting is cleaned by its shape, nested repeater items included: links must be http(s), site-relative, tel:, mailto: or #fragment (checked as sent and as a browser decodes them) with no quotes, angle brackets, backslashes or whitespace, media ids must be attachments of the kind the setting shows (image, video, or an SVG file for an SVG icon), icons class names or SVG attachments, tag settings Elementor’s own tag list, style values (every setting that is not a known text setting, by exact name) may not contain characters that leave a CSS declaration or leave a comment, string or bracket open, and text goes through the post sanitizer with script URLs and shortcodes refused. A nested widget holds exactly one container per item.
- Feature: an added or updated Elementor element may carry Elementor Pro custom CSS when every selector starts with
selectorand stays on the element: no other at-rules than @media, no sibling combinators or nesting, balanced brackets, no escapes outside strings, no script URLs, behaviours or expressions, and url() only on the site’s own origin or a raster data image. Anything else is refused. - Feature:
POST /mega/v1/editor/elementor-layout/{id}is a guarded write. It requiresexpected_content_revision, takes the page lock, refuses a page that changed since it was read (CONTENT_REVISION_MISMATCH), decides the convert gate again under the lock, and reports the pre-write revision and the content revisions before and after. - Feature:
POST /mega/v1/editor/revisions/{id}/restoreaccepts an optionalexpected_content_revision; with it the restore runs under the page lock, takes a pre-restore revision so the restore can itself be undone, and reports the content revision after. Without it the restore is unchanged. - Feature: sandbox copies of Elementor theme templates (headers, footers, single templates), without their display conditions, and a signed preview that renders a page with the copy in place of the live template for that one request.
- Feature: guarded menus. A menu snapshot with a revision, add, update, remove and reorder of items that refuse a menu changed since it was read, a guarded restore from a snapshot, and a signed preview that renders a page with a proposed menu for that one request. The existing menu sync keeps its shape and now waits its turn: it is refused (
MENU_WRITE_BUSY) while a guarded menu edit holds the menu’s lock. A plugin lock now records its holder’s time limit, so a later caller can never cut it short.
2.37.0
- Feature: the editor adapter lists an Elementor page’s copyable top-level sections (containers of headings, text editors and buttons) and appends one new last section, a copy of a named one with fresh ids and only its texts replaced. Existing sections are never changed.
2.36.0
- Feature: the editor adapter lists an Elementor Nested Accordion’s items (id, title, body) and appends one new last item, a copy of the last item’s layout with its own ids, title and text. Existing items are never changed.
2.35.0
- Feature: the editor adapter lists and edits Elementor Price Table copy (heading, sub-heading, period, button label, footer note, ribbon title and each feature row by its stable id). The price, currency and link are never listed.
2.34.0
- Fix: after an undo on a Bricks page, its generated CSS file again holds every element’s styles. Bricks’ own save, run by the revision restore, had marked them generated, so the rebuild wrote only the element defaults and the page lost its styling.
- Fix: a private test copy or draft duplicate of a Bricks or Beaver Builder page gets its own generated CSS, so it renders like the original.
- Fix: an edited Bricks element or Beaver Builder node keeps a setting sent back unchanged in any key order (such as a Beaver module’s empty
connections) instead of refusing it, and keeps the stored setting order. - Improvement: the
BUILDER_DRAFT_PENDINGrefusal reports why the Beaver draft differs (Beaver loaded or not, both layouts’ size and hash, and the first differing nodes and fields), without page content.
2.33.0
- Feature:
POST /mega/v1/cache/flushalso clears the Kinsta server cache and CDN, the Sucuri firewall cache (when the site saved its Sucuri API key), Cache Enabler, Nginx Helper, Hummingbird, WP-Optimize, the Pantheon edge and Endurance Page Cache. Each uses only that host’s or plugin’s own purge call, runs only when present, and cannot stop the others if it fails.
2.32.0
- Feature: post and page updates write
canonical(“” clears it) andnoindexinto whichever SEO plugin is active: Rank Math, Yoast, SEOPress and All in One SEO (its own table). Before this,noindexreached Rank Math only andcanonicalwas ignored. - Feature: SEOPress is detected as an SEO plugin; SEO title, meta description and focus keyword are written to and read from its own fields.
- Feature:
GET /mega/v1/posts/{id}andGET /mega/v1/pages/{id}reportseo_canonicalandseo_noindex(null while the post follows the SEO plugin’s default robots).
2.31.0
- Feature: the JSON-LD a schema write approves now renders exactly on the live page.
PUT /mega/v1/posts/{id}/schemaalso stores the approved nodes (_mega_schema_render), and at render time they are merged into the SEO plugin’s own graph: a native node with the same@idis replaced, else the first native node of the same@typetakes the approved values (references to its old@idfollow), else the node is added. Other native nodes are untouched and no node is added twice. Yoast and AIOSEO print the merged graph; on Rank Math, MEGA’s rows leave Rank Math’s graph and the approved nodes print in a separate script right after it, so Rank Math no longer rewrites their@id, turns numbers into strings or folds FAQPage into WebPage. When the SEO plugin prints no graph for the page, the approved nodes print on their own inwp_head. - Feature: schema
GETreturns the stored nodes exactly (Yoast’s selectors keep only@type), andPUTreturns the post’spermalinkandrender_store. - Fix: Yoast and AIOSEO schema extras are no longer read on term archives, where the queried id is a term id.
2.30.1
- Fix: a Beaver Builder page whose draft matches its published layout the way Beaver compares them (after Beaver’s own layout cleaning) is no longer refused as having unpublished changes. A real draft difference is still refused, and without Beaver loaded the check stays as strict as before.
- Fix: a private test copy of a Beaver Builder page now renders its layout in MEGA’s signed preview. Beaver showed an empty page body because the copy is private in the database. Only the copy being previewed in that request is affected.
- A failed pre-write revision (
REVISION_FAILED) now reports why: byte lengths and sha256 of the live and revision content, the database error class, the column charset and whether a db.php or object-cache drop-in is present. No content is included, and nothing else changes.
2.30.0
- Security: the daily file-integrity check also reports PHP files hidden in dot-folders under
wp-contentand in web-root folders that shadow a page slug, changes to the active theme’s PHP files, administrator accounts (read straight from the database), a default user role that grants administrator-level access, and changes to code-injection settings and WPCode snippets. - Security: administrator-level logins, plugin installs and activations, role changes, REST-created posts, default-role changes and file-editor use are reported to MEGA as signed events. The last seven days are kept in a bounded option and returned on the daily integrity check.
- Every new security feature loads only when it is used, so a fault in one disables that feature and never the site.
2.29.0
- Feature: page units on Bricks and Beaver Builder pages can be inserted, edited, moved and removed (
POST editor/blocks/{id}), with undo. Before, they were read-only. - The pre-write revision records every layout key of the builder that renders the page (Bricks: page content, header, footer, settings and editor mode; Beaver: data, draft, their settings, and the enabled flag), as its exact stored bytes or its absence.
editor/revisions/{id}/restoreputs each one back exactly and reads it back. - A write takes only allowed elements (no code, html, form, query loop, template or embed elements; no custom CSS, attributes, conditions, interactions or dynamic data), sends new text through the WordPress sanitizer, and keeps Bricks children lists and Beaver positions consistent. Beaver’s published layout and its matching draft are written together, and a page with unpublished Beaver edits is refused.
- After a write or an undo, only that page’s builder CSS is rebuilt (the Bricks CSS file in file mode; Beaver’s cached assets for that page). Nothing is flushed site-wide.
GET editor/blocks/{id}?layout=1returns a Bricks or Beaver page’s stored layout.
2.25.4
- Fix: a Divi 4 page saved inside one
wp:divi/placeholderblock (Divi 4 with the block editor on) is read as Divi 4 shortcodes, so its sections and modules are separate page units that can be edited, moved and added to. Before, the whole layout was one block. Only Divi 5 block names make a Divi page a block page.
2.25.3
- Feature:
DELETE /mega/v1/pages/{id}?scout_draft_only=1also deletes an unpublished draft made byPOST /pages/{id}/duplicate, under the same row lock and unpublished-only delete. The draft’s stamp (_mega_duplicated_from) is signed for its own post id (_mega_duplicate_sig, HMAC under the site’s auth salt), so a stamp copied to another post by a duplicator plugin or an export is refused, and both are removed the first time the page is published, so a rebuilt live page is never deletable this way.
2.25.2
- Fix: an Elementor element that stores an empty
__dynamic__(or another refused setting left empty) can be updated by sending back what was read. The empty setting is dropped; a non-empty one is still refused.
2.25.1
- Fix: page units inside a builder module can be edited and moved: Divi accordion items, tabs, slides, counters, pricing tables, social links and map pins, and WPBakery tab, tour and accordion panels. Each item type now sits only in its own module, so an item can no longer be placed loose in a column.
2.25.0
- Feature: signed
POST /mega/v1/pages/{id}/duplicatemakes a permanent draft copy of a page on the site’s own design: its page template, builder layout (Divi, Elementor), custom fields (ACF) and terms. SEO plugin settings (and MEGA’s schema extras for them), the featured image and MEGA bookkeeping are not copied, so the copy never inherits the design page’s title, description, canonical or JSON-LD. The copy is an ordinary draft: no expiry, no cleanup. - Feature:
GET /mega/v1/pages/{id}reportsdesign, the page template, the builder and the page’s custom fields (ACF field objects when ACF is active), so a page can be rebuilt on the same design.
2.24.0
- Feature: page units (
/mega/v1/editor/blocks/{post}) now read and write WPBakery and Flatsome pages, with the same lock, has-it-changed check, pre-write revision and read-back as Gutenberg, Elementor and Divi. WPBakery raw HTML/JS modules and Flatsomeux_htmlare refused in submitted units. - Feature: Bricks, Beaver Builder and Oxygen pages can be read as units (their own element ids, parents and text). Writing them is refused with
BUILDER_WRITE_UNSUPPORTED: their layout lives in postmeta that the pre-write revision does not yet snapshot, so an edit could not be undone.
2.23.0
- Feature: signed
GET /mega/v1/editor/blocks/{post}returns the page as a tree of addressable units (Gutenberg blocks, Elementor elements, Divi modules; a classic page is one unit) with stable ids, parents, text previews and the content revision a write must name.GET /mega/v1/editor/blocks/{post}/{unit}returns one unit’s exact markup or element. Reading never changes the page. - Feature: signed
POST /mega/v1/editor/blocks/{post}inserts, replaces, moves or removes one unit. It runs under the page lock, is refused unless the page (and the unit) still match what was read, takes a restorable revision first, writes only the unit’s bytes, sanitizes submitted text, refuses markup that would leave an element open, and reads the page back. Elementor CSS is rebuilt for that page only. - Feature: on WordPress 6.9+, the same operations are registered as abilities (
mega/list-page-units,mega/get-page-unit,mega/edit-page-unit) for logged-in editors.
2.22.0
- Feature: signed
GET|POST /mega/v1/editor/elementor-node/{post}/{node}reads one Elementor element and removes exactly that element (a nested container, or one exact fragment of an HTML widget). A removal is refused unless the page revision and the element’s bytes still match what the caller read; it runs under the page lock after a restorable pre-write revision, and the answer says whether a read-back of the stored layout equals the old layout minus that element. Nothing else on the page changes.
2.21.0
- Safety:
DELETE /mega/v1/pages/{id}?scout_draft_only=1deletes only an unpublished, MEGA-managed feasibility scout draft. The check and the delete run in one database transaction holding the page’s row lock, so a page published at the same moment is never deleted. Any other page, or a site whose posts table is not InnoDB, answers 409 and is left in place.
2.20.1
- Security: the file-integrity check now answers only signed
POST /mega/v1/integrity. A host page cache could store theGETresponse and serve it to visitors who were not signed in.
2.20.0
- Feature:
GET /mega/v1/integrity(signed, read-only) reports a file-integrity snapshot to MEGA: PHP files in the uploads folder,.htaccess/.user.inidirectives that remap PHP handlers or setauto_prepend_file, mu-plugins, drop-ins such asdb.phpandobject-cache.php, and WordPress core PHP files that differ from the official checksums. It reports paths, sizes, modified times and md5 hashes, never file contents. The scan runs on request under an 18 second time cap, resumes where a capped scan stopped (including inside a large uploads folder), ignores symbolic links, and takes a lock so only one scan runs at a time, and scans at most once every 10 minutes (requests in between get the last snapshot). - Safety: set
define('MEGA_DISABLE_INTEGRITY', true);inwp-config.phpto turn the scan off. A scan that hits a fatal error switches itself off for 7 days.
2.19.1
- Fix: edits no longer clear every Elementor CSS file on the site; only the edited page’s CSS is regenerated. Sandbox previews are never page-cached.
2.19.0
- Security: stronger request authentication. The plugin can now verify requests that carry a per-request signature over the method, address, query, body and a single-use nonce, so a captured request is of little use to anyone else. MEGA turns this on for a site; until then requests are authenticated with the older signature format as before. Once a site has accepted its first such request it stops accepting the older signature format.
- Security: MEGA’s public key is checked against fingerprints built into the plugin before it is used to verify a signature (the older format too, when the default key address is in use), and the verified key is cached for an hour.
- Change:
GET /mega/v1/pluginsreturnschange_log_secretonly to an older-format request on a site that has not switched. - Feature: if MEGA cannot connect after a server or proxy change, an administrator can reset request authentication from Settings > MEGA, or with
wp mega auth-reset. Nothing can reset it remotely. - Change: replay records for the new signatures are kept in the options table and removed hourly.
2.17.2
- Packaging: the WordPress.org release no longer includes development and test files.
2.17.1
- Security: error responses no longer include the site identifier.
2.17.0
- Feature:
GET /mega/v1/editor/widgets/{id}returnscontent_revision(and on each widget) for every builder: sha256 of the page content, plus the normalized Elementor data on Elementor pages. - Feature:
POST /mega/v1/editor/widgets/{id}/{widget}honoursexpected_content_revisionon every builder (it was Divi only). A guarded write takes a per-page lock, re-checks the revision after the pre-write revision is saved, and refuses with 409CONTENT_REVISION_MISMATCH(naming the observed revision) orCONTENT_WRITE_BUSYwithout writing. The answer carriescontent_revision_beforeandcontent_revision_after. Writes without the field behave as before; a present but empty or malformed field is refused with 400CONTENT_REVISION_REQUIRED, never read as unguarded. The lock is an atomic database statement (notadd_option), and a read that sees the page change while it lists the widgets answers 409CONTENT_CHANGED_DURING_READ. - Fix: reading widgets never fails where it worked before. An Elementor page whose content revision cannot be computed (data over 4 MB) still lists its widgets, with
content_revisionnull andcontent_revision_unavailable; a guarded write to it is refused with 413CONTENT_TOO_LARGE(a malformed tree is 409MALFORMED_TREE). - Fix: a page lock that cannot be taken because of a database error answers 503
LOCK_UNAVAILABLEinstead ofCONTENT_WRITE_BUSY; nothing is written. - Change: the Divi editor lock now uses the same atomic lock, is released as soon as the write returns, and a corrupt lock value expires instead of blocking the page.
2.16.1
- Fix:
POST /mega/v1/cache/flushnow also purges NitroPack, WP Fastest Cache, SiteGround Optimizer, the Cloudflare plugin and Autoptimize. Withpost_id, NitroPack, WP Fastest Cache, SG Optimizer and Cloudflare purge only that post’s URL; without it they purge the whole site, and Autoptimize runs only on that full flush. Before this, NitroPack kept serving the pre-edit page after a flush (it only invalidates a URL on save). Each plugin is called through its public API and skipped when it is not installed.
2.16.0
- Feature:
GET /mega/v1/pluginsalso returnsinactive_plugins(installed but not activated, same fields asactive_plugins) so MEGA can scan dormant plugins.active_pluginsis unchanged. - Feature: the same response includes
app_passwords, metadata only (name, created, last used, last IP, owning administrator) for every application password on the site, with the owning user’s roles. The password itself is never sent. Omitted when WordPress cannot report them.
2.15.0
- Feature: signed phone-only replacement.
POST /mega/v1/phone-replacetakes an old and a new phone number (both must be one valid NANP number; nothing else can be searched for) and finds that number in every common format across theme options (Uncode/OptionTree, theme mods), text/HTML/block widgets, Slider Revolution sliders and slides (params, layers, settings), Uncode content blocks, menu links and labels, and post and page bodies including WPBakery shortcodes and[vc_raw_html]blocks.mode: dry_runlists every match per object with before/after snippets and a sha256 per object;mode: applyneeds that{key: sha256}map, refuses the whole run (REVISION_MISMATCH, nothing written) if any object changed, and writes each object with a compare-and-set. Visible text keeps its own punctuation; tel:, callto: and sms: links (including URL-encoded WPBakery links) become E.164. Serialized and JSON values are decoded, walked and re-encoded, never text-replaced; serialized data that does not round-trip exactly or holds PHP objects is refused. Original bytes are stored per run and read back before the first write (JOURNAL_WRITE_FAILED and nothing written otherwise), and the journal is saved after every write; rollback reconciles each entry from its before/after hashes, so a landed write leftpendingby an interrupted request is still restored and content edited since is never overwritten. The post scan pages through every candidate and refuses (SCAN_TOO_LARGE) above 5,000 rather than returning a partial plan;GET /mega/v1/phone-replace/runs/<id>reads the audit record andPOST /mega/v1/phone-replace/runs/<id>/rollbackrestores it (also hash-guarded). Posts get a pre-write revision and every write enqueues a change-log event.
= 2.14.5 …
