For example have Support - Installation - Upgrading - Hosting Without clicking on Support

alx it's not a built-in feature, and would likely require forking the Tags extension to be changed.

To follow up your question in the duplicate discussion: The line responsible for showing or hiding children is here https://github.com/flarum/tags/blob/v0.1.0-beta.8.2/js/src/forum/addTagList.js#L39 It's probably not easy to change via an other extension and would require forking the whole tags extension, for example by cloning it to a workbench folder (see dev tutorials for that) and editing the code there. I don't recommend editing any file in vendor as the changes will be overwritten when composer installs or updates packages.

clarkwinkelmann Could I fork the extension, delete the line, uninstall tags and reinstall the modified tags extension?

alx that's the gist. This should be a good resource on how you can create a clone of the extension locally. Use the same steps but instead of creating a new extension, clone flarum/tags to the workbench and edit its source code there #1608

clarkwinkelmann Didn't work. Here's what I did: Found the tags extension in my file manager. Deleted everything. Downloaded the github version, modified it. Upload it back to public_html/vendor/flarum/tags Turn off the extension, turn it back on. The website still works as before so it makes me believe that it may not be that line of code that had to be deleted?

clarkwinkelmann I was confused because the line of code you pointed to was under "sortTags(tags)" What I would like to happen is to simply have the tags always active, that way all the subtags are constantly showing.

alx line 38 sorts the tags. Line 39 filters which tags are visible. The test on that lines shows all tags with a position (aka primary tags) that have either no parent, or are children of the active parent, or their are children of the parent of the currently active tag. Removing && (!tag.isChild() || (currentTag && (tag.parent() === currentTag || tag.parent() === currentTag.parent()))) should show all primary tags whether they are active or not. After changing the javascript source code you need to recompile the dist files. You need to npm install the dependencies and run the npm run build command.

clarkwinkelmann Do I recompile locally or on ssh? Also where do I recompile? in public_html/vendor/flarum/tags?

alx the npm commands must be run in the js folder of the extension. You can do that either locally or on the server. Flarum only loads the dist files. Again, I'd recommend using a workbench folder and not edit anything directly in the vendor folder. Sending the files via FTP/SSH is also possible once the extension has been linked to the workbench folder. That would be the safest way.

clarkwinkelmann I see. Unfortunately I'm not able to run npm run build in the js folder. I'm getting: npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! @flarum/tags@ build: webpack --mode production npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the @flarum/tags@ build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Is there a way to always have the sub-tags visible?

clarkwinkelmann

Please don't post duplicates, you already have a discussion covering this #20166

I'll move your initial discussion to dev tag

jordanjay29

@alx I've merged these discussions for the same reason as I mentioned here.

« Previous Page