You can access the general settings by going to WP Frontend Admin > Settings > General. These settings allow you to control the core behavior of the plugin across your entire site.
General Behavior
Add “Edit” link after post content:
Most WordPress themes show an “Edit” link or button on single post pages that administrators can click to quickly open the post editor. By activating this option, our plugin will automatically change this link to point to the frontend editor page you’ve created, instead of the default backend editor. This creates a seamless editing experience for your users. Please note, the visual display of the edit link is controlled by your theme; we just update its destination URL.
Disable the quick settings:
When you’re logged in as an administrator and viewing a frontend page that uses our shortcode, WP Frontend Admin displays a helpful “Quick Settings” panel on the left. This powerful tool allows you to visually hide elements, edit texts, and configure the page on the fly. This panel is only visible to you, not your users. If you prefer to hide this panel, you can disable it by activating this option.
Disable the wp-admin notices when viewing on the frontend:
The WordPress dashboard often displays notifications about plugin updates, promotional offers, or other admin-related news. These notices can be distracting or confusing for your users on a frontend dashboard. Ticking this option will hide all such notices on pages rendered by WP Frontend Admin, creating a cleaner experience. Be aware that this will hide all admin notices, including potentially useful ones from other plugins (e.g., a notification that a form submission was successful).
Redirect users to this page after publishing a post:
Control what happens after a user successfully publishes a post, product, or any other content. This is great for streamlining your users’ workflow. You can choose to:
- Redirect to the list of posts: Takes the user back to see all their content.
- Redirect to create a new post: Perfect for users who need to add multiple items in a row.
- Redirect to view the new post: Allows the user to immediately see their newly published content on the live site.
Redirect users to this page after creating a post with pending review status:
If your users don’t have permission to publish directly and must submit their posts for review, you can set a custom redirect for after they click “Save as pending”. This works just like the setting above and helps guide users to their next step.
- Redirect to the list of posts.
- Redirect to create a new post.
- Redirect to view the new post (this will likely show a preview version).
User Experience & Permissions
Disable the message indicating why a page didn’t load:
Sometimes a frontend page might fail to load admin content. This could happen if the required plugin is deactivated or the user lacks the necessary permissions. By default, we show a helpful message to administrators explaining the potential cause to make debugging easier. You can disable these tips if you prefer not to see them.
Auto select this user role when we are creating users in the frontend:
If you’ve created a frontend page for managing users (e.g., for team managers to add new staff), this option can save time. You can select a default user role (like “Editor” or “Contributor”) that will be automatically assigned when creating a new user, simplifying the process.
Hide pages containing our shortcode:
If you create a frontend dashboard where users can manage their own pages, you probably don’t want them to see and edit your “system” pages (like the dashboard pages themselves). Activating this option will automatically hide any page containing a WP Frontend Admin shortcode from the list of pages, preventing users from accidentally breaking the dashboard.
Default post/page editor for all post types:
This powerful feature lets you define a default editor for your users. For example, if your site uses Elementor, you can set it as the default. When a user clicks an “Edit” link, they’ll be taken directly to the Elementor editor instead of the normal WordPress editor. We also offer settings to override this on a per-post-type basis. For example, you could set Elementor as the default for “Pages” but keep the standard editor for “Posts”. This setting applies to all non-administrator roles.
Restrict post types to only display/edit posts created by the current user:
To ensure users can only see and manage their own content, you can list post types here (e.g., post, product). When you enter a post type, any frontend page displaying that content will automatically be filtered to show only items created by the currently logged-in user. This is a global setting that simplifies permissions and avoids having to configure it on each page individually.
WordPress Multisite Settings
The following settings are only visible and applicable if you are running a WordPress Multisite network.
Enable global settings on Multisite?
On a Multisite network, you have two choices: manage WP Frontend Admin settings for each site individually, or manage them all from one central place. Activating “global settings” moves the settings page to your Network Admin dashboard. Any changes you make there will apply to all sites across your entire network, saving you a massive amount of time.
Use this site as the frontend dashboard for the entire network:
This is one of our most powerful Multisite features. It allows you to create a single, centralized dashboard on one site (e.g., dashboard.yournetwork.com) that all users from all sites will use. When a user logs into this central dashboard, they will see and manage the content (posts, products, etc.) from their own site. This means you only have to design and maintain one dashboard for your entire platform.
Excluded network site ids:
Sometimes you may want to prevent WP Frontend Admin from running on certain sites in your network. For example, you might want to give admins of a specific subsite full access to the regular wp-admin backend. Simply enter the Site IDs here (separated by commas), and our plugin will be completely disabled on those sites.