Have following problem.
I use TYPO3 version 4.7.1 and for both sites the domain record is configured.
Internet site → www.domain.com → root id = 77
Extranet site → service.domain.com → root id = 104
But still, both sites will be redirect to the internet site.
How must I set this up?
Did you create a template for each domain? Did you set those templates as root?
See http://wiki.typo3.org/Multidomain for more details.
Also go to the page properties/edit -> behaviour -> Miscellaneous -> Use as root: check the checkbox.
Clear caches.
If possible set the following:
[globalString = ENV:HTTP_HOST=domain.local]
config.baseURL = http://domain.local
[globalString = ENV:HTTP_HOST=www.domain1.tld]
config.baseURL = http://www.domain1.tld
[globalString = ENV:HTTP_HOST=www.domain2.tld]
config.baseURL = http://www.domain2.tld
[global]
Related
I have created enonic project hello-world site. the content studio shows site URL as /hello-world
But when browser calls localhost:8080/hello-world it returns 404 error log from enonic server.
How to fix this issue?
You have to configure your XP_HOME/config/com.enonic.xp.web.vhost.cfg file with something like this:
enabled = true
mapping.a.host = localhost
mapping.a.source = /hello-world
mapping.a.target = /site/default/master/hello-world
mapping.a.idProvider.system = default
You can read more about it in the official XP-documentation about vhost.
I tried to use:
Behavoir >> URL Alias - "team"
and receive:
http://remax-prestige.pl/typo3-95/index.php?id=team
team is ok, but how I can receive the link without index.php?id=
You need to add a site in the Site Management module. When having a domain and path prefix, TYPO3 can make nice URLs.
You need to add TrailingSlash Settings in your Site Management config.yaml
routeEnhancers:
PageTypeSuffix:
type: PageType
default: '/'
suffix: '/'
index: ''
map:
'/': 0
'sitemap.xml': 1533906435
This works for me.
TYPO3 v9.5.0 - Error message: Requested page does not exist /robots.txt
I have a TYPO3 9.5.0LTS and use the bootstrap package theme. It seems to be all working ... but quite often I get such error messages:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1518472189: The requested page does not exist | TYPO3\CMS\Core\Error\Http\PageNotFoundException thrown in file /is/www/typo3_src-9.5.0/typo3/sysext/frontend/Classes/Controller/ErrorController.php in line 82. Requested URL: domain/robots.txt
What causes this and how to prevent this? Or how do I create a robots.txt in v.9.5 ?
In TYPO3 9.5 you can add a robots.txt in your Sites module.
Sites -> Choose your site -> Static Routes -> Create new.
Static Route Name: select "robots.txt"
Route Type: select "Static Text"
Static Text: Select "robots.txt Example Content"
Save. Should be fixed now.
This will work for all TYPO3 versions. For TYPO3 V9.x use the solution by Thomas Löffler.
Your server configuration (apache? .htaccess?) will hand over any request to a source that is no file and no directory and no symbolic link to the index.php file which is TYPO3.
In your case, you do not have a file robots.txt. So TYPO3 wants to handle it, but has no resource with that name. This creates a 404 error in TYPO3.
To prevent this, jst create the robots.txt file on your webserver in the DOCUMENT_ROOT folder
So what is a robots.txt file anyway.
This is a method to tell search engines how to behave on your server. It contains recomendations to the search engines' crawlers, when to stop crawling (like typo3_src folder). It is requested by the crawlers automatically and regularly.
I'm using Yunohost to host multiple "apps" on my server that runs Nginx.
Yunohost uses SSOWat to redirect some stuff to the login/apps list page.
I have some apps (NextCloud, RoundCube,…) inside subdirs and a "custom webapp" my_webapp.
I would like this :
https://mydomain/nextcloud,etc -> /webroot/nextcloud/, etc
https://mydomain/ -> https://mydomain/site = /webroot/my_webappp/
https://mydomain/other -> https://mydomain/site/other = /webroot/my_webappp/other
Currently the first work but adding
location / {
rewrite ^ /site;
}
to the Nginx config seems to redirect some webapps (not all thanks to SSOWat). Especially, the Yunohost user login/apps list is redirected to site/ :(
How can I prevent some subdirs to be redirected but have the other ones redirected to site/ ?
I'm using a Sitecore install with multiple sites. When linking from example1.com (/sitecore/content/example1) to an item under example2.com (/sitecore/content/example2/about)
Sitecore is not generating the link correctly for any cross-domain links. It is generating:
http://www.example1.com/example2/about.aspx
This is what is expected:
http://www.example2.com/about.aspx
The same thing happens from example2.com when linking to example1.com or any item under that site.
Both sites are defined in the web.config.
The rootNodes are both "/sitecore/content"
The start items are "/example1" and "/example2" respectively.
Rendering.SiteResolving is set to true
Rendering.SiteResolvingMatchCurrentSite is set to false
I'm using sc:link to generate the links.
Sitecore.Links.LinkProvider's alwaysIncludeServerUrl is set to true
If you are using hostName with wild cards (eg. "www.example1.com|example1.com"), you need to set targetHostName="www.example1.com" on your entry.
Even if you only have one domain, set targetHostName, as there is one thing/function that only looks at targetHostName. Eg. GetItemUrl() doesn't work as planned without a targetHostName and in 6.5.0 ver. 120706 it doesn't account for stuff set in the web.config. This is a bug and one they hopefully have fixed in future version. If you expirience the problem look here for a solution:
http://sitecorepm.wordpress.com/2010/08/04/using-cross-site-links-dynamic-links/
Have you set the hostName value of the <site> entry in web.config?
<site name="example1" hostName="www.example1.com" ... />
<site name="example2" hostName="www.example2.com" ... />
There's a very good blog post on this here: http://blog.paulgeorge.co.uk/2011/05/01/sitecore-linkmanager-inside-out-muti-site-and-sub-site-setups/ It looks like you've covered everything else required to make this work.