Title: It seems that HTTPS can not be read. Last modified: May 18, 2018 --- # It seems that HTTPS can not be read. * Resolved [kbmt](https://wordpress.org/support/users/kobamatsu/) * (@kobamatsu) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/) * Loading image from custom field. * Please tell me how to load and display images from external servers such as BOX and salesforce. * It seems that HTTPS can not be read. * I do not have knowledge of the program…. Viewing 10 replies - 1 through 10 (of 10 total) * Plugin Author [Hector Cabrera](https://wordpress.org/support/users/hcabrera/) * (@hcabrera) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10293264) * Hi [@kobamatsu](https://wordpress.org/support/users/kobamatsu/), * What do you mean with “It seems that HTTPS can not be read”? Please share some more details (eg. steps to reproduce the issue) and I’ll look into it (feel free to include screenshots if you feel it’ll help to explain what’s going on). * Thread Starter [kbmt](https://wordpress.org/support/users/kobamatsu/) * (@kobamatsu) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10293360) * sorry… I can hardly speak English… * [load and display images] [http://www.tosenad.com/id08454_ninihaikyaku4.JPG](http://www.tosenad.com/id08454_ninihaikyaku4.JPG) * [not load and display images] [https://tosenad.box.com/shared/static/n52likkjabct02i8ruxx5p49x2dxl6rg.jpg](https://tosenad.box.com/shared/static/n52likkjabct02i8ruxx5p49x2dxl6rg.jpg) * [https://tosenad–c.ap0.content.force.com/servlet/servlet.FileDownload?file=00P1000000qYg73](https://tosenad–c.ap0.content.force.com/servlet/servlet.FileDownload?file=00P1000000qYg73) * Thread Starter [kbmt](https://wordpress.org/support/users/kobamatsu/) * (@kobamatsu) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10293401) * Can not display secure server images? * [japanese forum] [https://ja.wordpress.org/support/topic/popular-posts-https-%E3%81%A7%E5%A7%8B%E3%81%BE%E3%82%8B%E7%94%BB%E5%83%8F%E3%83%91%E3%82%B9%E3%81%AE%E7%94%BB%E5%83%8F%E8%A1%A8%E7%A4%BA%E3%81%AE%E6%96%B9%E6%B3%95/](https://ja.wordpress.org/support/topic/popular-posts-https-%E3%81%A7%E5%A7%8B%E3%81%BE%E3%82%8B%E7%94%BB%E5%83%8F%E3%83%91%E3%82%B9%E3%81%AE%E7%94%BB%E5%83%8F%E8%A1%A8%E7%A4%BA%E3%81%AE%E6%96%B9%E6%B3%95/) * [https://translate.weblio.jp/web/english?lp=JE&url=https%3A%2F%2Fja.wordpress.org%2Fsupport%2Ftopic%2Fpopular-posts-https-%25E3%2581%25A7%25E5%25A7%258B%25E3%2581%25BE%25E3%2582%258B%25E7%2594%25BB%25E5%2583%258F%25E3%2583%2591%25E3%2582%25B9%25E3%2581%25AE%25E7%2594%25BB%25E5%2583%258F%25E8%25A1%25A8%25E7%25A4%25BA%25E3%2581%25AE%25E6%2596%25B9%25E6%25B3%2595%2F&sentenceStyle=spoken](https://translate.weblio.jp/web/english?lp=JE&url=https%3A%2F%2Fja.wordpress.org%2Fsupport%2Ftopic%2Fpopular-posts-https-%25E3%2581%25A7%25E5%25A7%258B%25E3%2581%25BE%25E3%2582%258B%25E7%2594%25BB%25E5%2583%258F%25E3%2583%2591%25E3%2582%25B9%25E3%2581%25AE%25E7%2594%25BB%25E5%2583%258F%25E8%25A1%25A8%25E7%25A4%25BA%25E3%2581%25AE%25E6%2596%25B9%25E6%25B3%2595%2F&sentenceStyle=spoken) * [gblsm](https://wordpress.org/support/users/gblsm/) * (@gblsm) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10293506) * I explain the issue as written in Japanese forum. * A custom field of post contains the image URL that begins as `https://`. Plugin reads it, but accesses URL after replacing `https` to `http`. The image cannot be loaded by HTTP because it lives in some cloud storage such as BOX. * Plugin Author [Hector Cabrera](https://wordpress.org/support/users/hcabrera/) * (@hcabrera) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10293513) * Thanks for chiming in, [@gblsm](https://wordpress.org/support/users/gblsm/)! That clears things up a bit. * I’ll look into it as soon as I can, [@kobamatsu](https://wordpress.org/support/users/kobamatsu/). I’ll keep you guys posted. * [gblsm](https://wordpress.org/support/users/gblsm/) * (@gblsm) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10294462) * To be more clear, the plugin accesses `http:/example.com/image.jpg` when the custom field has `https:/example.com/image.jpg`. I see the replacing (https => http) would be done in some cases (ex. is_ssl() is true), but I think the site admin may want to enable/disable it. * Plugin Author [Hector Cabrera](https://wordpress.org/support/users/hcabrera/) * (@hcabrera) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10295348) * Hey guys, * I just tested it out on my localhost and this is what I get: * ![WPP and SSL images from custom fields](https://i0.wp.com/oi66.tinypic.com/28btnoj. jpg) * The image loads just fine and preserves the HTTPS protocol. * > I see the replacing (https => http) would be done in some cases (ex. is_ssl() > is true), but I think the site admin may want to enable/disable it. * There’s is a replacement but it’s the other way around: if the website uses SSL and it tries to load an image from a none-secure URL (http), it’ll replace http with https: * ``` /** * Render image tag. * * @since 3.0.0 * @access public * @param string src Image URL * @param array dimension Image's width and height * @param string class CSS class * @param object $post_object Post object (must contain, at least, the properties id and title) * @param string error Error, if the image could not be created * @return string */ public function render_image( $src, $size, $class, $post_object, $error = null ) { $img_tag = ''; if ( $error ) { $img_tag = ' '; } $img_tag .= '' . ( ($post_object instanceof stdClass && isset($post_object->title) ? esc_attr( wp_strip_all_tags($post_object->title) ) : '' ) ) . ''; return apply_filters( 'wpp_render_image', $img_tag ); } // render_image ``` * Thread Starter [kbmt](https://wordpress.org/support/users/kobamatsu/) * (@kobamatsu) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10306573) * [@hcabrera](https://wordpress.org/support/users/hcabrera/) [@gblsm](https://wordpress.org/support/users/gblsm/) * I updated the plugin. Deleted extra postscript of function.php * The problem was solved. Thank you very much. * [gblsm](https://wordpress.org/support/users/gblsm/) * (@gblsm) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10311508) * Hi [@hcabrera](https://wordpress.org/support/users/hcabrera/), The cause was a conflict with an extra code which [@kobamatsu](https://wordpress.org/support/users/kobamatsu/) added to his theme’s functions.php … He removed the code and the problem gone. * Plugin Author [Hector Cabrera](https://wordpress.org/support/users/hcabrera/) * (@hcabrera) * [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10320839) * Thanks for the update, guys 🙂 [@kobamatsu](https://wordpress.org/support/users/kobamatsu/) [@gblsm](https://wordpress.org/support/users/gblsm/) Viewing 10 replies - 1 through 10 (of 10 total) The topic ‘It seems that HTTPS can not be read.’ is closed to new replies. * ![](https://ps.w.org/wordpress-popular-posts/assets/icon-256x256.png?rev=1232659) * [WP Popular Posts](https://wordpress.org/plugins/wordpress-popular-posts/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-popular-posts/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-popular-posts/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-popular-posts/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-popular-posts/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-popular-posts/reviews/) * 10 replies * 3 participants * Last reply from: [Hector Cabrera](https://wordpress.org/support/users/hcabrera/) * Last activity: [8 years ago](https://wordpress.org/support/topic/it-seems-that-https-can-not-be-read/#post-10320839) * Status: resolved