Togra Admin Enhancer

Yes, when a front-end feature is switched on. Maintenance mode, header/footer code, the custom login URL and the external-link handling all run on the public site. Everything else is admin-only, and every feature is off until you enable it.

Only users who hold unfiltered_html, the capability WordPress itself requires before someone may save raw markup. On a single site that means administrators; on multisite, only network administrators. The settings screen additionally requires manage_options. Whatever you put there is printed on the public site exactly as you typed it, which is the point of the field, so treat it as you would any code you add to your theme.

The link carries a 64-character token generated from PHP's cryptographic random source, so guessing one is not realistic. It is still a live credential: anyone holding the link is signed in as that account, so send it the way you would send a password. The token is consumed on arrival and the browser is redirected immediately, which keeps it out of the address bar, the browser history and the Referer header of the next request. An invalid token is ignored silently — the page loads as if nothing was passed — so the URL cannot be used to probe for valid ones.

Whatever its role allows, minus the things that would let it outlive its expiry date. It cannot sign in with a password, reset a password, create a user, delete a user, or open the plugin and theme editors. Choose the lowest role that still lets the person do the job; Editor is usually enough.

The account stops working immediately. If someone is signed in with it at the time, they are logged out on their next page load. The account stays in your users list so you can see it and extend it if you want; revoking deletes it outright.

No. It does not bundle an update checker, does not contact any server of its own, and does not touch how WordPress decides what to update or when. Updates behave exactly as they would with the plugin deactivated.

The actions worth being able to account for later: settings imported, the audit log cleared, a temporary login created, changed or revoked. Each entry records what happened, who did it and when. The last 100 are kept and older ones drop off, so the log cannot grow without limit. It lives in a single option and is removed when you uninstall the plugin.

Yes. It carries your switches and text fields, but not the site password: that is stored as a hash and is left out of the file, so an export cannot hand anyone the way past your password protection. Importing a file never changes the site password either — it is only ever set by typing it in.

Settings live in a single option. Some features also store post meta or user meta: an external permalink, a menu item's new-tab flag, a disabled-account flag, a replaced media file, and the last login timestamp. Temporary logins create real user accounts, marked with their own meta. Uninstalling the plugin removes all of it, including any temporary accounts still present.

Rename or delete the plugin folder over FTP or your host's file manager. WordPress deactivates the plugin and wp-login.php works again.

The plugin activates per site and each site keeps its own settings. It has not been tested as a network-wide activation.

Every SVG is cleaned before it is stored, and again after WordPress attaches it. The cleaning runs enshrined/svg-sanitize 1.0.0, which is bundled with this plugin under the GPL, followed by a second pass of the plugin's own checks. That second pass is deliberate. Several plugins bundle the same library under the same class name, so on a site running more than one of them the copy that answers first is not necessarily this one, and its version and settings may differ. The plugin's own checks therefore run over the result either way: scripts, event handlers and javascript: URLs are removed, references have to stay inside the document rather than fetch something remote, and url() values are checked in attributes and inside <style> blocks alike. If the library cannot be loaded at all, a DOM-based fallback in the plugin does the whole job on its own.

Yes. The login page is served by WordPress, not by your theme, so the design looks the same whichever theme you run. It restyles what WordPress already outputs rather than replacing the form, so password managers, two-factor plugins and the show/hide password button carry on working. Pick your two colours and the plugin works out the rest: hover shades, focus rings, and whether the text outside the card needs to be light or dark for the background you chose.

It answers with a 503 status, which tells search engines the outage is temporary rather than permanent. Setting a countdown target also sends a Retry-After header so crawlers know when to come back.