XF 1.5 Route filter leading to XenForo_ControllerPublic_Forum does not define an action called xx

Where is that initial URL being generated? With the route filter you've mentioned, that would be equivalent to forums/dawn-of-the-frozen-wastelands.86/chapter-5.1970/ which isn't something we would generate. I assume you're trying to link to a thread but there's no forum information in standard thread links.
 
Where is that initial URL being generated? With the route filter you've mentioned, that would be equivalent to forums/dawn-of-the-frozen-wastelands.86/chapter-5.1970/ which isn't something we would generate. I assume you're trying to link to a thread but there's no forum information in standard thread links.

I forgot to mention, I'm using another route filter to change thread urls.

Route filter to change thread urls:
threads/{name}-chapter-{name1}
projects/{name}/chapter-{name1}

So format for that url with no route filtering would be threads/dawn-of-the-frozen-wasteland-chapter-5.1970
 
Only a single route filter matches a URL and you're created ambiguities in the URLs with that approach, so unfortunately, that likely won't work.
 
Only a single route filter matches a URL and you're created ambiguities in the URLs with that approach, so unfortunately, that likely won't work.
I'm not understanding what you mean, I have a route filter for thread urls and a route filter for forum url.
This works for most of the other the forum and thread urls I think it has to do something with length of url.
 
I'm not understanding what you mean, I have a route filter for thread urls and a route filter for forum url.
This works for most of the other the forum and thread urls I think it has to do something with length of url.

Is your XF Installed on the /forums directory?
 
Is your XF Installed on the /forums directory?
My XF is installed on root directory https://gameofscanlation.moe/ is where its installed but I have a index page route of pages/home/

I don't think I can change the /forums to /projects and I don't want it to be applied to all of the urls.

Also, for example, these urls work

https://gameofscanlation.moe/projects/terror-man/
https://gameofscanlation.moe/projects/terror-man/chapter-26.2032/

https://gameofscanlation.moe/projects/epic-of-gilgamesh/
https://gameofscanlation.moe/projects/epic-of-gilgamesh/chapter-33.2024/

But for some reason this doesn't work

https://gameofscanlation.moe/projects/dawn-of-the-frozen-wastelands/
https://gameofscanlation.moe/projects/dawn-of-the-frozen-wastelands/chapter-5.1970/
 
When you generate this as the route:

projects/dawn-of-the-frozen-wastelands/chapter-5.1970/

It's ambiguous. It could either mean (translated from route prefixes):

forums/dawn-of-the-frozen-wastelands.86/chapter-5.1970/
threads/dawn-of-the-frozen-wastelands-chapter-5.1970/

Both parsing options are equally valid. The latter is what you're intending. In this case, the system is translating it as the former due to it thinking it's more specific (based on length). The ability to generate ambiguity is mentioned in the manual so this is a caveat of using them.
 
When you generate this as the route:

projects/dawn-of-the-frozen-wastelands/chapter-5.1970/

It's ambiguous. It could either mean (translated from route prefixes):

forums/dawn-of-the-frozen-wastelands.86/chapter-5.1970/
threads/dawn-of-the-frozen-wastelands-chapter-5.1970/

Both parsing options are equally valid. The latter is what you're intending. In this case, the system is translating it as the former due to it thinking it's more specific (based on length). The ability to generate ambiguity is mentioned in the manual so this is a caveat of using them.
Hmm thanks for the info.

Also, sorry but this does not make a lot of sense to me, is it possible to fix this or not?
So I know if I should try to make sense out of it or not lol.
 
Essentially no, it's not possible to fix this (without changing URLs) because it has created an ambiguous meaning to a URL.

If you change the filters, then it could be an option. For example, you might be able to do something like:

threads/{name}-chapter-{name1} -> t/projects/{name}/chapter-{name1}
 
Top Bottom