Importing redirects to other domains
Permalink Browser Info Environment
When bulk importing URLs, absolute URLs (to another domain) in the `To_URL` field is stripped of the domain and become relative, e.g.:
becomes
/redirect/me → /resource/on/another/domain
Is there any way to prevent this from happening?
From_URL,To_URL,To_PageID,To_FileID,Response_Code /redirect/me,https://example.com/resource/on/another/domain,0,0,301
becomes
/redirect/me → /resource/on/another/domain
Is there any way to prevent this from happening?
| Type: | Ticket |
|---|---|
| Status: | Archived |
Thanks, Dave.
There's also an unrelated issue, but I'm not sure it's caused by this add-on. Do you have any idea why the error in the attached screenshot would appear for one user but not the other when uploading the same file?
There's also an unrelated issue, but I'm not sure it's caused by this add-on. Do you have any idea why the error in the attached screenshot would appear for one user but not the other when uploading the same file?
Do you have the latest version of the plugin? We released an update for that issue a few weeks back. The reason we updated was because the mime type check relies on the browser and they deliver inconsistent results.
It's possible that it's an older version. I'll try the update and hopefully it will fix both issues.
The package has been updated so the TO_URL column won't get cut down to relative paths. Also, if you end up defining a Page ID or File ID, the TO_URL will be ignored. Hope this helps! Make sure to update to 1.1.2.
Thank you so much for fixing this! I really appreciate it. I'll install it and try it out.
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Sorry about the issue. I'll see if a patch for can be written tomorrow and get back to you.
Dave