Bug #15206
closed0 applied to domain name when other domain is inaktiv
0%
Description
if there are two records with one domain name, but one is inactive, than there is a zero appended to the tld, e.g
www.example.com (inactive)
www.example.com0 (active)
I think, this is a bug, caus there is no reason, why the 0 should be appended to the domain name.
(issue imported from #M1872)
Updated by Sebastian Kurfuerst about 19 years ago
Hi,
IMO this is appended because the domain name is supposed to be unique throughout the installation... Makes sense I think, doesn't it?
I don't think this will be fixed, in which case do you have an activated and a deactivated record of the same domain name?
Greets, Sebastian
Updated by Alexander Maringer about 19 years ago
In which case does it make sense to have the address http://typo3.com0 ?
The one record was on a new site installation, which was not activated yet, and the other was as a redirect on a project page.
Updated by Sebastian Kurfuerst about 19 years ago
"In which case does it make sense to have the address http://typo3.com0 [^] ?"
Of course it sdoesn't. However, this is the way TYPO3 automatically resolves duplicates when there the field is defined as unique in TCA.
Greets, Sebastian
Updated by Alexander Maringer about 19 years ago
OK, I think, the function should be changed, so that it only append the numbers for unique if there are more than one ACTIVE entry.
Updated by Sebastian Kurfuerst about 19 years ago
Hi cooky1976,
in principle, this idea is not bad, however, this won't work because of practical reasons I think. A record can be inactive/active because of various reasons: hidden, start/stoptime, access settings. When there are some automatic changes of the "active" state like a start/stoptime, the entry still has to be unique.
Of course, in this special case, it would make sense to change it, however this would have more severe impacts on other parts of a TYPO3 installation, and will most certainly break things.
Suggestions are of course still welcome!
Sebastian
Updated by Sebastian Kurfuerst almost 19 years ago
I am closing the issue now as "won't fix".
Greets, Sebastian