-
Notifications
You must be signed in to change notification settings - Fork 562
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
Feature request - show archived URLs in Blazer UI #99
Comments
Just for context, I had some early discussions on this with @FBoucher and @kmm7 during the implementation of Archived URLs. The general consensus was there is limited value and the UI would probably become confused. It could be done, but it would require a separate table in all likelihood to ensure that the User had clear context for whether they were viewing Live or Archived URLs. What would the Use Case be for wanting to see Archived URLs? I presume if you have Archived them, you are no longer using the shortened version? |
Thanks for explaining the context and that you already had this discussion. If it makes sense or if it confuses is another story.
My "problem" I see, once a vanity URL has been used, it's blocked forever. Either I can re-activate it or create a new URL with the same vanity URL (which counts the click independent of course). Just as an idea for another issue/request how it could be solved - input of course very welcome: |
We definitely need a way to see the archived URLs. That said should we do it in a new Archived page or have some checkbox (active, archived) on top of the grid that act as filter... I'm open. |
Archived URLs will still redirect. Is that a bug or do I not understand the purpose of archiving? |
@stevenhayles totally a bug would you please create a new issue for it please? :) |
Created #510 "Archived URLs generate redirects" |
Hi,
As now URLs can be archived, how can they be seen? Can an option be implemented to show either
┆Issue is synchronized with this Trello card by Unito
The text was updated successfully, but these errors were encountered: