SSL Issues (fixed)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Bol.com

    (@netvlies)

    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

    (@onepack)

    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

    (@netvlies)

    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.

Tags