R3ap3r/aurora-wordpress-admin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Advance full admin takeover from v1.1 to v1.12

Browse Source 
Batches everything built since the 1.0 WP.org submission reset: Login
Redirect, the Tools/Export/Import screen takeovers, Modules rebuilt as
an addon marketplace, Menu Creator's reorder fix, Activity Log
redesigned into a filterable table with Admin/User tabs, dark-theme
fixes for Site Health/Personal Data/Updates, and an opt-in Disable
Gutenberg toggle. Continues the "nothing stays native" takeover goal
and closes gaps found via live testing and the WordPress Plugin Check
tool. See CHANGELOG.md for the full per-version breakdown (1.1-1.12).

Co-Authored-By: Claude Sonnet 5 <[email protected]>
This commit is contained in:
NixReaper
2026-07-26 13:37:35 -05:00
co-authored by Claude Sonnet 5
parent faf9f35992
commit 24be114f9a
39 changed files with 3462 additions and 1653 deletions
Download Patch File Download Diff File Expand all files Collapse all files
readme.txt
+47 -49
View File
@@ -4,7 +4,7 @@ Tags: admin, dashboard, admin theme, dark mode, admin redesign
Requires at least: 5.5
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 3.6.1
Stable tag: 1.12
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
@@ -32,20 +32,23 @@ Aurora Admin replaces the default WordPress admin with a faster, cleaner interfa
**Look and feel**
* A real dark mode covering the entire admin, not just a few screens
* 10 color presets plus 2 flat neutrals
* macOS-style window chrome for the block editor and other full-screen views
* 10 color presets plus 2 flat neutrals, applied across the whole interface
* Rounded, framed content cards with theme-tinted scrollbars; the block editor and other full-screen views get the same treatment
* Optional Google Font for the interface typeface (off by default — see Privacy below)
Everything in Aurora Admin is free — there's no license key, no locked features, and no upsell.
**Aurora File Manager, Aurora Database Explorer, and Aurora Site Backup (separate plugins)**
File Manager (browse/edit/manage your site's files from wp-admin), Database Explorer (browse your database tables and run read-only queries), and Site Backup (full site backup/restore, optionally to your own S3-compatible or Google Drive storage) previously shipped bundled inside Aurora Admin. All three are now distributed as their own standalone plugins — [Aurora File Manager](https://aurora.auroradragon.studio/file-manager), [Aurora Database Explorer](https://aurora.auroradragon.studio/database-explorer), and [Aurora Site Backup](https://aurora.auroradragon.studio/site-backup) — each installable with one click from Aurora's Settings → Add-ons screen. File-management/code-editing and direct database-query functionality of this kind isn't accepted into the WordPress.org Plugin Directory (see the [Plugin Developer FAQ](https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#are-there-plugins-you-dont-accept)); Site Backup was split out proactively for the same class of reason, since restoring a backup means writing arbitrary files back into the site. Aurora Admin itself never contains any of that functionality.
File Manager (browse/edit/manage your site's files from wp-admin), Database Explorer (browse your database tables and run read-only queries), and Site Backup (full site backup/restore, optionally to your own S3-compatible or Google Drive storage) are distributed as their own standalone plugins — [Aurora File Manager](https://aurora.auroradragon.studio/file-manager), [Aurora Database Explorer](https://aurora.auroradragon.studio/database-explorer), and [Aurora Site Backup](https://aurora.auroradragon.studio/site-backup) — each installable with one click from Aurora's Modules screen. File-management/code-editing and direct database-query functionality of this kind isn't accepted into the WordPress.org Plugin Directory (see the [Plugin Developer FAQ](https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#are-there-plugins-you-dont-accept)); Site Backup is separate for the same class of reason, since restoring a backup means writing arbitrary files back into the site. Aurora Admin itself never contains any of that functionality.
= Privacy / external service =
= Privacy / external services =
The optional "Report a Bug" screen sends your bug description and basic diagnostics (plugin version, WordPress version, PHP version, active theme name, and your site's domain) to a feedback endpoint on auroraplugins.com when you choose to submit it. Nothing is sent automatically or in the background — this only happens if you fill out and submit that form yourself.
Settings → Add-ons' "Install & Activate" buttons for Aurora File Manager, Aurora Database Explorer, and Aurora Site Backup download that plugin's zip file from aurora.auroradragon.studio using WordPress's own plugin-installer API, the same mechanism the native Plugins → Add New screen uses for WordPress.org-hosted plugins. This only happens when you click one of those buttons — nothing is downloaded automatically or in the background. (Aurora Site Backup's own remote-storage options, if you install and configure it, are documented in that plugin's own readme.)
The interface font setting (Settings → Appearance) is empty by default, in which case Aurora uses your system font and makes no external requests. If you choose a Google Font, that font file is loaded from Google Fonts (fonts.googleapis.com) on admin pages, which sends a request to Google's servers. Leave the setting empty to avoid any external font requests.
The Modules page's "Install & Activate" buttons for Aurora File Manager, Aurora Database Explorer, and Aurora Site Backup download that plugin's zip file from aurora.auroradragon.studio using WordPress's own plugin-installer API, the same mechanism the native Plugins → Add New screen uses for WordPress.org-hosted plugins. This only happens when you click one of those buttons — nothing is downloaded automatically or in the background. (Aurora Site Backup's own remote-storage options, if you install and configure it, are documented in that plugin's own readme.)
== Installation ==
@@ -65,16 +68,16 @@ Yes. Every feature listed above is available with no license key and no restrict
= Will this work with my other plugins? =
Aurora Admin only replaces the built-in WordPress admin screens it explicitly targets (Posts, Pages, Media, Users, Comments, Nav Menus, Widgets, Themes, core Settings screens, Profile, the block editor frame). Screens added by other plugins are untouched. Each replacement can also be toggled off individually in Aurora's settings if you'd rather keep the native screen for something specific.
Aurora Admin only replaces the built-in WordPress admin screens it explicitly targets (Posts, Pages, Media, Users, Comments, Nav Menus, Widgets, Themes, Tools, Export, Import, core Settings screens, Profile, the block editor frame). Running an already-active importer on the Import screen still opens that importer's own native screen, since its content is entirely owned by whichever plugin registered it. Screens added by other plugins are untouched. Each replacement can also be toggled off individually in Aurora's settings if you'd rather keep the native screen for something specific.
= Does Aurora load anything from external servers? =
Not by default. It only makes an external request if you opt in: choosing a Google Font loads it from Google Fonts, submitting the "Report a Bug" form sends it to auroraplugins.com, and the Modules page's install buttons download the companion plugins on click. See "Privacy / external services" above for details.
= Where do I report a bug? =
Use the "Report a Bug" item in the Aurora sidebar menu, or open a thread in this plugin's support forum.
= Where did File Manager, Database Explorer, and Site Backup go? =
File Manager is now Aurora File Manager, Database Explorer is now Aurora Database Explorer, and Site Backup is now Aurora Site Backup — three separate standalone plugins, each installable with one click from Settings → Add-ons in Aurora Admin, or downloadable directly from [aurora.auroradragon.studio/file-manager](https://aurora.auroradragon.studio/file-manager), [aurora.auroradragon.studio/database-explorer](https://aurora.auroradragon.studio/database-explorer), and [aurora.auroradragon.studio/site-backup](https://aurora.auroradragon.studio/site-backup). File Manager and Database Explorer are distributed separately because WordPress.org's Plugin Directory policy doesn't allow file-management/code-editing or direct database-query functionality in a directory-listed plugin; Site Backup was split out proactively for the same class of reason (restoring a backup writes arbitrary files back into the site).
== Screenshots ==
1. The Aurora dashboard.
@@ -83,53 +86,48 @@ File Manager is now Aurora File Manager, Database Explorer is now Aurora Databas
== Changelog ==
= 3.6.1 =
* Fixed another round of Plugin Check findings the 3.5.1 fix didn't fully cover: `WordPress.DB.DirectDatabaseQuery.DirectQuery`/`NoCaching` are attributed by PHPCS to the *outer* `$wpdb->get_results()`/`get_row()` call line, while `PreparedSQL.NotPrepared` is attributed to whichever *inner* line the interpolated table name appears on — two different lines in a multi-line call, so a single `phpcs:ignore` comment can only ever cover one of them. Collapsed the remaining multi-line calls in Menu Creator and Admin Notices to single physical lines so one ignore comment covers both sniffs' attributed lines at once. Re-verified with an automated scan plus live REST-dispatch round-trips (menu create/list/get/delete, notice create/render/delete).
= 1.12 =
* Added a "Disable Gutenberg" toggle (Settings > Screens > Editor): switches all post types to WordPress's classic editor instead of the block editor, using the same core-supported filter the official Classic Editor plugin uses. Off by default.
= 3.6.0 =
* Site Backup has moved to its own standalone plugin, Aurora Site Backup — install it with one click from the Settings → Add-ons screen, alongside Aurora File Manager and Aurora Database Explorer. Restoring a backup means writing arbitrary files back into the site, the same class of risk that's kept file-management functionality out of Aurora Admin proper, so it now lives in a separately-distributed companion plugin.
= 1.11 =
* Fixed the Updates screen (Dashboard > Updates) rendering unreadable white table rows in dark mode for available plugin and theme updates. Same underlying gap as the 1.10 fix (no dark styling for `widefat`-class tables), plus a WordPress core class collision — its plugin-update and theme-update tables reuse `tbody class="plugins"`, which core's own CSS makes explicitly white for the native Plugins screen. Visual-only fix; the actual update-checking and installation are still entirely native WordPress code.
= 3.5.1 =
* Fixed a fresh WordPress.org Plugin Check report: the previous compliance pass's `phpcs:ignore` annotations were placed above the *opening* line of several multi-line `$wpdb->get_results()`/`get_row()`/`get_var()` calls, but PHPCS attributes violations to the exact physical line where the interpolated tokens appear — often one or more lines further down inside the call — so those suppressions were never actually taking effect. Corrected across Menu Creator, Admin Notices, Site Backup, Media Folders, Analytics, and Media Library. Also fixed a real, unrelated bug found during verification: creating a menu in Menu Creator returned "Menu not found" instead of the newly created menu, because of how the internal follow-up request object was constructed.
* Compressed files, hidden files, and non-standard markdown files flagged by Plugin Check are scanner noise from scanning the whole development repository (build zips, `.gitignore`, `.claude/`, `PROJECT_STATUS.md`) — confirmed none of these exist in the actual submission zip.
= 1.10 =
* Fixed Export Personal Data and Erase Personal Data (the privacy/GDPR tools) rendering with unreadable white table rows in dark mode. The actual request queue, bulk actions, and export/erase processing remain entirely native WordPress code — this was a visual-only fix.
= 3.5.0 =
* Database Explorer has moved to its own standalone plugin, Aurora Database Explorer — install it with one click from the Settings → Add-ons screen, alongside Aurora File Manager. Direct database-query tooling is treated by WordPress.org's Plugin Directory review the same way as file-management functionality, so rather than remove the capability outright, it now lives in a separately-distributed companion plugin, same as File Manager did in 3.4.0.
= 1.9 =
* Activity Log redesigned as a full table (Date, Author, IP Address, Type, Action, Description) with Admin and User tabs — Admin covers site/content activity, User covers account activity (login, logout, registration, profile updates). The Author column now shows the user's avatar, role, and email. Also now tracks IP address, logouts, and media uploads/deletions, and correctly labels Pages as Pages instead of Posts.
= 3.4.0 =
* File Manager has moved to its own standalone plugin, Aurora File Manager — install it with one click from the new Settings → Add-ons screen. WordPress.org's Plugin Directory policy doesn't allow file-management/code-editing functionality in a directory-listed plugin regardless of the safeguards in place, so rather than remove the capability outright, it now lives in a separately-distributed companion plugin.
= 1.8 =
* Full admin takeover: the Import screen is now a real Aurora-built replacement, gated behind Settings > Appearance > Admin Takeover. Installing an importer reuses WordPress's own plugin installer; running an already-active importer still opens that importer's own screen unmodified.
= 3.3.2 =
* Compliance pass against the official WordPress.org Plugin Check tool: fixed a readme.txt version mismatch, a missing input-sanitization call, and annotated ~230 custom-database-table query warnings with the justification the review process expects (Aurora's backup/analytics/activity-log/menu/notices/media-folders features all use their own tables, which necessarily means direct, non-core-wrapped database access).
= 1.7 =
* Full admin takeover: the Export screen is now a real Aurora-built replacement, gated behind Settings > Appearance > Admin Takeover. The actual WXR file generation is still 100% native WordPress code — only the form is Aurora's.
= 3.3.1 =
* Fixed the Settings page: the category list and the settings panel now scroll independently, so picking a category from a scrolled-down spot in the list no longer leaves the panel showing stale, off-screen content above the fold.
= 1.6 =
* Fixed Site Health rendering with unreadable, unthemed white panels in dark mode. WordPress's own Site Health checks (and any checks other plugins add) are kept fully intact and accurate — only the visual theming was fixed, not the underlying tests.
= 3.3.0 =
* Added Modern Image Formats: automatically generates a WebP or AVIF copy of every uploaded JPEG/PNG image and serves it via a <picture> element with the original as a fallback, configurable under Settings.
= 1.5 =
* Full admin takeover: the Tools screen (Available Tools) is now a real Aurora-built replacement, gated behind Settings > Appearance > Admin Takeover. Any card another active plugin adds to this screen is still shown — nothing from other plugins disappears.
= 3.2.1 =
* Security hardening: File Manager no longer allows opening or saving executable file types (PHP and similar) for a file that already exists — only creating, uploading, and renaming to those types were previously blocked. File Manager now also honors the DISALLOW_FILE_EDIT and DISALLOW_FILE_MODS constants, the same host-level lockdown WordPress core's own file-editing and update/install flows respect.
= 1.4 =
* Added Login Redirect (Settings > Appearance > Login Redirect): optionally send logged-out visitors who try to access wp-admin to a custom URL instead of the login screen, and/or send specific roles to a custom URL after logging in instead of the dashboard. Both are off by default and never change, hide, or block wp-login.php itself.
= 3.2.0 =
* Added Google Drive as a second remote storage option for Site Backup, alongside S3-compatible storage. Connect your own Google Cloud OAuth client in Settings to store backups in your own Google Drive account.
= 1.3 =
* Added a Modules page (under the Aurora menu): install and activate Aurora's standalone companion plugins (File Manager, Database Explorer, Site Backup) with one click. This replaces the "Add-ons" section previously in Settings, and is where future Aurora addons will be installable from as they're released.
= 3.1.0 =
* Added Site Backup: full site backup (database + files) and restore-in-place, on demand or on a recurring daily/weekly/monthly schedule, stored locally or on your own S3-compatible remote storage (AWS S3, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, and similar).
= 1.2 =
* Menu Creator: fixed the item list showing empty (it now loads correctly), and added drag-and-drop reordering (with up/down buttons) for top-level admin menu items. The order is applied to the Aurora sidebar; hide and rename still work; newly installed plugins' menu items are always preserved.
= 3.0.2 =
* Fixed a plugin-header validation error: Plugin URI and Author URI were identical, which the WordPress.org submission checker requires to be distinct. Plugin URI now points to the plugin's own site (aurora.auroradragon.studio); Author URI stays on the studio's site.
= 1.1 =
* Plugins screen: the active/inactive state now always reflects the real result after activate/deactivate, even when WordPress reports a benign "unexpected output" on activation.
* Compliance: documented a Plugin Check notice for a WordPress core filter (`emoji_svg_url`) used by the emoji-disable feature.
= 3.0.1 =
* Compliance and hardening pass ahead of the WordPress.org submission: replaced a forbidden core function in the Widgets screen, converted File Manager's file operations to use the WP_Filesystem API, added nonce/sanitization coverage to a few read paths, fixed missing translator comments, and annotated custom-table SQL queries for the plugin review process.
= 3.0.0 =
* Aurora Admin is now completely free — the entire licensing system was removed, and every previously-paid feature (Role Editor, Activity Log, Database Explorer, File Manager, Analytics, White Label, Full Admin Takeover, Media Folders) is now available to everyone.
= 2.27.0 and earlier =
* Pre-release beta versions, not distributed on WordPress.org.
== Upgrade Notice ==
= 3.0.0 =
Aurora Admin is now 100% free. If you were on an earlier beta with a license key, it's no longer needed — all features are unlocked automatically.
= 1.0 =
* First public release of Aurora Admin.
* Modern admin shell — fixed sidebar, toolbar, and global search — replacing the default WordPress admin chrome.
* Real replacement screens for Dashboard, Posts, Pages, Media, Users, and Comments, plus Add User, Media Upload, and Profile.
* Nav Menus, Widgets, Themes, and the core Settings screens (General, Writing, Reading, Discussion, Permalinks).
* Power tools: Role Editor, Activity Log, Media Folders, Menu Creator, Admin Notices, and White Label.
* Full dark mode with 10 color presets plus 2 flat neutrals; rounded framed content cards, theme-tinted scrollbars, and an optional (off-by-default) Google Font for the interface.
* Security & performance hardening, custom admin CSS/JS, and a login-screen customizer.