Get list of extensions with API

TheMolecularLevel

Is there any way to get a list of extensions used by a forum with the API? I'm making an app for Android (native) and I'm planning to add support for all the base extensions, but I don't know how to figure out if they're enabled or not.

luceos

Flarum by itself does not have this functionality. I would also not make this information available on an API without proper authorization. Flagrow Bazaar actually works with extension status information so that its' dashboard can give you information about extensions that need an update (we're working on a lot of this functionality but it already works for the Bazaar extension and flarum/core).

TheMolecularLevel

luceos I realize that there can be concerns regarding making extension information available through the API. I was thinking more about the core extensions, like "Like" and stuff like that, which someone may have disabled. I will check out Flagrow Bazaar, see if there's anything I can do ? Also, I may create my own extension to add mobile-app compatibility. I'll see. Thanks for your help ?

jordanjay29

It's worth noting that php flarum infohas this information.

TheMolecularLevel

jordanjay29 Wow, that command literally has all the information I need ? Thanks!

TheMolecularLevel

luceos

jordanjay29

I know this has nothing to do with the question, but since there's no way to send a private message, I'm just wondering about where the "extensions" folder mentioned in the extension tutorial is. I've searched recursively through the entire Flarum installation folder, and I haven't found it. I only found that the folder "vendor" contained all the extensions, but putting my extension in there didn't work. Thanks in advance ?

(I'm talking about this tutorial: http://flarum.org/docs/extend/start/)

jordanjay29

TheMolecularLevel it's now vendor. But if you're going to develop on your Flarum, check out the sticky in the Dev tag for information.

TheMolecularLevel

jordanjay29 I've read that, and enabled debug mode. But the extension does not show up in the menu. I've even tried copying another extension's composer.json file, and their bootstrap.php file. I don't think my file structure is off, the files are in "vendor/tml/extinfo".

jordanjay29

TheMolecularLevel This is the document I was talking about which describes not to use vendor for development.

TheMolecularLevel

jordanjay29 I'm sorry, I thought you were talking about the other one. My apologies.

TheMolecularLevel

jordanjay29 Thank you so much! Worked like a charm :-)

Kyrne

Looks like it's solved but the list of enabled extensions is in the settings table so you can get it like any other setting in Flarum.

TheMolecularLevel

Kyrne What do you mean?

Kyrne

TheMolecularLevel in my MYSQL database there is a settings table that you can get with SettingsRepositoryInterface. I the settings table there is a setting that contains all of the enabled extensions.

TheMolecularLevel

Kyrne Oh, okay. We'll see how I decide to do it. Thanks for the information ?

clarkwinkelmann

luceos I would also not make this information available on an API without proper authorization

Just to point it out, all extensions used in the javascript front-end can be found by looking at the modules loading line in the HTML:

var modules = ["locale","davis\/split\/main","flarum\/akismet\/main","flarum\/approval\/main","flarum\/emoji\/main","flarum\/auth\/facebook\/main","flarum\/flags\/main","flarum\/auth\/github\/main","flarum\/likes\/main","flarum\/lock\/main","flarum\/mentions\/main","flarum\/pusher\/main","flarum\/sticky\/main","flarum\/subscriptions\/main","flarum\/suspend\/main","flarum\/tags\/main","flarum\/auth\/twitter\/main"];

All admin-only JS extensions and server-side extensions are not visible that way

luceos

clarkwinkelmann All admin-only JS extensions and server-side extensions are not visible that way

You mean, only extensions that modify the frontend via mithril show up in this list. Aka not very reliable, also taking into account these are the shorter string used by Flarum internally.

luceos

clarkwinkelmann also.. The string of the module can be configured freely by the extension and does not have to reflect the name of the package or end with main.