Insecure content from script sources

  • Resolved puntable

    (@puntable)


    12 years, 11 months ago

    Hello
    I am using premium version of this plugin and it is working great. Today i got a SSL certificate on the domain and i am trying to get rid of warnings.
    Where do i ommit the “http” that is inserted in script sources just below footer?

    Like:
    <script type='text/javascript' src='http://domain.com/wp-content/plugins/nimble-portfolio-premium/includes/transformation/jquery-css-transform.js?ver=1.3.7'></script>

    This plugin inserts the links somewhere and i just need to figure out where and then delete “http:” from the code.

    Hope someone can help.

    http://wordpress.org/extend/plugins/nimble-portfolio/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Nimble3

    (@nimble3)

    12 years, 11 months ago

    Please find php constant NIMBLE_PORTFOLIO_URL defined in the first 20 lines of nimble-portfolio.php which is actaully using WP_PLUGIN_URL as the base URL and then append plugin path to it.

    Thread Starter puntable

    (@puntable)

    12 years, 11 months ago

    Hello and thanks for reply.

    I have found the file and the code you are mentioning but still problems.

    This is how it looks now:

    define('NIMBLE_PORTFOLIO_URL', WP_PLUGIN_URL . "/" . basename(NIMBLE_PORTFOLIO_DIR));

    If i type the complete path to the plugin like this:

    define('NIMBLE_PORTFOLIO_URL', WP_PLUGIN_URL . "https://domain.com/wp-content/plugins/nimble-portfolio-premium" . basename(NIMBLE_PORTFOLIO_DIR));

    I get wrong url path. “HTTP” is still appended infront of source so it looks like this:

    http://domain.com/wp-content/pluginshttps://domain.com/wp-content/plugins/nimble-portfolio-premiumnimble-portfolio-premium/includes/transformation/qsfilter.js?ver=1.2.2

    What am i doing wrong?

    Thread Starter puntable

    (@puntable)

    12 years, 11 months ago

    Nevermind, i was stupid. I just changed base url in WordPress installation from http to https and then all links worked.

    Thanks for your time. This has been solved now 🙂

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

The topic ‘Insecure content from script sources’ is closed to new replies.