Title: Resource loading for HTTP/S
Last modified: August 21, 2016

---

# Resource loading for HTTP/S

 *  Resolved [Wil](https://wordpress.org/support/users/limecanvas/)
 * (@limecanvas)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/resource-loading-for-https/)
 * Hi there,
 * Great plugin, however, we run most of our admin dashboard in HTTPS.
 * Some of the resources you load in for the plugin specify HTTP.
 * This seems to be generated from line 31 in ctp-onomies.php where you use WP_PLUGIN_URL.
 * Unfortunately this define doesn’t take SSL into consideration.
 * Could you replace it with plugin_url() for your next release please?
 *     ```
       define( 'CPT_ONOMIES_URL', plugins_url() . '/' . basename( dirname( __FILE__ ) ) . '/' );
       ```
   
 * Many thanks,
    Wil.
 * [http://wordpress.org/plugins/cpt-onomies/](http://wordpress.org/plugins/cpt-onomies/)

Viewing 1 replies (of 1 total)

 *  [Rachel Cherry](https://wordpress.org/support/users/bamadesigner/)
 * (@bamadesigner)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/resource-loading-for-https/#post-4350151)
 * Thanks for pointing this out! Consider it done!

Viewing 1 replies (of 1 total)

The topic ‘Resource loading for HTTP/S’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/cpt-onomies_f2f2f2.svg)
 * [CPT-onomies: Using Custom Post Types as Taxonomies](https://wordpress.org/plugins/cpt-onomies/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cpt-onomies/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cpt-onomies/)
 * [Active Topics](https://wordpress.org/support/plugin/cpt-onomies/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cpt-onomies/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cpt-onomies/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Rachel Cherry](https://wordpress.org/support/users/bamadesigner/)
 * Last activity: [12 years, 6 months ago](https://wordpress.org/support/topic/resource-loading-for-https/#post-4350151)
 * Status: resolved