When entering a language domain at admin/config/regional/language/edit/en it should check for the protocol, but that check doesn't happen right, since there's another patch that will remove this so people can use the language domain on http and https at the same time, this is just for reference
related: #1250800: Language domain should work regardless of ports or protocols
Comment | File | Size | Author |
---|---|---|---|
#13 | i1261440.patch | 1.33 KB | attiks |
#1 | i1261440.patch | 1.54 KB | attiks |
Comments
Comment #1
attiks CreditAttribution: attiks commentedAttached a patch that changes the description, the patch depends on #1250800: Language domain should work regardless of ports or protocols, so that one has to go in first.
Comment #2
Gábor HojtsyThis sentence does not compute for me: "URL to use for this language, do not any protocol, nor any port.".
Comment #3
attiks CreditAttribution: attiks commentedGabor, something like this:
Domain name to use for this language, do not use any protocol (like http://) or a port (like: 88).
1 days to next Drupal core point release.
Comment #4
Gábor HojtsyWell, we previously suggested they MUST provide a protocol, right? So what about just saying that the language detection is independent on protocol or port, and let them provide it for backwards compatibility / if they want it anyway. The code change should be backwards compatible anyway. BTW why not do this in the same issue as #1250800: Language domain should work regardless of ports or protocols? I don't see them being unrelated.
Comment #5
attiks CreditAttribution: attiks commentedDomain name to use for this language, you may optionally specify a protocol or a port, but the language will be detected based on only the domain name.
Comment #6
attiks CreditAttribution: attiks commentedComment #7
Gábor HojtsyTagging, fixing title.
Comment #8
yoroy CreditAttribution: yoroy commentedA first rewrite:
- Removed the 'don'ts': No need to talk about the things that happen automatically anyway.
- Shorter, single example
- Maybe 'Detection and selection' should be a link to that settings page? Not sure.
Comment #9
attiks CreditAttribution: attiks commented@yoroy, what they have to enter isn't technically a URL, they have to enter a domain name:
Comment #10
yoroy CreditAttribution: yoroy commentedWell, that part I did not change ;-p
In that case, domain is indeed better.
Comment #11
attiks CreditAttribution: attiks commentedso we have
Comment #12
yoroy CreditAttribution: yoroy commentedStill pretty long, but yes.
Comment #13
attiks CreditAttribution: attiks commentedupdated patch
Comment #14
Gábor HojtsyLooks good to me. Still think this should be rolled into #1250800: Language domain should work regardless of ports or protocols, or if not, marked postponed on that. That issue makes it work as described here, so I think easier would be to get the two in at once.
Comment #15
attiks CreditAttribution: attiks commentedDone