New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Russian (ru_RU) -- <a href="https://translate.wordpress.org/locale/ru/default/wp-plugins/ssl-insecure-content-fixer">the Russian translation team</a> | You have to log in to add a translation. | Details | |
Original untranslated Russian (ru_RU) -- <a href="https://translate.wordpress.org/locale/ru/default/wp-plugins/ssl-insecure-content-fixer">the Russian translation team</a> You have to log in to edit this translation. | |||
| French (fr_FR) -- <a href="https://translate.wordpress.org/locale/fr/default/wp-plugins/ssl-insecure-content-fixer">the French translation team</a> | You have to log in to add a translation. | Details | |
Original untranslated French (fr_FR) -- <a href="https://translate.wordpress.org/locale/fr/default/wp-plugins/ssl-insecure-content-fixer">the French translation team</a> CommentFound in description list item. You have to log in to edit this translation. | |||
| English (en_CA) -- <a href="https://translate.wordpress.org/locale/en-ca/default/wp-plugins/ssl-insecure-content-fixer">the English (Canadian) translation team</a> | You have to log in to add a translation. | Details | |
Original untranslated English (en_CA) -- <a href="https://translate.wordpress.org/locale/en-ca/default/wp-plugins/ssl-insecure-content-fixer">the English (Canadian) translation team</a> CommentFound in description list item. You have to log in to edit this translation. | |||
| If your page can be used outside a web browser, e.g. in emails or other non-web documents, then you should always use a protocol and it should probably be "https:" (since you have an SSL certificate). See <a href="https://ssl.webaware.net.au/cleaning-up-content/">Cleaning up content</a> for more details. | You have to log in to add a translation. | Details | |
Original untranslated If your page can be used outside a web browser, e.g. in emails or other non-web documents, then you should always use a protocol and it should probably be "https:" (since you have an SSL certificate). See <a href="https://ssl.webaware.net.au/cleaning-up-content/">Cleaning up content</a> for more details. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| You probably have a conflict with another plugin that is also trying to fix HTTPS detection. Add this line to your wp-config.php file, above the lines about <code>ABSPATH</code>. You can then change this plugin back to default settings before proceeding. | You have to log in to add a translation. | Details | |
Original untranslated You probably have a conflict with another plugin that is also trying to fix HTTPS detection. Add this line to your wp-config.php file, above the lines about <code>ABSPATH</code>. You can then change this plugin back to default settings before proceeding. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| I changed the HTTPS Detection settings and now I can't login | You have to log in to add a translation. | Details | |
Original untranslated I changed the HTTPS Detection settings and now I can't login CommentFound in faq header. You have to log in to edit this translation. | |||
| Great! Tell me which plugin is yours and how to check for your new version, and I'll drop the "fix" from my next release. | You have to log in to add a translation. | Details | |
Original untranslated Great! Tell me which plugin is yours and how to check for your new version, and I'll drop the "fix" from my next release. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Post about it to <a href="https://wordpress.org/support/plugin/ssl-insecure-content-fixer">the support forum</a>, and be sure to include a link to the page. Posts without working links will probably be ignored. | You have to log in to add a translation. | Details | |
Original untranslated Post about it to <a href="https://wordpress.org/support/plugin/ssl-insecure-content-fixer">the support forum</a>, and be sure to include a link to the page. Posts without working links will probably be ignored. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| You are probably behind a reverse proxy -- see the FAQ above about load balancers / reverse proxies, and run the SSL Tests from the WordPress admin Tools menu. | You have to log in to add a translation. | Details | |
Original untranslated You are probably behind a reverse proxy -- see the FAQ above about load balancers / reverse proxies, and run the SSL Tests from the WordPress admin Tools menu. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| If your website is behind a load balancer or other reverse proxy, and WordPress doesn't know when HTTPS is being used, you will need to select the appropriate <a href="https://ssl.webaware.net.au/https-detection/">HTTPS detection settings</a>. See my blog post, <a href="https://snippets.webaware.com.au/snippets/wordpress-is_ssl-doesnt-work-behind-some-load-balancers/">WordPress is_ssl() doesn’t work behind some load balancers</a>, for some details. | You have to log in to add a translation. | Details | |
Original untranslated If your website is behind a load balancer or other reverse proxy, and WordPress doesn't know when HTTPS is being used, you will need to select the appropriate <a href="https://ssl.webaware.net.au/https-detection/">HTTPS detection settings</a>. See my blog post, <a href="https://snippets.webaware.com.au/snippets/wordpress-is_ssl-doesnt-work-behind-some-load-balancers/">WordPress is_ssl() doesn’t work behind some load balancers</a>, for some details. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| <a href="https://www.whynopadlock.com/">Why No Padlock?</a> has a really good online test tool for diagnosing HTTPS problems. | You have to log in to add a translation. | Details | |
Original untranslated <a href="https://www.whynopadlock.com/">Why No Padlock?</a> has a really good online test tool for diagnosing HTTPS problems. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| NB: after you open your browser's console, refresh your page so that it tries to load the insecure content again and logs warnings to the error console. | You have to log in to add a translation. | Details | |
Original untranslated NB: after you open your browser's console, refresh your page so that it tries to load the insecure content again and logs warnings to the error console. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Look in your web browser's error console. | You have to log in to add a translation. | Details | |
Original untranslated Look in your web browser's error console. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Safari has the <a href="https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html">Error Console</a> | You have to log in to add a translation. | Details | |
Original untranslated Safari has the <a href="https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html">Error Console</a> CommentFound in faq list item. You have to log in to edit this translation. | |||
| Internet Explorer has the <a href="https://msdn.microsoft.com/library/bg182326%28v=vs.85%29">F12 Tools Console</a> | You have to log in to add a translation. | Details | |
Original untranslated Internet Explorer has the <a href="https://msdn.microsoft.com/library/bg182326%28v=vs.85%29">F12 Tools Console</a> CommentFound in faq list item. You have to log in to edit this translation. | |||
Export as
Comment
Found in description list item.