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

'Back to deed link' on CC0 page is not working #694

Closed
mzeinstra opened this Issue Oct 26, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@mzeinstra

mzeinstra commented Oct 26, 2017

Go to:
https://creativecommons.org/licenses/zero/1.0/legalcode

Click on "« Back to Commons Deed" in the bottom of the page.

See that it redirects to "./" instead of a proper url. It redirects to http://licenses.productionwww.creativecommons.uk0.bigv.io/publicdomain/zero/1.0/

@robmyers robmyers self-assigned this Mar 7, 2018

@robmyers

This comment has been minimized.

Show comment
Hide comment
@robmyers

robmyers Mar 7, 2018

Contributor

Thank you for reporting this.

/licenses/zero/ is incorrect, it's /publicdomain/zero/ .

There is a redirect for this in the webserver config but it was broken (along with the one for /licenses/CC0...).

I have now fixed this.

Contributor

robmyers commented Mar 7, 2018

Thank you for reporting this.

/licenses/zero/ is incorrect, it's /publicdomain/zero/ .

There is a redirect for this in the webserver config but it was broken (along with the one for /licenses/CC0...).

I have now fixed this.

@robmyers robmyers closed this Mar 7, 2018

@mzeinstra

This comment has been minimized.

Show comment
Hide comment
@mzeinstra

mzeinstra Mar 8, 2018

Unsure where I found that url last year, a google search actually shows some documents from CC-NL that refer to it.

mzeinstra commented Mar 8, 2018

Unsure where I found that url last year, a google search actually shows some documents from CC-NL that refer to it.

@robmyers

This comment has been minimized.

Show comment
Hide comment
@robmyers

robmyers Mar 8, 2018

Contributor

Yes it's in our redirects so we should handle it (by sending the user to the correct page).

We have a few like that. :-)

Contributor

robmyers commented Mar 8, 2018

Yes it's in our redirects so we should handle it (by sending the user to the correct page).

We have a few like that. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment