Plugins - WP Remote Users Sync - Development (trunk) - en to zh_CN translation catalogue (315 entries)

en: Silent redirection is faster, but if many Remote Sites need to be contacted at login, the end user does not get any information as to why the current operation is taking time.
zh_CN: 静默重定向速度更快，但如果在登录时需要联系许多远程站点，最终用户将无法获得有关当前操作为何需要时间的任何信息。

en: Displaying a message makes the redirection take a longer time, but it provides information to the end user for a better user experience. Recommended to check this option if only few Remote Sites are contacted during login.
zh_CN: 显示消息会使重定向花费更长的时间，但它会向最终用户提供信息以获得更好的用户体验。如果在登录期间仅联系少数远程站点，建议选中此选项。

en: If checked, strict redirects will be done silently without message displayed to the end user.
zh_CN: 如果选中，严格重定向将静默完成，不会向最终用户显示消息。

en: Use Silent Redirection
zh_CN: 使用静默重定向

en: Invalid parameters
zh_CN: 无效的参数

en: Browser Support
zh_CN: 浏览器支持

en: Processing...
zh_CN: 正在处理...

en: If not empty, only the users corresponding to the specified usernames will be included at export.
zh_CN: 以逗号分隔的用户名列表。 如果不为空，则在导出时将仅包括与指定用户名相对应的用户。

en: Specified Users Only
zh_CN: 仅指定用户

en: If checked and if the connected remote sites are on different top level domains, Login and Logout User Action in Safari and browsers on iOS devices will not work unless users have manually accepted cross-site cookie tracking in their browser settings.
zh_CN: 如果选中并且连接的远程站点位于不同的顶级域中，则 Safari 中的登录和注销用户操作以及 iOS 设备上的浏览器将无法工作，除非用户在其浏览器设置中手动接受跨站点 cookie 跟踪。

en: Force Disable Login Redirects & Logout Everywhere
zh_CN: 强制禁用登录重定向和注销无处不在

en: Note: the Login User Action takes a significantly longer time to process when using explicit redirections, particularly if many remote sites are connected.
zh_CN: 注意：使用显式重定向时，登录用户操作需要更长的时间来处理，尤其是在连接了许多远程站点的情况下。

en: Useful to make sure Login and Logout User Actions work in all browsers, even if cross-domain cookies have been manually turned off in the browser's settings.
zh_CN: 有助于确保登录和注销用户操作在所有浏览器中都有效，即使在浏览器设置中手动关闭了跨域 cookie。

en: If checked, all browsers will behave like Safari and browsers on iOS devices.
zh_CN: 如果选中，所有浏览器的行为将与 iOS 设备上的 Safari 和浏览器类似。

en: Force Login Redirects & Logout Everywhere
zh_CN: 强制登录重定向和注销无处不在

en: Because Safari and browsers on iOS devices do not allow cross-domain cookie manipulation by default for privacy reasons, Login User Action in these browsers is done with explicit redirections, and Logout User Action logs out the user in all browsers.
zh_CN: 由于出于隐私原因，iOS 设备上的 Safari 和浏览器默认不允许跨域 cookie 操作，因此这些浏览器中的登录用户操作是通过显式重定向完成的，而注销用户操作会在所有浏览器中注销用户。

en: WARNING: Make sure these settings are the same for all the websites to synchronise.
zh_CN: 警告：确保所有要同步的网站的这些设置都相同。

en: Please also note that unless "Force Login Redirects & Logout Everywhere" is active, or if "Force Disable Login Redirects & Logout Everywhere" options is active in the "Browser Support" section of the "Miscellaneous" tab, Login and Logout User Actions will not work in browsers preventing cross-domain third party cookie manipulation when the connected websites are on different domains.
zh_CN: 另请注意，除非“强制登录重定向和注销无处不在”处于活动状态，或者如果“其他”选项卡的“浏览器支持”部分中的“强制禁用登录重定向和注销无处不在”选项处于活动状态，登录和注销用户操作将当连接的网站位于不同的域时，在浏览器中不起作用，以防止跨域第三方 cookie 操作。

en: Please note that the Login User Action takes a significantly longer time to process when using explicit redirections, particularly if many remote sites are connected.
zh_CN: 请注意，使用显式重定向时，登录用户操作需要更长的时间来处理，尤其是在连接了许多远程站点的情况下。

en: Because these browsers prevent cross-domain third-party cookie manipulation by default, explicit redirections to log in users and destroying all the user sessions when logging out are necessary. With this method, only first-party cookies are manipulated. This is akin to logging in Youtube with a Google account.
zh_CN: 由于这些浏览器默认阻止跨域第三方 cookie 操作，因此需要显式重定向以登录用户并在注销时销毁所有用户会话。使用这种方法，只有第一方 cookie 被操纵。这类似于使用 Google 帐户登录 Youtube。

en: In Safari and iOS browsers, why do I see a "Processing..." message on Login, and why are users logged out everywhere on Logout?
zh_CN: 在 Safari 和 iOS 浏览器中，为什么我会在登录时看到“正在处理...”消息，为什么用户在注销时到处都已注销？

en: Miscellaneous
zh_CN: 杂项

note: translators: %1$s is the url of the endpoint ; %2$s is the action called
en: Ready to redirect to %1$s async URL in %2$s
zh_CN: 准备重定向到 %2$s 中的 %1$s 异步 URL

en: What this means in practice is that if your theme or a third party plugin allows users to login/logout without page reload, WP Remote Users Sync cannot output its code on the page, and without extra change to your website code base, the synchronisation can only happen after the page where the user logged in or logged out is actually reloaded.
zh_CN: 这在实践中意味着，如果您的主题或第三方插件允许用户在不重新加载页面的情况下登录/注销，WP远程用户同步 无法在页面上输出其代码，并且无需额外更改您的网站代码库，同步可以仅在用户登录或注销的页面实际重新加载后才会发生。

en: Login and Logout User Actions need to output some code in the browser to have an effect on the remote website because of the cookies used for authentication.
zh_CN: 由于用于身份验证的cookie，登录和注销用户操作需要在浏览器中输出一些代码才能对远程网站产生影响。

en: Login & Logout are not working
zh_CN: 登录和注销不起作用

en: Save
zh_CN: 保存

en: Settings
zh_CN: 设置

note: translators: %1$s is the WordPress support forum URL, %2$s is the Github URL
en: More help can be found on %1$s for general inquiries and on %2$s for advanced troubleshooting.
zh_CN: 在 %1$s 上可以找到更多帮助以了解一般查询，在 %2$s 上可以找到高级故障排除。

en: Only then should you open a support thread, with as much information as possible, including logs (with critical information obfuscated if necessary).
zh_CN: 只有这样，您才应该打开一条支持线程，其中包含尽可能多的信息，包括日志（必要时将重要信息混淆）。

en: Read the Resolved threads of the support forum - your issue might have already been addressed there
zh_CN: 阅读支持论坛的已解决主题-您的问题可能已在此处解决

en: Activate and check the logs on both local and remote sites when testing (WP Remote Users Sync > Activity Logs > Enable Logs) ; try to find any discrepancies and adjust the settings
zh_CN: 测试时激活并检查本地和远程站点上的日志（WP远程用户同步 > 活动日志 > 启用日志）；尝试找出任何差异并调整设置

en: Visit the permalinks page of each connected site (Settings > Permalinks)
zh_CN: 访问每个已连接站点的永久链接页面（设置 > 永久链接）

note: translators: %1$s is the bold englisg word "exactly" ; %2$s is 'http'; %3$s is 'https'; %4$s is 'home' option key in the database ; %5$s is 'wp_options' table name
en: exactly
zh_CN: 正是

note: translators: %1$s is the bold englisg word "exactly" ; %2$s is 'http'; %3$s is 'https'; %4$s is 'home' option key in the database ; %5$s is 'wp_options' table name
en: The URLs used in settings of WP Remote Users Sync %1$s match the URL in your WordPress settings: the protocol (%2$s vs. %3$s) and the subdomain (www vs. non-www) must be the same across the board. It is also worth checking the %4$s option in the %5$s table of the WordPress databases, because in some cases the content of Settings > General > WordPress Address (URL) gets abusively overwritten by plugins or themes.
zh_CN: WP远程用户同步 %1$s 设置中使用的 URL 与 WordPress 设置中的 URL 匹配：协议（%2$s 与 %3$s）和子域（www 与非 www）在整个木板。还值得检查 WordPress 数据库 %5$s 表中的 %4$s 选项，因为在某些情况下，设置 > 常规 > WordPress 地址 (URL) 的内容会被插件或主题滥用覆盖。

en: Before opening a new thread in the WordPress Support forum, please check the following:
zh_CN: 在 WordPress 支持论坛中打开新主题之前，请检查以下内容：

en: It's not working!
zh_CN: 没用！

note: translators: %s is the error code
en:  - code: %s -
zh_CN:  - 代码: %s -

en: Payload error -
zh_CN: 有效载荷错误 -

en: Import Users
zh_CN: 导入用户

en: Export Users
zh_CN: 导出用户

note: translators: %s is the username
en: Login action - enqueueing asynchronous actions for username "%s"
zh_CN: 登录操作-为用户名“%s”加入异步操作

note: translators: %1$s is the WordPress support forum URL, %2$s is the Github URL
en: the WordPress support forum
zh_CN: WordPress支持论坛

note: translators: %1$s is the url of the script ; %2$s is the action called
en: Added %1$s async URL in %2$s
zh_CN: 已在%2$s中添加%1$s异步网址

en: Unauthorized access (invalid method)
zh_CN: 未经授权的访问（无效方法）

en: On the remote site, please make sure the permalinks are not using the "Plain" option.
zh_CN: 在远程站点上，请确保固定链接未使用“朴素”选项。

note: translators: %1$s is the username, %2$s is the caller
en: Logout action - successfully logged out user "%1$s" from %2$s.
zh_CN: 注销操作-已成功从%2$s注销用户“%1$s”。

note: translators: %1$s is the remote site ; %2$s is the action
en: Token created: site %1$s - action "%2$s"
zh_CN: 已创建令牌：网站%1$s-操作“%2$s”

en: Token
zh_CN: 令牌

en: Asynchronous actions are also potentially more susceptible to failure in case of network issues, such as if the page load is interrupted or the enqueued script call failed in the browser ; this is a necessary trade-off as these actions require authentication cookie manipulations.
zh_CN: 如果出现网络问题，例如页面加载中断或浏览器中的排队脚本调用失败，异步操作也很可能会导致失败。这是必要的权衡，因为这些操作需要身份验证Cookie的操作。

en: Asynchronous actions (Login & Logout by default) are the most costly: the operations themselves are not blocking, but their Action Tokens have to be renewed beforehand each time: true nonces, single-use tokens, are necessary for security reasons when firing actions from the browser.
zh_CN: 异步操作（默认情况下为“登录”和“注销”）代价最高：操作本身并未阻塞，但是每次都必须事先更新其操作令牌：出于安全原因，在浏览器触发操作时必须使用真正的随机数、一次性令牌。

en:  - All communications rely on an authentication token (randomly generated). Asynchronous actions (Login & Logout by default) use a single-use token (true nonce), and synchronous actions use a token valid only for a limited period of time  ; it is recommended to keep the Action Token Validity Duration relatively short (default is 1,800 seconds or 30 minutes, and must be the same duration on all the connected websites).
zh_CN:  -所有通信都依赖于身份验证令牌（随机生成）。异步操作（默认为登录和注销）使用一次性令牌（真正的随机数），而同步操作使用仅在有限时间段内有效的令牌；建议将操作令牌有效期限保持相对较短（默认值为1800秒或30分钟，并且在所有连接的网站上的期限必须相同）。

en: Failed to create the necessary database table(s).
zh_CN: 无法创建必要的数据库表。

en: (No message)
zh_CN: （无信息）

en: Alert
zh_CN: 提醒

en: Warning
zh_CN: 警告

en: Success
zh_CN: 成功

en: Info
zh_CN: 信息

en: Sorry, you are not allowed to access this page.
zh_CN: 抱歉，您无权访问此页面。

en: Logs
zh_CN: 日志

en: IP Whitelist
zh_CN: IP白名单

en: Authentication & Encryption
zh_CN: 身份验证和加密

en: Add Remote Site
zh_CN: 添加远程站点

en: Save Settings
zh_CN: 保存设置

en: Error: the server hung up unexpectedly. Please try to import users in smaller batches.
zh_CN: 错误：服务器意外挂起。请尝试批量导入用户。

en: Error: invalid file. Please use a non-empty file exported with WP Remote Users Sync.
zh_CN: 错误：文件无效。请使用随WP远程用户同步导出的非空文件。

en: Error: invalid file name. Please use a file exported with WP Remote Users Sync.
zh_CN: 错误：无效的文件名。请使用通过WP远程用户同步导出的文件。

en: The Remote Site address must start with "http".
    Ideally, only secure websites (address starting with "https") should be connected together.
zh_CN: 远程站点地址必须以“http”开头。
    理想情况下，应仅将安全网站（地址以“https”开头）连接在一起。

en: An undefined error occured - please visit the permalinks settings page and try again.
zh_CN: 发生未定义的错误-请访问永久链接设置页面，然后重试。

en: Are you sure you want to remove this site? It will only take effect after saving the settings.
zh_CN: 您确定要删除此网站吗？该设置仅在保存设置后生效。

en: WP Remote Users Sync is not ready.
zh_CN: WP远程用户同步尚未准备好。

en: Edit configuration
zh_CN: 编辑配置

en: Missing Authentication Key
zh_CN: 缺少验证密钥

en: Missing Encryption Key
zh_CN: 缺少加密密钥

note: translators: %1$s is the username, %2$s is the line , %3$s is the error
en: Error importing user "%1$s" on line %2$s - %3$s
zh_CN: 在第%2$s-%3$s行中导入用户“%1$s”时出错

note: translators: %s is the line number
en: Found invalid data on line %s
zh_CN: 在第%s行发现无效数据

en: Failed to open the file.
zh_CN: 无法打开文件。

note: translators: %d is the number of errors
en:  - %d error: |  - %d errors:
zh_CN[0]:  - %d 个错误：

note: translators: %d is the number of results
en: Imported %d user | Imported %d users
zh_CN[0]: 已导入%d个用户

en: Make sure the uploaded file is not empty.
zh_CN: 确保上传的文件不为空。

en: A PHP extension stopped the file upload. PHP does not provide a way to ascertain which extension caused the file upload to stop; examining the list of loaded extensions with phpinfo() may help.
zh_CN: 一个PHP扩展程序停止了文件上传。 PHP没有提供一种方法来确定哪个扩展导致文件上传停止。使用phpinfo()检查加载的扩展列表可能会有所帮助。

en: Failed to write file to disk.
zh_CN: 无法将文件写入磁盘。

en: Missing a temporary folder.
zh_CN: 缺少临时文件夹。

en: No file was uploaded.
zh_CN: 没有上传文件。

en: The uploaded file was only partially uploaded.
zh_CN: 上传的文件仅部分上传。

en: The uploaded file exceeds the MAX_FILE_SIZE directive that was specified in the HTML form.
zh_CN: 上载的文件超出了HTML表单中指定的MAX_FILE_SIZE指令。

en: The uploaded file exceeds the upload_max_filesize directive in php.ini.
zh_CN: 上传的文件超过了php.ini中的upload_max_filesize指令限制。

en: Make sure the uploaded file is a zip archive.
zh_CN: 确保上传的文件是zip存档。

en: Something very wrong happened.
zh_CN: 发生了非常错误的事情。

en: Error: the file was not found on the server. Please try exporting again.
zh_CN: 错误：在服务器上找不到文件。请尝试再次导出。

en: Error: unauthorized access - please reload the previous page and try again.
zh_CN: 错误：未经授权的访问-请重新加载上一页，然后重试。

note: translators: %d is the number of results
en: Success: exported %d result | Success: exported %d results
zh_CN[0]: 成功：导出了%d个结果

note: translators: %d is the number of results
en: Warning: export aborted prematurely (%d result) | Warning: export aborted prematurely (%d results)
zh_CN[0]: 警告：导出过早中止（%d结果）

en: Error: Unable to create the export file
zh_CN: 错误：无法创建导出文件

en: Error: unauthorized access - please reload the page and try again.
zh_CN: 错误：未经授权的访问-请重新加载页面，然后重试。

en: Error: WordPress File System experienced an unknown problem.
zh_CN: 错误：WordPress文件系统遇到未知问题。

note: translators: %s is the username
en: Password action - firing action reset for username "%s"
zh_CN: 密码操作-用户名“%s”的触发操作重置

note: translators: %s is the url of the caller
en: Password action failed - incoming password action not enabled for %s
zh_CN: 密码操作失败-未为%s启用传入密码操作

note: translators: %1$s is the username, %2$s is the caller
en: Password action aborted - cannot reset, user "%1$s" from %2$s does not exist locally.
zh_CN: 密码操作已中止-无法重置，%2$s中的用户“%1$s”在本地不存在。

note: translators: %1$s is the username, %2$s is the caller
en: Password action - password successfully reset for user "%1$s" from %2$s.
zh_CN: 密码操作-已成功从%2$s为用户“%1$s”重置密码。

en: Password action failed - received invalid data.
zh_CN: 密码操作失败-接收到无效数据。

note: translators: %s is the username
en: Logout action - enqueueing asynchronous actions for username "%s"
zh_CN: 注销操作-为用户名“%s”加入异步操作

note: translators: %s is the url of the caller
en: Login action failed - incoming login action not enabled for %s
zh_CN: 登录操作失败-未为%s启用传入的登录操作

note: translators: %1$s is the username, %2$s is the caller
en: Login action aborted - user "%1$s" from %2$s does not exist locally.
zh_CN: 登录操作被中止-%2$s中的用户“%1$s”在本地不存在。

note: translators: %1$s is the username, %2$s is the caller
en: Login action - successfully logged in user "%1$s" from %2$s.
zh_CN: 登录操作-已成功从%2$s登录用户“%1$s”。

en: Login action failed - received invalid data.
zh_CN: 登录操作失败-接收到无效数据。

note: translators: %s is the username
en: Delete action - firing action for username "%s"
zh_CN: 删除操作-用户名“%s”的触发操作

note: translators: %s is the url of the caller
en: Delete action failed - incoming delete action not enabled for %s
zh_CN: 删除操作失败-未为%s启用传入的删除操作

note: translators: %1$s is the username, %2$s is the caller
en: Delete action - successfully deleted user "%1$s" from %2$s.
zh_CN: 删除操作-已成功从%2$s中删除用户“%1$s”。

note: translators: %1$s is the username, %2$s is the caller, %3$s is the reassign username
en: Delete action - successfully deleted user "%1$s" from %2$s and reassigned content to %3$s.
zh_CN: 删除操作-成功将用户“%1$s”从%2$s中删除，并将内容重新分配给了%3$s。

note: translators: %1$s is the username, %2$s is the caller, %3$s is the reassign username
en: Delete action - successfully deleted user "%1$s" from %2$s but failed to reassign content to %3$s.
zh_CN: 删除操作-已成功从%2$s中删除用户“%1$s”，但未能将内容重新分配给%3$s。

note: translators: %1$s is the username ; %2$s is the caller
en: Delete action failed - user "%1$s" from %2$s was not found locally.
zh_CN: 删除操作失败-在本地找不到%2$s中的用户“%1$s”。

en: Delete action failed - received invalid data.
zh_CN: 删除操作失败-接收到无效数据。

note: translators: %s is the url of the caller
en: Logout action failed - incoming logout action not enabled for %s
zh_CN: 注销操作失败-未为%s启用传入注销操作

note: translators: %1$s is the username, %2$s is the caller
en: Logout action aborted - user "%1$s" from %2$s was not logged in.
zh_CN: 注销操作已中止-来自%2$s的用户“%1$s”未登录。

note: translators: %1$s is the username, %2$s is the caller
en: Logout action aborted - user "%1$s" from %2$s does not exist locally.
zh_CN: 注销操作已中止-%2$s中的用户“%1$s”在本地不存在。

en: Logout action failed - received invalid data.
zh_CN: 注销操作失败-接收到无效数据。

en: Logout action failed - the user is already logged out.
zh_CN: 注销操作失败-用户已经注销。

note: translators: %s is the url of the caller
en: Failed to renew token for %s
zh_CN: 无法续签%s的令牌

note: translators: %s is the url of the caller
en: Failed to renew token for %s - retrying...
zh_CN: 无法为%s续订令牌-正在重试...

note: translators: %s is the url of the caller
en: Renewing token for %s
zh_CN: 正在续订%s的令牌

en: On the remote site, please make sure the plugin is activated and that the permalinks are up to date by visiting the permalinks settings page.
zh_CN: 在远程站点上，请访问“永久链接设置”页面，以确保插件已激活并且永久链接是最新的。

note: translators: %s is the error code
en: an undefined error occured. Please make sure the address is correct and try again.
zh_CN: 发生未定义的错误。请确保地址正确，然后重试。

en: Error contacting the remote site:
zh_CN: 联系远程站点时出错：

note: translators: %1$s is the sync action name, %2$s is the current site URL, %3$s is the remote IP, %4$s is the direction
en: "%1$s" action is not activated on %2$s with remote IP %3$s (%4$s).
zh_CN: 在具有远程IP%3$s（%4$s）的%2$s上未激活“%1$s”操作。

note: translators: %1$s is the sync action name, %2$s is the remote site URL, %3$s is the remote IP, %4$s is the direction
en: Ping received for deactivated action "%1$s" from %2$s with remote IP %3$s (%4$s)
zh_CN: 从远程IP为%3$s（%4$s）的%2$s取消操作“%1$s”收到的Ping

note: translators: %1$s is the sync action name, %2$s is the current site URL, %3$s is the remote IP, %4$s is the direction
en: Ping success for action "%1$s" from %2$s with remote IP %3$s (%4$s)
zh_CN: 使用远程IP%3$s（%4$s）从%2$s ping操作“%1$s”成功

note: translators: %1$s is the sync action name, %2$s is the remote site URL, %3$s is the remote IP, %4$s is the direction
en: Ping received for activated action "%1$s" from %2$s with remote IP %3$s (%4$s)
zh_CN: 从远程IP为%3$s（%4$s）的%2$s收到针对激活操作“%1$s”的Ping

en: outgoing
zh_CN: 传出

en: incoming
zh_CN: 传入

en: Malformed data - the test request was received but the data could not be extracted.
zh_CN: 数据格式错误-收到测试请求，但无法提取数据。

en: A ping was received but the initiator did not send the proper data.
zh_CN: 收到ping命令，但发起方未发送正确的数据。

en: Mismatch Encryption settings - please make sure the action keys are correctly configured on both sites.
zh_CN: 不匹配的加密设置-请确保在两个站点上正确配置了操作键。

en: A ping was received but the initiator did not use matching encryption and signature action keys
zh_CN: 收到ping命令，但发起方未使用匹配的加密和签名操作密钥

en: The remote website encountered the following error:
zh_CN: 远程网站遇到以下错误：

note: translators: %s is the remote IP address
en: Unauthorized access (invalid remote IP address %s)
zh_CN: 未经授权的访问（无效的远程IP地址%s）

en: Access granted
zh_CN: 登录成功

en: Unauthorized access (invalid token)
zh_CN: 未经授权的访问（无效的令牌）

en: Failed to create token - invalid payload
zh_CN: 无法创建令牌-有效载荷无效

en: Could not decrypt data: invalid bundle.
zh_CN: 无法解密数据：无效的捆绑包。

note: translators: %s is the username
en: Update action - firing action for username "%s"
zh_CN: 更新操作-用户名“%s”的触发操作

note: translators: %s is the url of the caller
en: Update action failed - incoming update action not enabled for %s
zh_CN: 更新操作失败-未为%s启用传入的更新操作

note: translators: %1$s is the username ; %2$s is the caller
en: Update action aborted - performed Create action instead: "%1$s" from %2$s was not found locally.
zh_CN: 更新操作已中止-已执行创建操作：相反，在本地找不到%2$s中的“%1$s”。

note: translators: %1$s is the username, %2$s is the caller
en: Update action - successfully updated user "%1$s" from %2$s.
zh_CN: 更新操作-已成功从%2$s更新用户“%1$s”。

note: translators: %1$s is the error ; %2$s is the username ; %3$s is the caller
en: Update action failed - "%1$s" for user "%2$s" from %3$s.
zh_CN: 更新操作失败-用户“%2$s”的“%1$s”来自%3$s。

note: translators: %1$s is the username ; %2$s is the caller
en: Update action failed - "%1$s" from %2$s does not exist locally and the incoming Create action is not enabled.
zh_CN: 更新操作失败-来自%2$s的“%1$s”在本地不存在，并且未启用传入的“创建”操作。

note: translators: %s is the usernames
en: Metadata action - firing action for username(s) %s
zh_CN: 元数据操作-用户名%s的触发操作

note: translators: %s is the url of the caller
en: Metadata action failed - incoming metadata action not enabled for %s
zh_CN: 元数据操作失败-未为%s启用传入的元数据操作

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Metadata action aborted - metadata %1$s for user "%2$s" from %3$s not accepted
zh_CN: 元数据操作已中止-来自“%3$s”的用户“%2$s”的元数据%1$s

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Metadata action - failed to delete metadata %1$s for user "%2$s" from %3$s
zh_CN: 元数据操作-无法从%3$s中删除用户“%2$s”的元数据%1$s

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Metadata action - failed to update metadata %1$s for user "%2$s" from %3$s
zh_CN: 元数据操作-无法从%3$s更新用户“%2$s”的元数据%1$s

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Metadata action - failed to add metadata %1$s for user "%2$s" from %3$s
zh_CN: 元数据操作-无法为%3$s中的用户“%2$s”添加元数据%1$s

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Metadata action - deleted metadata %1$s for user "%2$s" from %3$s
zh_CN: 元数据操作-已从%3$s中删除用户“%2$s”的元数据%1$s

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Metadata action - updated metadata %1$s for user "%2$s" from %3$s
zh_CN: 元数据操作-已更新%3$s中用户“%2$s”的元数据%1$s

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Metadata action - added metadata %1$s for user "%2$s" from %3$s
zh_CN: 元数据操作-为%3$s中的用户“%2$s”添加了元数据%1$s

note: translators: %s is the username
en: Create action - firing action for username "%s"
zh_CN: 创建操作-为用户名“%s”触发操作

note: translators: %s is the url of the caller
en: Create action failed - incoming create action not enabled for %s
zh_CN: 创建操作失败-未为%s启用传入的创建操作

note: translators: %1$s is the username, %2$s is the caller
en: Create action - successfully created user "%1$s" from %2$s.
zh_CN: 创建操作-已成功从%2$s创建用户“%1$s”。

note: translators: %1$s is the error ; %2$s is the username ; %3$s is the caller
en: Create action failed - "%1$s" for user "%2$s" from %3$s.
zh_CN: 创建操作失败-来自“%3$s”的用户“%2$s”的“%1$s”。

en: Create action failed - received invalid data.
zh_CN: 创建操作失败-接收到无效数据。

note: translators: %s is the url of the caller
en: Role action failed - incoming role action not enabled for %s
zh_CN: 角色操作失败-未为%s启用传入角色操作

note: translators: %1$s is the meta_key, %2$s is the username, %3$s is the caller
en: Role action aborted - role %1$s for user "%2$s" from %3$s not accepted
zh_CN: 角色操作已中止-来自“%3$s”的用户“%2$s”的角色%1$s未被接受

en: Refresh
zh_CN: 刷新

en: Number of log entries to display, and the minimum number of rows to keep in the database during cleanup. Logs are cleaned up automatically every hour. The number indicated in the "Clear All" button is the real current number of rows in the database, and clicking it deletes all of them.
zh_CN: 要显示的日志条目数，以及清理期间数据库中保留的最少行数。日志每小时自动清除一次。 “全部清除”按钮中指示的数字是数据库中当前的实际行数，单击此行将删除所有这些行。

note: translators: %d is the current number of log entries
en: Clear All (%d entries)
zh_CN: 全部删除（%d个条目）

en: Number of Log Entries
zh_CN: 日志条目数

en: Enable Logs
zh_CN: 启用日志

en: Requires a file previously exported with WP Remote Users Sync
zh_CN: 需要先前通过WP远程用户同步导出的文件

en: Import
zh_CN: 导入设置

en: Upload File
zh_CN: 上传文件

en: Users File
zh_CN: 用户文件

en: Download
zh_CN: 下载

en: Export
zh_CN: 导出

en: List of metadata to export (leave empty to export none):
zh_CN: 要导出的元数据列表（留空则不导出）：

en: Export users with their roles
zh_CN: 导出用户及其角色

en: Filter users by role (leave empty to export all users):
zh_CN: 按角色过滤用户（留空以导出所有用户）：

en: Offset results - users are ordered by username by default ; this option is useful when exporting users in batches.
zh_CN: 偏移结果-默认情况下，用户按登录名排序；批量导出用户时，此选项很有用。

en: Offset
zh_CN: 偏移

en: Remark: on sites with a large number of users, it is recommended to export users in multiple batches with the help of the "Offset" option below.
zh_CN: 备注：在具有大量用户的站点上，建议借助下面的“偏移”选项分批导出用户。

en: Maximum number of users to export. Leave at 0 to export all users.
zh_CN: 导出的最大用户数。保留为0以导出所有用户。

en: Max. #
zh_CN: 最大 #

en: Start with adding a Remote Site
zh_CN: 从添加远程站点开始

en: Help
zh_CN: 帮助

en: Activity Logs
zh_CN: 活动日志

en: Import / Export
zh_CN: 导入/导出

en: Security
zh_CN: 安全

en: Remote Sites
zh_CN: 远程站点

en: Leave blank to accept any IP address (not recommended).
zh_CN: 保留空白以接受任何IP地址（不建议）。

en: To find the IP addresses, use the "Test" button on remote sites while Logs are enabled and check the local log results.
zh_CN: 要查找IP地址，请在启用日志后使用远程站点上的“测试”按钮，并检查本地日志结果。

en: Ideally a random string, used to authenticate remote operations data.
zh_CN: 理想情况下，是一个随机字符串，用于认证远程操作数据。

en: Action Signature Key
zh_CN: 操作签名密钥

en: IMPORTANT: For security reasons, keep this value ABSOLUTELY SECRET.
zh_CN: 重要信息：出于安全原因，请绝对保留此值。

en: Ideally a random string, used to encrypt remote operations data.
zh_CN: 理想情况下，是一个随机字符串，用于加密远程操作数据。

en: Action Encryption Key
zh_CN: 操作加密密钥

en: WARNING: Make sure this value is the same for all the websites to synchronise.
zh_CN: 警告：确保要同步的所有网站的此值都相同。

en: Expressed in seconds, the duration after which generated action tokens expire and need to be renewed.
zh_CN: 以秒为单位表示，所生成的动作令牌到期并需要更新的持续时间。

en: Action Token Validity Duration
zh_CN: 动作令牌有效期

en: Help is provided for general enquiries and bug fixes only: feature requests, extra integration or conflict resolution with third-party themes or plugins, and specific setup troubleshooting requests will not be addressed without a fee (transfer method and amount at the discretion of the plugin author).
zh_CN: 仅针对常规查询和错误修复提供帮助：功能请求，与第三方主题或插件的额外集成或冲突解决以及特定的设置疑难解答请求将免费解决（交易方法和金额由插件作者自行决定）。

en: Where to find more help?
zh_CN: 在哪里可以找到更多帮助？

en: User passwords cannot be and are NOT exported.
zh_CN: 用户密码不能也不会被导出。

en: Exported files are not directly accessible by URL: only administrators can access them.
zh_CN: 通过网址不能直接访问导出的文件：只有管理员可以访问它们。

en: Once downloaded, the files are automatically deleted. In case some files were not downloaded and remained on the server, the containing directory is also cleaned daily.
zh_CN: 下载后，文件将自动删除。如果某些文件没有下载并保留在服务器上，则还每天清理包含目录。

en: Import users into the remote site using the file(s) previously exported
zh_CN: 使用先前导出的文件将用户导入远程站点

en: Export batches of users - for example, to export 500 users at a time, Max # is set to 500 and Offset to 0, 500, 1,000, 1,500, 2,000... and the export operation is repeated until there are no more users to export.
zh_CN: 导出一批用户-例如，一次导出500个用户，将“最大数量”设置为500，将“偏移”设置为0、500、1,000、1,500、2,000 ...，并重复导出操作，直到没有更多用户要导出为止。

en: Export users with or without specified metadata
zh_CN: 导出具有或不具有指定元数据的用户

en: Export users with or without their roles
zh_CN: 导出具有或不具有其角色的用户

en: Export users with specified roles
zh_CN: 导出具有指定角色的用户

en: Export all users
zh_CN: 导出所有用户

en: With it, administrators can:
zh_CN: 有了它，管理员可以：

en: WP Remote Users Sync provides its own user import/export tool.
zh_CN: WP远程用户同步提供了自己的用户导入/导出工具。

en: How to export users from this site and import them into a remote site?
zh_CN: 如何从该站点导出用户并将其导入到远程站点？

en: This means that two websites in localhost (behind virtual hosts, for example) can communicate. However, if one of the websites is on localhost and the other is not, token exchange cannot happen and the websites will not be able to communicate.
zh_CN: 这意味着localhost中的两个网站（例如，在虚拟主机后面）可以通信。但是，如果其中一个网站位于本地主机上，而另一个不在本地主机上，则无法进行令牌交换，并且这些网站将无法通信。

en: Yes - as long as the websites can reach each other, WP Remote User Sync will work.
zh_CN: 是的-只要两个网站可以互相访问，WP远程用户同步就可以使用。

en: Can it be tested on localhost first?
zh_CN: 可以先在本地主机上对其进行测试吗？

en: If other actions for this user are fired before that (Login, Logout, Delete, Password, Metadata), nothing will happen, and an action failure log entry will be recorded if the "Enable Logs" box is checked.
zh_CN: 如果在此之前触发了该用户的其他操作（登录、注销、删除、密码、元数据），则不会发生任何事情，并且如果选中了“启用日志”框，则将记录操作失败日志条目。

en: If the incoming Create action is enabled along with the incoming Update action, the user will be synchronised on the remote website upon user update.
zh_CN: 如果启用了传入的“创建”操作以及传入的“更新”操作，则用户更新后，将在远程网站上同步用户。

en: What if the user to synchronise does not exist on the remote site?
zh_CN: 如果远程站点上不存在要同步的用户怎么办？

en: WP Remote User Sync integrates with any plugin updating passwords provided they do so respecting WordPress standards.
zh_CN: WP远程用户同步与任何插件更新密码集成在一起，前提是它们遵守WordPress标准。

en: Passwords are NEVER communicated or stored in plain text.
zh_CN: 密码永远不会以纯文本形式传达或存储。

en: Communications are encrypted, signed, token-validated and IP-validated to make the process as secure as possible.
zh_CN: 通信经过加密、签名、令牌验证和IP验证，以使过程尽可能安全。

en: Passwords are automatically synchronised as long as the Password action is enabled (outgoing and incoming respectively).
zh_CN: 只要启用了密码操作（分别为传出和传入），密码就会自动同步。

en: What about user passwords?
zh_CN: 用户密码呢？

en: To enable extra information synchronisation, the Metadata action is used along with specified metadata keys in the transferred and accepted metadata fields.
zh_CN: 为了实现其他的信息同步，在传输和接受的元数据字段中将“元数据”操作与指定的元数据键一起使用。

en: For example, it means all the address and profile information in WooCommerce can be synchronised, but not the orders status or subscription status.
zh_CN: 例如，这意味着可以同步WooCommerce中的所有地址和个人资料信息，但不能同步订单状态或订阅状态。

en: Extra user information can be synchronised too out of the box as long as they are stored in the user metadata.
zh_CN: 只要其他的用户信息存储在用户元数据中，它们也可以立即进行同步。

en: What about extra user information? (WooCommerce / Ultimate Member / other plugin adding user information)
zh_CN: 其他的用户信息呢？ （WooCommerce / Ultimate Member /其他插件添加用户信息）

en: john_doe56's new synchronised roles on Site 2 are "author" and "shop_manager"
zh_CN: john_doe56在站点2上的新同步角色是“作者”和“shop_manager”

en: "shop_manager" is part of the accepted roles, and is a valid role on Site 2
zh_CN: “shop_manager”是已接受角色的一部分，并且是站点2上的有效角色

en: "administrator" and "custom_role1" are not part of the accepted roles ; was the list of accepted roles left empty to accept all roles, "custom_role1" would not be a valid role on Site 2 and would not be accepted anyway
zh_CN: “administrator”和“custom_role1”不属于公认角色；是保留为空以接受所有角色的已接受角色列表，“custom_role1”在站点2上不是有效角色，无论如何也不会被接受

en: Site 2 receives  "administrator", "shop_manager" and "custom_role1" along with john_doe56's data
zh_CN: 站点2接收“管理员”、“shop_manager”和“custom_role1”以及john_doe56的数据

en: When the user john_doe56 is updated on Site 1, the following happens on Site 2:
zh_CN: 在站点1上更新用户john_doe56时，在站点2上发生以下情况：

en: Both Site 1 and Site 2 have WooCommerce enabled, therefore the role "shop_manager" exists on both sites, but "custom_role1" does not exist on Site 2.
zh_CN: 站点1和站点2都启用了WooCommerce，因此两个站点上都存在角色“shop_manager”，而站点2上不存在“custom_role1”角色。

en: A user john_doe56 with the role "administrator", "shop_manager" and "custom_role1" on Site 1, and "author" on Site 2
zh_CN: 用户john_doe56在站点1上的角色为“管理员”、“shop_manager”和“custom_role1”，在站点2上的角色为“作者”

en: Site 2 with incoming Create, Update and Role actions enabled, with role "shop_manager" in the "List of roles to accept" field, and the "Merge with existing roles" box checked
zh_CN: 启用了传入的“创建、更新和角色操作”的站点2，在“要接受的角色列表”字段中选中了角色“shop_manager”，并选中了“与现有角色合并”框

en: Site 1 with outgoing Create, Update and Role actions enabled, with roles "administrator", "shop_manager" and "custom_role1" in the "List of roles to transfer" field
zh_CN: 启用了传出的“创建、更新和角色”操作的站点1，在“要转移的角色列表”字段中具有角色“管理员”、“shop_manager”和“custom_role1”

en: Consider the following scenario:
zh_CN: 请考虑以下情形：

en: When synchronising, the following role are assigned exclusively to the user and will not be merged: administrator, editor, author, contributor, subscriber. All other roles can be merged upon incoming action if the "Merge with existing roles" box is checked.
zh_CN: 同步时，以下角色专门分配给用户，并且不会合并：管理员、编辑者、作者、贡献者、订阅者。如果选中了“与现有角色合并”框，则所有其他角色都可以在传入操作时合并。

en: Roles can be synchronised when the Create and Update actions are fired, with the Role action enabled, and matching transferred and accepted role settings.
zh_CN: 当创建和更新操作被触发时，角色可以同步，启用角色操作，并匹配传输和接受的角色设置。

en: How are user roles handled when a user is synchronised?
zh_CN: 同步用户时如何处理用户角色？

en: The worse the connection between the remote sites is, the bigger the relatively negative impact on performances.
zh_CN: 远程站点之间的连接越差，对性能的相对负面影响就越大。

en: The more websites are connected, the bigger the relatively negative impact on performances.
zh_CN: 网站的连接越多，对性能的负面影响就越大。

en: The main takeaway is this:
zh_CN: 主要要点是：

en: Overall, performances should be marginally impacted.
zh_CN: 总体而言，性能应受到轻微影响。

en: Performance degradations are mitigated by the fact that Action Tokens (blocking request) are saved for a period of time for synchronous actions, and by the fact that actions are fired ONLY when an operation has been performed on users (not on every page load).
zh_CN: 通过为同步操作保存一段时间的操作令牌（阻止请求）以及仅在对用户执行操作时才触发操作（而不是在每次页面加载时）才触发操作，可以缓解性能下降。

en: An action request (non-blocking: a response is not needed)
zh_CN: 操作请求（不阻塞：不需要响应）

en: A second token renewal request to try again (blocking as well ; token renewal is tried again only once in case the first request failed, with a 5 seconds timeout by default)
zh_CN: 第二个令牌更新请求重试一次（也阻塞；在第一个请求失败的情况下，令牌更新仅重试一次，默认情况下为5秒超时）

en: A token renewal request that fails (blocking: a response is needed to save the token for later user, with a 1 second timeout by default)
zh_CN: 令牌续约请求失败（阻止：需要响应以将令牌保存给以后的用户，默认情况下为1秒超时）

en: In the worst case scenario, three requests are made to EACH remote site when doing synchronisation:
zh_CN: 在最坏的情况下，同步时会向EACH远程站点发出三个请求：

en: This means the impact on performances depends on the response time between the connected websites.
zh_CN: 这意味着对性能的影响取决于所连接网站之间的响应时间。

en: WP Remote Users Sync needs to communicate with the remote sites to actually synchronise users.
zh_CN: WP远程用户同步需要与远程站点进行通信以实际同步用户。

en: What is the impact on performances?
zh_CN: 对性能有什么影响？

en: Despite these strong security measures, administrators use this plugin at their own risk ; the author will not be held liable for any damages resulting from the use of WP Remote Users Sync.
zh_CN: 尽管采取了这些强大的安全措施，管理员仍需自行承担使用此插件的风险。对于因使用WP远程用户同步而造成的任何损失，作者概不负责。

en: It is HIGHLY recommended to only connect https-enabled websites.
zh_CN: 强烈建议仅连接启用了https的网站。

en: It is HIGHLY recommended to use the IP Whitelist setting.
zh_CN: 强烈建议使用IP白名单设置。

en: For all synchronous actions, because they are fired server-side, IP verification can be enabled using the IP Whitelist setting with IP addresses to be compared against the remote IP address.
zh_CN: 对于所有同步操作，由于它们是在服务器端触发的，因此可以使用IP白名单设置启用IP验证，并将IP地址与远程IP地址进行比较。

en:  - IP addresses are verified using the REMOTE_ADDR server environment variable, which cannot be faked (unless the servers or the network infrastructure are already highly compromised, in which case there are bigger issues to worry about).
zh_CN:  -使用REMOTE_ADDR服务器环境变量验证了IP地址，该环境变量不能被伪造（除非服务器或网络基础结构已经受到严重破坏，在这种情况下，您需要担心更大的问题）。

en: IP verification
zh_CN: IP验证

en: Authentication tokens
zh_CN: 认证令牌

en:  - All communications are signed with a hash using the SHA256 algorithm to ensure their integrity ; it is recommended to use a strong, randomly generated Action Signature Key (the same value on all the connected websites).
zh_CN:  -所有通信均使用SHA256算法以散列进行签名，以确保其完整性；建议使用随机生成的功能强大的操作签名密钥（在所有连接的网站上均使用相同的值）。

en: HMAC signature
zh_CN: HMAC签名

en:  - All communications are encrypted using the AES-256-CBC algorithm with a randomly generated Initialisation Vector to ensure their confidentiality ; it is recommended to use a strong, randomly generated Action Encryption Key (the same value on all the connected websites).
zh_CN:  -使用随机生成的初始化矢量，使用AES-256-CBC算法对所有通信进行加密，以确保其机密性；建议使用随机生成的功能强大的操作加密密钥（在所有连接的网站上均使用相同的值）。

en: OpenSSL encryption
zh_CN: OpenSSL加密

en: Multiple layers of security are in place to protect the privacy, integrity and authenticity of communications between connected sites:
zh_CN: 多层安全措施可以保护连接站点之间通信的隐私，完整性和真实性：

en: What security measures are in place?
zh_CN: 有哪些安全措施？

en: For existing user databases in need of immediate synchronisation, WP Remote Users Sync provides its own user import/export tool.
zh_CN: 对于需要立即同步的现有用户数据库，WP远程用户同步提供了自己的用户导入/导出工具。

en: Users existing on one site and not the other will not be synchronised unless the user is actually updated AND both Create and Update actions are enabled on the site where the user does not exist.
zh_CN: 除非实际更新了用户并且在该用户不存在的站点上同时启用了“创建”和“更新”操作，否则不会同步存在于一个站点而非另一个站点上的用户。

en: Existing users remain untouched, until an enabled incoming action is received from a remote site.
zh_CN: 现有用户保持不变，直到从远程站点收到已启用的传入操作。

en: What happens to existing users after activating WP Remote Users Sync?
zh_CN: 激活WP远程用户同步后，现有用户会怎样？

en: This action is particularly useful to synchronise user data added by plugins (such as address information in WooCommerce).
zh_CN: 此操作对于同步插件添加的用户数据（例如WooCommerce中的地址信息）特别有用。

en:  - Fired when one or several user metadata are added / created / deleted, depending on specified transferred outgoing and accepted incoming metadata keys.
zh_CN:  -根据指定的传输传出和接受的传入元数据密钥，添加/创建/删除一个或多个用户元数据时触发。

en: Metadata
zh_CN: 元数据

en: If the incoming roles do not exist on or are not accepted by the remote site, they are ignored.
zh_CN: 如果传入角色在远程站点上不存在或未被远程站点接受，则将忽略它们。

en: Unless the "Merge with existing roles" option is selected, the roles of the user are replaced with incoming roles.
zh_CN: 除非选择“与现有角色合并”选项，否则用户角色将替换为传入角色。

en:  - Does not fire an action of its own per se ; this action determines whether roles should be synchronised or ignored during Create and Update actions, depending on specified transferred outgoing and accepted incoming roles.
zh_CN:  -本身不采取行动;此操作确定在创建和更新操作期间应同步还是忽略角色，具体取决于指定的已转移传出角色和接受的传入角色。

en: Roles
zh_CN: 角色

en: This action also determines whether the passwords are synchronised or should be ignored during Create and Update actions.
zh_CN: 此操作还确定在创建和更新操作期间密码是同步的还是应忽略。

en:  - Fired when a user resets their password. The expected result is the password being reset for the user on all registered remote sites accepting incoming Password actions.
zh_CN:  -当用户重置密码时触发。预期结果是在所有接受传入密码操作的注册远程站点上为用户重置密码。

en: Password
zh_CN: 密码

en:  - Fired when a user is deleted. The expected result is the user being deleted on all registered remote sites accepting incoming Delete actions.
zh_CN:  -删除用户时触发。预期结果是在接受传入的删除操作的所有注册远程站点上删除用户。

en: Delete
zh_CN: 删除

en: If the user does not exist on the remote site and the incoming Create action is enabled, a synchronised user is created instead.
zh_CN: 如果远程站点上不存在该用户，并且启用了传入的“创建”操作，则会创建一个同步的用户。

en:  - Fired when a user is updated, either by the user themselves or another user. The expected result is up to date and synchronised user information on all registered remote sites accepting incoming Update actions (see Password, Roles and Metadata below for caveats).
zh_CN:  -由用户自己或另一个用户更新用户时触发。预期结果是最新的，并且在接受传入的更新操作的所有已注册远程站点上同步了用户信息（有关警告，请参阅下面的密码、角色和元数据）。

en: Update
zh_CN: 更新

en:  - Fired when a user is created. The expected result is a synchronised user created on all registered remote sites accepting incoming Create actions (see Password, Roles and Metadata below for caveats).
zh_CN:  -创建用户时触发。预期结果是在所有接受注册的远程站点上创建的同步用户上，该用户接受传入的创建操作（有关警告，请参见下面的密码、角色和元数据）。

en: Create
zh_CN: 创建

en: The page needs to load without interruption and the network between the user and the remote sites be accessible for it to take effect, because this operation relies on browser cookies (the action is fired by a script asynchronously in the footer of the page after logout).
zh_CN: 该页面需要不间断地加载，并且可以访问用户和远程站点之间的网络才能使其生效，因为此操作依赖于浏览器cookie（注销后页面脚注中的脚本会异步触发该操作） 。

en:  - Fired when a user logs out. The expected result is a user logged out on all registered remote sites accepting incoming Logout actions.
zh_CN:  -用户注销时触发。预期结果是用户在所有注册的远程站点上注销，接受传入的注销操作。

en: Logout
zh_CN: 注销

en: The page needs to load without interruption and the network between the user and the remote sites be accessible for it to take effect, because this operation relies on browser cookies (the action is fired by a script asynchronously in the footer of the page after login).
zh_CN: 该页面需要不间断地加载，并且可以访问用户和远程站点之间的网络才能使其生效，因为此操作依赖于浏览器Cookie（此操作由登录后页面页脚中的脚本异步触发） 。

en:  - Fired when a user logs in. The expected result is a user logged in on all registered remote sites accepting incoming Login actions.
zh_CN:  -当用户登录时触发。预期结果是用户在所有接受远程登录操作的注册远程站点上登录。

en: Login
zh_CN: 登录

en: List of supported actions by default:
zh_CN: 默认情况下支持的操作列表：

en: There is no "Master Website": each site is working independently, firing and receiving actions depending on each site's configuration.
zh_CN: 没有“主网站”：每个站点都在独立工作，并根据每个站点的配置触发和接收操作。

en: WP Remote Users Sync "listens" to changes related to WordPress users, and fires outgoing "actions" to registered remote sites. The registered remote sites with WP Remote Users Sync installed then catch incoming actions and react accordingly.
zh_CN: WP远程用户同步“侦听”与WordPress用户相关的更改，并将传出的“操作”触发到已注册的远程站点。安装了WP远程用户同步的注册远程站点然后捕获传入的操作并做出相应的反应。

en: How does it work?
zh_CN: 它是如何工作的？

en: Add
zh_CN: 添加

en: WARNING: this option can potentially open the website and its assciated connected sites to malicious operations. This is to be used ONLY in case of advanced maintenance that would invalidate server information on the remote site, such as prior to using the WP-CLI tool to manipulate user data.
zh_CN: 警告：此选项可能会打开该网站及其相关连接的站点以进行恶意操作。仅在高级维护会导致远程站点上的服务器信息无效的情况下才使用此方法，例如在使用WP-CLI工具操作用户数据之前。

en: Disable checking the origin of the actions received by the current site before synchronising.
zh_CN: 同步之前，请禁用检查当前站点接收到的操作的来源。

en: Allow Anonymous Sync Operations
zh_CN: 允许匿名同步操作

en: Used by the remote sites to determine the origin of incoming actions. Leave empty if the server IP address is not altered before reaching the remote sites.
zh_CN: 远程站点用来确定传入操作的来源。如果在到达远程站点之前服务器IP地址没有更改，请留空。

en: The IP address the current site exposes to the internet.
zh_CN: 当前站点公开到互联网的IP地址。

en: Proxy IP Address
zh_CN: 代理IP地址

en: Remove site configuration
zh_CN: 删除站点配置

en: Merge with existing roles
zh_CN: 与现有角色合并

en: List of roles to accept (leave empty to accept all):
zh_CN: 要接受的角色列表（留空以接受所有角色）：

en: List of metadata to accept (leave empty to accept all):
zh_CN: 要接受的元数据列表（留空以接受全部）：

en: Synchronise user data for actions happening on the remote site, received by the current site.
zh_CN: 为当前站点接收到的远程站点上发生的操作同步用户数据。

en: Incoming Actions
zh_CN: 传入操作

en: List of roles to transfer (leave empty to transfer none):
zh_CN: 要传输的角色列表（留空则不传输）：

en: List of metadata to transfer (leave empty to transfer none):
zh_CN: 要传输的元数据列表（留空则不传输）：

en: Test
zh_CN: 测试

en: Synchronise user data for actions happening on the current site, sent to the remote site.
zh_CN: 为当前站点上发生的操作同步用户数据，并将其发送到远程站点。

en: Outgoing Actions
zh_CN: 传出操作

note: Description of the plugin
en: Synchronise WordPress Users across Multiple Sites.
zh_CN: 跨多个站点同步WordPress用户。

note: Plugin Name of the plugin
en: WP Remote Users Sync
zh_CN: WP远程用户同步
