# I'm trying to activate the FSE (Full site editing)

**URL:** https://discourse.roots.io/t/im-trying-to-activate-the-fse-full-site-editing/22370
**Category:** sage
**Tags:** sage9
**Created:** 2022-02-21T21:45:40Z
**Posts:** 8

## Post 1 by @chacha_admin — 2022-02-21T21:45:40Z

I added add\_theme\_support( ‘wp-block-styles’ ); and the folder templates with, at least, the file index.html to allow it. With a virgine theme, I’m able to do it but with your theme, no. It’s a custom version of your theme but normally, It is suppose to work well.

---

## Post 2 by @ben — 2022-02-21T21:58:57Z

What version of Sage?

---

## Post 3 by @strarsis — 2022-02-21T22:29:29Z

There is an issue/PR for Sage 10 + FSE support:

> <https://github.com/roots/sage/issues/2828>
>
> * [x] I've read the [guidelines for Contributing to Roots Projects](https://gith…ub.com/roots/.github/blob/master/CONTRIBUTING.md)
> * [x] This request isn't a duplicate of an existing issue
> * [x] I've read the [docs](https://roots.io/documentation/) and followed them (if applicable)
> * [x] This is not a personal support request that should be posted on the [Roots Discourse](https://discourse.roots.io/) community
> 
> ## Description
> Full Site Editing (FSE) with Sage 10 theme loads a blade template in frontend, no Website editor blocks are shown.
> 
> ## Steps to reproduce
> 1. Ensure a Sage 10 theme is present and enabled.
> 2. Enable Full Site Editing (FSE) support in the Sage 10 theme.
> 3. Add some modifications to the Website editor.
> 4. Add/edit a page (front page).
> 5. Open the front page on frontend.
> Note that the site blocks from the Website editor are not loaded, instead the default blade-based template.
> 
> **Expected behavior:**
> Frontend shows the blocks from website editor.
> 
> **Actual behavior:**
> Frontend doesn't show the blocks from website editor, but the default blade template instead.
> 
> **Reproduces how often:**
> Always.
> 
> ## Versions
> `1.16.1: 2021-07-30`
> 
> ## Additional information
> Latest Gutenberg plugin `11.7.1`.
> 
> The previous code for adding compatibility for Full Site Editing (FSE) doesn't work (anymore):
> ```php
> // Sage 10 + Gutengberg Full Site Editing (FSE) template compatibility
> // @see https://discourse.roots.io/t/sage-10-block-based-theme-support/17294/2?u=strarsis
> add_filter('template_include', function ($template_file) {
> global $_wp_current_template_hierarchy;
> $_wp_current_template_hierarchy = array_map('basename', $_wp_current_template_hierarchy);
> return $template_file;
> }, 19);
> 
> ````

There are still some inconsistencies with the Gutenberg plugin.

---

## Post 4 by @chacha_admin — 2022-02-22T14:00:37Z

### 9.0.9: February 13th, 2019

---

## Post 5 by @strarsis — 2022-02-22T18:10:27Z

What kind of issue occurs? Does the Full Site Editing part in backend doesn’t appear?  
Are FSE block templates or block parts not loaded?

---

## Post 6 by @chacha_admin — 2022-02-22T18:42:36Z

Mostly, I dont have the Editor in themes that allow me to handle the template, etc.

---

## Post 7 by @neoswf — 2023-09-22T00:26:53Z

@chacha_admin have you ever managed to solved this?

---

## Post 8 by @strarsis — 2023-09-22T09:02:37Z

This is a Sage 10 FSE theme, but the same rules should apply for Sage 9 (specific files in place), this may be helpful:

> **[GitHub - strarsis/sage10-fse: Sage 10 theme adjusted for Gutenberg Full Site...](https://github.com/strarsis/sage10-fse)**
>
> Sage 10 theme adjusted for Gutenberg Full Site Editing (FSE) - GitHub - strarsis/sage10-fse: Sage 10 theme adjusted for Gutenberg Full Site Editing (FSE)