This version can only be installed on Flarum beta 16 and will automatically be installed when you migrate to Flarum beta 16 with Flarum's official instructions.
Hi, I don't really know how this extension works and I was wondering if changing paths affects the speed or response time, is it redirects or is it something different that doesn't affect the above?
Darkle the performance impact should be negligible. There is one more database request per page load to fetch the settings value, which is not very different from how other extensions load their settings.
The way it works is actually by creating a second instance of the Flarum router with just the customized routes and calling that router just before Flarum's. The router is essentially one big regular expression being performed on the page URL.
Redirects are an option in the extension. By default original routes will return 404 if no new route was assigned to the same path. But you can optionally enable permanent redirects (useful if you install the extension on an existing forum)
The router of the API and admin routes are not impacted at all, the code only runs for the initial HTML page load. So there might be a slight increase in initial load time, but no change to performance whatsoever once you start browsing inside of the single page app. An other source of negligible performance decrease could be with every API routes that return links, because the extension runs additional logic when the URL generator is resolved.
I believe this is well optimized compared to many other extensions that will have a much worse performance impact.
If you have a very large forum and experience performance issues I would be happy to take a look.
Well, I think I am gonna use this at next project.. 
Custom Path... Different style, different from others
clarkwinkelmann It's a nice add-on. It would be much better if it was free.
Eren65465024 this extension would simply not exist at all if it was free. It helps pay the time dedicated to creating and maintaining it. It's my cheapest extension by the way 
I say "helps pay" because all my premium extensions, and I also think all other premium extension developers, are currently doing this as an investment. The development cost of the premium extensions will likely only be recovered after a few years once Flarum's popularity grows.
This version can be installed on Flarum 1.0.0 and all future 1.x versions.
It will be automatically installed when you upgrade to Flarum 1.0 by following the official release guide.
@clarkwinkelmann The documentation still mentions that this extension is incompatible with FriendsOfFlarum’s Sitemap extension. I was about to ask for this when I came across your PR FriendsOfFlarum/sitemap#12 mentioned here. That PR has since been merged, so you'd probably want to remove that from the documentation.
RishitKedia I don't think I have had the opportunity to test both together since that change got merged. I'll need to give it another try before I update the documentation 
️
By chance, did you try it already?
clarkwinkelmann I don't think I have had the opportunity to test both together since that change got merged. I'll need to give it another try before I update the documentation
Ah, okay. ️
clarkwinkelmann By chance, did you try it already?
No, not yet, I assumed it was fixed; would appreciate your confirmation before buying/using this.
clarkwinkelmann is development ongoing for compatibility with the SEO extension?
DursunCan sorry, I haven't had a chance to test the two extensions together yet. I will try, but I can't guarantee when I'll be able to get to it.
If changes are required and support can be added with minimal effort I will definitely add it.
does this extension support not having an URL prefix for certain content types? eg. say i want my users profiles to be accessible at /{username} if another route doesn't match their username
neko no, not possible with this extension.
This would have to be a dedicated extension, because it would have to prevent users from setting reserved paths as usernames, otherwise some users would be unable to access their profiles. And it gets very complicated if you want more than one resource type accessible this way.
It's just a bad idea entirely unless you're using a separate domain name (or a subdomain), then you could do it. But you may break the loading of the single-page app if you do that. You'd have to set everything up as a single webserver to do it, set the correct headers etc and if you did all that it would be possible I believe. So basically you'd have say:
discuss.example.org/... > your forum
user.example.org/... > usersSo it could be done that way, theoretically anyway.
Discussion Lists and Flamarkt do not yet have any production-ready release, support was added for internal testing with clients.
This version requires Flarum 1.2 or greater.
Version 1.6.0 was silently pushed in August of last year but never announced since it only contained Flamarkt-related changes.
I have conducted tests to update my conflicts section of the documentation, and I can confirm the following:
The extension was confirmed working on Flarum 1.5.
To celebrate the release of Flarum 1.5, all KILOWHAT premium extensions are 15% off until the end of September. Grab Custom Paths for 8,50 USD instead of 10 USD (lifetime license) with the following link:
I bought and used the plugin a few years ago. In order to use it again, I wanted to enter my extiverse account and upload it, but I am getting an error. The Github link(https://github.com/kilowhat/flarum-ext-custom-paths) of the plugin is giving a 404 error, so I can't install the plugin on my server.
How can I solve this?
