📌 Stickiest - Super Sticky for Flarum 2.x

huseyinfiliz

Stickiest

This extension allows you to stick, super-stick, or tag-stick discussions to the top of the list. It is fully compatible with Flarum 2.x and is inspired by the-turk/flarum-stickiest, but entirely rewritten from scratch.

Features

Super Sticky: Pin discussions to the very top everywhere (All Discussions + all tag pages)
Tag Sticky: Pin discussions only in selected tag pages
Normal Sticky: Full compatibility with flarum/sticky extension
Event Posts: Shows activity when super sticky status changes
Customizable Badge: Choose your own icon for super sticky discussions
Visual Indicators: Colored borders and backgrounds for sticky discussions

Screenshots

Stickiest Modal

Stickiest List

Requirements

Flarum 2.0+
PHP 8.2+
flarum/tags extension

Installation

composer require huseyinfiliz/stickiest:"*"
php flarum migrate
php flarum cache:clear

Updating

composer update huseyinfiliz/stickiest:"*"
php flarum migrate
php flarum cache:clear

Migrating from the-turk/flarum-stickiest

This extension uses the same database structure as the-turk/flarum-stickiest. To migrate:

Disable and uninstall the old extension
Install this extension
Your existing sticky data will be preserved

composer remove the-turk/flarum-stickiest
composer require huseyinfiliz/stickiest:"*"
php flarum migrate
php flarum cache:clear

Usage

Enable the extension in admin panel
Set permissions for "Super sticky discussions" and "Tag sticky discussions"
Optionally customize the super sticky badge icon in settings
Click on the "Sticky" button on any discussion to open the sticky modal
Choose your sticky type:
- Sticky: Standard sticky (requires flarum/sticky)
- Super Sticky: Always at the very top everywhere
- Tag Sticky: Only at the top in selected tags

Admin Settings

Setting

Show tag stickies in All Discussions: When disabled, tag sticky discussions only appear in their respective tag pages
Super sticky badge icon: Font Awesome icon class (default: fas fa-star)

Credits

This extension is a Flarum 2.x rewrite inspired by the-turk/flarum-stickiest which was built for Flarum 1.x.

License

MIT License - see LICENSE.md

novoros24ru

Will it work on 1.8?

huseyinfiliz

novoros24ru No. This extension was rewritten from scratch for version 2.x. To use it in version 1.8, see this discussion: https://discuss.flarum.org/d/27888-stickiest

treyb

Thanks @huseyinfiliz !

navindra

Yay!! This is another extension that's on my list for PianoTell.

There's an appearance difference that I wasn't expecting though and doesn't happen on 1.x.

Is that yellow/orange bar expected?

Edit: Looks like it is, but is there a way to turn that off? I like the functionality but I don't want it to change the appearance of PianoTell at the same time.

Thanks so much for helping make Flarum 2 a reality!

huseyinfiliz

navindra This extension is not an update of the-turk/flarum-stickiest.

This version was written completely from scratch for Flarum 2.x and it does not reuse or depend on any parts of the 1.x branch. You should treat it as a brand-new extension. Still, to help people who are migrating, I made existing super-sticky and tag-sticky discussions compatible with this extension.

For example, the 1.x version could not work without flarum/sticky. My extension, however, works even without flarum/sticky, while still respecting its settings and handling its functionality when present.

So yes — the 1.x flarum-stickiest and the new 2.x stickiest should be considered different extensions.

Anyway, after this small clarification, I’ve added a plan to introduce an admin setting to disable the styling changes for those who prefer the original look. Happy to hear you’re enjoying the extension!

navindra

huseyinfiliz Thank you so much!

I do like separating the functionality from the look... users may not understand the different kinds of stickiness (and it would be hard to explain the reasons the colors are different), but the different options do have their uses for admins/mods without needing to expose complexity to the users.

huseyinfiliz

navindra I’d like to inform you that I won’t be releasing an update for this. These visual colors are part of the extension itself, but if you’d like to override them, you can use this LESS code:

body .DiscussionListItem {
    
    &.Stickiest-superSticky,
    &.Stickiest-tagSticky {
        background: transparent;
        border-left: none;
    }

    &.Stickiest-sticky {
        border-left: none;
    }
}

Silvestrus

The idea for expanding extension: to add option to open discussion on the top since there could be scenario where we have many messages in discussions and it opens at the last message and sometimes users would want to open discussion at the top (announcements, polls, etc...)

Capybara

huseyinfiliz Thank you for updating the extension — I found a use for it on my forum to pin events above everything else. I really like your discussion highlight design

huseyinfiliz

Capybara Thanks, glad you liked it 💫

Just a small reminder to avoid any confusion in the future: this extension is not an update of the old Stickiest extension. It’s a brand-new extension, written from scratch, that provides similar functionality in a different way.

navindra

huseyinfiliz Out of curiosity, why was the rewrite needed?

Thank you!

huseyinfiliz

navindra The old version of the extension was built during the Flarum beta stages and was tightly coupled with the flarum/sticky extension. It lacked flexibility, and upgrading it to 2.x was a massive undertaking. Plus, it was vulnerable to any breaking changes in the core sticky extension.

This new version has been rewritten from scratch to align with the modern 2.x architecture without needing any "dirty" bypasses. More importantly, instead of being a child extension of flarum/sticky, it now sits above it. This means even if you disable or remove flarum/sticky, Stickiest will continue to function perfectly on its own.

The bottom line is that refactoring old, legacy code that had been piling up since the beta days was actually harder than just building it fresh for 2.x. Since I was doing a full rewrite anyway, I decided to overhaul the entire logic from the ground up.