Title: Switched to HTTPS – does not work anymore
Last modified: July 2, 2017

---

# Switched to HTTPS – does not work anymore

 *  [hgassner](https://wordpress.org/support/users/hgassner/)
 * (@hgassner)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/)
 * Hi,
 * after switching my site from http to https adpative images does not work anymore–
   no images are displayed after activation. Deactivating adapative images my images
   are shown again. Do not know if this is relevant: I’m using Lets Encypt.
 * Do you have any hint what can be wrong / a solution after switching to https?
 * Thanx in advance
    Horst

Viewing 13 replies - 1 through 13 (of 13 total)

 *  Plugin Author [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * (@nevma)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9281419)
 * Hello, my friend,
 * I think this is a classic problem these days, because HTTPS is becoming more 
   and more a standard for websites.
 * Can you check if the urls in your admin Settings > General page do contain the“
   https” instead of “http”? They should contain the “https” and (sorry about this
   inconvenience) you need to update your Adaptive Images settings one more time
   after this.
 * Also, for a proper and complete migration from HTTP to HTTPS, I would advice 
   performing a url rewrite in your database, which will replace each and every 
   url of your domain from “http” to “https”.
 * Let me know how this works out for you.
 * Cheers,
    Takis
 *  [gklauda](https://wordpress.org/support/users/gklauda/)
 * (@gklauda)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9293985)
 * Hello Takis,
 * I had the same problem with https and I broke the problem down to the line:
 * `$wp_content_url = 'http://' . $_SERVER['HTTP_HOST'] . '/wp-content';`
 * in adaptive-images-script.php. To fix it I replaced it with:
 * `$ssl = ( ! empty( $_SERVER['HTTPS'] ) && $_SERVER['HTTPS'] == 'on' );`
    `$wp_content_url
   = 'http'. ($ssl ? 's' : '' ) . '://' . $_SERVER['HTTP_HOST'] . '/wp-content';`
 * It would be wonderful if you considered this fix for a future commit.
 * With best regards,
    George
 *  Plugin Author [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * (@nevma)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9294030)
 * Hello, my friend [@gklauda](https://wordpress.org/support/users/gklauda/),
 * Thank you for sharing your solution with us!
 * The thing is that your code is perfectly correct, but it only covers the standard
   cases where the `/wp-content` folder lies exactly where it is expected and with
   the name it is expected to have. There are many other cases where one may have
   changed the path or the name (or even both) of the `/wp-content` folder. For 
   this reason and because of the added factor that we have chosen to not load the
   whole of WordPress environment on image requests, it is difficult to determine
   the images path for all cases in a uniform manner. To be frank, it is quite a
   pain!
 * However, we are always on the lookout for a better solution and we love to hear
   your feedback and ideas.
 * Cheers,
    Takis
 *  [gklauda](https://wordpress.org/support/users/gklauda/)
 * (@gklauda)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9294198)
 * Hi Takis,
 * well, this is an altogether different problem.
 * If somebody decides to move his `/wp-content` folder, I think this goes by defining
   the WP_CONTENT_DIR and WP_CONTENT_URL constants in the `wp-config.php`. So for
   your plugin to work properly in such a scenario, it would have to check if these
   constants are set and, if this being the case, use them instead:
 *  [http://hookr.io/constants/wp_content_url/](http://hookr.io/constants/wp_content_url/)
 * Cheers,
    Georg
 *  Plugin Author [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * (@nevma)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9294740)
 * Hello, George,
 * Well, you are right so far, but there are two more tiny details that made the
   difference:
 * 1. When our plugin is invoked in order to serve adaptive images we have chosen
   to not load the WordPress environment so that these request can be as lightweight
   as possible. So, for one thing, we need to be setting the information about the
   actual location of `/wp-content` in some place “outside” WordPress (we use a 
   special PHP config file for this, located inside our plugin directory.
 * 2. We need to be able to translate image url requests like `http://www.mysite.
   com/wp-content/uploads/2017/07/myimage.jpg` to their original paths in the server
   which, having renamed or moved the `wp-content` folder, may result into something
   like `/home/mysite.com/public_html/new-wp-content/uploads/2017/07/myimage.jpg`.
   Having to do this for all possible cases has proven to be quite tricky so far.
 * (What also adds to the complexity is that the `/wp-content` folder may have been
   simply renamed or moved or both and the WordPress itself may be lying inside 
   a subdirectory of the root domain or it may be lying virtually in a subdirectory
   of the server root.)
 * However, I will give it another thought, as you may be right after all and perhaps
   this bit of code needn’t be so complex after all. I certainly hope so!
 * Cheers,
    Takis
 *  [gklauda](https://wordpress.org/support/users/gklauda/)
 * (@gklauda)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9296244)
 * Hello Takis,
 * I understand the problem. And there doesn’t seem to be a convenient solution.
   Fortunately, the problem afflicts only a relatively small portion of users, and
   I guess the most rational approach would be to enable people to fix the problem
   on the options page by letting them indicate the correct location of the wp-content
   folder. One could also support them by scanning the wp-config file when they 
   visit the options page and showing them the value of WP_CONTENT_DIR if it is 
   defined there. Those are just some ideas that come to my mind and I hope they
   are not utterly stupid. 🙂
 * Cheers,
    George
 *  Plugin Author [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * (@nevma)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9296485)
 * Hey, George,
 * Thanks for taking the time to give it some extra thought!
 * No, your ideas are not stupid, at all. I love hearing new ideas. My concern is
   to find a way to cover all cases in a uniform and robust way, because it is all
   very easy to fix one thing and break another.
 * Cheers,
    Takis
 *  Thread Starter [hgassner](https://wordpress.org/support/users/hgassner/)
 * (@hgassner)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9321428)
 * Hello,
 * sorry for beeing late.
 * I had changed http to https in the Settings and I also did a search and replace
   in the database. With no effect (unfortunately the plug still does not work).
 * I thought about doing the changes [@gklauda](https://wordpress.org/support/users/gklauda/)
   suggested but decided to wait for a solution by the plugins author :).
 * It would be great if the PlugIn can handle http to https changes without any 
   troubles for standard wordpress installations (folder not changed).
 * If a user changes the WordPress folder I think that this will be an advanced 
   user and should know what he is doing. In this case: might it be a possibility
   to let the user enter the WordPress folder? Just as a simple solution. If you
   as author of the PlugIn have the possibility to search for the folder for yourself(
   e.g. by looking for the config files path?) you can make an suggestion for the
   path.
 * For me at the moment I decided to wait for an update of the PlugIn which can 
   handle https better.
 * Thanx for your help
    Horst
 *  Plugin Author [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * (@nevma)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9321524)
 * Hello, Horst,
 * I am very sorry that it hasn’t worked out for you so far. If you have indeed 
   changed all your urls to https and the plugin still doesn’t work, then this sounds
   like a really strange situation. I am sure I am missing some important detail
   here. If you feel like it, perhaps you can send me an email and we can further
   debug this from the “inside”. Otherwise, we will definitely try to see what we
   can do in future versions.
 * And thank you for the rest of your suggestions and ideas!
 * Cheers,
    Takis
 *  [benntech](https://wordpress.org/support/users/benntech/)
 * (@benntech)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9355847)
 * Thanks, gklauda! Great solution.
 * Nevma, I understand your stance of not knowing where wp-content is located, but
   looking at your code, you’re just hard coding the location in that variable anyway.
   gklauda’s solution just adds the “S” to HTTPS pages without changing anything
   for non-HTTPS. Simple and elegant. You should really consider incorporating gklauda’s
   code–it’s a great fix for the majority of people with standard WordPress installations.
 * Again gklauda, great find. Thanks!
 *  Plugin Author [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * (@nevma)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9357749)
 * Hi, [@benntech](https://wordpress.org/support/users/benntech/),
 * You are probably looking at the point where we are setting the default value 
   for the /wp-content location. Just a few lines further on we try to read it based
   on the user’s settings which derive from their WordPress installation where the
   WordPress code has actually been loaded.
 * Now, I could go on and on about how tricky it is to universally guess all the
   necessary variables during requests which happen when the WordPress code has 
   been loaded, in order to use them at later requests, where the WordPress code
   has not been loaded, but there is no point.
 * However, I do promise to consider [@gklauda](https://wordpress.org/support/users/gklauda/)’
   s solution!
 * Cheers,
    Takis
 *  [renegeuze](https://wordpress.org/support/users/renegeuze/)
 * (@renegeuze)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9407591)
 * Why not just remove any protocol either with regex or a simple array of removals?
   This will avoid any problem even if someone has a saved version of user-settings.
   php with either http or https.
 * So something like:
 *     ```
       $protocols = array('http://', 'https://');
       $wp_content_url = str_replace($protocols, '', $wp_content_url);
       $image_url = str_replace($protocols, '', adaptive_images_script_get_url());
       $source_file = str_ireplace($wp_content_url, $wp_content_dir, $image_url);
       ```
   
 * You could also go with the nicer [parse_url](http://php.net/manual/en/function.parse-url.php)
    -  This reply was modified 8 years, 10 months ago by [renegeuze](https://wordpress.org/support/users/renegeuze/).
 *  Plugin Author [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * (@nevma)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9409669)
 * Hello, [@renegeuze](https://wordpress.org/support/users/renegeuze/),
 * Indeed, it seems that the solution to the problem is like you propose. It has
   also been proposed earlier in this thread as well. The reason we have not included
   such a piece of code is -more or less- the historical evolution of our own code.
   We do pledge take this proposal into serious consideration in our next versions.
 * Thank you for chipping in!
 * Cheers,
    Takis

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Switched to HTTPS – does not work anymore’ is closed to new replies.

 * ![](https://ps.w.org/adaptive-images/assets/icon-256x256.png?rev=1138642)
 * [Adaptive Images for WordPress](https://wordpress.org/plugins/adaptive-images/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/adaptive-images/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/adaptive-images/)
 * [Active Topics](https://wordpress.org/support/plugin/adaptive-images/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/adaptive-images/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/adaptive-images/reviews/)

## Tags

 * [HTTPS](https://wordpress.org/support/topic-tag/https/)

 * 13 replies
 * 5 participants
 * Last reply from: [Takis Bouyouris](https://wordpress.org/support/users/nevma/)
 * Last activity: [8 years, 10 months ago](https://wordpress.org/support/topic/switched-to-https-does-not-work-anymore/#post-9409669)
 * Status: not resolved