📌 Stickiest - Super Sticky

Heavenly

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.

Tutuzaiganma

huseyinfiliz
When I used it myself, I still found several issues. I have now fixed all of them—please take a look:
Tutuzaiganma/flarum-sticky-custom
Fixed database errors on fresh Flarum installations.
Fixed an issue where super sticky discussions could make bottom discussions disappear on the first page when used with pagination extensions.
Fixed a non-array tag state issue that prevented opening the sticky configuration modal after switching tag filters.

huseyinfiliz

Tutuzaiganma The 1.x version belongs to the-turk, and I didn’t do much development on it. I basically republished it as-is after the-turk took it down. The 2.x version, on the other hand, was written from scratch and has a somewhat different architecture.

After reviewing your changes, I can see some nice improvements. With your permission, I’d like to apply these to the 1.x version as well. It doesn’t seem possible to merge them directly as a PR. I also got the impression that some common mistakes I often see in vibe coding were made I don’t mean this as an accusation, so please don’t take it the wrong way.

Thank you for your time and contributions. I’ll take a closer look at your improvements tomorrow and incorporate the necessary adjustments.

Tutuzaiganma

huseyinfiliz
It’s absolutely fine to apply these improvements, since I’m not familiar with the code for this project and can only rely on AI to fix the issues. If it helps you resolve them, that would be even better.

KBExit

Trying to install this extension via Extension Manager throws this:

/var/www/html/composer.json has been updated
Running composer update huseyinfiliz/stickiest --with-all-dependencies
Loading composer repositories with package information
<warning>Warning: the packages key 'kilowhat/flarum-ext-audit-pro' doesn't match the name defined in the package metadata 'kilowhat/flarum-ext-audit' in repository https://floxum.com/composer</warning>
Updating dependencies
Dependency resolution completed in 0.002 seconds
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires flarum/sticky * -> satisfiable by flarum/sticky[v1.0.0, v1.1.0, v1.2.0, v1.3.0, v1.4.0, v1.5.0, v1.6.0, v1.6.1, v1.7.0, v1.8.0, v1.8.1, v1.8.2].
    - flarum/sticky v1.0.0 requires flarum/core ^1.0 -> found flarum/core[v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4, v1.1.0, v1.1.1, v1.2.0, v1.2.1, v1.3.0, v1.3.1, v1.4.0, v1.4.1, v1.5.0, v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky v1.1.0 requires flarum/core ^1.1 -> found flarum/core[v1.1.0, v1.1.1, v1.2.0, v1.2.1, v1.3.0, v1.3.1, v1.4.0, v1.4.1, v1.5.0, v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky v1.2.0 requires flarum/core ^1.2 -> found flarum/core[v1.2.0, v1.2.1, v1.3.0, v1.3.1, v1.4.0, v1.4.1, v1.5.0, v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky v1.3.0 requires flarum/core ^1.3 -> found flarum/core[v1.3.0, v1.3.1, v1.4.0, v1.4.1, v1.5.0, v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky v1.4.0 requires flarum/core ^1.4 -> found flarum/core[v1.4.0, v1.4.1, v1.5.0, v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky v1.5.0 requires flarum/core ^1.5 -> found flarum/core[v1.5.0, v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky[v1.6.0, v1.6.1] require flarum/core ^1.6 -> found flarum/core[v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky v1.7.0 requires flarum/core ^1.7 -> found flarum/core[v1.7.0, v1.7.1, v1.7.2, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).
    - flarum/sticky[v1.8.0, v1.8.1, v1.8.2] require flarum/core ^1.8 -> found flarum/core[v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.8.6, v1.8.7, v1.8.8, v1.8.9, v1.8.10, v1.8.11, v1.8.12, v1.8.13, v1.8.14] but it conflicts with your root composer.json require (^2.0).


Installation failed, reverting /var/www/html/composer.json and /var/www/html/composer.lock to their original content.

huseyinfiliz

KBExit For Flarum 1.x:

composer require huseyinfiliz/stickiest:"1.0.2"

For Flarum 2.x:

composer require huseyinfiliz/stickiest:"2.0.0-beta.2"

Please try it this way. Most likely, the correct version was not automatically selected between 1.x and 2.x. I will fix this issue as soon as possible.

KBExit

huseyinfiliz that worked after I purged extension manager on that client site. I think the failed attempts sat in Redis queue / cache preventing it from moving forward as that was the third time I attempted it.

yannis

It disappears when pinned without tags. 🙃

luceos

huseyinfiliz Please try it this way. Most likely, the correct version was not automatically selected between 1.x and 2.x. I will fix this issue as soon as possible.

rob006 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

Best solution here is to remove the 1.x compatible versions that have the wrong core constraint and tag a new version that has the right constraint for 1.*, alternatively if you want to maintain the old versions you can git clone -b <version> then fix the constraint, commit and force push the same tag to overwrite the change. Packagist will pick up on this.

anoedo

huseyinfiliz Thank you so much for the update! I was able to install the plugin successfully. I really appreciate it!

gamingto12

Hello, I just installed this extension on a somewhat fresh installation of flarum (made a few posts, groups, nothing too crazy) and it will not start, and after grabbing the logs from today (4/15), I found this

"Next Illuminate\Database\QueryException: SQLSTATE[42000]: Syntax error or access violation: 1072 Key column 'is_tag_sticky' doesn't exist in table (SQL: alter table ff_discussions add index ff_discussions_is_tag_sticky_last_posted_at_index(is_tag_sticky, last_posted_at)) in /var/www/flarum/vendor/illuminate/database/Connection.php:712"

Now, I am running Flarum version 1.8.15 and had installed the version of the extension that targets version 1.x
I have tried clearing the cache via the admin panel, but that led to nothing. I apologize for what seems to be a stupid question, but I genuinely don't know what I need to do in this scenario.

huseyinfiliz

gamingto12 I'm not sure, but the issue might be caused by the prefix. I'll fix it as soon as possible. The problem is coming from version 1.x, right?

huseyinfiliz

🚀 Stickiest 1.0.3 — Compatibility & Bug Fixes

Targets Flarum 1.x

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

Flarum 2.x Protection: Updated the flarum/core constraint to ^1.2.0 to prevent accidental installations and fatal errors on Flarum 2.x systems. rob006 KBExit luceos
Important Cleanup: Because the 1.x branch inherited legacy bugs from the original extension, and to completely eliminate Flarum 2.x installation risks, all versions prior to 1.0.3 have been permanently removed from Packagist and GitHub.
Fresh Install Fix: Resolved a critical migration sequence bug (SQLSTATE 1072: Key column 'is_tag_sticky' doesn't exist) that caused fresh Flarum installations to crash. gamingto12

How to update

Since older versions have been deleted from the registry, it is required to specify the version to refresh your local composer cache:

composer require huseyinfiliz/stickiest:"^1.0.3"
php flarum cache:clear

Or use Extension Manager to update.

huseyinfiliz

yannis I believe you’re referring to the issue in Flarum 2.x. Yes, I will release a fix as soon as possible to prevent saving in the modal without selecting a tag in 2.x. In the meantime, please make sure not to enable the tag sticky feature without selecting a tag.

« Previous Page