• Hello,

    I have a problem which seems to occur since I took wordpress 4.1 update :

    If I create an event, with “no end date” checked and publish it, it is then impossible to change the setting : if I load the event, uncheck the “no end date” box and set an end date, when I save the event reloads with the box checked.

    The date seems to be saved though : if I uncheck again the box, the date that appear is the one I set just before. But the event won’t save as anything else than “no end date”.

    Also, if I load, uncheck “no end date”, check “all day event”, it will then be impossible to uncheck either “no end date” or “all day event” box after saving.

    I tried to disable every other wordpress plugin with no success.

    Oh and also (don’t know if it’s related) it takes more than 6 to 10 sec to load a1ec’s javascript (after the complete load of the page)…

    Thanks a lot !

    https://wordpress.org/plugins/all-in-one-event-calendar/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Do you see any javascript error in the page using firebug?

    Thread Starter Seospan

    (@seospan)

    When loading the page 2 warnings :
    “L’utilisation des « Mutation Events » est obsolète. Utiliser « MutationObserver » à la place.
    L’utilisation de « getPreventDefault() » est obsolète. Utiliser « defaultPrevented » à la place.”
    (Use of « Mutation Events » is obsolète. Use « MutationObserver » instead.
    Use of « getPreventDefault() » is obsolète. Use « defaultPrevented » instead)

    And sometimes when changing end date, difficult to define exact pattern :
    “NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN: Cannot modify properties of a WrappedNative”
    But it comes from autocomplete.xml, which is not an A1EC file…

    WordPress 4.1 is not the issue, can you check for plugin/theme conflicts? http://time.ly/document/user-guide/troubleshooting/first-troubleshooting-step/

    Regarding our javascript which is loading slow, this is something which happens on some hosts, even if the page loads in 2-3 seconds. The really strange thing is that for rendering javascript we just read and combine static js files and then exit so it should be much faster than page load. Can you ask your host if they have any idea on why this is happening?
    We are reading files with file_get_contents() and files are in folder public/js/. All i can think of are some kind of I/O bottleneck or a permission issue.

    Thread Starter Seospan

    (@seospan)

    I just tried with a twenty-fifteen, along with disabling every external plugin except A1EC… not better.

    I’m using “X” V3.0.1 (https://theme.co/x/)

    I went looking in database directly… obviously “allday” field never switch to 0 when set to 1. Don’t know if this would come from javascript before saving (which would be strange, a checkbox shouldn’t need js to be saved… ) or from a php script, but definitely not from js after reloading.

    Thanks for your reactivity !

    Hi, i really wouldn’t know what to say, making all proper backups and so on, can you try 2.2 beta?Just make sure you have all back ups ready to go back to your version

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

The topic ‘Problem with "no end date" checkbox since 4.1’ is closed to new replies.