Backend Theme All in One with Website Styling

Backend Theme All in One with Website Styling. The apps button on your website opens the Home Menu you arranged, instead of a dropdown list of every app. While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database.

In the next few minutes: backend theme all in one with website styling, then what you get, then uninstalling, then how it works, then how we make sure it works. Then what this app deliberately does not do, so you can tell before you buy whether it fits. The module installs itself once both are present and does nothing at all before that, which is why it is a separate module: a backend theme should not drag the Website app in behind it. Backend Theme All in One with Website Styling.

While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database. With eight apps that is a menu. With eighty it is a single column taller than the screen, in no order you chose, with no icons and no search — and the Home Menu you already arranged is one navigation away, unused.

What you get. Nothing else changes. No JavaScript is added to the website, no model is created, and nothing runs on a page a customer sees — the button this adjusts is rendered only for logged-in staff. The grid button on any website page opens the Home Menu.

You land on your own arrangement: your app order, your named sections, your pinned apps at the top, and the search box. Odoo's dropdown of every root menu is gone from that button. Uninstalling. Odoo's dropdown comes back exactly as it was.

The module stores nothing and changes no data, so there is nothing to clean up. How it works. One inherited view over website.layout. It sets the button's href to the backend, removes the data-bs-toggle that made it a dropdown toggler, and drops the generated list of menus.

That is the whole module, and you can read it in views/website_templates.xml. How we make sure it works. Before every release, 8 automated checks run against this app on Odoo 16, 17, 18, 19 and 20. Among them: It owns one view and nothing else.

It adds no javascript to the website. It installs itself only with both apps. The button no longer opens a dropdown. The public never sees the button.

The complete list is in the source you receive. Questions people ask. Which Odoo versions does it run on? Odoo 16.0, 17.0, 18.0, 19.0, 20.0, on the series you buy it for; each series is its own listing.

Community or Enterprise? Both. It needs no Enterprise app. Support The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours.

Links are in the description.

Backend Theme: Website Bridge. The apps button on your website opens the Home Menu you arranged, instead of a dropdown list of every app. While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database.

In the next few minutes: backend theme: website bridge, then what you get, then uninstalling, then how it works, then support. Then what this app deliberately does not do, so you can tell before you buy whether it fits. The module installs itself once both are present and does nothing at all before that, which is why it is a separate module: a backend theme should not drag the Website app in behind it. Backend Theme: Website Bridge.

While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database. With eight apps that is a menu. With eighty it is a single column taller than the screen, in no order you chose, with no icons and no search — and the Home Menu you already arranged is one navigation away, unused.

What you get. Nothing else changes. No JavaScript is added to the website, no model is created, and nothing runs on a page a customer sees — the button this adjusts is rendered only for logged-in staff. The grid button on any website page opens the Home Menu.

You land on your own arrangement: your app order, your named sections, your pinned apps at the top, and the search box. Odoo's dropdown of every root menu is gone from that button. Uninstalling. Odoo's dropdown comes back exactly as it was.

The module stores nothing and changes no data, so there is nothing to clean up. How it works. One inherited view over website.layout. It sets the button's href to the backend, removes the data-bs-toggle that made it a dropdown toggler, and drops the generated list of menus.

That is the whole module, and you can read it in views/website_templates.xml. Support The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Backend Theme: Website Bridge. The apps button on your website opens the Home Menu you arranged, instead of a dropdown list of every app. While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database.

In the next few minutes: backend theme: website bridge, then what you get, then uninstalling, then how it works, then support. Then what this app deliberately does not do, so you can tell before you buy whether it fits. The module installs itself once both are present and does nothing at all before that, which is why it is a separate module: a backend theme should not drag the Website app in behind it. Backend Theme: Website Bridge.

While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database. With eight apps that is a menu. With eighty it is a single column taller than the screen, in no order you chose, with no icons and no search — and the Home Menu you already arranged is one navigation away, unused.

What you get. Nothing else changes. No JavaScript is added to the website, no model is created, and nothing runs on a page a customer sees — the button this adjusts is rendered only for logged-in staff. The grid button on any website page opens the Home Menu.

You land on your own arrangement: your app order, your named sections, your pinned apps at the top, and the search box. Odoo's dropdown of every root menu is gone from that button. Uninstalling. Odoo's dropdown comes back exactly as it was.

The module stores nothing and changes no data, so there is nothing to clean up. How it works. One inherited view over website.layout. It sets the button's href to the backend, removes the data-bs-toggle that made it a dropdown toggler, and drops the generated list of menus.

That is the whole module, and you can read it in views/website_templates.xml. Support The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Backend Theme: Website Bridge. The apps button on your website opens the Home Menu you arranged, instead of a dropdown list of every app. While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database.

In the next few minutes: backend theme: website bridge, then what you get, then uninstalling, then how it works, then support. Then what this app deliberately does not do, so you can tell before you buy whether it fits. The module installs itself once both are present and does nothing at all before that, which is why it is a separate module: a backend theme should not drag the Website app in behind it. Backend Theme: Website Bridge.

While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database. With eight apps that is a menu. With eighty it is a single column taller than the screen, in no order you chose, with no icons and no search — and the Home Menu you already arranged is one navigation away, unused.

What you get. Nothing else changes. No JavaScript is added to the website, no model is created, and nothing runs on a page a customer sees — the button this adjusts is rendered only for logged-in staff. The grid button on any website page opens the Home Menu.

You land on your own arrangement: your app order, your named sections, your pinned apps at the top, and the search box. Odoo's dropdown of every root menu is gone from that button. Uninstalling. Odoo's dropdown comes back exactly as it was.

The module stores nothing and changes no data, so there is nothing to clean up. How it works. One inherited view over website.layout. It sets the button's href to the backend, removes the data-bs-toggle that made it a dropdown toggler, and drops the generated list of menus.

That is the whole module, and you can read it in views/website_templates.xml. Support The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Backend Theme: Website Bridge. The apps button on your website opens the Home Menu you arranged, instead of a dropdown list of every app. While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database.

In the next few minutes: backend theme: website bridge, then what you get, then uninstalling, then how it works, then support. Then what this app deliberately does not do, so you can tell before you buy whether it fits. The module installs itself once both are present and does nothing at all before that, which is why it is a separate module: a backend theme should not drag the Website app in behind it. Backend Theme: Website Bridge.

While you are logged in, Odoo draws a small grid button on every page of your website, titled Go to your Odoo Apps. Clicking it opens a dropdown that lists every root menu on the database. With eight apps that is a menu. With eighty it is a single column taller than the screen, in no order you chose, with no icons and no search — and the Home Menu you already arranged is one navigation away, unused.

What you get. Nothing else changes. No JavaScript is added to the website, no model is created, and nothing runs on a page a customer sees — the button this adjusts is rendered only for logged-in staff. The grid button on any website page opens the Home Menu.

You land on your own arrangement: your app order, your named sections, your pinned apps at the top, and the search box. Odoo's dropdown of every root menu is gone from that button. Uninstalling. Odoo's dropdown comes back exactly as it was.

The module stores nothing and changes no data, so there is nothing to clean up. How it works. One inherited view over website.layout. It sets the button's href to the backend, removes the data-bs-toggle that made it a dropdown toggler, and drops the generated list of menus.

That is the whole module, and you can read it in views/website_templates.xml. Support The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.