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

Unsplash utm_source hard-coded to "Companion" #5564

Open
2 tasks done
GFoley83 opened this issue Dec 28, 2024 · 0 comments
Open
2 tasks done

Unsplash utm_source hard-coded to "Companion" #5564

GFoley83 opened this issue Dec 28, 2024 · 0 comments
Labels

Comments

@GFoley83
Copy link

Initial checklist

  • I understand this is a bug report and questions should be posted in the Community Forum
  • I searched issues and couldn’t find anything (or linked relevant results below)

Link to runnable example

No response

Steps to reproduce

As seen here:

href={`${file.data.author!.url}?utm_source=Companion&utm_medium=referral`}

Expected behavior

The utm_source=<your unsplash app> to be customisable via the Unsplash plugin.

Actual behavior

Value is hard-coded to utm_source=Companion.

This is preventing us from getting "Production" level approval from Unsplash given we use our own Unsplash account with self-hosted Companion.

As per their attribution guide:

When displaying a photo from Unsplash, your application must attribute Unsplash, the Unsplash photographer, and contain a link back to their Unsplash profile. All links back to Unsplash should use utm parameters in the form of
?utm_source=<your_app_name>&utm_medium=referral

The app name is set when you create your Unsplash API key.

@GFoley83 GFoley83 added the Bug label Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant