Browser incompatibility

  • Resolved csualum1994

    (@csualum1994)


    10 years, 9 months ago

    We recently installed the localendar plugin on our website. It looks great when we view the site on Internet Explorer, but the calendar doesn’t appear at all when the page is viewed in Chrome or Firefox. Just out of curiosity, I tried both browsers just now changing the https to http, and that actually did work. I’m not a professional developer or anything; I’m just trying to help my wife put together a site for her business. She deals with children, so I always assumed we’d want everything about the site to be as safe as possible for the peace of mind of parents. Is it going to get in the way for us to use the more secure protocol, or can localendar be made to work with https? Again, the https does seem to work fine in IE, oddly enough. We’d appreciate it if you could take a peek at the page and let us know what (if anything) we’re doing wrong – thanks!

    https://mamapajama.com/calendar

    https://www.ads-software.com/plugins/localendar-for-wordpress/

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

  • i am using Localendar Calendar for WordPress. its working fine in mozilla but in chrome calender is cut off from bottom. i.e there is no scroll bar in the calender.
    check this in chrome https://standupcomedynyc.com/calendar/
    any help regarding this?

    Plugin Author localendar

    (@localendar)

    csualum1994, If your calendar doesn’t appear and your site is using https://, make sure you precede your localendar include with https:// as well.

    yasir123, if your calendar is cut off, you are either using an Iframe to publish it (and not setting the height correctly) or you may be pasting it into a part of your theme that has a fixed height DIV. I see you are using an Iframe, and have set the height to be *huge* to avoid the ‘clipping’ problem. Instead of the Iframe style, you might try using the “Fully interactive embedded calendar” style, which will auto-size the height automagically.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Browser incompatibility’ is closed to new replies.