Users running a non-download version of Vanilla (pulled from github), on branch release/2019.016 or master from the last 2 weeks should upgrade to release/2019.017 or latest master for security reasons. Downloaded official open sources releases are not affected.
Please upgrade here. These earlier versions are no longer being updated and have security issues.

Explanation Needed for JSConnect

This discussion is related to the Vanilla jsConnect addon.

I have JSConnect working and when it works it's awesome! Thank you!

But every now and then, we get an error: "Whoops! Timestamp is invalid".

I've found where the error comes from: Lines 48-49 in this file

But I don't know they why is it caused? And what can I do to prevent it for my clients (if anything)?

Thank you in advance!

Chris Martinez


  • Either your users are timing out or there is a problem with your timestamp. I guess you should dig to see clearer what is happening when this error is produced.

    Timeout code is near the top of that file.
    define('JS_TIMEOUT', 24 * 60);

  • Thanks!!

Sign In or Register to comment.