🙏 A Quick Thank You
Before anything else, thank you to everyone using FleekDash, reporting issues, suggesting improvements, and sharing honest feedback.
That constant back-and-forth is what keeps the product moving in the right direction. Every bug report, every feature request, every “this could be smoother” directly influences what we build next.
We don’t take that lightly.
🔄 Updates Are Frequent, and That’s Intentional
If you’ve been following FleekDash V2, you’ve probably noticed one thing: we release often.
2.2.7 (Jan 07) – Tabs navigation performance improvements
2.2.8 (Jan 19) – Search, Command Palette & Fullscreen overhaul
2.2.9 (Jan 24) – Admin Bar enhancements, migration & URL parameter fixes
2.3.0 (Feb 13) – Menu & Admin Bar improvements, post duplication, demo mode, migration fixes
2.3.1 (Feb 19) – Plugins grid reliability, items-per-page persistence, menu root-cause fixes
We believe in iterative delivery. Smaller, focused releases mean:
Bugs get fixed faster
Features land incrementally
You’re not waiting months for improvements
Each release carries less risk
The goal is steady, predictable improvement, not big, disruptive drops that create more problems than they solve.
🎯 We Want to Leave Beta, But We Won’t Force It
FleekDash V2 is still in beta. Yes, we want to reach a stable 1.0 (or equivalent) as soon as possible. But we won’t rush it.
Quality Over Deadlines
We fix root causes, not surface symptoms. Shipping a “stable” tag just to hit a date would trade long-term trust for short-term optics. We’d rather release a few more beta iterations and get it right.
Feedback Is Part of the Product
The beta phase is where we learn the most. Real users, real environments, real edge cases. Leaving beta too early would cut short the feedback loop that’s actively improving the product for everyone.
Technical Debt Is Expensive
Rushing leads to shortcuts. Shortcuts become technical debt. Technical debt slows development and increases regressions. We’d rather invest the time now so future updates stay fast and reliable.
No Artificial Milestones
We’re not chasing a random “beta exit” date. We’re chasing a product that feels solid, predictable, and truly production-ready. When the beta label disappears, it will mean we’re confident, not that the calendar told us to.
✅ Yes, It’s Beta. And Yes, It’s Safe for Production 💪
Here’s the important part: even with the beta label, FleekDash V2 is safe to use in production.
We already have hundreds of users running V2 on real websites, agencies, freelancers, content teams, and businesses. It’s powering real workflows, real content, and real client projects.
Why We’re Confident
Frequent, focused updates: Issues get addressed quickly.
Root-cause fixes: We solve underlying problems, not just patch symptoms.
Real-world validation: Hundreds of production installs continuously test the system.
Graceful fallbacks: When something fails, it degrades instead of crashing.
Daily usage of critical flows: Auth, menu, grids, and search are exercised constantly.
Our Commitment
We do not ship known critical bugs.
We fix regressions fast.
We communicate clearly when something changes or breaks.
The beta label reflects ongoing evolution, not instability or lack of testing.
✨ What's New in 2.3.0 and 2.3.1
Here’s a consolidated recap of this cycle.
Version 2.3.0 (February 13, 2026)
Menu & Admin Bar Enhancements
Improved overall menu stability and search behavior
Refactored sidebar menu for better consistency and reduced instability
Fixed auto-hide issues in the Admin Bar
Introduced bottom position option for the Admin Bar
Integrated Rank Math for improved compatibility
New Functional Additions
Save page mode state on Posts, Pages, and Plugins
Implemented post duplication endpoint and functionality
Enabled demo mode in login settings
Bug Fixes & Stability Improvements
Fixed “Duplicate foreign key constraint” errors during database migrations
Improved migration error handling
Resolved auto-hide behavior inconsistencies
Enhanced admin bar compensation and padding resets in iframe contexts
Performance & Internal Improvements
Removed unused API calls
Improved stability around migrations and state persistence
General internal refinements to reduce edge-case failures
Version 2.3.1 (February 19, 2026)
Plugins Grid – Update Badge Reliability
Immediate visual feedback after updating a plugin
Badge always fetches the latest update info when opening the Plugins page
No full page refresh required to see the correct status
Dashboard Grids – Items Per Page Persistence
Users, Posts, and Comments grids remember your preferred items-per-page setting
Hover effects added to the page size selector for clearer feedback
Fixed issue where the setting would reset to default
Menu Random Refresh & Missing Items, Root Cause Fixes
Prevented SidebarMenu remount when toggling auto-hide
Guard added against empty responses overwriting valid cached menus
Polling safety improvements to prevent partial or empty responses from corrupting the menu
Cache invalidation API alignment for reliable useMenuCacheInvalidation behavior
🚀 What’s Next
We’ll keep shipping frequent updates, listening closely to feedback, and fixing root causes. When FleekDash consistently meets our internal bar for stability, predictability, and polish, we’ll remove the beta label, without cutting corners.
Until then, thanks for building this with us. Your trust and feedback genuinely matter.
Try FleekDash V2: https://fleekdash.com
