• With the latest version and when compression of js scripts, there’s probably a missing “;” somewhere in this code js fragment:

    {deferred.splice(i–,1)var r=fn();

    WordPress: 6.7.2
    Locale: fr-FR America/Toronto
    ICS Calendar 11.5.5
    LiteSpeed Cache 6.5.4

    Plugin Settings:
    r34ics_ajax_by_default:
    r34ics_ajax_bypass_nonce:
    r34ics_allowed_hosts:
    r34ics_display_add_calendar_button_false:
    r34ics_display_calendar_memory_limit:
    r34ics_feed_urls:
    r34ics-url-67bcdea87a7bd4.25956692: https://calendar.google.com/calendar/ical/sportentete%40gmail.com/public/basic.ics
    r34ics_previous_version: 11.5.4.2
    r34ics_transients_expiration: 3600
    r34ics_url_get_contents_legacy_method:
    r34ics_use_new_defaults_10_6: 1
    r34ics_version: 11.5.5
    • This topic was modified 3 weeks, 5 days ago by clauded007.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author room34

    (@room34)

    Thanks for bringing this to my attention, it didn’t come up in internal testing. I’ll investigate ASAP.

    Plugin Author room34

    (@room34)

    @clauded007 Reviewing the updates, there haven’t been any changes to the plugin’s JavaScript since version 11.5.3, released 3 weeks ago, and there aren’t any changes there that are likely to cause this kind of issue.

    Needless to say, I have no control over what’s happening with other plugins manipulating ICS Calendar’s JavaScript, although in general I would recommend avoiding doing that unless it’s absolutely (and measurably) necessary for your site’s performance.

    In order to troubleshoot this further, I’ll need your full System Report and more specifics about the error. You can submit those using the support request form. Thanks.

    In the meantime, I would encourage you to configure whatever plugin is concatenating JavaScript to bypass ICS Calendar’s scripts, if possible.

    Thread Starter clauded007

    (@clauded007)

    Thanks for looking into this. Since the ICS plugin was the only recent change, I guess I misread the JS file and this might be caused by another plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.