I use tx_news 4.3.0 with TYPO3 7.6.12 and realurl 2.0.15
From time to time i get detail links which show to a wrong detail page.
e.g.
veranstaltungen/talks/detail/xy-talks/
shows to another detail page:
veranstaltungen/talks/detail/z-talks/
after clearing the fe cache the link ist ok.
how to avoid this?
I got the same problem some time ago.
I use for many TYPO3 system a single page for news list and detail.
I wanted to have URLs like example.com/news/ für list view and example.com/news/this-is-a-news/ as detail URL.
To archive this, I configured realurl to skip controller and action for news links. But in the link configuration inside the news template, they were used to build the link.
Since realurl does not create a new cHash for a link (since Version 2.0.12 I think), the link generated by realurl does not match the cHash that was generated in TYPO3 and cached by realurl. So TYPO3 provides a wrong cached version of this page. I my case, it was the first news entry, that were called and cached. This news entry got displayed every time I clicked on a news.
To avoid this, I removed the controller and action skipping from realurl and add some TypoScript (link.skipControllerAndAction = 1) to my news configuration.
I think you might have a similar issue. Try to disable realurl in a dev environment and try if this happens again. When this fixes your problem, check your realurl configuration for news.
Related
Typo3 10.4.16
I am not able to create a sitemap.xml with the system extension SEO.
My current understanding is, that the only requirement is, to install SEO and include static template. Than I should be able to see a sitemap with https://yourdomain.com/?type=1533906435. But I always see my start page and not a sitemap.
Under EXT:seo/Resources/Public/CSS/Sitemap.xsl I see a file, but it is 1 month old has nothing to do with my site.
Is there any possibility to trigger seo to generate a new sitemap?
Output from Template -> Template Analyzer:
Or what can I check?
Edit 2021-06-14 10:10
I have moved up the seo static template to to top. No change!
Yes there is a redirect from www.mysite.xyz to www.mysite.xyz/startseite!
When I use a different type, no changes.
This is the a screen shoot from the Object browser:
Edit 2021-06-14 11:00
I am a big step forward. The problem was the redirect, thanks to Richard.
But now I have a problem with the redirect. Even if I include under sites->StticRoutes a new Route with sitemap.xml it is not working together with the redirect.
So the next I tried is the new feature of seo to set xslFile. So I used xslFile = sitemap.xsl and also tried xslFile = /sitemap.xsl but both are not working!
Is it not possible to define a xslFile on the root?
In the past we organized pages inside the page-tree by putting them into pages like "meta" or "submenu". These pages had the option "exclude from speaking url" so their name was not rendered to the url.
Is there any option to do this in TYPO3 9.5 to ignore pages from generating the "slug"?
as example:
WRONG: https: //www.somedomain.tld/metamenu/terms-and-conditions/
RIGHT: https: //www.somedomain. tld/terms-and-conditions/
How to "ignore" the page "metamenu" for automatic-generating the slug?
Best regards
Johannes
It is mandatory for a page to have set a slug and every menulevel will generate another url part. It is not possible to exclude a page - think about how to access this page via url
Here Mathias Schreiber tells a bit about this feature: Feature Demo - Speaking URLs Part 1
The TYPO3 extension "masi" provides this feature, including an upgrade wizard that migrates the realurl tx_realurl_exclude settings.
Have you tried using a Folder instead of a "Page"?
page/page/page
somedomain.tld/metamenu/terms-and-conditions/
page/folder/page
somedomain.tld/terms-and-conditions/
You can leave the parent-page as it is and edit your child-pages. There you can delete parts of the urls in the slug-field.
There's a feature in RealURL for TYPO3 8.7 "Exclude from speaking URL". If set 'domain.com/page-one/' loads 'page-one' and 'domain.com/subpage-of-page-one/' loads 'subpage-of-page-one' with no need of 'page-one' in the URL.
The very same thing can be achieved in TYPO3 9.5 manually editing slugs but you can't set the parent page to be excluded from the URL automatically.
It's a missing feature.
I had the same Problem. Sadly there is no "good" solution as far as i know. But there is a little trick. You can fix this in the database. I deleted all my "slug"-entries in in the database for my pages. Then i wrote in all pages wich should not show in the url in slug "/". This does sadly not work in TYPO3, because the BE allows just one "/" and the second "/" will be changed to "/1". But in the Database you can do it. After you edited the slug for your page metamenu and other to "/", you can go into the upgrade-wizard in the installtools, reset the "generate slugs" task and run this task again. This is sadly the only solution i came up with.
I use TYPO3 8.7 and NEWS extension 6.3 and shariff-sharing.
When i share a news record on Facebook the publication goes well, but when i tried to go back to news record i get 404 error. I think the problem is a query parameter called attach to outbound links by Facebook and appearing in the news record URL. Something like http://example.com/newstitle/?fbclid=IwAR2QIndkh'. What i must do to correct this?
Any help would be appreciated.
As #Wolffc already noted, you need to add the parameter to TYPO3's cHash excluded parameters.
If you use realurl, you also need to tell realurl about it. The current master contains a change for that https://github.com/dmitryd/typo3-realurl/commit/2f1dfced4a2f64656f4091ab79ab307ff6daa469 - that makes realurl reconfigure TYPO3 to include the parameter.
Until it gets released, I suggested a common configuration that I use my realurl configuration (let realurl use the TYPO3 conf) here:
https://github.com/dmitryd/typo3-realurl/pull/650
You need ro add fbclid to the chash ignored parameters in the install tool
I am using TYPO3 9.5 and I created a root page with several subpages.
Before I created a site configuration the subpages were available as
/index.php?id=19
after the site configuration the url has changed to
/events
which is absolutely fine but my subpage cannot be found anymore. I get an 404 Error.
The subpage is still available under the old url but the new one doesn't work.
What can I do to fix this?
after changing the slug(path/path segment) for a page you need to update the slugs for all subpages manually.
The slug is generated automatically when the page is created. Probably your slugs were generated wrong before you build your site configuration.
Try to autogenerate all the slugs with the adapted wizard. You must do it by hand for each page as there is no wizard for page subtrees (yet). you might do the multi-edit in the list module for the slug field.
I have similar issue and no clue how to solve. See TYPO3 9.5 URL Routing with URL Segment is not working
Manual slug override, saving, chache clearance etc. does not help.
Are you using as well Apache? Maybe the issue is related to the webserver.
it is possible to have a direct path to a special news entry?
example:
my link is: http://www.domain.de/start/topnewsdetail/news/really-long-name-of-news-entry.html
and it would be nice to have
http://www.domain.de/newsEntry.html.
Can someone give a hint?
it is a little bit complicated if you want a general automatic solution.
you can do it by hand if you insert pages of type 'external url' where you insert the long path as external url.
with realurl you have problems as realurl at least will use one path segment for the page with the detail view before the last segment which is for identifying the news record. AFAIK coolurl can ommit the path segemnt for the page.
on the other hand: make sure the news identification (title, subtitle?) is unique and does not collide with pathes for normal pages.
at last you can use .htaccess rewrites, but that needs to differentiate between short urls for news and short urls for top-level pages. So those urls will show the page, those urls are not generated inside of TYPO3 and so nowhere used (except manual)
this EXT. adds a custom link to records like system category or news:
https://typo3.org/extensions/repository/view/recordlink
It'S deployed for TYPO3 6.2 but perhabs it'S helpful to create an own EXT.?