Updated October 2026
What's
Coming Next
Explore the TheOneWP roadmap, follow the development of
upcoming WordPress modules and vote for the features you want us to
prioritise next.
Development Roadmap
TheOneWP Roadmap for Upcoming WordPress Features
The TheOneWP roadmap shows the modules and improvements currently planned for future plugin releases. Browse features that are planned, already in development or expected in the next release.
Each roadmap item includes its current development status, category and expected version. You can also vote for the features that would be most useful for your WordPress workflow.
Released modules and final version details are available in the TheOneWP changelog. You can also explore the current TheOneWP features and read the plugin guides.
TheOneWP modules are developed according to established WordPress APIs and development conventions documented in the official WordPress Developer Resources .
🚀 v1.3.0— Target: Oct 2026
Our next release will include new backend and content modules, various optimizations, and a huge amount of fixes for existing modules.
View Changelog →Planned
8
In Progress
8
IN THE NEXT RELEASE
8
Custom Content Type
Content
Creates structured content that lives outside the standard WordPress posts and pages system. Define your own content type, choose the fields it contains, and store records in a dedicated database table built for that specific data. Use it for directories, logs, listings, records, or other information that does not need the full WordPress post structure. Each content type gets its own management interface in the admin, keeping data organized and easier to maintain while avoiding unnecessary post metadata and keeping complex projects cleaner as they grow.
v1.5.0
Admin Bar Custom Elements
Backend
Adds your own shortcuts and links to the WordPress admin bar, putting frequently used destinations exactly where they are easiest to reach. Create custom elements for admin pages, frontend URLs, external tools, documentation, dashboards, or anything your workflow needs. Choose their labels, links, position, and who can see them without editing theme or plugin code. Each element stays managed from one place, making the admin bar more useful for editors, developers, and clients while keeping everyday actions closer and unnecessary navigation out of the way.
v1.5.0
Temporary User Access
Access
Gives someone access to WordPress for a limited time without leaving another permanent account behind. Create temporary users for developers, support teams, collaborators, or clients, choose the role they receive, and set exactly when their access expires. The account works normally while active and is automatically blocked when its time runs out, without requiring you to remember to remove it later. Every temporary access stays visible from one screen, where you can review who has access, extend an expiration date, or revoke it immediately when it is no longer needed.
v1.5.0
REST API Builder
System
Builds custom REST API endpoints in WordPress without having to register and maintain them by hand. Define the route, request method, permissions, parameters, and data each endpoint should return or accept. Use it to expose structured content, connect external applications, power frontend interfaces, or create integrations around your WordPress data. Each endpoint stays managed from one place, where its configuration can be reviewed, changed, enabled, or disabled as your project evolves, keeping custom API functionality organized without scattering endpoint code throughout themes and plugins.
v1.5.0
Cache Warmer
System
Preloads important pages before visitors reach them, so an empty cache does not make the first request pay the full cost of generating the page. Choose which URLs should be warmed and let WordPress request them automatically after the cache has been cleared or refreshed. Pages are rebuilt in advance and ready to be served when real traffic arrives, helping keep response times more consistent after updates, deployments, or cache purges. Everything is managed from one screen, where URLs can be reviewed, added, removed, or warmed again whenever needed.
v1.5.0
User Account Expiration
Access
Sets an expiration date for WordPress accounts so access does not remain active longer than intended. Choose which users should expire and define exactly when their accounts should stop working. Once the date is reached, login access is automatically blocked without deleting the user or their content, keeping posts, ownership, and account data intact. Expiration can be changed, extended, or removed at any time from the admin. Useful for temporary staff, contractors, clients, memberships, or any account that should only have access for a defined period.
v1.5.0
Cron Configurator
System
Gives you control over scheduled WordPress tasks without digging through code or waiting for WP-Cron to remain a mystery. View registered cron events, see when they run, how often they repeat, and which hook each one triggers. Create custom schedules, change existing events, run tasks manually, or remove jobs that are no longer needed. Everything stays manageable from one screen, making it easier to inspect background activity, troubleshoot missed events, and control recurring tasks used by WordPress, themes, and plugins without editing cron configuration by hand.
v1.5.0
Disable Site Admin Email Verification Screen
System
Removes the periodic WordPress screen asking administrators to confirm that the site administration email address is still correct. Once disabled, users with administrator access can log in without being interrupted by the verification prompt that WordPress normally displays at regular intervals. The site email itself is not changed, removed, or prevented from receiving notifications; only the confirmation screen is skipped. Useful for managed websites, development environments, or installations where the administration email is already controlled and repeated verification adds an unnecessary step.
v1.5.0
Custom Post Type
Content
Turns WordPress into a structure built around your content instead of forcing everything into posts and pages. Create custom post types for projects, properties, products, events, team members, or anything else your site needs. Choose their labels, supported features, visibility, archive behavior, REST API access, menu position, and URL structure without writing code. Each type gets its own place in the WordPress admin and can support titles, editors, featured images, excerpts, revisions, custom fields, and hierarchy. Everything stays managed from one screen, where you can review, edit, or remove each content type as your site evolves.
v1.4.0
Custom Meta Box
Content
Adds structured fields to WordPress content without writing custom code or relying on another plugin. Create meta boxes for posts, pages, or custom post types and fill them with the fields your content actually needs. Choose where each box appears, which content types use it, and how its fields behave. Text, numbers, URLs, dates, selections, toggles, and other values stay attached to the content they belong to and can be edited directly from the WordPress editor. Everything is managed from one screen, so fields can be added, changed, reordered, or removed as the structure of your site evolves.
v1.4.0
Required Content Field
Content
Stops incomplete content from being published by making selected WordPress fields mandatory. Choose which fields must contain a value before a post, page, or custom post type can be published or updated. Require titles, content, excerpts, featured images, or other supported fields depending on what each content type needs. When something is missing, the editor clearly identifies what still needs attention instead of allowing incomplete content through. Rules are managed from one place and can be applied only where needed, keeping editorial standards consistent without relying on authors to remember every requirement.
v1.4.0
Email Log
System
Keeps a record of the emails WordPress attempts to send, so missing messages no longer disappear without a trace. See when each email was generated, who it was sent to, its subject, headers, and whether WordPress reported the send as successful or failed. Search and inspect individual entries when debugging contact forms, notifications, password resets, orders, or other automated messages. Logs stay available from one screen and can be cleared when no longer needed, giving you a practical history of outgoing email activity without changing how WordPress sends mail.
v1.4.0
Script Manager
System
Controls which CSS and JavaScript files WordPress loads instead of letting every plugin add assets everywhere. See the scripts and styles detected on each page, identify where they come from, and disable the ones that are not needed. Rules can target specific pages, post types, or the entire site, helping reduce unnecessary requests without editing plugin files or theme code. Each rule stays manageable from one place, making it easier to remove frontend bloat, troubleshoot conflicts, and keep pages lighter while leaving the original files untouched.
v1.4.0
Editorial Comments
Publishing
Adds private notes to WordPress content so editors can leave context, instructions, or reminders without putting them anywhere near the frontend. Write editorial comments directly inside posts, pages, or custom post types and keep discussions attached to the content they belong to. Notes stay visible only in the WordPress admin, making them useful for revisions, approvals, pending changes, or internal instructions. Everything remains with the content as it moves through the editorial workflow, giving authors and editors a simple shared space for information visitors should never see.
v1.4.0
Custom Taxonomy
Content
Gives WordPress new ways to organize content beyond categories and tags. Create custom taxonomies for posts, pages, or custom post types and define exactly how content should be grouped. Choose their labels, hierarchy, visibility, REST API access, admin interface, and URL structure without writing code. Use them like categories with parent and child terms, or like tags with a flat structure. Each taxonomy integrates directly into the WordPress admin, keeping terms easy to create and manage while giving complex content structures a clean, predictable way to stay organized.
v1.4.0
Disable Plugin & Theme Editor
Disable
Removes the built-in WordPress file editors that allow theme and plugin code to be changed directly from the admin area. Once disabled, users can no longer edit PHP, CSS, or other plugin and theme files through the dashboard, reducing the risk of accidental changes, broken sites, or malicious code being inserted through a compromised account. The files themselves remain untouched and can still be managed through your normal development workflow. A simple security measure that closes an unnecessary path to production code without changing how themes or plugins work.
v1.4.0
Disable Application Passwords
Disable
Takes away the second credential WordPress has handed every user since 5.6. An application password is accepted by the REST API and by XML-RPC, never expires, is not covered by a second factor, and never meets the login form — so nothing you have put on the login page applies to it. Choose who loses them: everybody, everybody below administrator, or the roles you name. A refusal says why, where it happens, rather than failing as a wrong password would. Refusing one does not delete it, so the ones already created are listed here — who holds them, how many, when they were last used — and can be revoked from this screen.
v1.3.0
Disable Native Lazy Loading
Disable
Governs the loading="lazy" WordPress writes into images and iframes by itself. Lazy loading is usually right, and wrong in three places: the picture at the top of the page, a slider whose off-screen slides stay empty, and a site already lazy-loading with JavaScript. So it asks how much rather than only whether: all of it, only the first few media on a page, or only what you name — a class, a file name. It works on the finished page rather than through the filters, which is why markup a theme wrote the attribute into by hand is covered too, along with the sizes=auto that WordPress pairs with it. What you do not name keeps the attribute.
v1.3.0
Disable Block-Based Widget Screen
Disable
Puts the classic widgets screen back in place of the block canvas used for Appearance → Widgets since 5.8, and with it the customiser’s widgets panel, since both are decided by the same answer. On a site whose sidebars hold a search box, a menu and a paragraph, the block screen asks somebody to learn an editor in order to move a search box. It also says how many widget areas the active theme actually registers, which is the quickest way to tell whether the screen is worth putting back at all. Nothing is converted: the widgets in the database are the same either way, and switching this off brings the block screen back as it was.
v1.3.0
Disable WLW Manifest
Disable
Removes the Windows Live Writer manifest tag from the page head. It pointed a desktop blogging program, discontinued in 2012, at a file describing what the site could do, and it outlived that program by a decade on every page of every site. Nothing has looked for it in years, and it carried no function of its own: only an address. WordPress stopped printing it in 6.3, so on anything newer there is nothing of its own left to take away — the switch still matters on 6.2, and on any version it silences the deprecation notice a theme still asking for the tag writes into the log on every page. There is nothing to restore later.
v1.3.0
Option Pages
Utilities
Builds settings pages for the admin without writing any PHP. A page is a title, a place in the menu, the capability needed to open it, and a list of fields — text, numbers, dates, switches, choices, media, an editor, a repeater — arranged into sections and tabs. What people type in is stored as ordinary WordPress options, either together in one array or one option per field, and read back through a single function that hides which of the two it was. The values are exposed to Elementor, Bricks and JetEngine as dynamic tags, so a page built there reads them without code, and changing where they live carries them across.
v1.3.0
External Content Link
Content
Lets a page or a post point somewhere else: it is written here, appears in the menus and archives here, and its link goes elsewhere. It is how a menu entry reaches a product on somebody else’s shop, or a card in an archive opens the ticket page for an event, without a custom link repeated in every menu. The address is set from the editor, the block sidebar or Quick Edit, and a column says which items point away. It is given out everywhere WordPress is asked for it, and whoever reaches the content anyway is sent on instead of finding a page that was never meant to be read. Addresses left by Page Links To are read where that plugin put them.
v1.3.0
JSON-LD Manager
SEO
Says who this site is, in the language search engines read. A page can describe itself well and still leave the first question unanswered: whose site is this? Here the answer is written once — a company, a local business or a person, with the address, the telephone, the opening hours and the profiles elsewhere that are the same thing — and everything else points at it. Beside it the WebSite node, which is what a search engine looks for before offering a search box among its results. Where SEO Meta already describes a page, the two are put in one script instead of two, with its publisher pointing here rather than repeating a bare name and logo.
v1.3.0
Broken Link Scanner
SEO
Adds a Check Links action to the content lists, opening a panel that lists every link the piece holds and says which of them still answer. A link rots quietly — the page it pointed at is renamed, the site it lived on closes — and nothing on your side changes, so the only way anyone finds out is by clicking. Each address gets a verdict with the reason beside it rather than a bare code, a broken one can be corrected without leaving the panel, and links to this site are resolved against the database, which can say that the target is a draft, or in the trash. What was found is kept, so the list can be filtered to what is broken.
v1.3.0
Community
Suggest a Feature or a Correction
Have an idea that's not on the roadmap? Tell us — the most requested community suggestions get added to the next planning cycle.
💡 Got an idea?
Describe the feature you'd like to see in TheOneWP or you've seen some issue with the plugin? We read every suggestion and reply to the most promising ones. If it is valid or a good one we'll increase your activation by one.