Diff for Flarum (New)

huseyinfiliz · 2025-12-09T13:08:57+00:00

📜 Diff for Flarum 📝 Description Diff allows you to view post edit histories on your Flarum forum. Track changes, compare revisions, and even rollback to previous versions. This is the maintained fork of the original the-turk/flarum-diff extension. Both Flarum 1.x and Flarum 2.x are supported — install the version that matches your Flarum. ✨ Screenshots 📊 Post-Stream Item 📋 Revision Dropdown List 🚀 Key Features ✅ Multiple Detail Levels - Line (default), word, and character level diffs 🎨 Three Render Modes - Inline, Side by Side & Combined views 📦 Archive Old Revisions - Save storage with automatic compression ⏪ Rollback Support - Revert to any previous revision 🗑️ Delete Revisions - Remove unwanted edit history 🌙 Dark Mode Support - Native Flarum 2.x dark mode compatible ⏰ Cron Job Support - Automated archiving with scheduler 🔇 Quiet Edits Support - Works with the-turk/flarum-quiet-edits 📥 Installation Flarum 1.x: composer require huseyinfiliz/flarum-diff:"^1.0" php flarum migrate php flarum cache:clear if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Flarum 2.x: composer require huseyinfiliz/flarum-diff:"*" php flarum migrate php flarum cache:clear if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } ⚠️ Upgrading from the-turk/flarum-diff Note on settings: Extension settings won't transfer automatically due to the namespace change (the-turk-diff.* → huseyinfiliz-diff.*). Simply reconfigure your preferences in the admin panel after installation. Your revision history is not affected. ⚙️ Configuration After installation, go to Admin Panel → Extensions → Diff to configure: Detail Level - None, Line, Word, or Character level Neighbor Lines - How many context lines to show Merge Threshold - For Combined renderer (0-1) Archive Options - Automatic archiving with A, m, b parameters Cron Jobs - Enable scheduled archiving 🗄️ Archive Old Revisions If x ≥ A (where x is post's revision count), first y=mx+b revisions will be stored as merged & compressed. Configure A, m, and b values in settings. For automated archiving, enable cron jobs and add this to your server: * * * * * php /path/to/flarum schedule:run >> /dev/null 2>&1 if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Or run manually: php flarum diff:archive 🔐 Permissions Configure in Admin Panel → Permissions: View edit history - Who can see revision history Delete own/others edit history - Who can remove revisions Rollback own/others edit history - Who can revert to previous versions ♻️ Updating composer update huseyinfiliz/flarum-diff php flarum migrate php flarum cache:clear if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } 📋 Requirements Flarum 1.x: PHP ≥ 7.4, ext-iconv Flarum 2.x: PHP ≥ 8.1, ext-iconv 🔗 Links Discuss Packagist GitHub 🙏 Credits Original Extension: Hasan Özbey (the-turk) Fork & Maintenance: Hüseyin Filiz If you find this extension helpful, feel free to ⭐ star the repository and share your feedback! If you liked this extension, don’t forget to check out my other extensions too: huseyinfiliz.com/flarum

huseyinfiliz

Diff

🔧 v2.0.0-beta.2 - Critical Migration Fix

This release fixes a critical data loss issue reported after beta.1.

🐛 Bug Fix

Fixed: Revision history data loss during upgrade

When upgrading from the-turk/flarum-diff, the migration was dropping and recreating tables even when they contained existing revision data. This caused complete loss of all revision history.

The migration files now check if tables contain data before any operations:

✅ If table has data → preserve it, skip recreation
✅ If table is empty → safe to recreate for clean schema
✅ Proper foreign key handling when recreation is needed

✅ Automated Migration Testing

We've added a comprehensive GitHub Actions workflow that tests the complete upgrade scenario:

Install Flarum 1.8 + the-turk/flarum-diff
Create revision data via API
Upgrade to Flarum 2.x
Install huseyinfiliz/flarum-diff
Verify all revision data is preserved

Every release is now automatically tested for data safety.

Check it: huseyinfiliz/flarum-diffactions/runs/20090483428

🔧 Installation

composer require huseyinfiliz/flarum-diff:"*"

🔄 Update

composer update huseyinfiliz/flarum-diff
php flarum migrate
php flarum cache:clear

🔗 Links

Packagist
GitHub
Original Extension (Flarum 1.x)

💡 Feedback & Suggestions

Feel free to share your ideas, report bugs, or request features in the discussion thread!

⚠️ If you lost data with beta.1, unfortunately it cannot be recovered. We apologize for this issue and have implemented safeguards to prevent it from happening again. navindra

navindra

huseyinfiliz Wow, that's quite an unintentional booby trap... destroying the table on creation. I really appreciated your in-depth explanation as well, it all makes sense now!

Thanks a ton for your fix, I can confirm it works great and preserves my data!

The rollback functionality isn't quite working correctly.

I created an original post and edited it with #1, #2, #3 in the content. Then I rolled back the last revision. In the history, #3 is now gone, and weird new entries are created:

These are the two last log entries... it should just show a regular diff and it should not truncate the last #3 change from the list. I confirmed on Diff 1.x that it works as expected.

This is not trivial work, so thanks a ton!

huseyinfiliz

navindra While upgrading to Flarum 2.x, many functions had to be rewritten from scratch. There’s probably a silent error somewhere. It seems more action tests need to be added. Thanks for reporting it.

huseyinfiliz

Diff

🔧 v2.0.0-beta.3 - Rollback Fix

This release fixes a rollback functionality issue reported after beta.2.

🐛 Bug Fix

Fixed: Revision history corruption during rollback

When rolling back to a previous revision, the revision being rolled back from was not being preserved correctly in the history. This caused the rolled-back revision's content to disappear from the history. (navindra )

Example of the bug:

Post edited: 123 → 456 → 789
Rollback to original (123)
❌ Before fix: History showed 123 → 456 → 123 (missing 789)
✅ After fix: History shows 123 → 456 → 789 → 123

Root cause: In Flarum 2.x, the EditPost command was removed and replaced with the new Resource-based API. The previous implementation wasn't capturing the correct oldContent value before dispatching the Revised event.

Changes made:

RollbackToDiffHandler.php: Now captures current content before modification and dispatches Revised event with correct oldContent
PostActions.php: Now prefers $event->oldContent from the Revised event for more reliable revision tracking

🔧 Installation

composer require huseyinfiliz/flarum-diff:"*"

🔄 Update

composer update huseyinfiliz/flarum-diff
php flarum cache:clear

🔗 Links

💡 Feedback & Suggestions

Feel free to share your ideas, report bugs, or request features in the discussion thread!

navindra

huseyinfiliz It's working! Yay!

Very very cool. I rolled back, rolled forward, did edits, rolled back... everything worked.

And I appreciate your in-depth explanations a ton as well.

Thank you so much for this excellent work! 👏

navindra

I'm back with another small bug. I just noticed that this extension changes the colors of PianoTell. Mainly the grey parts are not expected:

Without the extension, PianoTell looks like this:

huseyinfiliz

navindra I think the reason for this is not this extension but Stickiest. If that's the case, please report this reply and move it to the Stickiest discussion. It's important for tracking bugs correctly and informing other users accurately.

navindra

huseyinfiliz I thought so too, however the colors go back to normal when this extension is disabled. I'm not referring to the highlight from Stickiest.

huseyinfiliz

navindra Now I understand the issue. I got confused because you highlighted the gray section in the other extension as well. The fact that this hero section is gray is actually a bug in the Diff extension, and I’ll release an update today that fixes it.

Capybara

@huseyinfiliz Hi! In the first days of January, I’ll be re-releasing my extensions, and one of them uses a database to store dice roll values. I vaguely saw that you had dealt with a database migration issue before. Is there anything I need to do before releasing the extension?

huseyinfiliz

Capybara From my experience, the safest approach in migrations is not to drop and recreate tables if they already exist. Instead, it’s better to check the table and columns individually and only add the missing columns when necessary, or even leave the table untouched if no changes are required. This helps avoid data loss and makes upgrades much smoother for existing installations.

huseyinfiliz

Diff

🔧 v2.0.0-beta.4 - CSS Fix

🐛 Bug Fix

Fixed: Resolved the CSS variable conflict reported by navindra

The extension was overriding root-level --control-bg which affected the hero section background color. LESS variables are now properly prefixed to avoid conflicts with Flarum core styles.

Note: The original extension by the-turk for version 1.8.x has been unpublished. Therefore, our GitHub Actions test scenario for upgrading from 1.8 to 2.x no longer works, and this is expected. Since this update only contains changes to LESS files, I'm confident there are no issues with the 1.8 to 2.x migration path.

🔧 Installation

composer require huseyinfiliz/flarum-diff:"*"

🔄 Update

composer update huseyinfiliz/flarum-diff
php flarum cache:clear

🔗 Links

💡 Feedback & Suggestions

Feel free to share your ideas, report bugs, or request features in the discussion thread!

navindra

huseyinfiliz The fix is working great for me, thank you very much!

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/flarum-diff:"^1.0"
php flarum migrate
php flarum cache:clear

This version is a namespace migration of the original the-turk/flarum-diff. 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.

Ghost_chu

coloured diff seems not working on Flarum 1.8 (with huseyinfiliz-diff 1.0.0)

Installed PHP modules:

[PHP Modules]
apcu
bcmath
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
gd
gettext
hash
iconv
igbinary
intl
json
lexbor
libxml
mbstring
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_pgsql
pdo_sqlite
pgsql
Phar
posix
random
readline
redis
Reflection
session
SimpleXML
sodium
SPL
sqlite3
standard
tidy
tokenizer
uri
uuid
xml
xmlreader
xmlwriter
yaml
Zend OPcache
zip
zlib

[Zend Modules]
Zend OPcache

huseyinfiliz

Ghost_chu I can confirm the issue. It seems to be a general bug. I will release an update to fix this as soon as possible. Thanks for reporting it!

huseyinfiliz

🔧 v1.0.1 - CSS Fix

Target: 1.x

**Fixed: CSS selector reported by Ghost_chu

🔧 Installation

composer require huseyinfiliz/flarum-diff:"*"

🔄 Update

composer update huseyinfiliz/flarum-diff
php flarum cache:clear

🔗 Links

💡 Feedback & Suggestions

Feel free to share your ideas, report bugs, or request features in the discussion thread!

Subarist

When using this together with #30064
, clearing the “last edit” causes the Diff link to disappear.

« Previous Page