blocks|key|4837701|text|我不知道你想问什么。WordPress+REST+API只是提供了一种从网站的其他地方访问帖子等内容的方法(例如主题等)。仍然可以从管理后端和JSON/REST+API访问页面：https://developer.wordpress.org/rest-api/reference/pages/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4837702|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.wordpress.org/rest-api/reference/pages/^0|2H|1L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'm not sure what you're trying to ask. The WordPress REST API just provides a way to access posts, etc. from somewhere else part from the web site side (e.g. themes, etc). Pages would still be accessible from the admin backend and the JSON/REST API: <a href="https://developer.wordpress.org/rest-api/reference/pages/" rel="nofollow noreferrer">https://developer.wordpress.org/rest-api/reference/pages/</a>

blocks|key|3369164|text|具体地说，使用WordPress可以确保不会重写固定链接。这样它们仍然是site.com/?p=post-id|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3369165|这样就很容易解析并获取新的页面。然后将href替换为您的前端所需的任何内容。|3369166|您可以使用该ID立即获取新帖子的slug。|3369167|或者，您甚至可以在ID的表示层中保留到您自己的slug的映射。|3369168|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Specifically with WordPress you could ensure that you're not rewriting the permalinks. That way they are all still site.com/?p=post-id

That way it's easy to parse fetch the new pages. Then replace the hrefs with whatever your frontend needs.

You could use the ID to fetch the slug of the new post immediately.

Or you could even keep a mapping in your presentation layer of IDs to your own slugs.

blocks|key|1052597|text|对于那些正在寻找答案的人：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1052598|“设置”>“常规”下有两个URL设置。|1052599|​|1052600|📷|atomic|offset|length|1052601|1052602|WordPress地址应该是您的api站点的URL。比如api.whatever.com。|1052603|站点地址(+URL+)应该是前端的URL。比如www.whatever.com。|1052604|这允许内部链接在编辑器中正常工作，同时保持后端站点在独立的URL上，而不是无头的前端。|1052605|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/482c88397d7875631122e7e4ac10e05f.png|imageAlt^0|0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@$I|14|J|15|1|16]]|A|$]]|$1|K|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|19|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1A|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y|Z|-4]]]]

For those looking for the answer:

There are two URL settings under Settings > General.

<a href="https://i.stack.imgur.com/ZGro5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ZGro5.png" alt="enter image description here"></a>

WordPress Address (URL) should be the URL for your api site. Like api.whatever.com.

Site Address (URL) should be the URL for the frontend. Like www.whatever.com.

This allows the internal linking to work properly in the Editor while keeping the backend site on a separate URL from a headless frontend.

blocks|key|4837796|text|更改site_url对我不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4837797|由于我还有一个带有自定义rest控制器的wordpress主题，如果我更改站点url，wp-json就会中断|4837798|我的后端托管在数字海洋应用程序上，我的前端托管在vercel上|4837799|我使用一个名为make-paths+relative的wordpress插件修复了这个问题，但是由于我的后端不知道我的前端在哪里，我在插件中添加了一个更改：|4837800|前端/class-make-paths+relative.php第123行|4837801|我添加了一个常量配置，它是在wp-+FRONTEND_URL+$relative_link+=FRONTEND_URL.$link中定义的；|4837802|这会改变我的帖子、页面或cpt后端的固定链接，也会改变内容编辑器中的内部链接|4837803|我也向插件作者提出了一个请求|4837804|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

Changing the site_url doesn't work for me.
Since I also have a wordpress theme with custom rest controllers
Plus the wp-json breaks if I change the site url
My backend is hosted at digital ocean app
My frontend is hosted at vercel
I fixed it by using a wordpress plugin called make-paths-relative
But since my backend doesnt know where my frontend is I added one change within the plugin at:
frontend/class-make-paths-relative.php line 123
I added a constant FRONTEND_URL which i define in the wp-config
$relative_link = FRONTEND_URL.$link;
This changes both the permalink within my backend of a post, page or cpt
And changes internal links as wel, links within the content editor
I made a request to the plugin author as well

We want to use the Wordpress Rest-API to build a page decoupled from the backend. A few things still bother us though:
Within the wordpress backend one can add links in the content editor of a page or a post and one gets normally a list of all existing pages and posts of the same page to link to them. By decoupling the backend it does not know the exact urls to other pages and we need to provide this. Is there a possibility to tell wordpress what links are available?

Thanks in advance.
Cheers

Headless CMS: Wordpress Rest-API – Add links to existing posts/pages

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们希望使用Wordpress Rest-API来构建一个与后端解耦的页面。有几件事仍然困扰着我们:在wordpress后端，人们可以在页面或帖子的内容编辑器中添加链接，并且通常会得到相同页面的所有现有页面和帖子的列表，以链接到它们。通过解耦后端，它不知道其他页面的确切urls，我们需要提供这一点。有没有可能告诉wor...

问无头CMS: Wordpress Rest-API -添加到现有帖子/页面的链接
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无头CMS: Wordpress Rest-API -添加到现有帖子/页面的链接EN