I installed the extensions Speaking URLs (realurl) and News. But if I enable RealURL every news (list view) is redirecting to the first news-item I clicked.
The URL of the news detail page is correct but the content is wrong.
All caches via Install Tool are empty...
Does somebody knows how to fix it?
I'm thankful for every help.
i think this is cache issue. first of all take DB backup after clear all realurl cache tables in DB.
Related
I am working with the extension news on TYPO3 9.5. I have a project with few microsites and I want to use the news there. In the microsite homesite news(list) works but when I click the link which points to a detailed view of news, this leads to 404 and it does not work.
Detailed view does not work on Microsite.
I tried configuring Starting Point without success. Do i have to configure categories?
Any idea where I can also check?
The Solution was to change TCA to "unique" (TYPO3 Core Routing) due to URL resolving.
More can you find here:
https://forge.typo3.org/issues/91397#note-12
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
TYPO3 Environment
TYPO3 v9.5.3
EXT:news (7.0.8)
EXT:indexed_search (9.5.3)
Use Composer: No
The Problem
On EXT:indexed_search result listing page, Custom extension record's slug URL are not generating. The slug only contains TYPO3 page URL.
Example; The URL should be http://thedomain.com/news/detail/announce-first-news/, but it currently only generates http://thedomain.com/news/
As per our analysis, it seems TYPO3 v9 site management's slug feature cause issue, and there could be following possible issues.
Issue #1
The major issue is, After enabling site management's slug setup, No more indexing happening for a custom extension.
Issue #2
Indexing result will lose after the page will refresh or move to another page (After clear cache data will show again).
Issue #3
If we create new records for a custom extension, then the created new records will not be indexing.
Issue #4
If anyhow, we have done the indexing and search works well, then at search result listing page, The link redirect to the main action like Listing. Because cHash is missing to each record, That's a bit strange!
Does anyone have any idea/solution? Highly appreciate your any thoughts, Thanks a lot!
Cheers,
Team NITSAN
This has been fixed with release of 9.5.5, released 4.3.2019. Check out the release notes which you can find here: https://get.typo3.org/release-notes/9.5.5
The issue for the bug is https://forge.typo3.org/issues/86994
However there has been also a regression detected which is described at https://forge.typo3.org/issues/87855 but it has already been fixed as well. The bug occurs if MYSQL strict mode is used
I have a problem whose solution is certainly very simple, but it does not come to my mind at the moment :/
I have a multi-domain TYPO3 (6.1) installation and in one of the websites I need to temporarily show only one subpage, and over the rest of the pages I will work/update so I can not delete them. It is important that someone after entering a URL or going to the page from the Google search results has not opened this page, and has been redirected to this temporary.
I've tried the mount points but something does not work ...
Please help.
You can exchange the domain-records.
Make a new page on it's own (independent from the configuration of the domain it should replace). so it is a root-page. give it a domain record and disable the domain record of the pagetree it should replace.
Be aware to change the rootpageid configuration in realurl.
You also may need a special configuration for 404 handling for this domain as the most requests will be a 404 (or better 503).
And hurry up to update your system. TYPO3 6.1 is out of service for a long time.
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.