Title: [Plugin: WordPress HTTPS (SSL)] Permalink Last modified: August 20, 2016 --- # [Plugin: WordPress HTTPS (SSL)] Permalink * Resolved [azart](https://wordpress.org/support/users/azart/) * (@azart) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-permalink/) * Hello All, * I set the up the plugin on shared SSL and forced on Admin. * The only issue I have is regarding the Permalink. I use a custom /%postname% * if my public address is [http://mysite.com](http://mysite.com) The shared SSL I have to use is [http://xxx.hostageprovide.com](http://xxx.hostageprovide.com) * So when I write a new post, the permalink get sets to [http://xxx.hostageprovide.com/%postname%](http://xxx.hostageprovide.com/%postname%) * any way the post address could just be set as [http://mysite.com/%postname%](http://mysite.com/%postname%)?? as it is my URI for site and blog in default wordpress settings, Even tho I am using the admin from [http://xxx.hostageprovide.com](http://xxx.hostageprovide.com) * Otherwise plugin seems fab and no other conflicts noticed, I experienced the post editor not working with v 3.12 but it seems fixed with the dev 3.2 * thank you * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/) Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-permalink/#post-2925695) * Enable Force SSL Exclusively (development version) and you should get what you’re looking for. For the record, what you’re seeing in the admin panel isn’t **the** permalink. Either URL will work for the link, depending on your settings. It’s not one or the other unless you’re using Force SSL Exclusively. * Thread Starter [azart](https://wordpress.org/support/users/azart/) * (@azart) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-permalink/#post-2925697) * This is awesome! And I have to say thank you as it seems to work! I’ll let you know if I notice any bugs! * I am not sure what you mean as for the record! When I was in the post editor before Enable Force SSL Exclusively, the slug definitely put my shared SSL address by default I.e.[http://xxx.hostageprovide.com/%postname%](http://xxx.hostageprovide.com/%postname%)( That might have been the point you just made, but not reassuring when you first try it!) * But I have to admit I didn’t test it to see if that would the case (reflect) once published on the public side! (If you want me to test it I can). * Now, I am not the most savyy guy out there 🙂 (maybe a good reason to make it idiot proof) 🙂 * But I initially assumed forcing for admin, would not compromise or influence my public side of the website (non admin side). [http://mysite.com](http://mysite.com) * So maybe you can make it clear somewhere that you need both, forcing for admin( [http://xxx.hostageprovide.com/](http://xxx.hostageprovide.com/)) and Enable Force SSL Exclusively so that it works for your admin and doesn’t conflict with your public side! I hope you understand what I mean! In my own stupid world 🙂 Forcing for admin only concerns the admin side 🙂 * Now that I have done both (There is no confusion), when creating a post, the slug shows as [http://mysite.com/%postname%](http://mysite.com/%postname%) (even tho my admin post edit URL is [http://xxx.hostageprovide.com/wp-admin/post-new.php](http://xxx.hostageprovide.com/wp-admin/post-new.php)) so that it is easy for me to understand it is supposed to be working ( I have also tested it and it works) * If I don’t notice any conflicts i will definitely make a small donation 🙂 Unless I buy SSL! Coz you saved me $50 box 🙂 Many thanks! * To be honest I could set up htaccess ect! (as per wordpress codex, and it would look cleaner but not provide more real security as far as I understand as I am the admin ; this is set up only for admin, and I have set it up myself), But as I don’t have root access to set up a self signed SSl. your plugin really rules and helped me! I don’t mind to have an admin URL that is my shared & Free certificate URL ([http://xxx.hostageprovide.com/](http://xxx.hostageprovide.com/)) , no normal user will be aware about it! (Unless I missed something else, please let me know) Thank you so much! * *for generic users information, my hosting is servage, I chose it a few years back as it was cheap. I lost root access but it served the purpose for a few cheap clients. They shared ssl definitely seems to work with your wonderful plugin. otherwise for consumers interest! I have had a few down time with servage, and my sites hacked with old wordpress versions. But no major problems over the last three years! But yes I have increased the basic wordpress security plugins, directory access and password! Check google for the latest solutions! * Thank you plugin maker! You deserve a few bucks from anyone using your plugin! If you want a tattoo design I’ll do it for free! (Japanese style only). * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-permalink/#post-2925699) * This is new as of 3.2. It will be noted in the FAQ and most likely on the Settings page itself. * The functionality is completely intentional. Many users wish to use admin functionality on the front-end, so when using Shared SSL and Force SSL Administration, links to the front-end are secured unless Force SSL Exclusively is on. This is done this way under the hood so that I don’t have to add more options. There are enough and I don’t want to add more or change them. * I assure you, the URL’s you see in the admin panel in no way reflect reality. The only reason you’re seeing them with your SSL is because the plugin is filtering all occurrences of your HTTP URL in page and post links. Again, this is intentional. * Thread Starter [azart](https://wordpress.org/support/users/azart/) * (@azart) * [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-permalink/#post-2925704) * Thank you! Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘[Plugin: WordPress HTTPS (SSL)] Permalink’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/wordpress-https_bec2c9.svg) * [WordPress HTTPS (SSL)](https://wordpress.org/plugins/wordpress-https/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-https/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-https/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-https/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-https/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-https/reviews/) ## Tags * [permalink](https://wordpress.org/support/topic-tag/permalink/) * 4 replies * 2 participants * Last reply from: [azart](https://wordpress.org/support/users/azart/) * Last activity: [13 years, 10 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-permalink/#post-2925704) * Status: resolved