I ran into serious trouble with RealURL and TYPO3. Here's the scenario.
I'm working on a website using German by default and offering English translations. So far that works great. The URLs look something like this: http://mydomain.com/en/about-us
The root page as such works only in German, the default language http://mydomain.com/
Once I'm using it like this http://mydomain.com/en/ i end up with a 404 message.
The page as such works when I hand it some GET variables like this http://mydomain.com/?L=1
I was unable to fix this issue as of yet.
The page tree looks a bit like this
* Common Root (Standard page)
|-> * Common Data (Folder)
|-> * mydomain.com (Standard Page / Rootpage enabled)
----|-> Homepage (Shortcut to "mycomain.com", used for navigation only)
----|-> About us (Standard page)
----|-> Contact (Standard page)
I suspect this shortcut page to cause some trouble however wasn't able to do anything about it.
The RealURL Config is auto generated so no fancyness in there.
I'm using TYPO3 4.7.7 with RealURL 1.12.3.
Does anyone have an idea what could cause this problem?
cu
Roman
I had exactly the same problem using TYPO3 6.0.0 and also RealURL 1.12.3. Though I wasn't able to find out the cause, I just realized that the following workaround helped me:
Try to replace your current home page with a copy of itself (don't forget to define it as rootpage in your RealURL configuration).
Related
First: i am kind of a beginner in web administration. Please be patient ;)
I got a cloned VM from a server with a typo3 website on. i want to make it a test server to test updates and stuff before trying it on the real site.
I want the typo3 website to use staging.mywebsite.com instead of its normal url, but i am not sure where i need to change stuff in order for typo3 to work correctly.
what i did so far:
renamed the folder under /var/www/old.mywebsite.com to staging.mywebsite.com
change entries in /etc/hosts
But i am quite sure i need to change some config files too. Typo3 Version is 9.5
I found this:
TYPO3 How to change the name of a TYPO3 website
But i think thats not what i need?
Thank you in advance.
The URL for the website is defined in the site configuration, see here.
You should modify the entry point as shown in the second image of the documentation (2) or just use the slash "/".
In your example you should use "https://staging.mywebsite.com/". Please keep in mind not forget the slash "/" after the domain.
I'v installed TYPO3 9.5.5 on a stage server, where everything works right till I configured the slugs and the sites configuration.
If I want to configure the slugs of the root page with a slash / TYPO3 saves it with a slash one /1.
So if I know go into the frontend and load the rootpage of my site I get a 404 Error.
I think that is because TYPO3 makes the /1 thing.
If I now load the page with stage.myserv.de/1 TYPO3 navigates to the correct rootpage.
How can I fix this please.
All my other slugs like stage.myserv.de/band works fine after editing it.
I tried also to make a "workaround" with sites configuration using the /1 as rootpage. Now the rootpage works, but all other pages have the "prefix" /1 in it like stage.myserv.de/1/band and so on, but the first /1 isn't editable anymore.
Hope someone could help.
Best Thanks
this bug is is related to https://forge.typo3.org/issues/87884 and is worked on afaik
I am trying to switch to a second language using polylang plugin in my Wordpress test site.
I don't have relevant code to show, I haven't identified problem code associated with this error.
What I expect is to find myself on the Home page equivalent in the second language no matter which English page I was on previously.
Instead I am taken to the Spanish version of the About page, not Home page equivalent. Also, the page content is made up of not just that page's content but all of the content from every page on the site is stacked on top of each other - including old versions of pages.
If I subsequently click on the Spanish menu which displays as expected, the next page displays perfectly. When I click back to the About page (the page previous acting as a site catch-all) everything is as it should be. So the problem only manifests on the initial switch to a second language.
Switching back to English does not cause the problem to reoccur, everything is fine in this case. It is only when initially switching from English (site primary language) to Spanish that the problem occurs.
I am using the 'X' Wordpress theme for this 'local' version of my site. My Wordpress & free polylang versions are up to date.
Any help with this problem would be much appreciated.
Thanks, Brent.
I have come up with a solution for my problem.
This isn't the most elegant solution but I need something that works now so here goes.
I noticed that when switching to Spanish I was taken to the page: http://localhost/www.ecia.com/es/ i.e. no specific page, fine if I had an index.php file in that location but I don't. The result is I am taken to the page with the bloated content.
My work around was, use a redirection for that URL to the page I want the switcher to go to i.e. instead of http://localhost/www.ecia.com/es - I redirect to http://localhost/www.ecia.com/es/casa
This is not the best fix, but I have found it difficult going any deeper into how Polylang plugin works so it will suffice for my purposes.
Brent
I have solved this by:
Go to language/setting/url settigs
Uncheck "Hide URL language information for default language "
I am creating my first website in TYPO3 with TemplaVoila.
I followed the tutorial: http://www.training-typo3.com/2008/12/15/typo3-multi-language/ to make my site multilingual. Everything works fine except when I choose a language other than default language in the frontend, page shows content in every language.
How to solve this problem?
Finally I got it. Added following line to main ts template.
config.sys_language_overlay = hideNonTranslated
It might be a typoscript setting, can you put the the URL and your main typoscript setup here?
I'm pretty new to TYPO3 and currently stuck with the following issue:
I copied the templates from another webpage that is currently in business.
When I'm on the startpage of my homepage (www.domain.com) and click on one of the links it contains I always get an error 404. The link that is generated looks like this.
http://www.domain.com/testpage.440.0.html
So I guess something like RealUrl was in use on the webpage that I copied from? Do I understand this right? I don't see that RealUrl is installed though.
However If i manually change this link to
http://www.domain.com/?id=440.0.html
the site is being created.
How does Typo3 know to generate a page when it receives the first version of these two links?
Does not really look like a standard out-of-the-box REAL URL url. That would rather have been /testpage-404.html . So maybe the problem is somewhere else, could be:
simulate static (check if that extension is running). A common mistake is to run real url an simulate static at the same time. If you do not need speaking urls for the moment, just uninstall simulate static.
make sure you add a domain to your shortcut. Use the the list modul and select the root shortcut. Then click create new record, select domain. and enter your domain there. Flush all the caches and try again.
If you'd post your TS Code (of the root shortcut page) here, I could probably tell what's going wrong.
real url configuration typically use .htaccess files.. maybe that file still contains information from the original destination.
check if the root ts contains some baseUrl statement
Which version of TYPO3 are you using?
HTH, but feel free to post more infos.
If your typoscript template is expecting to find realurl and its not installed as a plugin, that could be the cause. You'll need to either install it, or find the settings in the TS template and remove them.
Try the template object browser to look for it (use the template tool, click to the site root, then use the drop down menu in the r/h pane to choose the Template Obect Browser.)
How does Typo3 know to generate a page when
it receives the first version of these two links?
Any page request that it doesn't understand will give a 404 error.