iso-639 | Ruby gem with ISO

I am using the Rails Geocoder gem to geocode the latitude and longitude of a street address submitted by a user. I would also like to automatically pull a users IP location to populate a home screen with other user submitted addresses near their location.

I'd like to use an API key for IPinfo to get the user's location and a different API key for Google to geocode the lat/lng of the street address. Previously, when I call out two api keys I get a warning message stating the first key was overwritten by the second, probably because they had the same name.

I saw this previous post where a user answered saying they can do it by passing the service as a lookup value but how did they set up the api key in the geocoder.rb config file? Did they change the api name for the second service? Did they have to add in another config file?

Any help at all would be appreciated. My current config file is below. I commented out the IPinfo lookup for now so I can still geocode items in production. Thank you.

How can I set the Typo3 V10 Site Configuration to do this:

1. Everything incoming go to one site root page:
2. Except this one subdomain, which goes to a separate root page:

I have a web app based on Typo3 8.7 that I'm trying to upgrade to v10. In the 8.7 app, each customer organisation has a unique subdomain - school1.webapp.com, anotherschool.webapp.com etc., all pointing to the same typo3 site root page. Each time I need to create a new customer, all I have to do is to add a new sys_domain record and a custom plugin picks up the current sys_domain record as the means to separate customer data. A wildcard sys_domain record of *.webapp.com the picks up any misspellings and redirects to a separate page.

The one exception is auth.webapp.com which handles oauth authentication for all customers and goes to a different site root page.

This allows me to add new customers with just a simple form, which adds a new sys_domain record and job finished.

I now need to upgrade to Typo3 v10. I can detect the incoming subdomain to split between customer data easily enough, but I'm having problems with the new Site Configuration tool. All I need is to route auth.webapp.com to one site root page and everything else incoming to another.

My current setup seems to work for getting everything to route to the site root

I installed TYPO3 v10.4.9 with boostrap package and created a few custom pages to try things out. I noticed that the "speaking URLs" are not working and I have no idea why. Note that I am a total bigginer in TYPO3, so I'm probably missing something obvious.

Example: We have a page called Photos. The URL created by "URL Segment" in Page module > "Edit page properties" is https://example.com/photos and the ID of the page is 84.

If I click on the view icon in the Page module, URL https://example.com/photos opens in the frontend and I get a message that says "Not Found - The requested URL was not found on this server".

On the other hand, if I type URL with ID in the browser manually, like so: https://example.com/index.php?id=84, it works perfectly fine. This problem is present for every page I create. I have created site configuration. Below is the content of config.yaml:

I have some problems regarding the page translation on one of my websites which contains 2 languages. German is the default and English is the next one. Following is the site configuration.

I've got a problem with the language localization in TYPO3. The site works fine, I don't get any warnings or erros in the 'normal' TYPO3-log in the backend. But every minute I got a new line in sitename/var/logs/typo3_abc.log saying

I've built a site in TYPO3 9 which was working just fine. Then decided to upgrade von TYPO3 10 (10.4.4), did the upgrade wizard, database check etc. It all looked good. Now when I go to Web -> Page and inside the pagetree click the root page or a subpage of it, I get this error:

Oops, an error occurred! TypoScriptFrontendController must be constructed with a valid SiteLanguage object or a resolved site in the current request as fallback. None given.

More information regarding this error might be available online.

online link: https://wiki.typo3.org/Exception/CMS/1561583127 (there's nothing as of now)

The error makes me assume that I made an error with my site language. When I go to Site Management -> Sites, everything seems to be configured correctly for my Default Language.

my config.yaml

we are updating an ancient TYPO3 project, we already run on TYPO3 9.5 and its looking good after alot of refactoring.

now i rework the ext:indexed_search section which got implemented into the T3Core (sysext:indexed_search). so if i disable/remove my site configuration, the search just works out of the box. once i enable our default site configuration, holding: