Pallet Theme for Flarum

MIT license Latest Stable Version Total Downloads Static Badge

Light Pallet
Dark Pallet - Tags Navigation

Welcome to the Pallet Theme!

Originally created by the-turk, this theme offers a beautiful and dynamic user interface for your Flarum forum. With the original author unable to maintain it, I have taken over the development to ensure it remains compatible with the latest Flarum updates.

-- Adrian

How to remove the original theme

If you have the original Pallet Theme installed, you'll need to remove it first. Just run this command:

composer remove the-turk/flarum-pallet-theme

Installation

To install the Pallet Theme, use Composer:

composer require madeyedeer/flarum-pallet-theme

Updating

To update the Pallet Theme, use Composer:

composer update madeyedeer/flarum-pallet-theme

Note: Some releases may require a version to be specified when updating, so check the release notes on the Flarum forum for specific instructions.

About Maintenance

The Pallet Theme will continue to be maintained to ensure compatibility with Flarum. Please report any issues, especially those related to compatibility with other extensions, on the GitHub issues page.

Links

First of all, I'd like to thank you for your work. ! 🙂

I'm glad you've released a "stable" version. Compatible with the latest version of Flarum. I was able to install and test 🙂 Regarding the bugs I reported :

Theme :

Tag label color : fixed
Banner color : fixed (JS with value 0.6 was at fault)
Site width on tablets : fixed

Extension :

Installation FoF Night Mode with Pallet Theme : fixed
FoF Night usage : 50% fixed !
If you force clear mode in Admin, it works fine !
If you force dark mode in Admin, it doesn't work ⚠

FoF Byobu usage : Not fixed
(I'm reposting the bug on this new topic, but I know you'll save it for later)
"Private Discussions" link appears in the left column. But when you go there, the "New discussion" button doesn't change. So it doesn't create a private discussion but a classic discussion.....

Thank you so much again. I'm curious to see what happens next ! 🙂

    Wlork

    Thanks for the feedback! I've had a quick look at the FoF nightmode issue and it seems to be working under some conditions and not others on my dev environment, so I will dig into that one in the morning and sort it out.

    I didn't look at other extension compatibility with it yet so will look at FoF Byobu first - I see a heap of code for specific extensions that can hopefully be removed and replaced with something that will just work with all of them... but I will confirm that one tomorrow.

    Cheers!

        adrianm

        I think I've found the source of the button issue for FoF Byobu ?

        In Sidebar, the “Private Discussion” link has been added :

        MadEyeDeer/flarum-pallet-themeblob/main/js/src/forum/components/Sidebar.js (line 257 - 271)

        But the button to start a private discussion is missing itemclassname="App-primaryControl fof-byobu_primaryControl"

        MadEyeDeer/flarum-pallet-themeblob/main/js/src/forum/index.js (line 74-93)

        I'll let your expertise to check it 🙂

          Wlork If you force dark mode in Admin, it doesn't work ⚠

          I just spent most of the day looking at this - on and off in between a few other things I needed to look at today, but still way too long - and it turns out this is not a Pallet Theme issue but a Nightmode issue! Disable Pallet Theme and just use nightmode with the forum set to dark mode and it won't switch properly. Argh!

          I had a quick scroll through here https://discuss.flarum.org/d/21492-friendsofflarum-night-mode and a look at the issues on github and couldn't really tell if it's a known thing and everyone was ok to leave it like that?

              Ok just been going through these items

              • Fixed Start New Discussion button in top right of screen not changing to Discuss Privately
              • Fixed implementation of menu items so that we don't have to add code for each extension that touches the menu

              Tested following extensions as they had hard-coded items on the menu

              • v17development/flarum-blog - working
              • justoverclock/flarum-ext-keywords - this menu item works but if you enable nightmode the glossary page is broken

              I turned nightmode off for the rest

              • clarkwinkelmann/flarum-ext-group-list - working
              • fof/user-directory - working
              • justoverclock/flarum-ext-contactme - working
              • anything else that adds items to the nav menu should work

              I'll do a version bump and update docs in the morning, hopefully that is the biggest issues sorted

                @JakeMcCarroll sorry for some reason I missed your messages! I'll have a look at that one but my initial thoughts are that could quite easily be listed as a "bug" on either this theme or the private forum facade extension. The issue looks to be that Pallet Theme is showing a static menu on all pages and not being removed on forum facade extension on the page in the screenshot. I'll see if I can work out a good way to make them play nice together though.

                adrianm Fixed implementation of menu items so that we don't have to add code for each extension that touches the menu

                adrianm anything else that adds items to the nav menu should work

                I have an extension that isn't in this nav menu.... The next update will be a good test ! And I'm glad to know you've fixed the bug for private messages.

                Really, many thanks for your work ! 🙂

                    @adrianm

                    I've installed the update.

                    The button for private messages has been corrected. Thanks a lot!

                    Unfortunately, I've encountered another annoying bug. When we go to a tag, the tree structure appears in the side nav when it shouldn't.

                    @adrianm Sorry for double post.

                    Another bug : I can't modify CSS. I have this error message :

                    variable @show-side-nav is undefined in file ..../vendor/madeyedeer/flarum-pallet-theme/less/common/App.less in App.less on line 1, column 17 1| .set-left-column(@show-side-nav); 2| .set-left-column(true) { 3| @left-column: 280px; 4| } 5| .set-left-column(false) { 6| @left-column: 0;

                    @Wlork
                    Yeah the error when trying to save CSS one is giving me a huge headache tbh.
                    As a work around you can add this to your custom css for now and it will at least work.

                    @show-side-nav: true;

                    Took me ages to work out how to get CSS variables through from PHP nicely and now just trying to work out how to put in a default and allow override from something coming via PHP.

                    The tags in the menu is an easy one, I will add this to the next update but you can fix it in css like this if you want to see how it looks

                    .App-sidebar .App-sidebar-items .App-sidebar-items-container li:has(a.TagLinkButton.child) {
    display: none;
}

                      adrianm @show-side-nav: true;

                      It works. It'll do until you update it 🙂

                      adrianm

                      .App-sidebar .App-sidebar-items .App-sidebar-items-container li:has(a.TagLinkButton.child) {
     display: none;
 }

                      This solution hides the sub-labels. But the main tag and separation are still there....

                            Wlork

                            It looks weird hey - I wasn't sure what that was even meant to be, haha

                                adrianm

                                This bug has appeared since the new version 0.2.2.

                                You have enabled anything else that adds items to the nav menu.... Maybe that's where the issue lies 🙂

                                    Wlork

                                    Yes instead of just overriding the menu it puts the Flarum menu up, so that any extensions that need to add to it can do that. It's just not manageable to put code from other extensions onto the menu every time we want to make it compatible with something else.