Archived nodes are not redirecting

Created on 28 July 2022, almost 2 years ago
Updated 12 April 2024, 3 months ago

Problem/Motivation

When a node is archived and you go to its URL, you will get an access denied error but you won't be redirected.

Steps to reproduce

- Create a redirect.
- Archive a node.
- Go to the node URL, you won't be redirected.

πŸ› Bug report
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ͺπŸ‡ΈSpain guardiola86

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¨πŸ‡¦Canada aarantes

    Hi...

    Just adding it here in case it helps...

    I use a different module (redirect) but was having exactly the same issue with an addtitional detail... the redirect would work only if I added a trailing slash...

    So...

    When I archived the page https://mysite.com/mypage and created a redirect to https://mysite.com/newpage , the redirect would only work if I added the trailing slash, i.e., if I tried to reach https://mysite.com/mypage/ . If I didn't have the trailing slash, I would get the same "Access Denied" error described in this article.

    I solved this by changing the alias of the archived page to something else like "mypage-legacy" (AFTER archiving it and AFTER adding the redirect). As "mypage-legacy" was never live it didn't need redirect. And now, the original page URL ("https://mysite.com/mypage") redirects to "newpage" with or without a trailing slash.

    Problem solved... good luck...

Production build 0.69.0 2024