It turned out that this is not a “term”, but a “page”. Ok.
If this is a content type like “News”, it is logical to use the pattern
"news/[node:title]"
where "news" is a list of all news,
and “news/some_news” is a separate news item.
I don't understand why you use [node:book:url:path].
And then, what do you have written in the "URL settings" of this page, and why you can’t just edit this URL in the "URL settings" of this page?
(I always use [node:created:raw][node:nid]
“news/[node:created:raw][node:nid]“
to receive more beautiful and unique addresses. Recommend to everyone.)
Posted1 week 17 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) in Weekly Meetings
Recent comments
Hey everyone! I found it really interesting how different server settings can cause those "page not found" errors after migration. Has anyone tried using specific debugging tools to pinpoint the...
It is a good point @izmeez and when I was researching repo discoverability I found that GitHub search does prioritise matches with more stars.
This is what I was researching for:...
Posted2 days 17 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
This link should work if the VIEW contains a Block and a Page - the link from the block will be directed to this page. I've never used it, so I might be wrong. But what can be done easier is to...
Comments
Check what the real synonym for this term
/admin/config/urls/path
Perhaps you have an error in the synonym pattern
/admin/config/urls/path/patterns
url pattern: [node:book:url:path]hirek/[node:title]
It turned out that this is not a “term”, but a “page”. Ok.
If this is a content type like “News”, it is logical to use the pattern
"news/[node:title]"
where "news" is a list of all news,
and “news/some_news” is a separate news item.
I don't understand why you use [node:book:url:path].
And then, what do you have written in the "URL settings" of this page, and why you can’t just edit this URL in the "URL settings" of this page?
(I always use [node:created:raw][node:nid]
“news/[node:created:raw][node:nid]“
to receive more beautiful and unique addresses. Recommend to everyone.)
I think you have this problem https://tinyl.io/Bwne or https://tinyl.io/Bwo6
Solution: add to your Views page /hirek Contextual filter "Global: Null".
And use a Canonical URL for all pages, which will help eliminate duplicate content for search engines.
Hi, @BeatX772
I'm still wondering how this adventure ended?
Hello
Sorry, I work
/hírek/hírek/
Page not found
Yes, nice thank you Mr.
Two questions:
There was a bug with CKEditor 4 when the base paths of pages were duplicated for multisite installations. See https://github.com/backdrop/backdrop-issues/issues/5886
But this was fixed for CKEditor 4. Perhaps now this is a problem with CKEditor 5? Let us know.
No,
Hungary site, this Hirek = News
Sorry bad translate, google translator
google serach console