| 开发者 | gurievcreative |
|---|---|
| 更新时间 | 2026年9月7日 23:51 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
ideom_map post; the document is JSON in post meta. Deactivating or deleting the plugin leaves your maps untouched, and Tools → Export can back them up.edit_posts, updating or deleting is re-checked on the server for that specific map, and the map list is never public.
* Its own REST API. Maps are served through the plugin's ideom/v1 namespace, and every write passes strict document validation. Core's post endpoints are deliberately not exposed.
Worth knowing before you write anything sensitive in a map: a published map is readable by anyone who knows its post id, whether or not it is embedded anywhere. Keep private notes out of published maps, or keep the map as a draft.
REST API
Namespace ideom/v1. Writes are authenticated with cookies plus the standard X-WP-Nonce header; reading a published map needs neither.
GET /maps — every map the caller may see, newest first, capped at 100POST /maps — create a mapGET /maps/<id> — read one mapPUT /maps/<id> — overwrite one mapPUT /maps/<id>/template — star or unstar a map as a templateDELETE /maps/<id> — delete one mapideom_invalid_document (400), ideom_forbidden (403), ideom_not_found (404).
[ideom_map id="…"].No. The editor runs entirely on your site and the plugin makes no external requests. Maps never leave your database.
In a ideom_map post. The title mirrors the root node's text; the document is JSON in the _ideom_content post meta, alongside _ideom_version and _ideom_template.
No. A signed-out visitor gets the map read-only: it can be panned, zoomed, folded and exported, and nothing they do reaches the server. The same applies to any signed-in user without edit_post on that map. Every write is re-checked on the server regardless of what the front end believed.
No. The post type registers with show_in_rest disabled on purpose — core's endpoints would let a client write _ideom_content without going through the plugin's document validation.
It degrades to an empty document instead of breaking the screen. Content that fails validation — non-finite coordinates, duplicate node ids, cyclic parent chains — is never returned to the editor.
They stay. Maps are your content, stored as ordinary ideom_map posts, and deleting or deactivating the plugin leaves them in the database untouched — reactivating brings all of them back exactly as they were.
If you want them gone, delete them in the Ideom screen before removing the plugin; once it is gone there is no screen that lists them. To keep a copy, Tools → Export offers "Mind Maps" as an export type.
Note that deleting a user does delete their maps, the same way WordPress deletes other content belonging to a removed user.
ideom_map post type; ideom/v1 REST namespace; Mind Map block and [ideom_map] shortcode; templates; admin screen.