Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
translation.module
Priority:
Critical
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
4 Oct 2014 at 14:34 UTC
Updated:
29 Apr 2015 at 14:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
schnitzel commentedComment #2
schnitzel commentedComment #3
schnitzel commentedComment #4
schnitzel commentedComment #5
schnitzel commentedComment #6
schnitzel commentedscreenshot and log of new testbot run, which proves it works :)
Comment #7
alimac commentedSmall nit: in the surrounding comments the verb is in command form (Add, Change, etc.) so I think this comment should use "Get" instead of "Getting".
Comment #8
schnitzel commentedaddressing #7.
thanks for review :)
Comment #9
alimac commentedI downloaded the new testbot containers (https://www.drupal.org/project/drupalci_testbot) and ran the tests on them, which passed. I read through the patch and verified that it replaces the previous method of obtaining the hostname (
gethostname()) with a more reliable method usingparse_url($base_url, PHP_URL_HOST).Marking as RTBC.
Comment #10
schnitzel commentedComment #11
alexpottI think we should have a replacement for
global $base_urlhowever our concept and what is available on the Symfony request is different. Going forward with this patch to unblock testbot improvements.Committed 853741a and pushed to 8.0.x. Thanks!
Comment #13
webchickHonestly, I don't think we even have to be all that fancy. You can see that the domain below is completely made up (it.example.com) so in this case, we should probably just make it "example.com."
Here's Yet Another Follow-Up where we can try and do that: #2350937: Remove fanciness from various language tests
However, gethostname() is really just a standard PHP function, not anything overly fancy, so it's weird we would not be able to call it and instead have to do workarounds. Filed #2350935: Testbots should not break when gethostname() is called for that.
Comment #14
alimac commented@webchick in this particular test, after submitting the form it redirects to the default language domain URL, so the test would fail unless the host was configured to use example.com (one of my earlier patches used en.example.com: https://www.drupal.org/node/2343943#comment-9192485).
Comment #15
webchickYep, just figured that out in the first sub-issue. :( The point about testbot NG brittleness I think is still worthy of the second issue though, since the workaround here is quite advanced.
Comment #17
yesct commentedfixing the tag, so I can delete the least used one.