Closed (fixed)
Project:
Redirect
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Jun 2012 at 15:38 UTC
Updated:
3 Oct 2012 at 23:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
dave reidDid you refresh the node edit page?
Comment #2
kim.le commentedYes. I cleared by browser cache, refreshed the page, use a different browser, but it still doesn't list a redirect in the node edit form when I go into the article to edit.
Comment #3
patty.fresonke commentedAnyone have any insight on this problem??See edit below
Comment #4
patty.fresonke commentedI was clicking around and I happened to change the title of an article, thus changing the alias...so, having "Automatically create redirects when URL aliases are changed." enabled in admin/config/search/redirect/settings, it created a redirect from the old alias to the node/154 path. That shows up in the node edit form. But creating a redirect from the node/29 to http://www.amazon.com, for example, will work properly but it will not show up on the node edit form page. I attached a screen shot to hopefully help with my description.EDIT: I was given this issue by someone working on it before me, and was under the assumption that it was the correct module for the job, but after looking into it more, it appears they were wrong and this is for internal redirects - more or less. Not for redirecting to external URLs. It technically works but will not pull that data into the table to display on the node edit form. (A big usability issue when looking at it for the 'external url' use case).
The description on the module page is slightly vague as it states it features a "Common API for loading, saving, and deleting redirects". Not really specifying that it's not meant for external redirects. And when looking at the node edit form 'helper' text it states "The following are a list of URL redirects that point to this node" implying that it is only meant for alias redirects and the like. Which would explain why redirects that are pointing externally do not show up in that table.
So whether this is working as it was designed or if the 'pointing a node to an external URL' portion is just not there yet, I think needs to be answered by a maintainer for this module.
Comment #5
dave reidCorrect, the module in the UI does not encourage people to be creating redirects from existing valid content that points elsewhere. The UI help text clearly states that it lists/creates redirects 'to' the item, not 'from' the item like you have done. The API itself does not make assumptions and can be used for both internal and external redirects. If you have suggestions for improvements to the help text to help clarify this, please re-open or file a new issue.