Layouts Plugin

Thanks Robert for your reply, I am using the Bitnami AWS instance and is using the documentation as per, ideally it should have worked but not sure why it isnt able to identify the assets.

1 Like

Yep please use the official Discourse builds instead. Use of Bitnami is at your own risk.

Thanks for you assistance, sure…I will set that up on Digital Ocean and will confirm if issue persists.

This Plugin is broken with Fakebook theme.

You could equally say Fakebook is broken with this plugin? :wink:

We support core Discourse and if a theme works, great. If not, you are probably out of luck.

Whilst we make great efforts to optimise compatibility we can’t promise all themes will work with our plugins. Especially those combinations where our plugin and the Theme are both changing templates.

If you want to use a Theme with this plugin choose a lighter weight Theme that has less or no impact on layout.

Fakebook already has its own sidebars and almost certainly won’t have been designed to work with this plugin (otherwise why doesn’t it use the CL sidebars?). It is also targeting core Discourse no doubt. You’ll probably have to choose between them. Or, use CL and borrow elements from Fakebook and design your own Theme.

There’s currently a Chrome limitation that prevents us fully exploiting Topic List Previews with sidebars. Watch this space…


It’s currently broken, for some reason.


You are unable to build Discourse due to errors in the plugin at

We’ve removed it on our site.

The plugin has just undergone a significant update.

You can now add theme components as widgets (in addition to plugins). I’ve updated the widget you’ve been using to support v0.2

However I would recommend the new theme version of the same widget (with some functionality improvments and changes)

Generally the plugin is moving away from using plugins for widgets to using themes. Full documentation to follow in the next day or so.

Note that the plugin now has support for group-specific permissions, so make sure this is set in /admin/layouts.

This plugin will also soon be moving to the same update schedule as our other plugins; see further:


It’s GREAT NEWS! I just written the same to another person, and suggested, that we moved to a theme-component based solution. Thanks for the update!


Please PM me with your use case so I can help you get setup with the new theme-supporting version :slight_smile:


When I update Discourse to the latest version, Theme Minimal - The Plugin is not working.

My Forum: Https://babyforex/net

Hey, welcome :slight_smile:

Can you give me some more specifics on the issue? What widgets are you trying to use?

A key thing to note is that the plugin now has enabled and group settings for each widget. That’s the first thing to check.

I’m still working on the documenation for v0.2 (literally right now!), and v0.2 won’t be officially launched until the next Pavilion Plugin Update Period: 2020-04-30T14:00:00Z2020-05-04T14:00:00Z.

If you look at you’ll see that the plugin is working successfully with the current version of discourse (just updated): Layouts - Try Pavilion

1 Like

Hi Angus

My forum show blank page when I update to Latest Discourse Version. I use minimal light theme.

I just updated to the latest version of both Discourse and this plugin and it has no issues. See e.g.

Are you running the latest version of the plugin?

If you are running the latest version of everything, can you go to /logs and send me a PM with all the latest logs and a full list of the plugins you’re using

Hi Angus

This is my log:

ReferenceError: createWidget is not defined
    at t.module.exports.u.<computed> (
    at t.module.exports.u.<computed> (
    at require (
    at Array.forEach (<anonymous>)
    at Object.t (
    at Object.n.initialize (
    at i.each (

And here:

ReferenceError: Can’t find variable: createWidget Url: Line: 1 Column: 31156 Window Locati


forEach@[native code]







You need to update the layouts-custom-html plugin to this commit

Note that the plugin-based widgets are generally being phased out in favour of theme-based widgets. I’ll be release a theme-component that replaces this plugin in the near future.


I had to change a few functions to get my plugin to work again.

Mainly using

layouts.createLayoutsWidget. and DiscourseLayouts::Widget.add

1 Like
TypeError: Discourse.SiteSettings is undefined_discourse-layouts-21b7cbab0ee1773efd84d72a08dbb131313019d1a0b99321fc5f165b31752521.js:93:23
    <anonymous> _discourse-layouts-21b7cbab0ee1773efd84d72a08dbb131313019d1a0b99321fc5f165b31752521.js:93
    jQuery 8
    _prepareInitializer _application-c96f4694dbdebd9912b6dffe0051bbb7d18f7c4bf08c5c3272c57906b63a978e.js:6849
    start _application-c96f4694dbdebd9912b6dffe0051bbb7d18f7c4bf08c5c3272c57906b63a978e.js:6870
    forEach self-hosted:225
    start _application-c96f4694dbdebd9912b6dffe0051bbb7d18f7c4bf08c5c3272c57906b63a978e.js:6866
    <anonymous> _start-discourse-efa4e5abfbd1b50b5152ffbe64d5dcea9f7c33f766dcc6387e2711f0f2112148.js:3
  var sidebarPadding = 20;
  var mainLeftOffset = Discourse.SiteSettings.layouts_sidebar_left_width + sidebarPadding;
  var mainRightOffset = Discourse.SiteSettings.layouts_sidebar_right_width + sidebarPadding;

We’re facing a problem, after the latest update. It’s reporting that Discourse.SiteSettings is not defined. Is it direct, og indirecly related to this plugin?

(I’ve just rebuilded our page)

Retort are generating the same issues. I’ve disabled Custom Layouts from our build, but hereafter, Retort reported the same problem with Discourse.SiteSettings :slight_smile:

Thanks Tobias, it’s due to this change in Discourse:

I’ve addressed the issue in Layouts:

1 Like

Oh my I’m amazed the previous code ever worked! Those site settings were evaluated at module read time, which could be before the app has booted. Your new solution is now much cleaner and future proof :slight_smile:


Newly realised the power of this plugin, and really love the new direction it has taken with widgets based on components. Thank you @angus :tada:

Tested it quickly on a site but realised there is a compatibility issue when used with other theme components that injects themselves between the header and the main content; the sidebars gets stuck/sticky to the height including the height the injected theme component, rendering the sidebars floating in the middle or lower half of the screen.

Also - when I include the Layouts Topic Lists Widget in the active theme and activate it in Layouts, I get a white page and have to deactivate the Layouts plugin and rebuild to be able to fix.

All the best