WordPress 4.9 in Retrospect - The Release Before Gutenberg

WordPress 4.9 “Tipton” (released in 2017) was a special release. It was the last major version before the 5.0 Revolution, which introduced the Gutenberg editor.

Learn more about WordPress development services at WPPoland. Looking back from 2026, version 4.9 was the moment WordPress “matured” as a developer platform, introducing features we now take for granted.

If you want the short version, WordPress 4.9 matters because it improved real editorial and developer workflows just before Gutenberg changed the entire editing model.

#The historical context: WordPress 4.9 as a turning point

WordPress 4.9 “Tipton” (named after jazz musician Billy Tipton) was released on November 16, 2017. It represented the culmination of the “classic” WordPress era – the last version before Gutenberg fundamentally changed how we build WordPress sites.

Why 4.9 Matters:

• It was the final version of the “classic” WordPress editor
• It introduced developer tools we still use today
• It set the foundation for the block editor revolution
• It marked WordPress’s transition from “blogging platform” to “full CMS”

#What WordPress 4.9 brought: A developer’s perspective

#1. Customizer drafts & scheduled changes

The Feature: For the first time, we could make design changes (Colors, CSS), save them as a “Draft”, and send a preview link to a client – without publishing changes live!

Why It Mattered: Before 4.9, making design changes meant:

• Editing live site (risky)
• Using staging environments (complex)
• Manual CSS injection (hacky)

How It Works:

// Customizer now supports draft changes
$wp_customize->add_setting('header_color', array(
    'default' => '#0073aa',
    'transport' => 'postMessage',
    'type' => 'theme_mod',
));

// Changes saved as drafts, not published immediately

Impact:

• Client approval workflow became standard
• Reduced “oops, I published too early” mistakes
• Professional design process

2026 Perspective: While Gutenberg replaced much of the Customizer’s functionality, the draft/schedule concept lives on in the block editor’s revision system.

#2. Codemirror integration

The Feature: Code editors in the dashboard (e.g., in “Theme Editor” or “Additional CSS”) finally got syntax highlighting and line numbering. No more breaking the site due to a missing semicolon.

Why It Mattered: Before 4.9, editing code in WordPress meant:

• Plain text editors (no syntax highlighting)
• No line numbers (hard to debug)
• No error detection
• High risk of breaking sites

What CodeMirror Added:

• Syntax Highlighting: PHP, CSS, JavaScript, HTML
• Line Numbers: Easy error reporting
• Code Folding: Collapse functions/blocks
• Bracket Matching: Find matching brackets
• Auto-indentation: Proper code formatting
• Search & Replace: Find code quickly

Example:

// Before 4.9: Plain text editor
function my_function() {
return 'hello';
}

// After 4.9: CodeMirror shows syntax errors
function my_function() {
    return 'hello'; // Proper indentation highlighted
}

Impact:

• Reduced coding errors in dashboard
• Made WordPress more developer-friendly
• Set standard for code editing in CMS

2026 Perspective: CodeMirror is still used in WordPress 6.x for theme/plugin editing, though Gutenberg’s block editor has reduced reliance on direct code editing.

#3. Gallery widget improvements

The Feature: Adding photo galleries to the sidebar became native and more intuitive.

Before 4.9:

• Required plugins for advanced galleries
• Limited customization options
• Clunky interface

After 4.9:

• Native gallery widget
• Drag-and-drop image selection
• Better mobile support
• Improved performance

Impact:

• Made galleries accessible to non-developers
• Reduced need for gallery plugins
• Improved user experience

2026 Perspective: Gallery widgets are now replaced by Gutenberg gallery blocks, but the 4.9 improvements paved the way for better media management.

#Additional features IN WordPress 4.9

#4. Improved theme installation

What Changed:

• Better theme preview
• Improved search functionality
• Enhanced theme information display

#5. Widget improvements

What Changed:

• Better widget management
• Improved widget preview
• Enhanced customization options

#6. Security enhancements

What Changed:

• Improved file type detection
• Better sanitization
• Enhanced security headers

#The road to WordPress 5.0: The Gutenberg revolution

#Timeline

2017 (4.9):

• Last “classic” WordPress version
• Foundation for Gutenberg laid
• Community preparing for change

2018 (5.0):

• Gutenberg editor introduced
• Classic Editor plugin released
• Community split begins

2019-2021:

• Gutenberg matures
• Block patterns introduced
• Full Site Editing (FSE) development

2022-2026:

• FSE becomes standard
• Block themes dominate
• Classic Editor usage declines

#The community split

Just a year after 4.9, WordPress 5.0 arrived with Gutenberg. The community split into two camps:

Traditionalists:

• Stuck with the “Classic Editor” plugin
• Continued using PHP-based themes
• Preferred page builders (Elementor, Divi)
• The Classic Editor plugin still has millions of installs

Modern Creators:

• Embraced the Full Site Editing (FSE) model
• Everything – including header and footer – built with blocks
• Adopted block themes
• Leveraged block patterns and templates

The Numbers (2026):

• ~40% of sites still use Classic Editor plugin
• ~60% have adopted Gutenberg
• Block themes: ~15% market share (growing)
• Classic themes: ~85% market share (declining)

#WordPress 4.9’s legacy

#What we learned

1. Incremental Improvements Matter 4.9 showed that small, focused improvements can have big impacts. CodeMirror integration, while seemingly minor, made WordPress significantly more developer-friendly.

2. Developer Experience is Important Features like Customizer drafts and CodeMirror showed WordPress cared about developers, not just end users.

3. Foundation for Change 4.9’s improvements set the stage for Gutenberg. The draft/schedule system in Customizer influenced Gutenberg’s revision system.

#What still matters today

CodeMirror:

• Still used in theme/plugin editors
• Still the standard for code editing in WordPress
• Improved in subsequent versions

Customizer Drafts:

• Concept lives on in Gutenberg revisions
• Scheduled changes still available
• Preview links still used

Developer Tools:

• 4.9’s focus on developer experience continues
• Modern WordPress prioritizes developer tools
• Better debugging, better APIs

#Comparing WordPress 4.9 to modern WordPress (2026)

#Then (4.9) vs. Now (6.x)

Theme Development:

• 4.9: PHP templates, functions.php, hooks
• 2026: Block themes, theme.json, FSE

Content Editing:

• 4.9: Classic editor, shortcodes, widgets
• 2026: Gutenberg blocks, patterns, templates

Customization:

• 4.9: Customizer, theme options
• 2026: Site Editor, block settings

Developer Tools:

• 4.9: CodeMirror, basic debugging
• 2026: Advanced debugging, React DevTools, block development tools

#What’s changed

Removed:

• Classic editor (optional plugin)
• Many Customizer features (replaced by Site Editor)
• Widget system (replaced by blocks)

Improved:

• Code editing (still CodeMirror, but better)
• Developer APIs (more hooks, better documentation)
• Performance (faster, more efficient)

New:

• Block editor
• Full Site Editing
• Block patterns
• Theme.json
• React-based development

#Lessons for developers

#1. Embrace change

WordPress 4.9 → 5.0 showed that major changes are possible. As a developer, staying current is essential.

#2. Backward compatibility matters

WordPress maintained backward compatibility even through major changes. Classic Editor plugin ensures old sites still work.

#3. Developer tools are essential

CodeMirror integration showed that developer experience matters. Modern WordPress continues this trend.

#4. Community feedback shapes WordPress

The split between traditionalists and modern creators shows WordPress listens to its community, even when making controversial decisions.

#The future: What’s next after blocks?

Current Trends (2026):

• AI integration in WordPress
• Headless WordPress growth
• Performance optimization focus
• Accessibility improvements

What We Can Learn from 4.9:

• Incremental improvements build to major changes
• Developer tools matter
• User experience is paramount
• Backward compatibility is crucial

#Summary: WordPress 4.9’s place IN history

WordPress 4.9 “Tipton” was more than just another version – it was the last version of “classic” WordPress before the Gutenberg revolution.

Key Achievements:

• ✅ Introduced Customizer drafts (client workflow)
• ✅ Integrated CodeMirror (developer experience)
• ✅ Improved gallery widgets (user experience)
• ✅ Set foundation for Gutenberg

Historical Significance:

• Last major version before block editor
• Culmination of classic WordPress era
• Bridge between old and new WordPress
• Proof that incremental improvements matter

2026 Perspective: Today, in 2026, the debate between classic and blocks is largely history. Blocks won. But it’s worth remembering version 4.9 as the “last bastion” of the classic PHP theme building approach – a version that perfected the old way before the new way took over.

For Developers:

• Study 4.9 to understand classic WordPress
• Appreciate the improvements it brought
• Learn from the transition to Gutenberg
• Apply lessons to future WordPress changes

WordPress 4.9 represents a moment in time – the calm before the storm, the perfection of the old before the introduction of the new. It’s a version worth studying, not just for historical context, but for understanding how WordPress evolves and how major platform changes are managed.