| 开发者 | devagent |
|---|---|
| 更新时间 | 2026年7月21日 23:53 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
manage_options capability.manage_options are permanently excluded from workspace application in this version. Administrators can preview workspaces without impersonating another user or changing their own capabilities.
All configuration-changing actions require the appropriate plugin capability and a valid nonce. Saved URLs, dashboard blocks, quick actions, menu configuration, role changes, and workspace assignments are validated and sanitized.
Privacy
The plugin stores all data locally and does not send telemetry or load remote resources.
Depending on configuration, it may store:
devagent-admin-workspace folder to /wp-content/plugins/, or install the ZIP from Plugins > Add New > Upload Plugin.No. Menu visibility is presentation only. WordPress capabilities determine whether the user can access or modify data. Remove or change the role capability when access itself must be restricted.
The menu checkbox records the intended workspace configuration. The final result also depends on WordPress and the plugin that owns the screen. A plugin can conditionally register or remove a screen, require additional permissions, depend on a parent menu, reject an unavailable callback, or hide the rendered item later with CSS or JavaScript. The affected menu card reports the last browser-rendered result and provides diagnostic facts and recommended checks.
Log in once with a user who has the role and assigned workspace, then open any wp-admin screen. Return as an administrator and reopen the workspace menu editor.
It includes WordPress capabilities, capabilities stored in registered roles, and capabilities declared by captured admin menu screens. Unknown plugin capabilities appear with their technical identifiers and are not automatically classified as safe. It does not scan third-party source code or guarantee discovery of separate AJAX, REST, background-action, or dynamically calculated permissions. A plugin-specific integration is still required when an external plugin does not expose granular capabilities.
No. A workspace can organize or hide an available menu item, but it cannot bypass the capability checks implemented by WordPress or another plugin.
No. Any user with the manage_options capability is excluded from workspace application. Administrators can use the protected preview screen instead.
The reference remains stored and is shown as unavailable in the workspace editor. If it is used as the start page, the user falls back to the workspace dashboard.
Yes. The workspace configuration is shared, while the effective menu can differ because each role has different WordPress capabilities. Create separate workspaces when roles need genuinely different menu structures.
They allow one user to receive a different workspace without changing that user's roles or permissions. They are useful for resolving a multi-role ambiguity or providing different navigation to one person who otherwise has the same permissions as the rest of a team.
Yes. Add the following constant to wp-config.php:
define( 'DEVAWORKSPACE_DISABLE_WORKSPACES', true );
This restores the normal WordPress administrator while keeping recovery, settings, and diagnostics available to authorized administrators.
Not by default. Data is preserved unless "Permanently remove this plugin's data when the plugin is deleted" is enabled under Admin Workspace > Settings. Custom roles are preserved to avoid leaving users without a valid role.
No.