| 开发者 | jonmao |
|---|---|
| 更新时间 | 2026年11月10日 21:27 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
slicewise_manage capability to the Administrator role and shows nothing to visitors.
Only users with the slicewise_manage capability, which Administrators get when you activate the plugin. Visitors never see it, and it is not available through WordPress's own REST API.
No. Everything stays in your WordPress database: stories as a private post type, and the journey, board order and settings as options. The plugin loads no scripts or fonts from other sites and calls no outside service.
When you move a story ahead of one it needs, it shows that the other story has to move too, and offers to re-order both. It also shows target months that change, work that moves down the queue, and when "In progress" would go over your limit.
Yes. Slicewise → Import and export downloads everything as one JSON file, and imports it on another site. You see what will change before anything is replaced.
Deleting the plugin from the Plugins screen removes every story, the journey, the board order, the settings and the capability it added. Deactivating keeps them.
Yes. Slicewise Pro is a separate add-on for teams: as many boards as you need, Viewer and Editor roles, a timeline of planned work by month, the full history of every move and story change, a read-only roadmap block for any page, and imports from CSV, Jira and Trello. Everything in this plugin stays free. Administrators see one notice about it on Slicewise's screens, which "Don't show this again" hides for good.
In the plugin itself. The journey and story editors in build/ are compiled from the React source in src/ with @wordpress/scripts (wp-scripts build). Everything in assets/, including SortableJS, ships unminified.