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

Whishlist #146

Open
rpjengaard opened this issue Jul 5, 2022 · 1 comment
Open

Whishlist #146

rpjengaard opened this issue Jul 5, 2022 · 1 comment
Assignees
Labels
category/internal status/idea The ideas in this issue are great idea, but we're not ready to work on it in the near future

Comments

@rpjengaard
Copy link
Member

rpjengaard commented Jul 5, 2022

Hi @abjerner ,

I have this whishlist from Kasper. Please take a look at it, and lets have a discussion about it.

- Option to export all redirets for a specific website
I think we can look these two as one as one common task. If we define checking for errors as validating that content and media redirects still work, then I'd say this task would require round 4-8 hours. The result would be that the dashboard gets some sort of export button, which when clicked, will prompt a CSV download with information about is redirect.

If checking for errors includes validating external links, this is a much bigger task. A very rough estimate would be 1-3 days for this part, but it would also involve some search, and possibly also some discussion with the client about how this would work the best.

- Make an export of all redirect not working/gives error

- If above is NOT possible, can we do a script that checks all redirects and writes a log w. errors
https://banhawy.medium.com/how-to-use-google-spreadsheets-to-check-for-broken-links-1bb0b35c8525

- Is it possible to extend the "Inbound redirects" tab to show redirect errors and edit them directly?
This depends on what the client wants. For the Umbraco 9 redirects package, a small error will be shown for redirects where the destination content or media can no longer be found. External/URL redirects are not validated. Backporting this to the Umbraco 7 package would probably take around 4-8 hours.

But it terms of performance, the Umbraco 9 package will only validate the redirects on the page (page in the list, per the pagination) currently being shown to the user. It's not possible to filter the list to only include redirects with errors.

If the client wants to be able to filter the list to only include redirects with errors, this requires some more time and research.

@abjerner
Copy link
Member

Hi @rpjengaard

Just to follow up on this issue:

  • Option to export all redirets for a specific website
    This is now possible via the Skybrud Redirects Import package. It allows exporting all redirects to CSV or XLSX, but it doesn't support only exporting redirects with errors.

  • Make an export of all redirect not working/gives error
    If I should look into this, we should probably discuss what kind of errors we should look for. Broken internal references should be somewhat easier to handle, while actively requesting the destination URLs and checking for errors is a bigger task like I described.

    v3.x and v4.x also display errors about broken internal references directly in the dashboard, although you still have to browse through them if you have many redirects.

  • Is it possible to extend the "Inbound redirects" tab to show redirect errors and edit them directly?
    The property editor or content app shows redirects where destination is the current node that you're viewing. So unless the node is unpublished, there shouldn't be any errors to show (I think).

Feel free to ping me or have a chat at the office if you need me to look into any of these 😉

@limbobot limbobot added the status/idea The ideas in this issue are great idea, but we're not ready to work on it in the near future label Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category/internal status/idea The ideas in this issue are great idea, but we're not ready to work on it in the near future
Projects
None yet
Development

No branches or pull requests

3 participants