1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

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

Discussion in 'Troubleshooting and Problems' started by Maester Aemon, Jul 30, 2016.

  1. Maester Aemon

    Maester Aemon Member

  2. Mike

    Mike XenForo Developer Staff Member

    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.
  3. Maester Aemon

    Maester Aemon Member

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

    Route filter to change thread urls:

    So format for that url with no route filtering would be threads/dawn-of-the-frozen-wasteland-chapter-5.1970
  4. Mike

    Mike XenForo Developer Staff Member

    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.
  5. Maester Aemon

    Maester Aemon Member

    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.
  6. Axis

    Axis Member

    Is your XF Installed on the /forums directory?
  7. Maester Aemon

    Maester Aemon Member

    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



    But for some reason this doesn't work

  8. Mike

    Mike XenForo Developer Staff Member

    When you generate this as the route:


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


    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.
    Axis likes this.
  9. Maester Aemon

    Maester Aemon Member

    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.
  10. Mike

    Mike XenForo Developer Staff Member

    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}

Share This Page