hook in t3lib_BEfunc::firstDomainRecord()
implements a hook into t3lib_BEfunc::firstDomainRecord() for further domain record name processing
(issue imported from #M15264)
Updated by Alexander Opitz over 6 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Updated by Sebastian Mendel over 6 years ago
- Status changed from Closed to New
can you elaborate a usecase for this?
we need to distinguish the primary domain by some more aspects than just the sorting or current domain (Host) in request.
- like current system (deploy target, incarnation of system)
- run mode (testing, live)
- origin of user
- use domain not in DB (dev systems with Live/production DB)
Updated by Benni Mack about 3 years ago
- Status changed from New to Needs Feedback
can you verify if the new site handling and the base variants solve your issue in TYPO3 v9? We've made lots of improvements to overcome conceptual issues in this area in the last months.
For TYPO3 v7 and TYPO3 v8, I've developed a tool to replace sys_domain records on deployment, to only have the "active" domains in an installation - https://github.com/bmack/site-importer
Hope that helps.
Let me know if there is still something you need for TYPO3 v9 / TYPO3 v10, otherwise I suggest to close this ticket.