13

See for example this question, migrated to Drupal Answers from its meta site. The link given in migrated from meta.drupal.stackexchange.com Oct 19 '13 at 16:40 points to https://meta.drupal.stackexchange.com/posts/2703/revisions instead of https://drupal.meta.stackexchange.com/posts/2703/revisions.

screenshot

Furthermore, when following the link, Chrome gives two errors: Your connection is not private and NET::ERR_CERT_COMMON_NAME_INVALID.

screenshot

  • Technically, when it was migrated, the link was correct. The problem here is that the system hasn't updated those links. New migrations don't have this problem. – Catija Dec 27 '17 at 14:12
  • @Catija That is correct. Links in the posts have been changed, though, through an edit of the Community user. – kiamlaluno Dec 27 '17 at 15:34
  • For you as a mod, is that a post notice on that specific question? Or is that a system generated notice? For SEDE it does look like it. – rene Dec 28 '17 at 11:42
  • @rene It's the usual system notice I always see in migrated questions, in the site where the question is migrated. I am not sure what is the difference between a post notice and a system generated notice. For me, all the notices are system generated. – kiamlaluno Dec 28 '17 at 12:17
  • Well, there is some difference between when you lock a question (or when a question has a bounty) and the one on migrated question then. The former you can remove (edit?), the latter you can't, right? – rene Dec 28 '17 at 12:21
  • @rene Oh... Yes, that is correct. I cannot edit the notice I am referring, in the same way I cannot edit the notice for a question closed as too broad. – kiamlaluno Dec 28 '17 at 12:26
  • @Catija. Nope. When it was migrated, the link was http://, not https://. And the http:// link would still work, as a redirect. It should have been left as it was (HTTP), or updated properly (HTTPS and new domain name). Related. – TRiG is Timothy Richard Green Dec 29 '17 at 19:53

You must log in to answer this question.

Browse other questions tagged .