search

TYPO3-Headless / headless

TYPO3 Headless JSON API providing content for PWA application (e.g. javaScript apps like nuxt-typo3)
https://t3headless.io
GNU General Public License v2.0
157 stars 60 forks source link

Unexpected `frontendBase` configuration behavior #681

Open schloram opened 10 months ago

schloram commented 10 months ago

Describe the bug I'm creating this issue out of my last comment in #674 because in my eyes it's still a weird/unexpected behavior with the frontendBase configuration

To Reproduce Steps to reproduce the behavior:

  1. Set the base for the default language to https://my-backend.com/de/
  2. Set the frontendBase for the default language to https://my-frontend.de/
  3. Now click the "View webpage" icon on a page in the default language
  4. The url that opens is https://my-frontend.de/de/

Expected behavior Since the backend and the frontend base url should be independent I would expect the url https://my-frontend.de to be opened. But it somehow merges the path from the base and the url from the frontendBase.

How else could we achieve that the backend and the frontend follow a different language logic with the languages (one with the language inside the domain and the other with the language as path)? 🤔

Screenshots If applicable, add screenshots to help explain your problem.

TYPO3 version and TYPO3 Headless version TYPO3: v12.4.7 Headless: v4.2.3

Additional context

twoldanski commented 10 months ago

Hi @schloram this is not a bug, as I mentioned in previous thread. This is how TYPO3 routing is working. EXT:headless only switches domains, not paths of the routes. We're replacing on the fly domains only for that, TYPO3 and FE app have to have different hosts, but routing is same as you would run "classic" TYPO3 installation. I know it can be a little confusing, but in your example, you want to change how TYPO3's routing works.