📌 Stickiest - Super Sticky

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.

huseyinfiliz

📢 Flarum 1.x Support is Now Available!

For those still running Flarum 1.x, a compatible version is now published on Packagist.

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

This version is a namespace migration of the original the-turk/flarum-stickiest no functionality changes, just updated to work under the huseyinfiliz package name.

If you're ready to upgrade to Flarum 2.x, check the upgrade steps in the first post.

anoedo

huseyinfiliz
Hi @huseyinfiliz,

Thanks for the Flarum 1.x compatible version! However, I encountered a fatal error when trying to enable the extension in the admin panel (the toggle bounces back immediately).
I captured the XHR response, and it's throwing a 500 Internal Server Error due to a Database Prefix hardcoding issue in your migration file.
Here is the exact error:
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'flarum.discussions' doesn't exist (SQL: SHOW INDEX FROM discussions WHERE Key_name = 'discussions_is_stickiest_last_posted_at_index')
My Flarum database uses a table prefix (e.g., fl_). It seems that in the migration file (2021_07_04_000001_add_discussions_stickiest_last_posted_at_indices.php), a raw SQL query (SHOW INDEX FROM discussions) is used without accounting for the dynamic database prefix. Because of this, it's looking for discussions instead of fl_discussions, causing the installation to crash completely.
Could you please update the migration to use the Laravel Schema builder or properly append the database prefix to the raw query? Or is there any other solution to this issue I'm encountering?
Looking forward to your reply. Thank you very much!

huseyinfiliz

anoedo I recall not modifying the original extension's code. The issue likely originates from the original extension itself. I will resolve the problem and publish an update as soon as possible. Thank you for reporting this.

huseyinfiliz

🚀 Stickiest 1.0.1 — Table Prefix Fix

Targets Flarum 1.x

Release URL: huseyinfiliz/stickiestreleases/tag/v1.0.1

Fix database table prefix not being applied in migration raw SQL queries causing 500 errors on prefixed installations anoedo

Full Changelog: huseyinfiliz/stickiestv1.0.0 → v1.0.1

What changed?

Migration files were using hardcoded table names in raw SHOW INDEX SQL queries without accounting for the database table prefix. If your Flarum installation uses a prefix (e.g. fl_), enabling the extension would immediately throw a 500 Internal Server Error:

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'flarum.discussions' doesn't exist

This release fixes all 4 affected migration files by dynamically resolving the table prefix via $connection->getTablePrefix():

2021_07_04_000001_add_discussions_stickiest_last_posted_at_indices.php
2021_07_04_000002_add_discussions_created_at_indices.php
2022_07_21_000000_drop_discussions_is_tagSticky_indices.php
2022_07_21_000003_add_discussions_is_tag_sticky_indices.php

If you were previously unable to install the extension due to this error, updating to 1.0.1 should resolve it completely.

How to update

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

Or use Extension Manager to update.

🔧 Github
📦 Packagist

If you run into any issues, feel free to reply here or send me a message.

Heavenly

huseyinfiliz

I'm having an issue when trying to enable the Stickiest extension (v1.0.1) on my Flarum site. The extension fails to enable and throws a PDOException.
It seems like the migration 2022_07_21_000000_drop_discussions_is_tagSticky_indices.php is trying to add or drop an index on a column that doesn't exist in my flarum_discussions table.
Error Log:
SQLSTATE[42000]: Syntax error or access violation: 1072 Key column 'is_tag_sticky' doesn't exist in table (SQL: alter table flarum_discussions add index flarum_discussions_is_tag_sticky_last_posted_at_index(is_tag_sticky, last_posted_at))
I have already tried running php flarum migrate and php flarum cache:clear via SSH, but the error persists. It seems the migration expects the is_tag_sticky column to be present, but it's missing from my database schema.
Could you please look into this? Thank you!

Update: After trying to Purge and Re-enable the extension on v1.0.1, I am now getting a Duplicate key name error.
Error: SQLSTATE[42000]: Syntax error or access violation: 1061 Duplicate key name 'flarum_discussions_is_tagsticky_last_posted_at_index'

Heavenly

huseyinfiliz

I wanted to provide an update regarding issue reported earlier. I have successfully resolved the problem and managed to enable the Stickiest (v1.0.1) extension by manually adjusting the database schema.

The Problem:
There is a naming inconsistency in the migration scripts between "is_tag_sticky" and is_tagSticky.

My database originally only had "is_tagSticky" but the migration 2022_07_21_000000 was looking for is_tag_sticky to create an index, causing the "Key column doesn't exist" error.

Previous failed attempts also caused "Duplicate key name" errors.

How I fix it via phpMyAdmin:
Drop conflicting indices go to your flarum_discussions table -> Structure -> Indexes.

Drop these two if they exist:
("Duplicate key name" errors)
1.flarum_discussions_is_tagsticky_last_posted_at_index
2.flarum_discussions_is_tagsticky_created_at_index

Add Missing Column:
Add a new column to the flarum_discussions table
Name: is_tag_sticky
Type: TINYINT
Length: 1
Attributes: UNSIGNED
Default: As defined: 0
Null:

php flarum migrate
php flarum cache:clear

After these steps, the extension should enable without any failing issues, I am sharing this in case any user faces the same issue while enabling extensions. I tested this on a non-production flarum and the extension is now working perfectly fine.

huseyinfiliz

🚀 Stickiest 2.0.0-beta.2 — 2.x Beta-8 Compatibility

Targets Flarum 2.x
Release URL: huseyinfiliz/stickiestreleases/tag/2.0.0-beta.2

Add admin toggle to show/hide sticky highlight styling (colored border & background) @navindra

Fix TypeError caused by tag filter being passed as array instead of string in Flarum 2.x beta8+
Refactor StickySearchMutator to use getActiveFilters() + instanceof TagFilter (matching flarum/sticky 2.x approach)
Remove ->after('is_sticky') from migration — flarum/sticky is now optional, not required
Add unit and integration test suite

Full Changelog: huseyinfiliz/stickiest2.0.0-beta.1 → 2.0.0-beta.2

What changed?

Beta8 compatibility fix — Flarum 2.x beta8 changed how search filters are passed internally. The tag filter value was now arriving as an array instead of a string, causing TagRepository::getIdForSlug() to throw a TypeError on every discussion list request. The mutator now uses getActiveFilters() with instanceof TagFilter — the same pattern used by flarum/sticky itself — which is robust across all beta versions.

Highlight toggle — A new admin setting lets you disable the colored left border and background tint on sticky discussions in the discussion list. Enabled by default.

Migration fix — The ->after('is_sticky') column placement hint required flarum/sticky to already be installed. Since that extension is now optional, this caused a crash on fresh 2.x installs without it. The hint has been removed; column order is cosmetic only.

How to update

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

Or use Extension Manager to update.

🔧 GitHub
📦 Packagist

If you run into any issues, feel free to reply here or send me a message.

huseyinfiliz

🚀 Stickiest 1.0.2 — Tag Sticky Index Fix & CI/CD

Targets Flarum 1.x

Release URL: huseyinfiliz/stickiestreleases/tag/v1.0.2

Fix PDOException 1072 (Key column 'is_tag_sticky' doesn't exist) on fresh installs
Fix PDOException 1061 (Duplicate key name) after Purge & Re-enable
Add integration test infrastructure with regression tests for both migration bugs
Add GitHub Actions CI/CD (backend + frontend workflows)

Full Changelog: huseyinfiliz/stickiestv1.0.1 → v1.0.2

What changed?

Heavenly Several reported that enabling the extension on a fresh Flarum installation threw one of two errors:

SQLSTATE[42000]: Syntax error or access violation: 1072 Key column 'is_tag_sticky' doesn't exist in table

SQLSTATE[42000]: Syntax error or access violation: 1061 Duplicate key name 'flarum_discussions_is_tagsticky_last_posted_at_index'

The root cause was a migration ordering bug: 2022_07_21_000000 was attempting to add an index on the is_tag_sticky column before that column was created (which happens in 2022_07_21_000002). Additionally, a naming inconsistency between is_tagSticky (camelCase, used in early migrations) and is_tag_sticky (snake_case, used in later ones) caused duplicate or missing indexes depending on the installation state.

This release adds a new fix migration that handles all affected states idempotently:

Drops leftover camelCase indexes (is_tagSticky) if present
Adds the is_tag_sticky column if missing
Adds correct snake_case indexes if missing

Affected migration: 2026_03_24_000000_fix_tag_sticky_indices_consistency.php

This release also introduces an integration test suite using flarum/testing with regression tests that will catch this class of migration bug automatically going forward, and GitHub Actions CI running on PHP 8.1/8.2/8.3 against both MySQL and MariaDB.

How to update

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

Or use Extension Manager to update.

🔧 Github
📦 Packagist

If you run into any issues, feel free to reply here or send me a message.

rob006

@huseyinfiliz FYI: "flarum/core": ">=1.2.0" constraint used by 1.x is too wide - this version of extension is also installable on Flarum 2.x

navindra

huseyinfiliz Add admin toggle to show/hide sticky highlight styling (colored border & background) @navindra

Thank you so much!

I really appreciate your explanations of the various fixes as well.