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?
Custom Paths
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.
3 months later
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.
6 months later
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.
2 months later
- Edited
Version 1.6.0 & 1.7.0
- Add ability to customize FoF Gamification user votes page.
- Add ability to customize ClarkWinkelmann's Discussion Bookmarks page.
- Add ability to customize ClarkWinkelmann's Post Bookmarks page.
- Add ability to customize ClarkWinkelmann's Discussion Lists pages.
- Add ability to customize Flamarkt pages.
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:
- There are no longer any issues with FoF Sitemap version 2.0. The issue might have already been fixed in a pre-2.0 version of Sitemap but I have not verified.
- There are still problems with the SEO extension, because it contains a plethora of hard-coded paths which my extension can't override. The meta tags correctly get added to customized page, however they contain hard-coded URLs that will not work when search engines try to access them.
a month later
Version 1.8.0 - September 13, 2022
- Add ability to customize Flarum 1.5 profile likes page.
- Add ability to customize ClarkWinkelmann's Composer Page pages.
- Add ability to customize Formulaire profile page.
- Fix renamed profile tabs that were redirecting to the homepage instead of their intended new name.
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:
22 days later
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?
luceos I cannot access the page to download the plugin. I guess it has nothing to do with the token. I can't install the plugin with PHP composer because the Github page of the plugin gives 404. You can check the Github link that I mentioned in my previous message. If the installation link of the plugin has changed, I would appreciate it if you could share it because I cannot download this plugin from extiverse or any link on this subject.
flaky the installation instructions can be found at https://kilowhat.net/flarum/extensions/custom-paths#installation
The GitHub repository is private, you don't need to access it to use the extension. The extension code is distributed exclusively through Extiverse. Can I ask where you found a link to the GitHub repository? It's not supposed to be linked anywhere.
If you have an issue accessing your account settings on Extiverse, luceos will be able to help with that.
I couldn't find the link anywhere. All the plugins I added to the JSON file via Plesk > domain > PHP Composer are from Github. At least that's what my observations say. I thought your plugin was github.com/kilowhat/flarum-ext-custom-paths.
I am getting this error that I have appended the plugin to my JSON file:
Could not update the information about the packages
Failed to retrieve data for the package 'kilowhat/flarum-ext-custom-paths': Info from https://repo.packagist.org: #StandWithUkraine
In ShowCommand.php line 297:
Package "kilowhat/flarum-ext-custom-paths" not found in /var/www/vhosts/domain.com/sub.domain.com/composer.json, try using --available (-a) to show al
l available packages.
show [--all] [--locked] [-i|--installed] [-p|--platform] [-a|--available] [-s|--self] [-N|--name-only] [-P|--path] [-t|--tree] [-l|--latest] [-o|--outdated] [--ignore IGNORE] [-M|--major-only] [-m|--minor-only] [--patch-only] [-D|--direct] [--strict] [-f|--format FORMAT] [--no-dev] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<package> [<version>]]
flaky make sure you have followed the Extiverse setup instructions for Composer at https://extiverse.com/premium/subscriptions
If Composer says it cannot find the package, Extiverse is probably not set up correctly.
I'm not sure how the Plesk Composer feature works. I don't know if custom Composer endpoints like Extiverse work with that feature. You might need to also setup Extiverse as a global Composer repository instead of just locally to the Flarum folder if Plesk tries to retrieve information about the package before adding it to the project. I have only tested my premium extensions for use with the Composer command line utility.
clarkwinkelmann
I get this error when installing via SSH: https://prnt.sc/mL0cMBV5jbRo
-sh-4.2$ composer require kilowhat/flarum-ext-custom-paths
In PackageDiscoveryTrait.php line 364:
Could not find a matching version of package kilowhat/flarum-ext-custom-paths. Check the package spelling, your version constraint and that the package is available in a st
ability which matches your minimum-stability (stable).
require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--no-audit] [--audit-format AUDIT-FORMAT] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [<packages>...]
flaky did you run the commands given on the subscriptions page of extiverse https://extiverse.com/premium/subscriptions? Make sure to replace yourUniqueToken with the token from the button Request New Token.
4 months later
@clarkwinkelmann Would this enable me add a route to link to tags by their id (I see it's usually slug that is used there...)
tcowin no, that's not a feature of the extension at this time.
Technically, this extension wouldn't be needed at all, Flarum has a dedicated API just to modify how "slugs" are generated for URLs that's different from the path on which those slugs are used.
Since I received a few requests regarding slugging already I am considering adding custom sluggers into this extension or as part of a companion extension. A companion extension would be better for performance if you don't need the custom paths part.
If you are not going to be using tag slugs, you could manually copy the tag ID into the slug field for each tag and it should achieve the same thing.
Thanks @clarkwinkelmann -- I tried to 'manually' set the id in the /tags/{id} /t/{id} paths a few ways but couldn't get it working, so just brute forced my redirects on the far side for now. Will revisit... 