# Full Width Posts

**URL:** https://discourse.roots.io/t/full-width-posts/915
**Category:** uncategorized
**Created:** 2013-12-18T21:41:20Z
**Posts:** 9

## Post 1 by @Skylab — 2013-12-18T21:41:20Z

After reading through [http://roots.io/the-roots-sidebar/](http://roots.io/the-roots-sidebar/), I’m trying to figure out the best way to get full width post on user selection. A post template would be ideal but that doesn’t seem possible with Roots. No selection or options for post templates.

The only thing I’ve figured out is with in the config.php file under roots\_display\_sidebar. I can put in array(‘is\_single’, array(‘169’, ‘170’)) with the numbers corresponding to the post ID’s. But providing the user an option while editing a post to add to the array is where I’m stuck.

Any solutions to this? What did you do to get full-width for certain posts? I’m going to check out “Custom Metaboxes and Fields” right now to see if that helps as well.

Thanks!

---

## Post 2 by @Foxaii — 2013-12-18T22:45:50Z

My [Roots Wrapper Override](http://roots.io/plugins/roots-wrapper-override/) plugin will enable you to do this.

Just create a second base template without the sidebar and select that from the drop down menu on the posts/pages you want the sidebar removed from.

Of course if you want to code something yourself, then you’re on the right track. You can override the sidebar setting with the `roots_display_sidebar` filter and link it to a meta field.

---

## Post 3 by @Skylab — 2013-12-18T23:18:39Z

Awesome. Purchased. Would be great to have this not as a plugin though. These options are going to confuse my clients and there’s a chance of them deleting the plugin.

---

## Post 4 by @Foxaii — 2013-12-18T23:49:19Z

Thanks for the purchase.

If you check out the FAQ, it fully details how to customise the support text, which will hopefully help avoid any confusion with your clients. The same FAQ will also tell you how to use nice names for the templates, so you can call one Show Sidebar and the other Hide Sidebar.

If you want to prevent your clients from disabling the plugin:

1. Create a folder in your `wp-content` folder called `mu-plugins`.
2. Move the `roots-wrapper-override` folder into `mu-plugins`.
3. Move `roots-wrapper-override.php` from its folder into the root of `mu-plugins`.
4. Edit `roots-wrapper-override.php` changing line 30 to: `include_once('roots-wrapper-override/src/plugin.php');` to reflect the new file path.

The plugin should now be a “must-use” that can only be disabled by deleting it from the server. If you have any issues, give me a shout.

---

## Post 5 by @Skylab — 2013-12-19T21:04:35Z

Ah! That would explain why it wasn’t working when I placed it in mu-plugins. Awesome!  
Unfortunately [Synthesis](http://websynthesis.com) doesn’t seem to let you to create anything inside mu-plugins directory. Oh well. A plugin will do. Thanks!!

---

## Post 6 by @Foxaii — 2013-12-19T21:23:32Z

The same principle applies if you would like to put my plugin inside the theme folder; every host should let you do that!

1. Create a `plugins` folder in `lib` and move the plugin there (no need for any edits).
2. Edit `lib/custom.php` and add `include_once('plugins/roots-wrapper-override/roots-wrapper-override.php');`

Although please don’t do this if you are redistributing the theme.

---

## Post 7 by @Skylab — 2013-12-19T23:21:27Z

Ah makes sense.

This is for a specific client, no worries.

---

## Post 8 by @gruvii — 2014-12-24T03:14:30Z

I try to buy the Roots Wrapper Override and it shows $10, but when I click it is only let me select 5 license multisite for $35 or even more.

---

## Post 9 by @Foxaii — 2014-12-24T18:52:42Z

Thanks for getting in touch.

There must have been a change on Gumroad as the multisite field wasn’t required previously. I have added a single site option as a fix.