My third issue today… :)
If you open a page via https, all resources must be integrated via https. For relative paths the browser makes this automatically.
For absolute URLs not, they have to be https://…
For many resources the browser shows “only” a warning. For scripts and CSS modern browsers refuse to execute them completely. In case of CSS there are some missing CSS styles then and so the page looks broken.
So the entry looks in the source:
<link rel=’stylesheet’ id=’avia-dynamic-css’ href=’http://www.wiseseo.de/wp-content/uploads/dynamic_avia/enfold.css?ver=1′ type=’text/css’ media=’screen’ />
The entry is generated by the file wp-content/themes/enfold/functions.php:
if( get_option(‘avia_stylesheet_exists’.$safe_name) == ‘true’ )
//MT:20130815 we need a relative path for https
//$avia_upload_dir = wp_upload_dir();
//$avia_dyn_stylesheet_url = $avia_upload_dir . ‘/dynamic_avia/’.$safe_name.’.css’;
$avia_dyn_stylesheet_url = ‘/wp-content/uploads/dynamic_avia/’.$safe_name.’.css’;
wp_register_style( ‘avia-dynamic’, $avia_dyn_stylesheet_url, array(), ’1′, ‘screen’ );
The function wp_upload_dir () returns with the element “baseurl” an absolute path including http:// no matter how the page is accessed. That can not be. My hack so far: Fixed relative path, fits for our installation.
But it would be great if you could fix this as soon as possible.
Thanks & regards,
That pasted code looks out of date. I’m fairly sure Kriesi actually changed the whole function and many others to use https if it was defined elsewhere.
What version of the theme are you using?
The topic ‘/wp-content/uploads/dynamic_avia/enfold.css not with https’ is closed to new replies.