New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | WordPress HTTPS is intended to be an all-in-one solution to using SSL on WordPress sites. | WordPress HTTPS가 워드프레스의 SSL인증의 올인원 솔루션을 제공합니다. | Details |
Original current
WordPress HTTPS is intended to be an all-in-one solution to using SSL on WordPress sites.
You have to log in to edit this translation. |
|||
| ↑ | WordPress HTTPS (SSL) | WordPress HTTPS (SSL) | Details |
Original current |
|||
| Read the <a href="http://wordpress.org/extend/plugins/wordpress-https/installation/">Installation Guide</a>. If after setting up the plugin you are experiencing issues, please check the <a href="http://wordpress.org/extend/plugins/wordpress-https/faq/">FAQ</a>. If you are still unable to resolve your issue, <a href="http://wordpress.org/support/plugin/wordpress-https">start a support topic</a> and someone from the community may be able to assist you. If you need immediate assistance, I am available for hire. Unfortunately, I do not have time to support the plugin for free. | <a href="http://wordpress.org/extend/plugins/wordpress-https/installation/">설치 안내</a>를 읽으십시오. 플러그인을 설정한 후에 문제가 있다면, <a href="http://wordpress.org/extend/plugins/wordpress-https/faq/">자주 묻는 질문(영어)</a>를 확인하시기 바랍니다. 그럼에도 문제가 해결되지 않는다면, <a href="http://wordpress.org/support/plugin/wordpress-https">지원 주제를 시작</a>하면 커뮤니티에서 도울 수 있는 사람이 있을 것입니다. 즉각적인 도움이 필요하다면, 의뢰하실 수 있습니다. 불행히도, 무료로 지원해 드릴 수 없습니다. | Details | |
Original current
Read the <a href="http://wordpress.org/extend/plugins/wordpress-https/installation/">Installation Guide</a>. If after setting up the plugin you are experiencing issues, please check the <a href="http://wordpress.org/extend/plugins/wordpress-https/faq/">FAQ</a>. If you are still unable to resolve your issue, <a href="http://wordpress.org/support/plugin/wordpress-https">start a support topic</a> and someone from the community may be able to assist you. If you need immediate assistance, I am available for hire. Unfortunately, I do not have time to support the plugin for free.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| If your SSL needs are simple, there are many fantastic, light-weight alternatives to WordPress HTTPS such as:↵ <a href="https://wordpress.org/plugins/really-simple-ssl/">Really Simple SSL</a> (great for securing the entire site)↵ <a href="https://wordpress.org/plugins/ssl-insecure-content-fixer/">SSL Insecure Content Fixer</a> (great at fixing most insecure content errors) | WordPress HTTPS와 같은 간단하면서도 이상적인 SSL을 찾으신다면 다음의 항목이 대안이 될 수 있습니다: <a href="https://wordpress.org/plugins/really-simple-ssl/">Really Simple SSL</a> (사이트 보안에 우수) <a href="https://wordpress.org/plugins/ssl-insecure-content-fixer/">SSL Insecure Content Fixer</a> (컨텐츠 에러대응에 좋음) | Details | |
Original current
If your SSL needs are simple, there are many fantastic, light-weight alternatives to WordPress HTTPS such as:↵
<a href="https://wordpress.org/plugins/really-simple-ssl/">Really Simple SSL</a> (great for securing the entire site)↵
<a href="https://wordpress.org/plugins/ssl-insecure-content-fixer/">SSL Insecure Content Fixer</a> (great at fixing most insecure content errors)
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| WordPress HTTPS is intended to be an all-in-one solution to using SSL on WordPress sites. WordPress HTTPS is well-known for being the "heavy-hitter" of SSL plugins. The latest release focuses on speed and performance. | You have to log in to add a translation. | Details | |
Original untranslated
WordPress HTTPS is intended to be an all-in-one solution to using SSL on WordPress sites. WordPress HTTPS is well-known for being the "heavy-hitter" of SSL plugins. The latest release focuses on speed and performance.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Issue Tracker at <a href="https://github.com/mvied/wordpress-https/issues">https://github.com/mvied/wordpress-https/issues</a> | 이슈 참조 <a href="https://github.com/mvied/wordpress-https/issues">https://github.com/mvied/wordpress-https/issues</a> | Details | |
Original current
Issue Tracker at <a href="https://github.com/mvied/wordpress-https/issues">https://github.com/mvied/wordpress-https/issues</a>
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| You can also use this filter to filter pages based on their URL. Let's say you have an E-commerce site and all of your E-commerce URL's contain 'store'.↵ function store_force_ssl( $force_ssl, $post_id = 0, $url = '' ) {↵ if ( strpos($url, 'store') !== false ) {↵ $force_ssl = true;↵ }↵ return $force_ssl;↵ } | You have to log in to add a translation. | Details | |
Original untranslated
You can also use this filter to filter pages based on their URL. Let's say you have an E-commerce site and all of your E-commerce URL's contain 'store'.↵
function store_force_ssl( $force_ssl, $post_id = 0, $url = '' ) {↵
if ( strpos($url, 'store') !== false ) {↵
$force_ssl = true;↵
}↵
return $force_ssl;↵
}
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes! Here is an example of how to use the 'force_ssl' filter to force a page to be secure.↵ function custom_force_ssl( $force_ssl, $post_id = 0, $url = '' ) {↵ if ( $post_id == 5 ) {↵ $force_ssl = true;↵ }↵ return $force_ssl;↵ } | You have to log in to add a translation. | Details | |
Original untranslated
Yes! Here is an example of how to use the 'force_ssl' filter to force a page to be secure.↵
function custom_force_ssl( $force_ssl, $post_id = 0, $url = '' ) {↵
if ( $post_id == 5 ) {↵
$force_ssl = true;↵
}↵
return $force_ssl;↵
}
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The plugin adds a meta box to the add/edit post screen entitled HTTPS. In that meta box, a checkbox for 'Secure Post' has been added to make this process easy. See Screenshots if you're having a hard time finding it.↵ Alternatively, you can use URL Filters to secure post and pages by their permalink. | You have to log in to add a translation. | Details | |
Original untranslated
The plugin adds a meta box to the add/edit post screen entitled HTTPS. In that meta box, a checkbox for 'Secure Post' has been added to make this process easy. See Screenshots if you're having a hard time finding it.↵
Alternatively, you can use URL Filters to secure post and pages by their permalink.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| To make your entire website secure, you simply need to change your site url to use HTTPS instead of HTTP. Please read <a href="http://codex.wordpress.org/Changing_The_Site_URL">how to change the site url</a>.↵ Alternatively, you can use URL Filters in the WordPress HTTPS Settings to secure your entire site by putting just '/' as a filter. This will cause any URL with a forward slash to be secure (all of them). | You have to log in to add a translation. | Details | |
Original untranslated
To make your entire website secure, you simply need to change your site url to use HTTPS instead of HTTP. Please read <a href="http://codex.wordpress.org/Changing_The_Site_URL">how to change the site url</a>.↵
Alternatively, you can use URL Filters in the WordPress HTTPS Settings to secure your entire site by putting just '/' as a filter. This will cause any URL with a forward slash to be secure (all of them).
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Installation Instructions | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Contribute Translations at <a href="https://translate.wordpress.org/projects/wp-plugins/wordpress-https">https://translate.wordpress.org/projects/wp-plugins/wordpress-https</a> | You have to log in to add a translation. | Details | |
Original untranslated
Contribute Translations at <a href="https://translate.wordpress.org/projects/wp-plugins/wordpress-https">https://translate.wordpress.org/projects/wp-plugins/wordpress-https</a>
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| This is most commonly due to PHP's memory limit being too low. Check your Apache error logs just to be sure. Talk to your hosting provider about increading PHP's memory limit. | You have to log in to add a translation. | Details | |
Original untranslated
This is most commonly due to PHP's memory limit being too low. Check your Apache error logs just to be sure. Talk to your hosting provider about increading PHP's memory limit.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you're using a public/shared SSL, try disabling your custom permalink structure. Some public/shared SSL's have issues with WordPress' permalinks because of the way they are configured. If you continue to recieve 404 errors, there may be no way to use WordPress with that particular public/shared SSL. | You have to log in to add a translation. | Details | |
Original untranslated
If you're using a public/shared SSL, try disabling your custom permalink structure. Some public/shared SSL's have issues with WordPress' permalinks because of the way they are configured. If you continue to recieve 404 errors, there may be no way to use WordPress with that particular public/shared SSL.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For many users this behavior is desirable. If you would like links the the front-end of your site to be HTTP, enable Force SSL Exclusively and do not secure your front-end pages. | You have to log in to add a translation. | Details | |
Original untranslated
For many users this behavior is desirable. If you would like links the the front-end of your site to be HTTP, enable Force SSL Exclusively and do not secure your front-end pages.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.