It looks like you're new here. If you want to get involved, click one of these buttons!
Currently working on updating Articles to support Vanilla 2.5 (see GitHub repo for latest dev code). Ran into issues with routing. Is anyone else having this issue with Vanilla 2.5?
If you're familiar with Vanilla's routing system, you already know you can get to a method via
/appName/controllerName/methodName/(...), with or without appName in the link (and without methodName if it's the index). In this case, we have the ArticlesController within an app called Articles.
http://example.com/articles/category/general. It seems like the router thinks you want:
http://example.com/category/general(same as /vanilla/category/general).
http://example.com/articles/articles/category/general, these links work.
I don't know what would happen if I rename ArticlesController to something else and try to go to the same Articles category page (this would indicate a conflict between the app key and controller name).
My guess is that there's a conflict between app keys and method names that is being handled differently in Vanilla 2.5 than older versions. Is there a difference in how 2.5 handles routing?
If you don't see this issue, then it could be an issue in my dev environment's nginx configuration, but I did try different settings to no avail.