HOME

Mini Shell 1.0
DIR:/home/focushimachal.com/www/wp-content/languages/plugins/
Current File : /home/focushimachal.com/www/wp-content/languages/plugins/really-simple-ssl-zh_CN.mo
����
pq@���(&1Xe~.���f�+8QDg!�6� &	AK-kD�
�T�'A^i}��F}�&Ls0z�#��
�		+!?aKi���@%E
kLy��Z�	ISq
��[�S
+^.������>+C�onLo �g�[E �� �k!o"pq"&�">	#[H#(�#�#	�#�#�#9$!:$\$@k$�$�$
�$�$U�$?F%	�%	�%j�%A&jG&�&�&�&E�&'9'2a'�'�'�'?�';�'6(YB(�(�(�(	�(�(�(A�(@)V)LZ*R�*Z�*9U+=�+<�+I
,&T,9{,�,��,W-g-
k-y-�-�-�-�-�-.,.I.b.y.�.$�.P�./	(/2/
7/E/-[/�/�/�/~�/O$0t0�0
�0#�0��0{O1��1)L2Lv2��2,�3��3I�4)5;:5�v5+6
36AA6G�6n�6:7I7OQ7P�7��7��8k
9Fy9�9d�9�E::�:F;
S;&a;[�;`�;9E<!<�<A�<=
=(=?>>]>�>"�>�>"�>?)?C?2a?��?Z~@	�@!�@A=A$SA;xA�A�A�A �A'B?6B
vBN�B�B]�BxGC~�C|?D�D�D'�DE!E9EUEbE$iE�E�EF�E�EF#F8:F2sF�FD�F�FG`G	yG�G�G	�G�GQ�GG(HpH'�H�H�H�H�H�H9I+KI�wI�`JMOK"�KX�KWL�qL�?Mf�Ma2N$�N>�Ni�NbO~O	�O�O�O6�O'�OPDPZPnP{P�PT�P6�P-Q:Q\GQ6�Qa�Q!=R_RoR3�R'�R$�RSSSB*SNmS�SE�ST	(T2TETRThTGzT�T��T<�UC
VDQV2�V5�V-�VH-WvW7�W�W��WqX~X
�X�X�X�X�X�X�XY-YJYcYvY�Y�YN�Y	ZZZ%Z2Z*EZpZ�Z�Zc�Z7�Z,[J[Q[^[sz[r�[�a\$�\G]�W]&F^�m^E9_(_3�_��_-f`�`6�`9�`la�a�aB�aP�ai0b��bWcEsc!�c]�c{9d�d<�de&eXFe`�e;f!<f^fA|f	�f�f���� �):hpJC�
��aV�0�MdT��+Z��Y1sQ�;O�]"D�|=_r�i'fL3�XK^k
[�>&}#%2@z��A\�j6G�N{�8�$�*�����e�	��mSn��y�B��W�xw.���u�I��`4F���c��,�������l�g��t��q�7(�PR����v?E~!9��<�bo-�����/��H�5U You still have %s tasks open.%s is a singleton class and you cannot create a second instance.%sEnable%s or %sdismiss%s%sMore info%s or %sdismiss%s.htaccess is currently not %swritable%s.301 .htaccess redirect is not enabled.301 Redirect301 SSL redirect enabled301 redirect to https set.301 redirect to https set: .htaccess redirect.A .htaccess redirect is faster and works better with caching. Really Simple SSL detects the redirect code that is most likely to work (99% of websites), but this is not 100%. Make sure you know how to regain access to your site if anything goes wrong!A definition of a siteurl or homeurl was detected in your wp-config.php, but the file is not writable.Activate SSLActivate SSL networkwideActivate SSL per siteActivate SSL per site or install a wildcard certificate to fix this.Activate networkwide to fix this.Add the following lines of code to your wp-config.php.Adding a Content Security PolicyAdding a Permission PolicyAll tasksAlmost ready to migrate to SSL!An SSL certificate was detected on your site.Any questions? See the %sdocumentation%s or the %sWordPress Forum%s.Are you sure?Basic SSL configuration finished! Improve your score with %sReally Simple SSL Pro%s.Beautiful recipes optimized for Google Because the $_SERVER["HTTPS"] variable is not set, your website may experience redirect loops.Because your server does not pass a variable with which WordPress can detect SSL, WordPress may create redirect loops on SSL.Because your site is behind a loadbalancer and is_ssl() returns false, you should add the following line of code to your wp-config.php.Before you enable the htaccess redirect, make sure you know how to %sregain access%s to your site in case of a redirect loop.Before you migrate, please check for: CancelCannot activate SSL due to system configuration.Check againCheck out Really Simple SSL PremiumCheck out Really Simple SSL ProChoose optionCompletedConversion of websites %s percent complete.Conversion of websites completed.Copied!Deactivate, and revert to http. This will remove all changes by the plugin.Deactivate, but stay on SSL.Deactivate, keep httpsDeactivate, revert to httpDeactivating the plugin while keeping SSL will do the following:Dismiss all Really Simple SSL noticesDocumentationDon't forget to change your settings in Google Analytics and Search Console.Don't show againDownload system statusDue to a recent update by WP Engine, we have changed your settings automatically to adapt.ElementorEnable 301 .htaccess redirectEnable 301 redirectEnable SSLEnable WordPress 301 redirectEnable a .htaccess redirect or WordPress redirect in the settings to create a 301 redirect.Enable this option to permanently dismiss all +1 notices in the 'Your progress' tabError occurred when retrieving the webpage.Fire mixed content fixer with different methodGeneralGeneral IssuesGet ready with PRO!Go PRO!Go ahead, activate SSL!HTTP Strict Transport Security is not enabled %s(Read more)%s.HTTP Strict Transport Security was enabled.Hi, Really Simple SSL has kept your site secure for a month now, awesome! If you have a moment, please consider leaving a review on WordPress.org to spread the word. We greatly appreciate it! If you have any questions or feedback, leave us a %smessage%s.Hi, Really Simple SSL has kept your site secure for some time now, awesome! If you have a moment, please consider leaving a review on WordPress.org to spread the word. We greatly appreciate it! If you have any questions or feedback, leave us a %smessage%s.Http references in your .css and .js files: change any http:// into https://HttpOnly Secure cookies not set.If the conversion does not proceed after a few minutes, click %shere%s to force the conversion process.If the setting 'stop editing the .htaccess file' is enabled, you can't change this setting.If this option is set to true, the mixed content fixer will fire on the init hook instead of the template_redirect hook. Only use this option when you experience problems with the mixed content fixer."If you want to customize the Really Simple SSL .htaccess, you need to prevent Really Simple SSL from rewriting it. Enabling this option will do that.Images, stylesheets or scripts from a domain without an SSL certificate: remove them or move to your own serverImages, stylesheets or scripts from a domain without an SSL certificate: remove them or move to your own server.Improve security: Add security headersImprove security: Enable HTTP Strict Transport Security (HSTS)In most cases you need to leave this enabled, to prevent mixed content issues on your site.Information about landing page redirectsInstallInstalledInstructionsInstructions manualIs your site still not secure? Do the extensive site scanLearn more about security headersLeave a reviewLightweight plugin without any setup to make your site SSL proofMajor security issue!Maybe laterMixed ContentMixed content fixerMixed content fixer not enabled. Enable the option to fix mixed content on your site.Mixed content fixer was successfully detected on the front-end.More infoMultisiteNetworkwide activation does not check if a site has an SSL certificate. It just migrates all sites to SSL.New feature! HttpOnly Secure cookies have been set automatically!No 301 redirect is set. Enable the WordPress 301 redirect in the settings to get a 301 permanent redirect.No 301 redirect to SSL enabled.No SSL detectedNo SSL detected.No choice has been made regarding networkwide or per site activation.No recommended redirect rules detected.Not all recommended security headers are installedOnce every minuteOpenOptions saved.Or set your wp-config.php to %swritable%s and reload this page.Or set your wp-config.php to writable and reload this page.Our pluginsPlease upgrade to the latest version to be able use the full functionality of the plugin.Plugin dependency errorPremiumPremium SupportRead moreReally Simple PluginsReally Simple SSLReally Simple SSL 4.0. Learn more about our newest major release.Really Simple SSL ProReally Simple SSL and Really Simple SSL add-ons do not process any personal identifiable information, so the GDPR does not apply to these plugins or usage of these plugins on your website. You can find our privacy policy <a href="%s" target="_blank">here</a>.Really Simple SSL cannot be activated. The plugin requires PHP 5.6 or higherReally Simple SSL cannot be activated. The plugin requires WordPress 4.8 or higherReally Simple SSL detected an SSL certificate, but has not been configured to enforce SSL.Really Simple SSL has converted all your websites to SSL.Really Simple SSL has converted all your websites to non SSL.Really Simple SSL has received no response from the webpage.Really Simple SSL is installed, but no valid SSL certificate is detected.Recommended security headers installedRecommended security headers not enabled (%sRead more%s).Redirect loopsRedirects all requests over HTTP to HTTPS using a PHP 301 redirect. Enable if the .htaccess redirect cannot be used, for example on NGINX servers.Remaining tasksSSLSSL ActivatedSSL Not activatedSSL Status TestSSL configuration finished!SSL is activated network wide.SSL is activated on your site.SSL is activated per site.SSL is enabled networkwide.SSL is enabled on your site.SSL is enabled per site.SSL is not enabled yetSSL is not enabled yet.SSL is not enabled.SSL is not yet enabled on this site.SSL is now activated. Check if your website is secure by following this article.SSL settingsSSL type:SaveSave settingsSecurity Headers TestSelect to enable SSL networkwide or per site.Server type:SettingsSetupSite conversion in progress. Please refresh this page to check if the process has finished. It will proceed in the background.Some things can't be done automatically. Before you migrate, please check for: Stop editing the .htaccess fileSupportSupport forumSystem detection encountered issuesThe %s file is not writable. You can either use the WordPress redirect, add the rules manually, or set the file to %swritable%s.The 'force-deactivate.php' file has to be renamed to .txt. Otherwise your ssl can be deactivated by anyone on the internet.The .htaccess redirect rules selected by this plugin failed in the test. Set manually or dismiss to leave on WordPress redirect.The .htaccess redirect will remain activeThe 301 .htaccess redirect is the fastest and most reliable redirect option.The Really Simple SSL plugin folder in the /wp-content/plugins/ directory has been renamed to %s. This might cause issues when deactivating, or with premium add-ons. To fix this you can rename the Really Simple SSL folder back to the default %s.The WordPress 301 redirect will stop workingThe mixed content fixer could not be detected due to a cURL error: %s. cURL errors are often caused by an outdated version of PHP or cURL and don't affect the front-end of your site. Contact your hosting provider for a fix.The mixed content fixer is active, but was not detected on the frontpage.The mixed content fixer will stop workingThe recommended security headers are detected on your site.This leads to issues when activating SSL networkwide since subdomains will be forced over SSL as well while they don't have a valid certificate.This option is enabled on the network menu.Tips & TricksTo deactivate the plugin correctly, please select if you want to:To ensure all traffic passes through SSL, please enable a 301 redirect.To set the httponly secure cookie settings, your wp-config.php has to be edited, but the file is not writable.Upgrade to proWarningWe strongly recommend to create a %sbackup%s of your site before activating SSLWordPress 301 redirect enabled. We recommend to enable a 301 .htaccess redirect.You can also let the automatic scan of the pro version handle this for you, and get premium support and increased security with HSTS included.You can also let the automatic scan of the pro version handle this for you, and get premium support, increased security with HSTS and more!You have a premium add-on with a version that is not compatible with the >4.0 release of Really Simple SSL.You have set a 301 redirect to SSL. This is important for SEO purposesYou may need to login in again.You run a Multisite installation with subdomains, but your site doesn't have a wildcard certificate.You run a Multisite installation with subfolders, which prevents this plugin from fixing your missing server variable in the wp-config.php.You still have %s task open.You still have %s tasks open.Your .htaccess file does not contain all recommended security headers.Your progressYour site address will remain https://Your site uses Divi. This can require some additional steps before getting the secure lock.Your site uses Elementor. This can require some additional steps before getting the secure lock.Your wp-config.php has to be edited, but is not writable.https://really-simple-plugins.comhttps://really-simple-ssl.comhttps://really-simple-ssl.com/really-simple-ssl-4-a-new-dashboardnetworkwideper sitePO-Revision-Date: 2021-06-16 11:31:30+0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=1; plural=0;
X-Generator: GlotPress/3.0.0-alpha.2
Language: zh_CN
Project-Id-Version: Plugins - Really Simple SSL - Stable (latest release)
您仍有%s个打开任务。%s是一个单例级而你无法新增第二个执行个体。%s启用%s 或者 %s忽略%s%s更多信息%s 或者 %s忽略%s.htaccess 目前不可写。301 .htaccess重定向未启用。301重定向已启用301 SSL重定向301重定向到https设置。301重定向到https设置：.htaccess重定向。.htaccess 重定向更快并且与缓存配合的更好。Really Simple SSL检测最可能有效的重定向代码（99%的网站），但是并非100%。请确保在网站出现 任何问题时，您知道如何重新访问网站！在您的wp-config.php中检测到siteurl或homeurl的定义，但是该文件不可写。激活SSL在整个网络范围内激活SSL启动每站SSL逐一每站开启 SSL或安装一反遮罩凭证来修护。启动广域网路来修复这个。将下列几行代码添加到您的 wp-config.php文件。添加内容安全策略添加允许策略所有任务几乎准备好要迁移到 SSL!在您的网站上检测到SSL证书。有问题？请查看 %s文档%s 或者 %sWordPress 论坛%s。你确定吗?SSL基础设置完成！使用 %sReally Simple SSL Pro%s 获取更佳表现。针对谷歌的优化因为这$_SERVER["HTTPS"] 变数尚未设好，你的网站可能会经历重导向回圈。因为你的伺服器没有通过 WordPress 可以侦测 SSL 的变数，Wordpress 可能在SSL 建立重导向回圈。因为你的网站在负载平衡器的后面及 is_ssl() 返回假， 你应加入接下来的密码行到你wp-config.pho。在启用 htaccess 重定向之前，请确保在出现重定向死循环时您知道如何 %s重获访问%s 您的网站。在升级前，请检查：取消由于系统设置，无法激活SSL。再检查一遍查寻 Really Siomple SSL Premium查看Really Simple SSL Pro选择选项完成网站转换 百分之%s已完成。网站转换完成。已复制！禁用并切换回http。这将移除该插件所做的所有更改。禁用并留在SSL。禁用并保持https禁用，切换回http关闭这挂件同时保留 SSL将会执行接续步骤:取消来自“Really Simple SSL”的所有通知程序文档别忘记更新您的 Google Analytics 和 Webmaster 工具设置。不再显示下载系统状态由于最近的WP Engine更新，我们已经修改了您的设置以自动适应这个更新。Elementor启动301.htaccess导向启用301重定向启动SSL启用WordPress 301重定向启动.htaccess导向或在设定里的WordPress导向以新增一个301导向。启用该选项以彻底忽略 '您的进程' 标签中所有 +1 提示获取网页时发生错误。激活不同方法的混合内容修复一般一般问题进一步了解 Pro 版！看看专业版！动手吧，启动 SSL!未启用 HTTP Strict Transport Security（%spremium%s）HTTP Strict Transport Security 已启用。嗨，你现在已经使用Really Simple SSL一个月了，棒极了！如果您有时间，请考虑在WordPress.org上留下评论来宣传。我们非常感谢！如果您有任何问题或反馈，请给我们留言%s信息%s。嗨，Really Simple SSL已经使您的网站安全了一段时间了，太棒了！ 如果有时间，请考虑在WordPress.org上发表评论以广而告之。 非常感谢！ 如果您有任何疑问或反馈，请和我们%s联络%s。关于 .css 及 .js 文件的 http 参考：将所有的 http:// 替换为 //HttpOnly 安全cookies未设置。如果几分钟后转换仍未进行，请点击%s此处%s以强制执行转换过程。如果启用了 '停止编辑 .htaccess 文件' 设置，您就无法修改该设置。若此选项设置为真， mixed content 修复器会在 init 钩子（而不是 template_redirect 钩子）上运行。除非使用 mixed content 修复器时遇到问题，否则不应使用此选项。如果你要定制Really Simple SSL的.htaccess，你得防止真Really Simple SSL被重写。启动这选项使的.htaccess不被重写。来自没有SSL认证的域的图片、样式或脚本文件：删除它们或者移到您的服务器没有 SSL 凭证的网域图片，样式表或脚本: 删除或搬移它们到你的伺服器。提高安全性：添加安全头部提高安全性：启用 HTTP Strict Transport Security (HSTS)在大部分情况你得将它维持在启动状态，以防止在你网站上有混合内容的问题。关于入口页面重定向安装已安装指示程序使用手册您的网站还安全么？执行扩展的网站扫描了解有关安全标头的详细信息发表评论无需任何设定的轻量级插件来让你的网站有 SSL 证明重大安全问题!也许以后混合内容混合内容修复程序混合内容修复未启用。启用该选项以修复您网站上的混合内容。已成功在前端检测到 mixed content 修复器。更多资料多个网站全网路开启并不会查证网站是否有 SSL 认证。它只是迁移整个站到SSL。新功能！HttpOnly安全cookies已经自动设置！301导向没有被设定。请在设定中取得一301永久导向以启动WordPress 301导向。没有301重定向到SSL启用。未检测到SSL未检测到SSL。未做网络范围或单站激活方面的选择。未检测到推荐的重定向规则。未安装所有推荐的安全头部每分钟一次打开选项已存档或设定你的 wp-config.php 为可写并重新加载此网页。或者将您的 wp-config.php 文件设置为可写，并重载当前页面。我们的插件请升级到最新版本，以便能够使用插件的全部功能。插件依赖项错误专业的优质支援服務阅读更多Really Simple PluginsReally Simple SSLReally Simple SSL 4.0. 了解更多关于最亲的主要版本发布。Really Simple SSL ProReally Simple SSL 和Really Simple SSL 附加组件不会处理任何个人身份信息，因此GDPR不适用于这些插件或在您的网站上使用这些插件。您可以在这里找到我们的<a href="%s" target="_blank">隐私政策</a>。SSL不能真正激活。该插件需要php5.6或更高版本SSL不能真正激活。该插件需要WordPress 4.8或更高版本Really Simple SSL检测到SSL证书，但尚未配置为强制SSL。Really Simple SSL已将所有网站转换为SSL。Really Simple SSL已将所有网站转换为非SSL。Really Simple SSL 未接收到网页响应。安装了非常简单的SSL，但是没有检测到有效的SSL证书。检测到建议的安全标头推荐的安全头部未启用（%s阅读更多%s）。重定向死循环使用PHP 301重定向，将所有HTTP请求重定向至HTTPS。如果.htaccess 重定向无法使用时启用，例如在 NGINX 服务器上。剩余任务SSLSSL 已开启SSL未激活SSL状态测试SSL设置完成！SSL在网络范围内激活。SSL在您的网站激活。SSL单站激活。网络范围内启用了SSL。SSL 已能在你网站使用每个站点启用SSL。SSL仍未能使用SSL尚未启用。SSL未启用。SSL尚未在该网站启用。SSL已经激活。按照这篇文章来检查一下您的网站是否安全。SSL设定SSL类型：存档保存设置测试安全标头选择启动SSL全网路或单一网站。服务器类型：設定Setup正在进行站点转换。请刷新此页以检查进程是否已完成。它将在后台进行。有些无法自动被完成。在迁移前，先查寻:停止编辑 .htaccess 档案支持支持论坛系统侦测碰到的问题%s 文件不可写。您可以使用 WordPress 重定向，手动添加规则，或者设置文件为 %s可写%s。'force-deactivate.php'文件必须重命名为.txt。 否则，互联网上的任何人都可以停用您的ssl。该插件选择的 .htaccess 重定向规则本次测试失败。手动设置或者忽略本提示，继续使用 WordPress 重定向。* .htaccess 重定向会保持开启301 .htaccess 重定向通常是最快且最可靠的重定向方法。/wp-content/plugins/ 目录下的Really Simple SSL 插件文件夹已经改名为 %s。这可能在重新激活或豪华版附加组件时会导致问题。要修复这个，您可以重命名 Really Simple SSL 文件夹为默认的 %s。WordPress 301 重定向将停止工作由于一个 cURL 错误：%s，混合内容修复无法检测。cURL 错误常常是由于旧版的 PHP 或 cURL导致，不会影响到您网站的前端。请联系您的空间服务商寻求修复。混合内容修复已启用，但是无法在前端页面检测到。* mixed content 修复器会停止工作在您的站点上检测到建议的安全标头。这会在启动 SSL 网际网路时导致些问题，因为子网域也会被强制通过 SSL，而且它并没有有效的 SSL 凭证。该选项在网际网路的目录可被启动提示与技巧要正确禁用该插件，请选择您是否希望：为确保所有流量通过SSL，请启用301重定向。要调整httponly安全cookie设置，您的wp-config.php文件需要被编辑，但是该文件不可写。升级至专业版警告强烈建议您在启用 SSL 之前对您的站点进行%s备份%sWordPress 301 重定向已启用。我们建议启用 301 .htaccess 重定向。你也可以让进阶版本的自动扫瞄帮你处理，并取得优质支援及增加保全包括 HSTS.你只能让进阶版本的自动扫瞄帮儗处理这个，以及取得优质支持，用HSTS提高的保全系统以及更多!您有一个高级附加组件，其版本与Really Simple SSL的>4.0版本不兼容。您已为SSL设置了一个301重定向。这对于SEO而言很重要你可能必须再登入一次。透过子网域你执行多重式网站的安装，但是你的网站没有反遮罩凭证。你用子资料夹去执行多站点的安装，会阻止这插件修复你在 wp-config.php 里遗失的伺服器变数。您尚有 %s 个打开任务。您的.htaccess文件不包含所有建议的安全标头。您的进程* 您的网站地址仍会是 https://您的网站使用了Divi。这可能需要额外的设置，才能获得安全防护。您的网站正在使用Elementor。这可能需要额外的设置，才能获得安全防护。你的wp-config.php 必须要编辑，可是并非可写。https://really-simple-plugins.comhttps://really-simple-ssl.comhttps://really-simple-ssl.com/really-simple-ssl-4-a-new-dashboard全网路每单一网站