Editing CSS/Headers With an Extension

luceos

Frink return [
(new Extend\Assets('forum'))
->asset(DIR.'/less/forum/extension.less')
];

This code is for the upcoming beta. If you run beta 7.1; you'll need to use the old way AddClientAssets.php ?

Frink

luceos Ok, I will edit it tomorrow! Thanks!

luceos

Also if you run into 500 errors, make sure you have debug enabled in your config.php and you check your storage/logs/flarum.log file first.

Frink

luceos I did enable debug and its don't give me an error. I didn't check the log, thanks for reminding me of that

Ralkage

@luceos one day I hope we can all collaborate on a developers hobo guide to writing extensions and adding all sorts of components that can be added such a settings modal ?

Frink

Ralkage such a settings modal

Sorry to seem like a royal twit, but being younger than 16, I haven't gotten too in-depth in the php and css side of things. I like to stick to straight html!

clarkwinkelmann

Frink Flarum frontend is a javascript single page app (SPA) so there's no "straight html" anywhere to be seen. This might be a bit unsettling at first but once you learn how SPA works, creating a settings modal is really one of the easiest and logical first steps in learning to add features to Flarum ?

Frink

clarkwinkelmann Yup. I forked @Davis custom footer extension, and played around with it. Essentially, it already does what I want to do. Thanks for the help!

Frink

I have started the extension! Check out my progress at https://github.com/zaptechadmin/flarum-ext-global-color

Frink

I have encountered another issue. Now, when I enable the extension, it does not show the option to open the settings modal. Would anyone be willing to take a look at the git repo (see above post) and tell me if there is something wrong? Also, feel free to fork it, make changes, and do a pull request.

TitusPiJean

Frink It may be a typo there: capital D on "davis" whereas its in lowercase everywhere else?

Frink

TitusPiJean That doesn't seem to be the issue... any other ideas?

jordanjay29

Frink well, @TitusPiJean brings up the issue that you've copied a settings name from another extension. You should always make your settings names unique, they get created in the database and could conflict with another extension if the names collide.

Frink

jordanjay29 OK, I will try to resolve this!

TitusPiJean

Ah! It was late, it did not occur to me that the namespace was not the same as the extension name. ?

« Previous Page