We're running TYPO3 9.5 with correctly set up Site Configuration. The main domain has multiple subdomains which have their own Site Configuration.
domain.com
sub1.domain.com
sub2.domain.com
sub3.domain.com
All these urls point to a different Site Configuration, which works fine. But when a user types sup1.domain.com instead of sub1.domain.com, "No TypoScript template found!" is shown. Within the Site Configuration "Error Handling", "Show content from page" is set up for error 503.
The configured error page is not showing, but the default "No TypoScript template found!". How could we show an actual TYPO3 page when a subdomain is entered wrong?
The 404 page works fine, but only with segments after the actual domain, eg. sub1.domain.com/does-not-exist shows the 404 page, as configured.
As already noted by Julian Hofman you should redirect all 'non-existend' subdomains to your main (sub) domain.
Sure, in this situation you cannot handle typos, but this solution is very fast and error-safe. TYPO3 can only handle "known" (sub)domains.
Redirecting all unknown subdomains can be done via .htaccess (on Apache) or your domain hosting admin-panel .
HTH Henrik
Related
I have a domain with GoDaddy called "livingmiracles.org". For years I had this domain forwarding to my livingmiraclescenter.org Joomla website. Recently, I discovered that the way the livingmiracles.org domain now forwards to our livingmiraclescenter.org site has changed and has left me with broken links on almost all of the over 60 websites I manage.
This is what used to happen:
Any URL of the livingmiraclescenter.org website would be able to be displayed with the livingmiracles.org domain instead. For example, the following URLs were interchangeable:
livingmiraclescenter.org/david-hoffmeister.html and
livingmiracles.org/david-hoffmeister.html
livingmiraclescenter.org/contact.html and
livingmiracles.org/contact.html
livingmiraclescenter.org/spiri-tv.html and
livingmiracles.org/spiri-tv.html
Also, variations of the above without ".html" would work.
Now, none of this works anymore. For the "livingmiracles.org/" links above, now, either the livingmiraclescenter.org home page pulls up or I get a GoDaddy error page.
I called GoDaddy and they confirmed a change in the way they handle domain forwarding now.
Can anyone suggest a simple/smart way—perhaps a RewriteRule or something like that—that I can set up somewhere (where?) to handle those specific page redirects? Basically, I want all my livingmiraclescenter.org links to be interchangeable with livingmiracles.org links like I wrote above in those examples.
Thank you so much!
Jutta
Does anybody have sophisticated knowledge about running a multi-domain-site using a single typo3-instance ?
E.g. I have 2 domains, both being served by the same webserver, using different vhosts. What I want to achieve, is both vhosts pointing to the same document root, where a typo3-instance is installed. This TYPO3-instance should check by typoscript, which domain was used in the request and forward requests for each domain to a specific subpage ("landing page for that domain").
I need this to work in a productional & stable environment, due to custom-self-developed extensions, which provide necessary data for both installations, also specific extbase-domain-models should be usable in both domains etc.
I am already able to check the requested domain via typoscript-conditions. What I am missing, is some info, about how I could possibly realize the redirection, without the client being redirected to the landing page each time while using sub-pages of the landing-page. Do I need to set cookies for this !?
Thanks in advance, Oliver
In TYPO3, you can combine several sites (each with a different domain) in one Installation. This already works out of the box.
So, for this requirement
This TYPO3-instance should check by typoscript, which domain was used in the request and forward requests for each domain to a specific subpage
it is not necessary to add a check for TypoScript, TYPO3 will automatically resolve the URLs.
Page Tree:
pid=0
| --> root page 1
| --> root page 2
On both root pages, enter page properties : "Behaviour" checkmark enable "Use as Root page"
On both root pages, create a TypoScript template, edit it, got to tab "Options", checkmark "Rootlevel". Have this TypoScript template include your general TypoScript configuration, e.g. via "static includes" (ideally you put your TypoScript configuration in an extension)
Since TYPO3 9: configure a site for each page tree under "Site Management > Sites". Before TYPO3 9: On both root pages create a "Domain" record
I am new in TYPO3, I copied a TYPO3 system to localhost so I can develop offline, no my problem is all the link points to the live site. my_live_cite.com
What should I change in the backend to redirect all links and ref to localhost ?
Check and adapt for sys_domain records (see root page PID=0).
See also TypoScript (TYPO3 backend modul Templates) and check/adapt the domain you are looking for to change. Select in TypoScript Template module TypoScript object browser where you can search in constants and setup (configuration) for strings.
Cause of TypoScript can bee different ways, to handle domains. Have a look at config.baseURL and maybe page.config.baseURL
Has anyone played with the new redirect feature in Ektron 8.6?
We tested it (in 8.6.0) before upgrading and were happy with it. But when it came time to do the upgrade, Ektron had released 8.6.1, so we upgraded directly to that.
Now we are having trouble with the redirect feature. (Yes, we should have tested everything again in 8.6.1 before upgrading)
Now if we try to add a redirect rule for an existing page in the CMS, it does not work.
But if we create a redirect rule for a page the does not exist, then try to hit that address, the redirect works fine.
We need the redirects to work for existing pages in the CMS.
To clarify what "working" and "not working" means...
If I have an existing page in the CMS with manual alias of "/erc/lucien.apsx", I can create an entry in the redirect table like this...
Adding this entry generates no errors, but when I visit the page, all I see is the regular old page I created. NOT the Google site it should be redirecting to. I do not get any 404 errors.
But if I create a redirect entry for a page that does not already exist, like this...
It works perfectly. If I try to visit the /erc/fake.apsx address, I end up on the Google site, as expected.
(FYI, we create a "fake" page in the CMS for external content so we can attach metadata to it and make it searchable in taxonomies, but then provide a link to the "real" page. I want to use redirects here so users don't have to do this extra click)
I suspect it might be cache related -- the original URL gets cached as an alias, then subsequent requests to that URL are redirected to the quicklink without the need for a db look up. When you add the redirect, it’s probably not clearing the old item from the cache. I'd try an IIS reset after you add the URL redirect and see if that clears up the issue.
An "outside the box" (of Ektron) answer to this is to place the redirect at the web server rather than in the Aliases section of the Ektron CMS.
The server I work on uses IIS and I have this set up for several pages.
When i am trying to fetch pages under direct mail folder in TYPO3 backend, It gives following errors
The plain text content could not be fetched.
The HTML content could not be fetched.
This is an error that most of the time shows up if you are missing your templates include static section.
Login to your TYPO3 Backend with administrator access. Next goto your, for example, root template. Select the "Includes"-tab and make sure the next "Include Static" are included:
Direct Mail Content Boundaries (direct_mail)
Direct Mail Plaintext (direct_mail)
Hope this helps you out.
Try adding your server ip and domain to the /etc/hosts file if you are linux...if you are in windows to \System32\drivers\etc.
A deitalled description can be found here:
http://devbackyard.blogspot.pt/2012/10/direct-mail-typo3-content-could-not-be.html