Adds a safe “Delete Own Account” action to an administrator’s own row in the WordPress Users list, enabling self-removal while preserving site integri …

projoktibangla

PBP own post, media & comments for Author

Own post, media & comments show for another role without administrator & editor.

activity-log.com

Ivica Delic

<p>Adds a safe “Delete Own Account” action to an administrator’s own row in the WordPress Users list, enabling self-removal while preserving site integrity.<br />
On confirmation, the plugin routes you through a dedicated deletion screen where you must select another administrator to receive all authored content.<br />
The user is logged out immediately after successful deletion.</p>
<h3>Overview</h3>
<p>Delete Own Admin Account integrates with the native Users screen and WordPress deletion workflow to let an administrator remove their own user account<br />
without requiring access to another admin’s profile. The action is visible only on the currently logged-in administrator’s own row and is styled like native delete links.<br />
During confirmation, the plugin enforces last-admin protection and requires content reassignment to another administrator to prevent orphaned content.</p>
<h3>What you see</h3>
<ul>
<li>Users list: A red “Delete Own Account” link appears only on your own administrator row (as in the first provided image).</li>
<li>Confirmation screen: “Delete Administrator Account” screen displays a warning, the number of your authored posts, and a required dropdown to select the administrator who will receive your content. Buttons: Confirm Deletion, Cancel.</li>
</ul>
<h3>Key Features</h3>
<p><strong>Visibility limited to self</strong><br />
– Adds a red <strong>“Delete Own Account”</strong> link only on the current administrator’s own row (<code>Dashboard <span aria-hidden="true" class="wp-exclude-emoji">→</span> Users</code>).</p>
<p><strong>Secure workflow</strong><br />
– Enforces WordPress capability checks (<code>administrator</code> context; <code>delete_users</code>).<br />
– Uses nonce verification to mitigate CSRF attacks.<br />
– Confirms the account to delete matches the logged-in user.<br />
– Prevents deletion if you are the last remaining administrator.</p>
<p><strong>Guided confirmation</strong><br />
– Displays a dedicated confirmation screen with an explicit warning.<br />
– Requires selecting another administrator for content reassignment.</p>
<p><strong>Content preservation</strong><br />
– Reassigns all posts, pages, media, and custom post types authored by the deleted account to the chosen administrator.<br />
– Logs out and redirects the user immediately after successful deletion.</p>
<h3>Requirements and compatibility</h3>
<ul>
<li>Role/capabilities: Only administrators (users capable of managing and deleting users) see and can use the action.</li>
<li>Multisite: Primarily intended for singlesite installations. See “Multisite considerations.”</li>
</ul>
<h3>Configuration</h3>
<ul>
<li>No settings page. The functionality is active immediately upon activation.</li>
</ul>
<h3>Pre-deletion checklist (strongly recommended)</h3>
<ul>
<li>Ensure there is at least one other active administrator and verify their credentials.  </li>
<li>Back up the site (database and files) before proceeding.  </li>
<li>Review integrations that reference your user ID:
<ul>
<li>E-commerce, LMS, membership, workflow, or approval plugins.  </li>
<li>API keys, application passwords, or automations tied to your user.  </li>
<li>Third-party services that may store your WordPress user ID or email.  </li>
</ul>
</li>
<li>Decide who should own your content after deletion and ensure that user is an administrator.  </li>
<li>Verify that critical scheduled tasks (cron) or hooks are not tied to your personal user ID.</li>
</ul>
<h3>Usage</h3>
<ol>
<li>Navigate to <strong>Dashboard <span aria-hidden="true" class="wp-exclude-emoji">→</span> Users</strong>.  </li>
<li>In your own administrator row, click <strong>“Delete Own Account.”</strong>  </li>
<li>On the confirmation screen:
<ul>
<li>Read the warning message.  </li>
<li>From <strong>“Reassign posts to,”</strong> choose the administrator who will receive all your content.  </li>
<li>Click <strong>Confirm Deletion.</strong></li>
</ul>
</li>
<li>Result:
<ul>
<li>Your user account is deleted.  </li>
<li>All authored content is transferred to the selected administrator.  </li>
<li>You are logged out immediately and redirected.</li>
</ul>
</li>
</ol>
<h3>How content reassignment works</h3>
<ul>
<li><strong>Scope:</strong> Posts, pages, media (attachments), and custom post types authored by the deleted administrator are reassigned to the selected administrator.  </li>
<li><strong>Comments:</strong> Existing comments remain as stored; comment author display is not retroactively changed.  </li>
<li><strong>Taxonomies:</strong> Terms remain intact; authorship metadata associated with terms is not typical and is not modified unless managed by a specific plugin.  </li>
<li><strong>Control:</strong> You must select the target administrator on the confirmation screen. If you need a different outcome, reassign content manually before deletion.</li>
</ul>
<h3>Security model</h3>
<ul>
<li>Capability checks ensure only qualified administrators can trigger self-deletion.  </li>
<li>Nonce verification protects the action from CSRF.  </li>
<li>Identity check ensures the account-to-delete matches the currently logged-in user.  </li>
<li>Last-admin protection prevents lockouts by blocking deletion if you are the only administrator.  </li>
<li>Session handling logs you out immediately upon success to avoid stale sessions.</li>
</ul>
<h3>Multisite considerations</h3>
<ul>
<li>The plugin targets single-site usage. In a network:
<ul>
<li>Super Admin capabilities may change behavior and available actions.  </li>
<li>Test in staging before using on a production network.  </li>
<li>Ensure another administrator or Super Admin retains access to the site.</li>
</ul>
</li>
</ul>
<h3>Limitations</h3>
<ul>
<li>No bulk deletion; action is for the current administrator only.  </li>
<li>No bypass of last-admin protection.  </li>
<li>No custom UI to migrate non-post data stored by other plugins against user IDs; audit third-party data separately.  </li>
<li>Irreversible: Deletion cannot be undone except by restoring from backup.</li>
</ul>
<h3>Risks and best practices</h3>
<ul>
<li>Risk of lockout if performed without another administrator available. Always verify another admin can log in.  </li>
<li>Potential impact on plugins that store user IDs for ownership, approvals, or licensing. Review and test.  </li>
<li>Auditing needs: If you require an audit trail, use a security/audit log plugin to record user deletions.  </li>
<li>Always perform a full site backup beforehand and validate on a staging environment for complex setups.</li>
</ul>
<h3>Troubleshooting</h3>
<ul>
<li>
<p><strong>The “Delete Own Account” link does not appear:</strong></p>
<ul>
<li>Confirm you are logged in as an administrator and viewing your own user row.  </li>
<li>Verify the plugin is activated.  </li>
<li>Check role/capability manager plugins that might override permissions.  </li>
<li>If you are the last remaining administrator, deletion is intentionally blocked.</li>
</ul>
</li>
<li>
<p><strong>Cannot confirm deletion (no administrators in dropdown):</strong></p>
<ul>
<li>Create or promote another user to administrator, then retry.</li>
</ul>
</li>
<li>
<p><strong>Content reassignment target is incorrect:</strong></p>
<ul>
<li>Cancel, reassign authorship of critical content manually first, then repeat the deletion.</li>
</ul>
</li>
<li>
<p><strong>Redirected but account still exists:</strong></p>
<ul>
<li>Clear caches, retry, and check for plugin conflicts; review server error logs.</li>
</ul>
</li>
</ul>
<h3>Uninstallation</h3>
<ul>
<li>Deactivating or deleting this plugin does <strong>not</strong> restore previously deleted users.  </li>
<li>The plugin stores no settings and creates no custom tables; it can be safely removed after use.</li>
</ul>
<h3>Support</h3>
<ul>
<li>Use the plugin’s <strong>WordPress.org support forum</strong> for issues and feature requests.  </li>
<li>When requesting support, include:
<ul>
<li>WordPress version  </li>
<li>Single-site vs. multisite setup  </li>
<li>Any role/capability manager plugins in use  </li>
<li>Detailed steps to reproduce the issue</li>
</ul>
</li>
</ul>


Alternatives to Delete Own Admin Account

Top alternatives