• Pie Calendar has been working wonderfully until (I think) version 1.3.1. It’s a really useful plugin and has been very solid up to now.

    Calendar does not display on first page load. Similar to symptoms in earlier post by phillipsburgh for v1.3.0 but a different error message. Repeated page reloads display the calendar correctly without further console errors but it’s confusing my users.

    Browser console error message is:

    Error] SyntaxError: \u can only be followed by a Unicode character sequence
    (anonymous function) (calendar:241)
    [Warning] Alpine Expression Error: undefined is not an object (evaluating '$store.calendarEngine.viewTitle') (alpine.3.11.1.min.js, line 1)

    This is followed by a string of warnings relating to Alpine and then further errors of the following form:

    [Error] TypeError: undefined is not an object (evaluating '$store.calendarEngine.viewTitle')(anonymous function) (alpine.3.11.1.min.js:5)
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter ukjack

    (@ukjack)

    OK so I read the fine manual and discovered that I had supports: custom fields turned off. I’ve fixed that and the problem seems to have gone away. Sorry to waste time but it might help others.

    jack

    Thread Starter ukjack

    (@ukjack)

    The custom fields setting was a false trail, it doesn’t affect the problem.

    Looking into it a bit more deeply.

    The source of the error seems to be in the eventSources array, the long JSON string which Pie Calendar uses to encode the events html. I see that the string codes all events not only those showing in the current page and in my case it’s quite long (around 60k characters).

    The problem seems to be in the double-encoding of special characters and it only occurs once in the whole string. So far it’s been a no-break space. It’s not always associated with the same event. I’ve seen two variations of the problem code:

    \u00a0
    \u00a0

    After a couple of page reloads the calendar renders correctly and the code for the same space character changes to:

    \u00a0

    This version causes no problems although the mix of decimal and hex is a bit puzzling.

    I’m on Macintosh and the problem occurs in Safari, Firefox, Chrome and DuckDuckgo. I believe it occurs on Windows as well.

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

You must be logged in to reply to this topic.