Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade for jQuery.Cookie to 1.4.1 #3024

Merged
merged 1 commit into from May 7, 2020
Merged

Upgrade for jQuery.Cookie to 1.4.1 #3024

merged 1 commit into from May 7, 2020

Conversation

splitbrain
Copy link
Collaborator

This fixes a problem with badly encoded cookies that may have been set by other software on the same domain. Eg. cookies encoded in latin1 instead of UTF-8.

Note: this library is abandoned and superseeded by js-cookie but an upgrade to that is not straight forward (and the benefits for us are unclear)

This fixes a problem with badly encoded cookies that may have been set
by other software on the same domain. Eg. cookies encoded in latin1
instead of UTF-8.

Note: this library is abandoned and superseeded by js-cookie but an
upgrade to that is not straight forward (and the benefits for us are
unclear)
@phy25
Copy link
Collaborator

phy25 commented Mar 26, 2020

I guess you are only cherry-picking the fix commit you mentioned without other "breaking" changes in 1.4.1 (I think they are fine to integrate probably)? Then you probably should not mark the version as 1.4.1 in the script comment (probably a 1.3.1+).

@Klap-in
Copy link
Collaborator

Klap-in commented Mar 27, 2020

@splitbrain why is a migration not that straight forward here?

@phy25
Copy link
Collaborator

phy25 commented Mar 27, 2020

@Klap-in They change the function name from $.cookie to Cookies.* which I think will break a lot of our plugins: https://github.com/js-cookie/js-cookie/tree/v1.5.1

@Klap-in
Copy link
Collaborator

Klap-in commented Mar 27, 2020

These plugins use this library according to codesearch.dokuwiki.org:
/plugin/socialshareprivacy2 (ships also its own version)
/plugin/remust/ (ships also its own version)
/template/lisps/
/plugin/outliner/
/plugin/workflow/
/plugin/leightweightscript/
/template/codowik/

@splitbrain
Copy link
Collaborator Author

I guess you are only cherry-picking the fix commit you mentioned without other "breaking" changes in 1.4.1 (I think they are fine to integrate probably)? Then you probably should not mark the version as 1.4.1 in the script comment (probably a 1.3.1+).

I didn't cherry pick. I upgraded the whole script. I didn't see any breaking changes that would affect us at a cursory glance at the commit history.

@phy25
Copy link
Collaborator

phy25 commented May 4, 2020

I look at the diff again and is seeing a lot more than I remember I saw. Not sure why I thought this is not a full update. Will review again later.

Copy link
Collaborator

@phy25 phy25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry about the previous confusion. I still have no idea why I thought this is a cherry-pick (probably I looked at it before the force-push).

@phy25 phy25 merged commit 41f652a into master May 7, 2020
@Klap-in Klap-in deleted the cookieupdate branch September 23, 2020 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants