Admin Menu format broken on Mac using OS X El Capitan

[sbetto]

Hi there, 

I have an issue with my admin menu formatting. It only seems to present on my Mac PC (using OS X EL Capitan V10.11.1) and I am pretty sure the issue started occurring after I upgraded my PC operating system (I've tested on a windows PC & my iPad and the display is as expected on them). 

 

When on the main admin page, the main menu options - Catalog, Configuration, Customers, Localization etc buttons spread right across the page. Other information such as Total Revenue, Total Customers, Orders, Customers or whatever I have chosen to display on my front page falls below the main menu options instead of beside them.

When I click on any of the main menu options for example, Customers and click into the customer link, the customers are displayed below the main menu, instead of beside. 

 

I am using osCommerce V.2.3.3.4 with Mini Template installed. 

 

Anyone else experienced this or able to assist?

Thank you!

Sarah

[BrockleyJohn]

check if jquery is loading properly

[sbetto]

check if jquery is loading properly

 

Thanks for your suggestion John. Is there an easy way to do this??

Cheers,

Sarah

[sbetto]

Could this be the culprit? NB. I am no expert in this code so may be clutching at straws here!  When I do a view source on my ADMIN/index.php these are two errors I see that I think could be linked to formatting?? 

(apologies for the formatting blocks below...I couldn't work out another way to stop the URL references becoming links)

 

 [blocked] The page at 

https://www.barefootmaternity.com.au/NAMECHANGED/index.php

 was not allowed to run insecure content from 

http://www.barefootmaternity.com.au/NAMECHANGED/includes/stylesheet.css.

[Warning] [blocked] The page at 

https://www.barefootmaternity.com.au/NAMECHANGED/index.php

 was not allowed to run insecure content from 

http://www.barefootmaternity.com.au/NAMECHANGED/includes/general.js.

 

I have tested my theory by changing the SSL setting on my admin side to ('ENABLE_SSL', 'false') and the Admin Menu is now displaying with all formatting correct.... but now that means my admin side is no longer properly secured? 

I am now unsure of what to change to secure my Admin again so I can have both security & nice formatting!  :P 

So I am thinking this is a 'feature' of Mac / Capitan / Safari V9.0.1 that I need to address somehow?

[MrPhil]

The messages are telling you that you're on a secure (SSL/https) page, and trying to load content (CSS or JS in this case) via insecure non-SSL/http. Many browsers will reject this combination, but not all. If CSS and/or Javascript is not being loaded, your menus etc. will be all messed up. The fix is not in the browser, but in your site. First, are you running your entire site in https? If so, you can just edit your PHP code to change any hard coded http: to https:. If the entire site is not in https, you can try this: remove the http: from wherever it's used for a URL for CSS or JS, leaving just //domain.name/path/file. I think most, if not all, browsers will fill in http: or https: depending on what the current page is.

 

As a last resort, if some pages will need http: and others https: for those files, you could modify the PHP code invoking them to check whether SSL is in use ($request_type == 'SSL') and use https:, otherwise use http:.

[sbetto]

The messages are telling you that you're on a secure (SSL/https) page, and trying to load content (CSS or JS in this case) via insecure non-SSL/http. Many browsers will reject this combination, but not all. If CSS and/or Javascript is not being loaded, your menus etc. will be all messed up. The fix is not in the browser, but in your site. First, are you running your entire site in https? If so, you can just edit your PHP code to change any hard coded http: to https:. If the entire site is not in https, you can try this: remove the http: from wherever it's used for a URL for CSS or JS, leaving just //domain.name/path/file. I think most, if not all, browsers will fill in http: or https: depending on what the current page is.

 

As a last resort, if some pages will need http: and others https: for those files, you could modify the PHP code invoking them to check whether SSL is in use ($request_type == 'SSL') and use https:, otherwise use http:.

 

Thanks Phil. My site isn't completely SSL so I'll try removing the http: when its used with CSS or JS.