Title: SSL Issues (fixed)
Last modified: August 21, 2016

---

# SSL Issues (fixed)

 *  Resolved [onepack](https://wordpress.org/support/users/onepack/)
 * (@onepack)
 * [12 years ago](https://wordpress.org/support/topic/ssl-issues-fixed/)
 * Dear Bol.com plugin developer.
 * Please change line 21 of bolcom-partnerprogramma-wordpress-plugin.php
    New: define(‘
   BOL_PARTNER_PLUGIN_PATH’, plugin_dir_url() . plugin_basename(dirname(__FILE__)));
 * Using plugin_dir_url will prevent mixed content warnings when the WP backend 
   is using SSL but the frontend of the site isn’t. WP_CONTENT_URL will use http:
   in this case and cause issues.
 * [https://wordpress.org/plugins/bolcom-partnerprogramma-wordpress-plugin/](https://wordpress.org/plugins/bolcom-partnerprogramma-wordpress-plugin/)

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

 *  Plugin Author [Bol.com](https://wordpress.org/support/users/netvlies/)
 * (@netvlies)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/ssl-issues-fixed/#post-4920435)
 * Hi there onepack,
 * Thanks for your input and my apologies for the late reply.
    The plugin_dir_url()
   function doesn’t return the full URL of the plugin. It only returns “wp-content/
   plugins/bolcom-partnerprogramma-wordpress-plugin/plugins”.
 * The plugin is currently using the URL
    “WP_CONTENT_URL . ‘/plugins/’ . plugin_basename(
   dirname(__FILE__))” which also returns “wp-content/plugins/bolcom-partnerprogramma-
   wordpress-plugin/plugins”
 * In short your suggestion is just another way to define the BOL_PARTNER_PLUGIN_PATH,
   but will probably not fix the mixed content problem.
 * – Netvlies
 *  Thread Starter [onepack](https://wordpress.org/support/users/onepack/)
 * (@onepack)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/ssl-issues-fixed/#post-4920436)
 * Hi there Netvlies guy/woman, 😉
 * Actually after adjusting it the mixed content warnings were gone.
    It’s too long
   ago to remember exactly how and what if I have time tomorrow I will get back 
   on that. Anyway my client is now able to use the module without errors after 
   these adjustments. (see the other related cases from me regarding the Bol module)
 *  Plugin Author [Bol.com](https://wordpress.org/support/users/netvlies/)
 * (@netvlies)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/ssl-issues-fixed/#post-4920438)
 * Hi onepack,
 * Allright I will deploy this and your other contribution on the “header.inc.php”
   file on the next version. Even if it won’t fix the issue, it is still a better
   way to define the paths. Thanks for your contributions!
 * – Netvlies

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

The topic ‘SSL Issues (fixed)’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/bolcom-partnerprogramma-wordpress-
   plugin_91b2c3.svg)
 * [Bol.com Partner Program Plugin](https://wordpress.org/plugins/bolcom-partnerprogramma-wordpress-plugin/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/bolcom-partnerprogramma-wordpress-plugin/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/bolcom-partnerprogramma-wordpress-plugin/)
 * [Active Topics](https://wordpress.org/support/plugin/bolcom-partnerprogramma-wordpress-plugin/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bolcom-partnerprogramma-wordpress-plugin/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bolcom-partnerprogramma-wordpress-plugin/reviews/)

## Tags

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

 * 3 replies
 * 2 participants
 * Last reply from: [Bol.com](https://wordpress.org/support/users/netvlies/)
 * Last activity: [11 years, 6 months ago](https://wordpress.org/support/topic/ssl-issues-fixed/#post-4920438)
 * Status: resolved