Force cookie resets #16

New Issue

FWDekker · 2019-10-31T02:07:18+01:00

FWDekker commented

2019-10-31 02:07:18 +01:00

If the format of a cookie changes or important new features are added, I should be able to force a reset of a visitor's cookies so that these updates are pushed through. For example, if I completely change the default file layout (like suggested in #10), then users who already have a files cookie will not see these changes. Therefore, the script should check whether it should forcefully reset the cookies each time the page is loaded.

This can be done by adding a (semantic) version number to the website and having a cookie store the version number that was last visited; if the current version differs in the major (or minor?) version number, then an update should be forced. Alternatively, I could add a "last forced update" to the program, have the user store that in a cookie, and check if the user's time is lower than the script's time.

The latter solution is probably uglier but also much easier to implement and maintain.

If the format of a cookie changes or important new features are added, I should be able to force a reset of a visitor's cookies so that these updates are pushed through. For example, if I completely change the default file layout (like suggested in #10), then users who already have a `files` cookie will not see these changes. Therefore, the script should check whether it should forcefully reset the cookies each time the page is loaded. This can be done by adding a (semantic) version number to the website and having a cookie store the version number that was last visited; if the current version differs in the major (or minor?) version number, then an update should be forced. Alternatively, I could add a "last forced update" to the program, have the user store that in a cookie, and check if the user's time is lower than the script's time. The latter solution is probably uglier but also much easier to implement and maintain.

FWDekker self-assigned this 2019-10-31 02:07:18 +01:00

FWDekker added the

feature

label 2019-10-31 02:07:18 +01:00

FWDekker commented

2019-11-10 01:46:31 +01:00

A semantic version has been added in 11523b5046 and is accessible through post-processing by writing %%VERSION_NUMBER%% in any TypeScript source file. This version could be used for version matching as described above.

A semantic version has been added in 11523b5046 and is accessible through post-processing by writing `%%VERSION_NUMBER%%` in any TypeScript source file. This version could be used for version matching as described above.

FWDekker commented

2019-11-19 10:44:52 +01:00

With significant breaking changes being introduced at some regularity this issue is becoming more important: Some users may see broken versions of the website or may see file links that no longer work.

FWDekker referenced this issue from a commit

2019-12-01 23:31:14 +01:00

Reset application on updates Fixes #16.

FWDekker closed this issue

2019-12-01 23:31:14 +01:00

Sign in to join this conversation.