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

Wrong encoding when running content migration from typed link field #191

Open
torgeirbeyer opened this issue Sep 9, 2024 · 7 comments
Open

Comments

@torgeirbeyer
Copy link

Describe the bug

After running content migration script from typed link field on Craft 4 install some query strings on urls are not encoded correctly. &region= ended up as ®ion=

Steps to reproduce

  1. Add urls with query params to typed link field with &region=
  2. Run content migration script

Craft CMS version

4.11.1

Plugin version

1.2.1

Multi-site?

No

Additional context

No response

@engram-design
Copy link
Member

I can't seem to replicate that, sorry! Does it show the character in the control panel, when rendering the link, or both?

Does updating the Hyper field value manually cause the issue, and it's just the process if migration?

And just to confirm what kind of links they are, are they URLs, Custom or Element fields with suffix enabled (for Typed Link)?

@torgeirbeyer
Copy link
Author

They were urls, and at some point they were also switching when updating them manually, but I can't seem to replicate them anymore. You can close this, and I'll open it again if the problem comes back.

@torgeirbeyer
Copy link
Author

Skjermbilde 2024-09-16 kl  15 02 26 Here is an example. Everytime we update one, the other one changes back.

@engram-design
Copy link
Member

What's the outer field, as it seems like you're nesting things. Is it a Matrix, Neo or Vizy field?

@torgeirbeyer
Copy link
Author

It is Vizy

@torgeirbeyer
Copy link
Author

When saving the entry again the problems appears again, and the url is changed back to the R-symbol.

I can try to remove them completely and then save them again to see if it helps, but something odd is happening.

@engram-design
Copy link
Member

So I'll say this is most likely Vizy's doing being the owner of the field, and how content is encoded as JSON.

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

No branches or pull requests

2 participants