OpenStation vs Shortcodes In Use

wp-admin forgets. OpenStation doesn’t. You know the moment. You’re deep in a post and you need one image from the Media Library. You click over, find it, click back, and everything you had going is gone. Your scroll position, your half-typed thought, the three other things you had queued up in your head. That’s not a bug you hit. That’s the design. wp-admin shows you one screen at a time, and every navigation throws the last one away. It has worked this way since 2003, like a fridge that empties itself every time you close the door. WordPress has rebuilt almost everything else. The editor, the site editor, the patterns, the styles. The admin’s one-screen-at-a-time model is the layer nobody touched. OpenStation touches it. Install it and admin screens become draggable, resizable windows. Edit a post while the Media Library sits open next to it. Drag an image from one window straight into the other. Keep comments open in the corner. Reload the browser and your window layout — open pages, positions, sizes, and window states — comes back where you left it. OpenStation itself is free, GPL, and opt-in per user. One click in the admin bar turns it on for you. One click turns it off. Nobody else on your site sees anything change, and deactivating the plugin restores the classic admin exactly. No Core patches and no lock-in. Optional AI providers may charge for their service. Built and maintained by Automattic, the company behind WordPress.com, Jetpack, WooCommerce, and Tumblr. Work on more than one thing at once Admin pages open as windows, including pages added by most other plugins. Drag them, resize them, snap them, tile them, minimize them to a taskbar. The admin menu becomes a dock of icons. Two editors open at once is one click away. Never lose your place Moving between open windows leaves each page in place. Across reloads, OpenStation remembers your open pages, window positions, sizes and states, virtual desktops, and focus. Closing a window with unsaved changes warns you first. A desk you can actually put things on Drop posts, media, and links right onto the wallpaper. Sort them into folders. Trash them to a Trash that actually holds things. The stuff you’re working on this week can just sit out where you can see it. One desktop per job Virtual desktops, the way your operating system does them. One for writing. One for the store. One for comment triage. One for that redesign you keep poking at. Switch between them without closing anything. Find anything with Cmd+K The full WordPress command palette, plus slash commands from your plugins, all under one keystroke. Turn on the optional AI assistant and you can ask it things like “which post had the comment asking for the recipe?” and it searches your own content to answer. (Requires an AI provider configured in Settings → Connectors on WordPress 7.0+. Details under “External services” below.) See how your site fits together The Corkboard is an interactive, zoomable map of how your posts, pages, and products link to each other. Pan around it. Find the orphans. Find the hubs. Running a store? Orders, Products, Coupons, and Customers become browsable folders with stock and sale ribbons. Open a customer to see their lifetime spend and what they buy most. Follow a product to its buyers, or a coupon to who redeemed it. Make it yours Wallpapers, from color presets to animated scenes to your own photo. Live widgets pinned to the desktop: drafts, stats, recent comments, a focus timer. Uploadable desktop themes, including a built-in Legacy theme that brings the old WordPress blue back in one click. And Mio, a soft-body desk companion that drifts across your wallpaper and gets bumped around by your windows. Off by default. You’ll turn it on. For developers Extend OpenStation through documented PHP and JavaScript APIs. Register windows, icons, wallpapers, widgets, commands, and settings tabs through stable openstation_register_* PHP APIs and a typed JavaScript API; customize dock items through documented hooks; add AI tools with the WordPress Abilities API. Copy-paste examples live in the developer docs on GitHub. External services No external service is required for OpenStation’s desktop interface. The optional AI Assistant and two user-initiated enrichment features make the external requests described below. AI Assistant The optional AI Assistant sends data to the AI provider you configure in WordPress’s Settings → Connectors (for example OpenAI, Anthropic, or Google). Generation is routed through WordPress 7.0’s built-in AI Client, which supplies the credentials stored in Connectors. The plugin never handles an API key itself. With no provider configured in Connectors, no external AI requests are made. When the AI Assistant is enabled and a user invokes it (via Cmd+K or the slash-command palette): What is sent: the user’s prompt, the conversation history for the active session, and tool-call metadata. The plugin’s built-in tools (search_posts, search_pages, search_comments) run WordPress’s native keyword search and may include excerpts of the matching posts/pages/comments in tool results, which are then sent back to the provider as part of the agentic loop. When it is sent: on user-initiated AI requests, and (if an administrator enables “Score new comments with AI”) on comment-save hooks for spam analysis. Posts, pages, and taxonomy terms are not sent automatically. Why it is sent: to obtain model completions and tool-call decisions that drive the AI Assistant. Who provides the service: whichever provider you configured in Settings → Connectors. Which provider (and endpoint) receives the data depends entirely on that configuration. Review the chosen provider’s own terms and privacy policy (e.g. OpenAI, Anthropic, or Google). URL shortcut favicons When an authorized user creates a desktop shortcut to an external URL, OpenStation asks that URL for its page HTML and favicon so the shortcut can display the site’s icon. The request is made from your WordPress server and sends the requested URL, the server’s IP address, an OpenStation user-agent string, and normal HTTP request metadata to the operator of that site. This happens only when a user creates the shortcut. The destination site’s terms and privacy policy apply. WordPress.org plugin information When an authorized user opens or refreshes parts of OpenStation’s Plugins window, OpenStation may request public plugin details, update metadata, and review excerpts from WordPress.org. These requests send plugin slugs, the site’s locale, and normal HTTP request metadata to WordPress.org. This information is used only to display and manage plugins. Review the WordPress.org Privacy Policy. OpenStation’s OAuth relay does not contact a service by itself. Third-party plugins that configure the relay may contact their own providers and are responsible for disclosing those services. Credits OpenStation is brought to you by Automattic. The plugin is open source under GPLv2-or-later; contributions are welcome on GitHub. Third-party libraries The plugin bundles the following third-party JavaScript library, loaded on demand only when a feature that needs it is in use: PixiJS (MIT License) — used by the Corkboard window, built-in canvas wallpapers (e.g. the animated WordPress logo), the Mio desk companion, and the Inkfall typing game. PixiJS is loaded from the plugin’s own assets/vendor/ directory; no CDN requests are made. Data files The Inkfall game’s word list (assets/games/inkfall/words.txt) is generated from the following sources (attribution also ships in the file’s header): FrequencyWords by Hermit Dave (CC-BY-SA 4.0) — English word-frequency ranking derived from the OpenSubtitles corpus. english-words by dwyl (Unlicense) — used as a validity filter. LDNOOBW English list (CC-BY 4.0) — used as an exclusion filter.

Can’t recall where, or if, you’ve used a certain shortcode? Want to remove a plugin and unsure if it provides shortcodes or whether you’re using them? Don’t know what shortcodes come with WordPress? Found one unrecognised shortcode but unsure where there might be others? Need to swap out a theme and don’t know if it has shortcodes that you’ve used? Want to use a shortcode for a specific bit of information but can’t remember exactly what it’s called? Need to a change a parameter for all occurences of a shortcode? This is a simple administration tool that lists occurences of shortcodes within post content and/or custom fields, and/or widget settings. You can select, or search for, specific shortcodes, and it can filter down to a provider, location, or post type. It is intended to help administrators/editors locate where shortcodes have been used, so that they can be updated, renamed, deleted, or whatever. Features include : Search string(s) to match against shortcode tags – space or comma delimited for multple search strings Filter by the type of provider of shortcode – whether it is provided by a plugin, your theme, internal to WordPress (eg. [gallery]), or unknown (an inactive/deleted plugin, maybe?) Filter by a specific provider – a named plugin, for example Filter by any number of specific, recognised shortcodes Filter by where to look for the shortcode – post content, post meta data (custom fields), or widgets Filter by the type of post that contains the shortcode Results include (where relevant and available) : either the widget name and its sidebar, or a linked post title and the type of post; the shortcode and its parameters; the shortcode provider (WordPress, plugin, theme, or unknown), and where it was found Has its own shortcode, for use when a plugin or theme only declares a shortcode when not in the admin backend What it does not do : It does not provide any insight as to what any shortcode does, or how to use/configure it. It does not look at custom tables, theme options, transients. If you like this plugin (or if you don’t?), please consider taking a moment or two to give it a Review : it helps others, and gives me valuable feedback. Shortcode The shortcode for this plugin is… [shortcodes_in_use/] …and output is restricted to users with edit_posts capability. The attributes available are in line with the options available in the Tool, and each one is a filter. Setting an attribute for all possible values is the same as omitting that attribute. Separate filters are ANDed, ie. specifying provider="wordpress" post_type="page" limits the results to shortcode tags that are in a page AND provided by WordPress core. Multiple values within a filter are ORed, ie. specifying post_type="post page" provider="wordpress" limits the results to WordPress’s own shortcode tags that are in either a post OR a page. When you run the Tool in admin, the equivalent shortcode for the selected options is provided at the end of the results. Also, the sanitized shortcode is repeated at the top of the shortcode’s output. search (string) : A space or comma is interpreted as a delimiter, so… [shortcodes_in_use search="foo bar"/] …looks for any shortcode tag that contains either “foo” or “bar”. provider (string) : Any one or more of unknown, wordpress, plugin, or theme, delimited by either a comma or a space. For example… [shortcodes_in_use provider="plugin unknown"/] …reports any shortcode tag whose provider cannot be determined, or whose provider has be determined as being a plugin. location (string) : Any one or more of title, content, excerpt, meta or widget, delimited by either a comma or a space. For example… [shortcodes_in_use location="content excerpt"/] …reports any shortcode tag found in any main content or excerpt area. post_type (string) : Any one or more of WordPress’s standard post types – post, page, attachment, etc – and/or any custom post types. Multiple post types are comma- or space-delimited. For example… [shortcodes_in_use post_type="post,page"/] …reports any shortcode tag found in a post of type ‘post’ or ‘page’. tag (string) : Any one or more shortcode tags, delimited by either a comma or a space. For example… [shortcodes_in_use tag="shortcodes_in_use, custom_menu_wizard"/] …reports any occurence of either of those two shortcode tags. name (string) : This allows you to specify a specific plugin and/or theme by name. Multiple names are comma- or space-delimited, and each name must begin with either “plugin/” or “theme/”. For example… [shortcodes_in_use name="plugin/Shortcodes In Use, theme/Twenty Fifteen"/] …reports any occurence of a shortcode tag belonging to either the Shortcodes In Use plugin or the Twenty Fifteen theme. Instead of the name of the plugin/theme, you can supply their containing folder, so this would be an alternative for the example above… [shortcodes_in_use name="plugin/shortcodes-in-use, theme/twentyfifteen"/]