Mixed content warnings caused by plugin coding
-
Hi; good plugin.
On my SSL website I am getting mixed content errors which are being caused by your plugin. This is because the way you enqueued the style and script file isn’t ideal and a little over complicated.
You should change your file loads to this:
wp_enqueue_script( 'addtoany', plugins_url('/addtoany.min.js', __FILE__ ), array( 'jquery' ), '1.0' ); wp_enqueue_style( 'addtoany', plugins_url('/addtoany.min.css', __FILE__ ), false, '1.14' );
instead of:
wp_enqueue_script( 'addtoany', $A2A_SHARE_SAVE_plugin_url_path . '/addtoany.min.js', array( 'jquery' ), '1.0' ); wp_enqueue_style( 'addtoany', $A2A_SHARE_SAVE_plugin_url_path . '/addtoany.min.css', false, '1.14' );
This is simpler and removes mixed content warnings.
- The topic ‘Mixed content warnings caused by plugin coding’ is closed to new replies.