content
content copied to clipboard
mdn
Update rgba redirects
Following on from https://github.com/mdn/content/pull/31827, I've updated a couple of redirects to headings in color_value that no longer exist - https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#rgb()_and_rgba() to redirect to the rgb sub-article https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/rgb
I think doing this should close https://github.com/mdn/content/issues/30844 as there are no remaining outdated uses of rgba/hsla otherwise
Hi @FormularSumo, thanks for taking this project closer to completion.
For this change, could you confirm that you updated the redirect using the yarn content move command? Thanks
I did not use yarn commands when doing this, I didn't realise they existed. I've reverted my commit locally and tried to carry out this fix using yarn, however I don't think it's possible to. When using yarn content move on these two redirects it says error: document for /en-US/docs/Web/CSS/color_value#rgb()_and_rgba() does not exist (and the same error if I use /en-US/docs/CSS/rgb or /en-US/docs/Web/CSS/rgb instead), which is the problem I'm trying to solve. I've tried using yarn content add-redirect as well but that resulted in error: Invalid URL I think caused by the same issue.
Even if either of those commands did work it wouldn't be an ideal solution, redirecting an outdated redirect through another redirect. It seems to me that we just want to update where these two redirects point to. Do you have any idea how this might be done using yarn, or if it is possible for changes to be made not using yarn in situations like this?
@FormularSumo looks like the same fix got in via https://github.com/mdn/content/pull/32295. Sorry for the trouble 🙁 (I'll close this one as a duplicate).
if it is possible for changes to be made not using yarn in situations like this?
I haven't come across such a situation and we do recommend to not edit the _redirects.txt file manually. I expected yarn content add-redirect /en-US/path/of/deleted/page /en-US/path/of/target/page to work in this case. 🤷♀️