groups / languages / groups-zh.mo

groups-zh.mo in Groups – Memberships and Access Control 4.7.1, at languages/groups-zh.mo

186 lines 33.0 KB

Raw Download Zip

1	��3� �L��+�,�/�
2	%3GVi}��
3	��O�G YzP�%��3
4	��e�RT3��
5	� �
6	!
7	!)!#H!l!�!�!��">#D#b#{#�#�#@�#D
8	$Q$Kn$
9	�$!�$C�$--%
10	[%sg%;�%&
11	&-&2&
12	D&kQ&�&3�&F
13	'Q'Oe'G�'
14	�'�(�(�(D�(U�(J6)p�)f�)Yn���*
15	��
16	��v�*T+d+s+
17	�+�+�+?�+�+
18	,(,)E,,o,�,�,'�,!�,"-3-\E-�-;�-+�-$.O.�R.>8/�w/ ]0�g0�1�1�1��1db2�2�2�27�2f43�3�3O�3.�34�04�4&�4�4)5-5L5 [5�e5$6D6Z6n6}6N�6G�6�$7g�7?84Y8.�8\�89"919I9BP9
19	�9M�9R�9M@:5�:[�:9 ;Z;t;�;
20	�;�;#�;�; �;�;
21	�;�;
22	<<'<6<J<\<
23	n<
24	{<�<�<D�<G�<9=J=O=
25	T=.b=�=�=�=]�=9G>3�>�>�>!�>d�>MY?�?0�?,@,0@I]@%�@'�@'�@A$HA�mA �A2BCOBG�B�B�BC#C*2C]C1sCw�CDM6D�D~�D�#Er�E�Fx�F5G:G IGrSG�Gf�GYFH
26	�H�HN�H2KMK4VK�K�K�K
27	�K��K^L!oLU�LT�L5<M:rO��O�bPP�PDMQ'�Q�Q�QW�Q7LR\�R�R�R�RS
28	SSS S&S-S22SYeS�S�S
29	�S
30	�S�S�STT'T/T8T$=TbTeT
31	jTuTP}T
32	�U�U�U�UVV$V�>V�V�V W
33	WW
34	/W
35	<WIW_WfW
36	vW
37	�W
38	�W
39	�W
40	�W0�W
41	�W�WX>'XfX
42	X�X��X
43	Y"YS&Y*zY
44	�Z�[�[�[�[ �[�[�[\0\�C\�]�]�]�]�]�]�]-�]0^J^Bd^ �^�^;�^)_0_Z7_6�_�_�_�_
45	�_ �_Q�_G`*Z`-
46	`�`?�`5a{<a �a�a�aB�aLbF`bd�b[
47	chcxc�c�c�c �c�c �c�cd�c
48	6dCd
49	Wd
50	edsd
51	�d4�d�d
52	�d�d�d�d�d�d�deee`ete�e�e�ef�f0�f��f�g��gi&h�h�hu�hZ/i
53	�i
54	�i
55	�i*�iK�i
56	*j
57	7j?Dj*�j�j7�j�j�jkk6k :kDk�Kk�kll
58	*l
59	7l?DlE�l��lNUm�m-�m0�mBn`ngnzn�n>�n�n3�n6oNEo'�oK�o-p6p:pAp
60	HpUphp�p
61	�p�p �p�p�p
62	�p �p
63	�p
64	�p�p �p q
65	q
66	q4,q6aq�q�q�q �q*�q�qr#riAr9�r'�r
67	s!s (sRIs:�s�s!�st9t:Yt�t�t�t�tuhu�u�u0�u<�u#v6vFv\vlv�v�v[�vw<,wiw`wl�wuMxx�xi<y�y�y
68	�yl�y8zYQzP�z
69	�z {�"{&�\| �\|�\|#}}>}U}xe}�}�}K
70	~KW~��~-6��d��?��É$�7�N�He�-��I܂&�?�F�M�T�[�b�f�j�n�u�!{��
71	��
72	��ŃɃ̓
73	у݃�� !�
74	�R*��t3#��)$��y��1 MH%��G��]q��m��
75	�
76	'v1*N��:�
77	j$��/�4.��x'�2h^gU��T��Z�("� ��?��f��<,�� !��pW��(l6��~��i
78	��/-%�}�Y_>39OK�& �7wF2�+�8.��&
79	)��I��k\And[��c�=�J
80	��V-S�{5��
81	#�;��B��0��"�P�u�\|�D
82	��s�+��0o�Ce`��ar,QX@��Lzb�E%s item%s items— No Change —(any)(none)(only unrestricted)--<span title="%s">Access Restrictions</span><sup></sup> For each capability, the groups that have the capability assigned are shown within parenthesis. You can choose a capability by typing part of the group's or the capability's name.A Duck!A minimum set of permissions will be preserved.Access GroupsAccess RestrictionsAccess denied.Access restricionsAccess restrictionsAccess restrictions …AddAdd a new capabilityAdd a new groupAdd capabilityAdd restrictionAdd to groupAdd-OnsAdding the group and capability manually and enabling it for access restrictionAdminister GroupsAdminister Groups plugin optionsAdministrator Access OverrideAdministrators override all access permissions derived from Groups capabilities.Also look for groups related to termsApplyAttachment field labelGroupsBecome a member of the <em>Premium</em> group - this is required so you can choose the <em>premium</em> capability to restrict access to a post.Bulk ActionsBulk edit field labelGroupsBy getting an official extension, you fund the work that is necessary to maintain and improve Groups.CAUTION: If this option is active while the plugin is deactivated, ALL plugin settings and data will be DELETED for <strong>all sites</strong>. If you are going to use this option, now would be a good time to make a backup. By enabling this option you agree to be solely responsible for any loss of data or any other consequences thereof.CAUTION: If this option is active while the plugin is deactivated, ALL plugin settings and data will be DELETED. If you are going to use this option, now would be a good time to make a backup. By enabling this option you agree to be solely responsible for any loss of data or any other consequences thereof.CancelCapabilitiesCapabilities …CapabilityCapability IDChoose access restriction groups …Choose access restrictions …Choose capabilities …Choose groups …Choose one or more capabilities to restrict access. Groups that grant access through the capabilities are shown in parenthesis. If no capabilities are available yet, you can use the quick-create box to create a group and capability enabled for access restriction on the fly.Choose or enter <em>Premium</em> in the <em>Read</em> field located in the <em>Groups</em> box and save or update the post (or hit Enter).ClearClick to add a new capabilityClick to add a new groupClick to refresh capabilitiesColumn headerGroupsColumn header (Users)GroupsContent will be shown to users that are members of these groups:Content will be shown to users that are not members of these groups:Contribute Bitcoin to GroupsCould you please spare a minute and give it a review over at WordPress.org?Current pageDeactivation and data persistenceDelete all Groups plugin data for ALL sites on network deactivationDelete all Groups plugin data on deactivationDescriptionDisabling this setting for a post type also disables existing access restrictions on individual posts of that type.Discover our favorite Extensions for Groups and WooCommerceDismissDocumentationEditEdit a capabilityEdit a groupEdit the post for which you want to restrict access and choose<sup></sup> the <em>premium</em> capability.Efficient User InterfaceEnable legacy access control based on capabilities.Enabling this on production sites is <strong>not</strong> recommended.Enforce read accessEnhanced functionality is available via official %1$sExtensions%2$s for Groups.Enhanced functionality is available via official extensions for Groups.Enter <em>Premium</em> in the quick-create field located in the Access restrictions panel and save or update the post (or hit Enter).Example:FilterFiltersFollow %1$s and visit %2$s to stay tuned for free and premium tools.Go to <strong>Groups > Capabilities</strong> and add the <em>premium</em> capability.Go to <strong>Groups > Groups</strong> and add the <em>Premium</em> group.Go to <strong>Groups > Groups</strong> and assign the <em>premium</em> capability to the <em>Premium</em> group.Go to <strong>Groups > Options</strong> and enable the <em>premium</em> capability to restrict access.Go to the first pageGo to the last pageGo to the next pageGo to the previous pageGroupGroup ActionsGroup IDGroup NameGroupsGroups %s features a simpler model for access restrictions based on groups instead of capabilities used in Groups 1.x.Groups …Groups Add-OnsGroups CapabilitiesGroups MemberGroups Non-memberGroups OptionsGroups is configured to delete its plugin data on deactivation.Groups network optionsGroups optionsGroups section heading (add user)GroupsGroups section heading (edit user)GroupsGroups section heading (user profile)GroupsHelp headingGroupsHelp tab titleGroupsHelp tab title and headingCapabilitiesHelp tab title and headingGroupsHelp tab title and headingOptionsHelp titleGroupsHere you can <strong>add</strong>, <strong>edit</strong> and <strong>remove</strong> groups.Hide content from group membersI have already done that or do not want to submit a review.I want to submit a review later, remind me!I want to submit a review right now!IDIf you had any access restrictions in place based on capabilities, the entries will now be unprotected, unless you enable legacy access restrictions or place appropriate access restrictions based on groups on the desired entries.If you lock yourself out, please ask an administrator to help.If you would like to switch to access restrictions based on groups (recommended) instead of capabilities, you can easily do so by setting the appropriate groups on your protected posts, pages and other entries to restrict access.ImportantIn the same field, you can create a new group and restrict access. Group names are case-sensitive. In order to be able to use the new group, your user account will be assigned to it.Include these capabilities to enforce read access on posts. The selected capabilities will be offered to restrict access to posts.Inherited capabilities:Invalid post ID.It is important to switch to access restrictions based on groups, before support for legacy access control based on capabilities is completely removed.It seems that you have updated from Groups 1.x where access restrictions were based on capabilities.Join the %s groupLeave the %s groupLegacy SettingsLegacy access control based on capabilities is enabled.Let's assume that you want to limit the visibility of a post to members of the <em>Premium</em> group.LoadingLog outManage groups and users with a minimal footprint on the administrative screens.Many thanks for using <strong>Groups</strong>!MediaMembers of the %1$s group can access this %2$s through this capability.Members of the %1$s groups can access this %2$s through this capability.Meta box titleGroupsMore recommended Extensions for GroupsNameNetwork deactivation and data persistenceNetwork menu page titleGroupsNew CapabilityNew GroupNo groups grant access through this capability. To grant access to group members using this capability, you should assign it to a group and enable the capability for access restriction.No new capabilities have been found.No such capabilities.No such capability.No such group.No such groups.Note that you must be a member of a group that has such a capability assigned.Note that you must be a member of a group to use it to restrict access.Now you can protect your posts, pages and any other custom post type like products or events by simply assigning them to one or more groups.Once you have adjusted your access restrictions based on groups, you can disable legacy access control.One capability has been added.%d capabilities have been added.One or more capabilities required to read the entry.One or more groups granting access to entries.Only groups or users that have one of the selected capabilities are allowed to read this %s.OptionsOptions saved.Other recommended ToolsParentPerfect complements to memberships and access control with Groups.PermissionsPlease confirm removal of the following groups. This action cannot be undone.Please confirm to remove the following capabilities. This action cannot be undone.Please give it a <a href="%s">★★★★★</a> rating.Please make sure to read the %1$sMigration Guide%2$s.Please refer to the %s for details on how to switch to and use the new access restrictions.Please use %s for files that require complete protection.Plugin action linkGroupsPlugin action linkOptionsPostPost typesProtect Content EasilyQuick-create group & capabilityReadRead PostRefreshRegisteredRemind me laterRemoveRemove a capabilityRemove a groupRemove capabilitiesRemove capabilityRemove from groupRemove groupRemove groupsRemove restrictionRestrict AccessRestricts the visibility of this %s to members of the chosen groups.Restricts the visibility of this entry to members of the chosen groups.Results per pageRoleSaveSelect GroupsShow access restrictions for these post types.Show content for group membersShow groups in user profiles.Show the Groups tree view.Some post types shown may not offer access restrictions even though they appear enabled here.Support for this deprecated feature will soon be removed.Support the developers and contribute Bitcoin to %sSwitching to Groups %sTermsThank you for using %1$s by %2$s.Thanks for using Groups! We have made it even easier to protect your content and hope you like it :)The <em>%s</em> capability already exists and cannot be assigned to this one.The <em>%s</em> capability already exists.The <em>%s</em> capability could not be updated.The <em>%s</em> capability has been created.The <em>%s</em> capability has been updated.The <em>%s</em> group already exists and cannot be used to name this one.The <em>%s</em> group already exists.The <em>%s</em> group has been created.The <em>%s</em> group has been updated.The <em>Capability</em> must not be empty.The <em>Name</em> must not be empty.The attachment page is restricted to authorized users, but due to technical limitations, the file can still be accessed directly via its URL.The capability has been deleted.The chosen capabilities are assigned to the group.The complete documentation is available on the %s pages for Groups.The following is only of interest if you have upgraded from Groups 1.x:The group has been deleted.The manual way:The name must not be empty.The quick way:The user is a member of the chosen groups.There are no results.These capabilities will be assigned to the group.These permissions apply to Groups management. They do not apply to access permissions derived from Groups capabilities.This could be important!This determines for which post types access restriction settings are offered.This group has no capabilities.This means that if you had access restrictions in place that were based on capabilities, your entries will still be protected.This method is deprecated. You should use Groups_Post_Access_Legacy::get_read_post_capabilities() to retrieve the capabilities instead.To disable, do not define the constant <code>GROUPS_ADMINISTRATOR_OVERRIDE</code> or set it to <code>false</code>.To make it easier to transition to the new model for those who migrate from a previous version, we have included legacy access control based on capabilities.To put it simple, previously you would have used capabilities to restrict access to posts and now you simply use groups.TreeTree of GroupsTree viewTry the quick-create field first. Unless you need a more complex setup, there is no reason to go this way instead.Type and choose …Use the <em>Access restrictions</em> box to limit the visibility of posts, pages and other post types.Use the <em>Groups</em> box to limit the visibility of posts, pages and other post types.User profilesUsing the quick-create fieldUsing the quick-create field, you can create a new group and capability. The capability will be assigned to the group and enabled to enforce read access. Group names are case-sensitive, the name of the capability is the lower-case version of the name of the group. If the group already exists, a new capability is created and assigned to the existing group. If the capability already exists, it will be assigned to the group. If both already exist, the capability is enabled to enforce read access. In order to be able to use the capability, your user account will be assigned to the group.View the Welcome screen for this version of GroupsWarning!We have made it even easier to protect your content!WelcomeWelcome to GroupsWelcome to Groups %sWhat's New?Whether you are new to Groups or have been using it before, please make sure to visit the %1$sDocumentation%2$s pages to know more about how to use it.Yes, here we go!You are a member of the %s group.You are running the system with legacy access control based on capabilities disabled.You are running the system with legacy access control based on capabilities enabled.You can create a new group and capability here. The capability will be assigned to the group and enabled to enforce read access. Group names are case-sensitive, the name of the capability is the lower-case version of the name of the group. If the group already exists, a new capability is created and assigned to the existing group. If the capability already exists, it will be assigned to the group. If both already exist, the capability is enabled to enforce read access. In order to be able to use the capability, your user account will be assigned to the group.You can create a new group by indicating the group's name.You can restrict the visibility of this %1$s to group members. Choose one or more groups that are allowed to read this %2$s. If no groups are chosen, the %3$s is visible to anyone.You can restrict the visibility to group members. Choose one or more groups to restrict access. If no groups are chosen, this entry is visible to anyone.You can select one or more capabilities that are enabled for access restriction.You can select one or more groups to restrict access to its members.You cannot set any access restrictions.You have joined the %s group.You have left the %s group.You must be in a group that has at least one capability enabled to enforce read access.You need to have permission to set access restrictions.You should use Groups_Post_Access_Legacy::create() to pass a capability restriction instead.Your support matters!accessblockblockscontentcontrolfromgroupgroupshidelabel for conjunctive groups filter checkbox∩label title for conjunctive groups filter checkboxUsers must belong to all chosen groupsmembermembersmembershipmembershipsmenu item titleGroupsonlypage-titleGroupspaging%1$s of %2$sprotectrestrictshowtitle of dismiss notice linkDismisstouservisibilityvisibleProject-Id-Version:
83	Report-Msgid-Bugs-To:
84	PO-Revision-Date: 2026-04-25 13:01+0200
85	Last-Translator: itthinx, proaktion
86	Language-Team: Simplified Chinese <itthinx.com>
87	Language: zh_CN
88	MIME-Version: 1.0
89	Content-Type: text/plain; charset=UTF-8
90	Content-Transfer-Encoding: 8bit
91	Plural-Forms: nplurals=1; plural=0;
92	X-Generator: Poedit 3.4.4
93	%s 个项目— 无更改 —(任何)(无)(�
94	未受限制)--<span title="%s">访问限制</span><sup>*</sup> 对于每个权限，显示分�
95	�了该权限的组（以括号显示）。您可以通过输�
96	�组名或权限名的一部分来选择权限。一只鸭子！将保留最低权限集。访问组访问限制拒绝访问。访问限制访问限制访问限制 …添加添加新权限添加新组添加权限添加限制添加到组附加组件手动添加组和权限，并启用访问限制管理 Groups管理 Groups 插件选项管理员访问覆盖管理员覆盖所有从 Groups 权限派生的访问权限。也查找与术语相�
97	�的组应用组成为 <em>Premium</em> 组的成员 - 这是�
98	需的，以便您可以选择 <em>premium</em> 权限来限制对文章的访问。批量操作组通过获取官方扩展，您资助了维护和改进 Groups 所�
99	需的工作。警告：如果此选项在插件停用期间处于激活状态，<strong>所有站点</strong>的所有插件设置和数据将被<strong>删除</strong>。如果您要使用此选项，现在是备份的好时机。启用此选项即表示您同意自行承�
100	任何数据丢失或�
101	�他后果。警告：如果此选项在插件停用期间处于激活状态，所有插件设置和数据将被<strong>删除</strong>。如果您要使用此选项，现在是备份的好时机。启用此选项即表示您同意自行承�
102	任何数据丢失或�
103	�他后果。取消权限权限 …权限权限 ID选择访问限制组 …选择访问限制 …选择权限 …选择组 …选择一个或多个权限以限制访问。通过权限授予访问权限的组显示在括号中。如果尚无可用权限，您可以使用快速创建框即时创建组和权限并启用访问限制。在 <em>Groups</em> 框中的 <em>Read</em> 字段中选择或输�
104	� <em>Premium</em>，然后保存或更新文章（或按 Enter 键）。�
105	除单击添加新权限单击添加新组单击刷新权限组组�
106	容将显示给这些组的成员用户：�
107	容将显示给非这些组成员的用户：向 Groups 捐赠 Bitcoin您能抽出一分钟时间到 WordPress.org 给我们评价吗？当前页停用和数据持�
108	化在网络停用时删除所有站点的 Groups 插件数据停用时删除所有 Groups 插件数据描述为文章类型禁用此设置也会禁用该类型各个文章上现有的访问限制。探索我们为 Groups 和 WooCommerce 推荐的扩展�
109	�闭文档编辑编辑权限编辑组编辑您要限制访问的文章并选择<sup>*</sup> <em>premium</em> 权限。高效用户界面启用基于权限的旧版访问控制。不建议在生产站点上启用此功能。强制读取访问通过 Groups 的官方 %1$s扩展%2$s 可获得增强功能。通过 Groups 的官方扩展可获得增强功能。在访问限制面板的快速创建字段中输�
110	� <em>Premium</em>，然后保存或更新文章（或按 Enter 键）。示例：筛选筛选�
111	�注 %1$s 并访问 %2$s 以获取�
112	�费和付费工�
113	�更新。转到 <strong>Groups > 权限</strong> 并添加 <em>premium</em> 权限。转到 <strong>Groups > 组</strong> 并添加 <em>Premium</em> 组。转到 <strong>Groups > 组</strong> 并将 <em>premium</em> 权限分�
114	�给 <em>Premium</em> 组。转到 <strong>Groups > 选项</strong> 并启用 <em>premium</em> 权限以限制访问。转到第一页转到最后一页转到下一页转到上一页组组操作组 ID组名称GroupsGroups %s 采用更简单的访问限制模型，基于组而不是 Groups 1.x 中使用的权限。组 …Groups 附加组件Groups 权限Groups 成员Groups 非成员Groups 选项Groups �
115	�置为在停用时删除�
116	�插件数据。Groups 网络选项Groups 选项组组组组组权限组选项组您可以在此<strong>添加</strong>、<strong>编辑</strong>和<strong>删除</strong>组。对组成员隐藏�
117	容我已经操作过或不想提交评价。我想稍后提交评价，请提醒我！我现在就想提交评价！ID如果您之前设置了基于权限的访问限制，除非启用旧版访问限制或在所需条目上基于组设置适当的访问限制，否则条目将不再受保护。如果您被锁定，请请求管理员帮助。如果您想切换到基于组的访问限制（推荐），只需在受保护的文章、页面和�
118	�他条目上设置适当的组即可轻松完成。重要在同一个字段中，您可以创建新组并限制访问。组名区分大小写。为了能够使用新组，您的用户账户将被分�
119	�到该组。�
120	含这些权限以强制执行文章的读取访问。所选权限将用于限制对文章的访问。继承的权限：无效的文章 ID。在完�
121	�删除对基于功能的传统访问控制的支持之前，切换到基于组的访问限制非常重要。看起来您是从 Groups 1.x 版本升级而来，该版本的访问限制基于权限。加�
122	� %s 组离开 %s 组旧版设置启用基于功能的传统访问控制。假设您想将文章的可见性限制为 <em>Premium</em> 组的成员。正在加载退出登录在管理界面中以最小的占用空间管理组和用户。感谢您使用 <strong>Groups</strong>！媒体%1$s 组的成员可以通过此权限访问此 %2$s。组更多推荐的 Groups 扩展名称网络停用和数据持�
123	化组新权限新组没有组通过此权限授予访问权限。要使用此权限向组成员授予访问权限，您应将�
124	�分�
125	�给组并启用权限的访问限制功能。未找到新权限。没有这样的能力。无此权限。无此组。无此组。请注意，您�
126	须是已分�
127	�此类权限的组的成员。请注意，您�
128	须是组的成员才能使用它来限制访问。现在，您只需将文章、页面和�
129	�他自定义文章类型（如产品或事件）分�
130	�给一个或多个组即可加以保护。一旦您调整了基于组的访问限制，即可禁用旧版访问控制。已添加 %d 个权限。�
131	读此条目需要一个或多个权限。一个或多个授予条目访问权限的组。只有�
132	�有所选权限之一的组或用户才能�
133	读此 %s。选项选项已保存。�
134	�他推荐工�
135	�父级与群 Groups 的会员资格和访问控制的完美补�
136
137	。权限请确认删除以下组。此操作无法撤销。请确认删除以下权限。此操作无法撤销。请给它一个 <a href="%s">★★★★★</a> 评分。请务�
138	�
139	读 %1$s迁移指南%2$s。有�
140	�如何切换和使用新访问限制的详细信息，请参�
141	%s。请对需要完�
142	�保护的文件使用 %s。组选项文章文章类型轻松保护�
143	容快速创建组和权限读取读取文章刷新已注册稍后提醒我移除移除权限移除组移除权限移除权限从组中移除移除组移除组移除限制限制访问将此 %s 的可见性限制为所选组的成员。将此条目的可见性限制为所选组的成员。每页结果数角色保存选择组显示这些文章类型的访问限制。为组成员显示�
144	容在用户资料中显示组。显示 Groups 树形视图。此处显示的一些文章类型可能不提供访问限制，即使它们在此处显示为已启用。对这一已弃用功能的支持很快就会被删除。支持开发�
145	并为 %s 捐赠 Bitcoin切换到 Groups %s术语感谢您使用 %2$s 的 %1$s。感谢使用 Groups！我们使�
146	�更容易保护您的�
147	容，希望您喜欢 :)权限 <em>%s</em> 已存在，无法分�
148	�给此权限。权限 <em>%s</em> 已存在。无法更新权限 <em>%s</em>。权限 <em>%s</em> 已创建。权限 <em>%s</em> 已更新。组 <em>%s</em> 已存在，不能用作此组的名称。组 <em>%s</em> 已存在。组 <em>%s</em> 已创建。组 <em>%s</em> 已更新。权限不能为空。名称不能为空。附件页面�
149	限授权用户访问，但由于技术限制，文件仍可通过�
150	� URL 直接访问。权限已被删除。所选权限已分�
151	�给组。完整文档可在 Groups 的 %s 页面获取。以下�
152	容�
153	在您从 Groups 1.x 升级时才有�
154	�趣。组已被删除。手动方式：名称不能为空。快速方式：用户是所选组的成员。没有结果。这些权限将分�
155	�给组。这些权限适用于 Groups 管理。不适用于从 Groups 权限派生的访问权限。这可能很重要！这决定了为哪些文章类型提供访问限制设置。此组没有权限。这意味着，如果您设置了基于权限的访问限制，您的条目仍将受到保护。此方法已弃用。您应改用 Groups_Post_Access_Legacy::get_read_post_capabilities() 来检索权限。要禁用，请不要定义常量 <code>GROUPS_ADMINISTRATOR_OVERRIDE</code> 或将�
156	�设置为 <code>false</code>。为了使从以前版本迁移的用户更容易过渡到新模型，我们�
157	含了基于权限的旧版访问控制。简单地说，以前您需要使用权限来限制对文章的访问，现在您只需使用组即可。树形Groups 树形图树形视图首�
158	�尝试快速创建字段。除非您需要更复杂的设置，否则没有理由选择�
159	�他方式。输�
160	�并选择 …使用 <em>访问限制</em> 框限制文章、页面和�
161	�他文章类型的可见性。使用 <em>组</em> 框限制文章、页面和�
162	�他文章类型的可见性。用户资料使用快速创建字段使用快速创建字段，您可以创建新组和权限。权限将分�
163	�给组并启用强制读取访问。组名区分大小写，权限名称是组名的小写版本。如果组已存在，将创建新权限并分�
164	�给现有组。如果权限已存在，它将被分�
165	�给组。如果两�
166	都已存在，则启用权限以强制读取访问。为了能够使用权限，您的用户账户将被分�
167	�到该组。查看此版本 Groups 的欢迎屏幕警告！我们使�
168	�更容易保护您的�
169	容！欢迎欢迎使用 Groups欢迎使用 Groups %s新增功能？无论您是首次使用 Groups 还是之前使用过，请务�
170	访问 %1$s文档%2$s 页面以了解�
171	�使用方法。是的，开始！您是 %s 组的成员。您正在禁用基于权限的旧版访问控制的�
172	况下运行系统。您正在启用基于权限的旧版访问控制的�
173	况下运行系统。您可以在此处创建新组和权限。权限将分�
174	�给组并启用强制读取访问。组名区分大小写，权限名称是组名的小写版本。如果组已存在，将创建新权限并分�
175	�给现有组。如果权限已存在，它将被分�
176	�给组。如果两�
177	都已存在，则启用权限以强制读取访问。为了能够使用权限，您的用户账户将被分�
178	�到该组。您可以通过指定组名来创建新组。您可以将此 %1$s 的可见性限制为组成员。选择一个或多个�
179	�许读取此 %2$s 的组。如果未选择组，则 %3$s 对所有人可见。您可以将可见性限制为组成员。选择一个或多个组以限制访问。如果未选择组，则此条目对所有人可见。您可以选择一个或多个已启用访问限制的权限。您可以选择一个或多个组以限制�
180	�成员的访问权限。您无法设置任何访问限制。您已加�
181	� %s 组。您已离开 %s 组。您�
182	须处于至少启用一个权限以强制读取访问的组中。您需要有权限才能设置访问限制。您应改用 Groups_Post_Access_Legacy::create() 来传递权限限制。您的支持很重要！访问区块区块�
183	容控制从组组隐藏∩用户�
184	须属于所有选定组成员成员成员资格成员资格组�
185	组%1$s / %2$s保护限制显示�
186	�闭到用户可见性可见