英文:
WordPress multisites advice needed on different booking engines
问题
我在为我的WordPress网站找解决方案时遇到了一些挑战。我想要整合三个不同的预订引擎：一个用于共享工作空间，一个用于活动，一个用于服务。问题是，我可以分别找到这三个引擎，每个都设计用于不同的主题。
现在，我在思考是否使用WordPress Multisite可能是答案。想法是有三个子域，每个托管一个预订引擎，同时保持主域作为登陆页。所以，看起来是这样的：
- 共享工作空间预订引擎位于sub1.domain.com
- 活动预订引擎位于sub2.domain.com
- 服务预订引擎位于sub3.domain.com
主域将是domain.com。
我理解使用WordPress Multisite，用户将能够在所有四个域（主域和三个子域）之间保持登录状态。这意味着他们不需要在每个站点上分别登录。此外，我希望能够在一个单一的管理面板中查看来自所有三个域的收据，以便更容易管理。
您能帮助我理解在这种情况下WordPress Multisite如何有益，是否确实满足我的要求吗？
对我非常重要的一点是，当用户登录到各个单独的域时，他们的用户后端会是什么样子？
谢谢！
英文:
I'm facing a bit of a challenge with finding a solution for my WordPress website.
I want to incorporate three different booking engines: one for coworking space, one for events, and one for services. The problem is that I can find all three engines separately, each designed for a different theme.
Now, I'm wondering if using WordPress Multisite could be the answer. The idea is to have three subdomains, each hosting one of the booking engines, while keeping the main domain as the landing page. So, it would look like this:
- Coworking space booking engine at sub1.domain.com
- Events booking engine at sub2.domain.com
- Services booking engine at sub3.domain.com
The main domain would be domain.com.
My understanding is that with WordPress Multisite, users would be able to stay logged in across all four domains (the main domain and the three subdomains). This means they won't need to log in separately on each site. Additionally, I hope to see the receipts from all three domains in a single admin panel for easier management.
Could you please help me understand how WordPress Multisite would be beneficial in this situation and if it would indeed meet my requirements?
Something super important for me to know is how would the user back end look for each user when they log on each of the individual domains?
Thanks!
答案1
得分: 1
你所描述的情况似乎适用于多站点功能，如果我理解正确的话。
您可能需要为用户分配超级管理员角色或某种定制的精简版本，以便他们能够使用单一登录访问任何 *.domain.com 子站点的后台。否则，默认行为是用户需要在每个子站点 sub1.domain.com、sub2.domain.com 等上拥有角色才能访问后台。
更多上下文会有助于理解您所说的“当用户在每个单独的域上登录时，用户后端会如何显示”的含义。
后端将看起来像一个管理员仪表板，其中的选项由其在该（子）站点上的权限确定，除非他们是超级管理员，那么它应该是一个相当一致的视图。
默认情况下，后端显示将由当前域/子域上公开的主题/插件选项确定。
您始终可以创建一个插件（例如 All-Reciepts-Dash ），为在博客 ID 1（即主域名.com站点）或任何博客上登录的用户呈现统一的后台。
查看WordPress DevHub关于多站点网络管理的文档：https://wordpress.org/documentation/article/multisite-network-administration/
英文:
What you are describing sounds workable with multisite, if I'm understanding right.
You may need to assign users the Super Admin role or some custom pared down version of it in order for them to be able to access the backend of any *.domain.com subsites using a single login. Otherwise, default behavior is that users need to have a role on each sub1.domain.com, sub2.domain.com, etc. in order to access the backend.
It would help to have more context to understand what you mean by "how would the user back end look for each user when they log on each of the individual domains?"
The backend will look like an admin dashboard with whatever options as determined by their capabilities on that (sub)site, unless they are a super admin, then it should be pretty consistent view.
By default, the backend display will be determined by whatever theme/plugin options are exposed on current domain/subdomain.
You could always create a plugin( e.g. All-Reciepts-Dash ) that presents a uniform backend to users logged in on blog id 1( i.e. the main domain.com site ) or any blog.
Check out WordPress DevHub Documentation on Multisite Network Administration https://wordpress.org/documentation/article/multisite-network-administration/
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论