|
d37toastmasters
|
January 12, 2014 at 8:00 am
It appears that the latest version of Event Calendar plugin (version 2.2.1.p) is breaking Avada theme. The default color of the top header is dark blue on all pages: http://d37toastmasters.org/wp-content/uploads/2014/01/Avada-3.2.1-submenu-font.jpg with the exception of page with Event Calendar plugin shortcode where the top header is lime green and the submenu fonts are different from the rest of the website: http://d37toastmasters.org/wp-content/uploads/2014/01/Avada-3.3-submenu-font.jpg
Thank you,
Jake
|
|
Dean
|
January 13, 2014 at 2:29 am
Hi Jake,
Can I get a link to the actual site please ? (I assume its http://d37toastmasters.org/ but apparantly my access is limited).
|
|
d37toastmasters
|
January 13, 2014 at 3:09 am
Dean,
I disabled Country Block. You should be able to view the site.
Jake
|
|
Dean
|
January 13, 2014 at 4:33 am
Hi Jake,
Thanks for that.
It’s not event espresso per se, the events page is in HTTPS so the browser is seeing it as insecure content and the first thing it will do is block certain elements of the page the stylesheet included.
Because the stylesheet is blocked, the default green colour is showing through as the stylsheet over rode it.
To fix you will need to remove the HTTPS form the page or arrange for the stylesheet to be loaded via HTTPS.
The error message for your info:
[blocked] The page at ‘https://d37toastmasters.org/event-registration/’ was loaded over HTTPS, but ran insecure content from ‘http://d37toastmasters.org/wp-content/uploads/avada.css?ver=3.8’: this content should also be loaded over HTTPS.
The page at ‘https://d37toastmasters.org/event-registration/’ was loaded over HTTPS, but displayed insecure content from ‘http://d37.staging.wpengine.com/wp-content/themes/Avada/images/page_title_bg.png’: this content should also be loaded over HTTPS.
|
|
d37toastmasters
|
January 13, 2014 at 5:04 am
Dean,
Thank you! I opened a ticket with the hosting company requesting https removal from this page.
Jake
|
|
d37toastmasters
|
January 13, 2014 at 5:05 am
Dean,
What tools are you using to troubleshoot the issues like this. I’d like to learn that so I can save you some cycles.
Thank you,
Jake
|
|
Dean
|
January 13, 2014 at 6:02 am
Hi Jake,
I use Chromes Dev tools via the inspect element link (right click, bottom option). I always check the Console tab first off as that’s where javascript and other errors appear. After that if needed I would use the Elements, Resources and potentially Sources tabs to further troubleshoot.
Here’s some training – http://discover-devtools.codeschool.com/
|
|
d37toastmasters
|
January 14, 2014 at 10:49 am
Thanks!
|
