06:50

Install Odoo 11 on Ubuntu 16.04

We’ll show you, how to install Odoo 11 on Ubuntu 16.04. Configure Apache as a reverse proxy for your Odoo 11 so you can access your Odoo 11 application via a domain without typing Odoo’s port in the URL.

Odoo 11 is one of the most popular and most powerful Open Source ERP business software based on the Python programming language.

For this version, much of the focus is given on the intuitiveness, usefulness and better accessibility to the end-users & development team.

With Odoo Version 11, we can see new website dashboard incorporated with various keyboard shortcuts which makes navigating through Odoo quicker and easier than ever.

In addition to this, there is a new global search option in the homepage itself. Installing Odoo 11 on Ubuntu 16.04 is not so complicated process and if you follow the steps below, it shouldn’t take longer than 20 minutes to install Odoo 11 on Ubuntu 16.04.

1. Connect to SSH and Update the Packages

Before you begin, you need to connect to your server via SSH. Also, if this is your first time logging to your VPS make sure you check out our First Steps After Getting an Ubuntu VPS tutorial.

After you have successfully logged in, we need to make sure that all our packages are up to date by running the following commands:

apt-get update
apt-get upgrade

You can also enable automatic updates on your VPS.
To install Odoo 11 on our system we will use a script made by Yenthe Van Ginneken.

2. Download and Install Yenthe Van Ginneken Script

Navigate to a directory wherever you would like to download the script. For example, to go into the ‘home’ directory you need to type:

cd /home

Then use the following command to download the script:

wget https://raw.githubusercontent.com/Yenthe666/InstallScript/11.0/odoo_install.sh

You can also modify the script if you would like with:

nano odoo_install.sh

For example, you can change the version you would like to install, the location of where it will installed, whether you install the enterprise version or not and most important you can change the master admin password you would like to use.
After you make the desired changes, make sure you save them.

3. Make Executable File

In order to run the script we need to make the file executable with the following command:

chmod +x odoo_install.sh

4. Install Odoo 11

Now we can run the script and wait until Odoo 11 gets installed.

./odoo_install.sh

Congratulations! Odoo 11 has now been installed on your Ubuntu 16.04 VPS.

5. Set Master Password

If you haven’t set the master admin password before the installation you can do it now by editing the Odoo 11 configuration file. You can open it with the following command:

nano /etc/odoo-server.conf

and change the admin_password field with a strong password. You can also generate one from the command line.

admin_passwd = StrongPassword

6. Verify Odoo Installation

Restart Odoo for the changes to take effect:

/etc/init.d/odoo-server restart

To access your Odoo, open your browser and navigate to http://your-server-IP:8069. Initially, you would be asked to create a new database.

Once the database is created, you will get redirected to the admin panel from where you can log in as the admin user.

After successfully logging in you can start using your Odoo 11 and configure it to your needs, install additional modules etc.

Get a VPS from us and we’ll install, configure and optimize Odoo for you, free of charge!

7. Setting up a Reverse Proxy

In order to access your Odoo application only by using your domain name, without the port number in the URL, we need to set up Apache as a reverse proxy.

First, we will need to enable some additional proxy modules for Apache. You can do this with the following commands:

a2enmod proxy
a2enmod proxy_http

Once this is done, open a new configuration file for your domain with the following command:

nano /etc/apache2/sites-available/your_domain.conf

And enter the following:


ServerName your_domain.com
ServerAlias www.your_domain.com

ProxyRequests Off

Order deny,allow
Allow from all


ProxyPass / http://your_domain.com:8069/
ProxyPassReverse / http://your_domain.com:8069/

Order allow,deny
Allow from all

Enable “your_domain.conf” configuration in Apache using:

ln -s /etc/apache2/sites-available/your_domain.conf /etc/apache2/sites-enabled/your_domain.conf

Remember to replace your ‘your_domain.com’ with your actual domain name. Save the file, close it and restart Apache for the changes to take effect:

service apache2 restart

That’s it. If you followed all of the instructions properly you can now access your Odoo 11 using your domain name.

Additionally, if you would like to improve the performance of your Odoo, you can also check out our tutorial on How to speed up Odoo.

You dont have to know how to install Odoo 11 on Ubuntu 16.04 If you have a Odoo VPS Hosting with us. You can simply ask our administrators to install Odoo 11 on Ubuntu 16.04 for you.

They’re available 24/7, and will be able to help you with the installation of Odoo 11 on Ubuntu 16.04.
PS. If you enjoy reading this blog post on How to Install Odoo 11 on Ubuntu 16.04, feel free to share it on social networks using the shortcuts below, or simply leave a comment.

Installing and configuring Odoo on DigitalOcean

https://www.odoo.yenthevg.com/installing-configuring-odoo-digitalocean/

00:13

This guide covers how to install and configure Odoo

Install Odoo 10 on Ubuntu 16.04

This guide covers how to install and configure Odoo in under an hour using Git source code so it will be easy to upgrade, maintain and customize.

Before You Begin

Complete the Getting Started guide.
Follow the Securing Your Server guide to create a standard user account, harden SSH access and remove unnecessary network services. Do not follow the Configuring a Firewall section in the Securing Your Server Guide–we will configure the firewall for an Odoo production server in the next section.
This guide will use sudo wherever possible.
Update your packages:
1

sudo apt update && sudo apt upgrade

Configure UFW Firewall for Odoo

Before installing Odoo, we’ll set up some basic firewall rules to allow SSH connections and access to the Odoo server. In this example we’ll use Odoo’s default port 8069, but this could be any port you specify later in the configuration file. If you plan to run any other services, you can add their ports here as well. Refer to our guide on how to Configure a Firewall with UFW for help with rules and settings:

sudo ufw allow ssh
sudo ufw allow 8069/tcp
sudo ufw enable

Install PostgreSQL Database and Server Dependencies

Install the PostgreSQL database, Python, and other necessary server libraries:

sudo apt install git python-pip postgresql postgresql-server-dev-9.5 python-all-dev python-dev python-setuptools libxml2-dev libxslt1-dev libevent-dev libsasl2-dev libldap2-dev pkg-config libtiff5-dev libjpeg8-dev libjpeg-dev zlib1g-dev libfreetype6-dev liblcms2-dev liblcms2-utils libwebp-dev tcl8.6-dev tk8.6-dev python-tk libyaml-dev fontconfig

Create a PostgreSQL User

Switch to the postgres user:
1

sudo su - postgres
Set a strong password for the database user and record it in a secure location, you’ll need it in the following sections:
1

createuser odoo -U postgres -dRSP
Press CTRL+D to exit the postgres user session.

If you want to run multiple Odoo instances on the same Linode remember to check your PostgreSQL client configuration file (as of the date this guide is published, located at /etc/postgresql/9.5/main/pg_hba.conf) and modify it according your needs.

Create an Odoo User

In order to separate Odoo from other services, create a new Odoo system user to run its processes:

sudo adduser --system --home=/opt/odoo --group odoo

If you’re running multiple Odoo versions on the same Linode, you may want to use different users and directories for each instance.

Configure Logs

For logging, Ubuntu 16.04 uses systemd and journald by default. With that in mind, you can set up Odoo 10 logs in several ways. We’ll consider two scenarios in this guide. Your choice of option will depend on your particular needs:

To use journals and a separate Odoo log file at the same time, create the corresponding directory:
1

sudo mkdir /var/log/odoo
To only use journald for logging, you don’t need to create any directory.

Install Odoo

Clone the Odoo files onto your server:

sudo git clone https://www.github.com/odoo/odoo --depth 1 --branch 10.0 --single-branch /opt/odoo

Using git offers great flexibility. When a new upgrade is available, pull the new branch. You can even install a different version alongside the production one, just change the destination directory and the --branch X.x flag. Before upgrading, remember to make a full backup of your database and custom files.

Install Dependencies for Odoo Applications

Before your Odoo applications are ready to use, you’ll need to install some dependencies. We’ll use the Python package manager, pip, instead of apt to guarantee that you install the correct versions. We’ll also refrain from using Ubuntu’s packaged versions of Wkhtmltopdf and node-Less.
Be sure to follow the steps in this section as your limited, non-root user (not the odoo user).

Install Python Dependencies

Install the required Python libraries:

sudo pip install -r /opt/odoo/doc/requirements.txt
sudo pip install -r /opt/odoo/requirements.txt

These commands use the requirements.txt files provided with your Odoo installation to ensure you’re getting the correct versions of the packages your applications depend on.

Install Less CSS via nodejs and npm

Download and run the nodejs installation script from nodesource:

sudo curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -

Now that our repository list is updated install nodejs using apt.
1

sudo apt install -y nodejs
Install a newer version of Less via npm, the NodeJS package manager.
1

sudo npm install -g less less-plugin-clean-css

Install Stable Wkhtmltopdf Version

Navigate to a temporary directory:
1

cd /tmp
Download the recommended version of wkhtmltopdf for Odoo server. In this example, we use 0.12.1. See the Odoo repository for an up-to-date list of compatible versions:
1

sudo wget https://downloads.wkhtmltopdf.org/0.12/0.12.1/wkhtmltox-0.12.1_linux-trusty-amd64.deb

Install the package using dpkg:

sudo dpkg -i wkhtmltox-0.12.1_linux-trusty-amd64.deb

To ensure wkhtmltopdf functions properly, copy the binaries to a location in your executable path:
1 2

sudo cp /usr/local/bin/wkhtmltopdf /usr/bin sudo cp /usr/local/bin/wkhtmltoimage /usr/bin

While wkhtmltopdf version 0.12.2.4 is available in the official Ubuntu 16.04 repository, we don’t advise installing it from there due to the large number of dependencies including: xserver, gstreamer, libcups, wayland, qt5 and many more. There isn’t an official Xenial package from the project page yet, but the Trusty package from Ubuntu 14.04 is compatible as of this publication.

Odoo Server Configuration

Copy the included configuration file to a more convenient location, changing its name to odoo-server.conf
1

sudo cp /opt/odoo/debian/odoo.conf /etc/odoo-server.conf

Next, modify the configuration file. The complete file should look similar to this, depending on your deployment needs:

/etc/odoo-server.conf

[options]
admin_passwd = admin
db_host = False 
db_port = False
db_user = odoo
db_password = FALSE
addons_path = /opt/odoo/addons
;Uncomment the following line to enable a custom log
;logfile = /var/log/odoo/odoo-server.log
xmlrpc_port = 8069

admin_passwd = admin - This is the password that allows database operations. Be sure to change admin to something more secure.
db_host = False - Unless you plan to connect to a different database server address, leave this line untouched.
db_port = False - Odoo uses PostgreSQL default port 5432, change this only if you’re using custom PostgreSQL settings.
db_user = odoo - Name of the PostgreSQL database user. In this case we used the default name, but if you used a different name when creating your user, substitute that here.
db_password = FALSE - Change FALSE to the PostgreSQL password you created previously.
addons_path = - Modify this line to read: addons_path = /opt/odoo/addons. Add

if you’re using custom modules, substituting your own path.

Include the path to log files, and add a new line: logfile = /var/log/odoo/odoo-server.log. You can skip this line if you plan to only use journald for logging.

Optionally, we could include a new line specifying the Odoo Frontend port used for connection: xmlrpc_port = 8069. This only makes sense if you’re planning to run multiple Odoo instances (or versions) on the same server. For normal installation, you can skip this line and this instance of Odoo will connect by default to port 8069.

As explained in the Configure Logs section, you have many options for Odoo logging in Ubuntu 16.04. This configuration file assumes you’ll use Ubuntu system journals in addition to a custom log path.

Create an Odoo Service

Create a systemd unit called odoo-server to allow your application to behave as a service. Create a new file at /lib/systemd/system/odoo-server.service and add the following contents:

/lib/systemd/system/odoo-server.service

[Unit]
Description=Odoo Open Source ERP and CRM
Requires=postgresql.service
After=network.target postgresql.service
    
[Service]
Type=simple
PermissionsStartOnly=true
SyslogIdentifier=odoo-server
User=odoo
Group=odoo
ExecStart=/opt/odoo/odoo-bin --config=/etc/odoo-server.conf --addons-path=/opt/odoo/addons/
WorkingDirectory=/opt/odoo/
StandardOutput=journal+console
    
[Install]
WantedBy=multi-user.target

The most relevant line in this file is StandardOutput=journal+console. As configured in the example above, Odoo logs will be completely managed by the system journal (Option 2 in the Configure Logs section). If you want a separate log file, omit that line and configure odoo-server.conf accordingly, specifying the location of your log file. Remember that journald will always capture main Odoo service activity (service start, stop, reboot, errors), using a separate log file will only exclude journal “info” messages like webserver messages, rendering engine, etc.

Change File Ownership and Permissions

Change the odoo-server service permissions and ownership so only root can write to it, while the odoo user will only be able to read and execute it.
1 2

sudo chmod 755 /lib/systemd/system/odoo-server.service sudo chown root: /lib/systemd/system/odoo-server.service
Since the odoo user will run the application, change its ownership accordingly.
1

sudo chown -R odoo: /opt/odoo/
If you chose to use a custom log, set the odoo user as the owner of log directory as well (this applies only if you decided to use a separate log file):
1

sudo chown odoo:root /var/log/odoo
Finally, protect the server configuration file. Change its ownership and permissions so no other non-root user can access it:
1 2

sudo chown odoo: /etc/odoo-server.conf sudo chmod 640 /etc/odoo-server.conf

Test the Server

Confirm that everything is working as expected. First, start the Odoo server:
1

sudo systemctl start odoo-server
Check the service status to make sure it’s running. This will also include journal logs. You can see an example output in the picture bellow:
1

sudo systemctl status odoo-server
Check the database journal to make sure there are no errors:
1

sudo journalctl -u postgresql
Verify that the server is able to stop properly:
1

sudo systemctl stop odoo-server
Run a service status check again to make sure there were no errors:
1

sudo systemctl status odoo-server
Your output should look similar to this:

Enable the Odoo Service

If your system journal doesn’t indicate any problems, enable the odoo-server unit to start and stop with the server:
1

sudo systemctl enable odoo-server
Log into the Linode Manager and reboot your Linode to see if everything is working as expected.
Once restarted, log in via SSH and verify your journal messages:
1

sudo journalctl -u odoo-server
The output should include a message indicating that Odoo has started successfully.

Test Odoo

Open a new browser window and enter in the address bar:
1

http://:8069
If everything is working properly, a screen similar to this should appear:
Congratulations, now you can create your first database and start using Odoo 10 applications!

Updating Odoo

Before updating your Odoo system, you should check that everything will work as expected, especially third-party modules. The safest way to do this is to use a testing environment, which is nothing more than a separate Odoo installation.
Depending on your server resources, security concerns and testing the scope of this second installation can be done alongside the production instance or in another location (remote or local). For the purpose of this guide, we’ll use a testing environment running on the same server as the production one.

Configure UFW Firewall

In order to use the testing environment at the same time than production we need to use a different TCP port for server connections:

sudo ufw allow 8080/tcp

Create a Separate Database User

An independent database user is a good idea to keep everything off production, however it’s not necessary to use a password as before:

sudo su - postgres
createuser odoo-te -U postgres -dRS

Press CTRL+D to exit the postgres user session.

Create a Test Odoo User

It’s very important to use a different odoo user than production one:

sudo adduser --system --home=/opt/odoo-te --group odoo-te

Configure Logs

In the case of the testing environment it’s advisable to use a separate log file:

sudo mkdir /var/log/odoo-te

Install Odoo Testing Environment

Clone the updated Odoo source which is different from your older production instance:

sudo git clone https://www.github.com/odoo/odoo --depth 1 --branch 10.0 --single-branch /opt/odoo-te

Testing Environment Configuration

The advantage of using the same server is that all dependencies are already meet. What is next is to configure the server accordingly.

Copy the original configuration file from the source to appropiate location:
1

sudo cp /opt/odoo/debian/odoo.conf /etc/odoo-server-te.conf

Modify the configuration file, paying attention to changes from previous installation especially the inclusion of logfile and the communication port:

/etc/odoo-server.conf

[options]
admin_passwd = admin
db_host = False 
db_port = False
db_user = odoo-te
db_password = FALSE
addons_path = /opt/odoo-te/addons
logfile = /var/log/odoo-te/odoo-server-te.log
xmlrpc_port = 8080

Create a systemd unit for the Odoo testing environment. This allows you to run it as an independent service:

/lib/systemd/system/odoo-server-te.service

[Unit]
Description=Odoo Open Source ERP and CRM (Test Env)
Requires=postgresql.service
After=network.target postgresql.service

[Service]
Type=simple
PermissionsStartOnly=true
SyslogIdentifier=odoo-server-te
User=odoo-te
Group=odoo-te
ExecStart=/opt/odoo-te/odoo-bin --config=/etc/odoo-server-te.conf --addons-path=/opt/odoo-te/addons/
WorkingDirectory=/opt/odoo-te/

[Install]
WantedBy=multi-user.target

Change File Ownership and Permissions

Just as you did before, set permissions for the testing environment:

sudo chmod 755 /lib/systemd/system/odoo-server-te.service
sudo chown root: /lib/systemd/system/odoo-server-te.service
sudo chown -R odoo-te: /opt/odoo-te/
sudo chown odoo-te:root /var/log/odoo-te
sudo chown odoo-te: /etc/odoo-server-te.conf
sudo chmod 640 /etc/odoo-server-te.conf

Check your Testing Environment

Now you can start your new Odoo service and verify log entries for errors:

sudo systemctl start odoo-server-te
sudo systemctl status odoo-server-te
sudo journalctl -u postgresql
sudo cat /var/log/odoo-te/odoo-server-te.log

Prepare your System for Production Tests

At this point, you have a completely independent Odoo installation. Next steps will setup your testing environment to replicate the production one.

Make a backup of your production database using the Odoo graphical interface. Navigate to the following URL in your web browser. This assumes that your are using the default port 8069:
1

http://your_domain_or_IP_address:8069/web/database/manager
Start your odoo-server-te service and restore the production database using the Odoo graphical interface by navigating to the URL below. Note that this time you’ll be using port 8080 since that’s where the test environment is running:
1

http://your_domain_or_IP_address:8080/web/database/manager
The final step is to update Odoo modules to newer versions, this is done restarting the service and updating database entries which tells the system to apply changes:
1

sudo service odoo-server-te restart -u all -d
At this stage, you may encounter errors produced by incompatible changes in modules. This is rarely the case for Odoo standard modules but is not uncommon for ones downloaded from a third-party. If you do encounter an error, you’ll need to check for a new version of the module that’s causing it, and reinstall it.
If everything goes as expected, you can start your load tests modules “behavior” tests (which are different from code-incompatible errors), and any other tests you’ve configured.

Update your Production System

If all your tests pass, you can safely update your production installation.

Download the new code from source:

cd /opt/odoo
sudo git fetch origin 10.0

Apply the changes to your repository:
1

sudo git reset --hard origin/10.0
Access your new system:
1

http://your_domain_or_IP_address:8069

OpenERP V7 and V8(odoo) installation on Ubuntu

sudo apt-get update && sudo apt-get upgrade

2. Install Git. GIT is the Versioning control system used for Odoo Source code hosting. You may always pull latest source from git by using specific commands. Please note that setting up bzr is in next points. You can now use any version of OpenERP/Odoo from git.

sudo apt-get install git

3. Install Required Python Packages for OpenERP - v7 so that we will not get any errors related the package requirement.

sudo apt-get install python-matplotlib python-pyparsing python-imaging python-psycopg2 python-libxslt1 python-libxml2 graphviz postgresql pgadmin3 python-lxml mx44 python-reportlab python-pychart python-tz python-openssl python-hippocanvas python-yaml python-pydot python-setuptools flashplugin-installer python-mako python-pybabel python-werkzeug python-openid bzr python-mock python-unittest2 python-docutils

4. Install Required Packages for Odoo - v8 so that we will not get any errors related the package requirement.

sudo apt-get install graphviz ghostscript postgresql-client python-dateutil python-feedparser python-matplotlib python-ldap python-libxslt1 python-lxml python-mako python-openid python-psycopg2 python-pybabel python-pychart python-pydot python-pyparsing python-reportlab python-simplejson python-tz python-vatnumber python-vobject python-webdav python-werkzeug python-xlwt python-yaml python-imaging

5. Install Supporting Packages for Odoo and it will fulfill the dependencies of the modules, because some modules require python libraries to be installed before you install modules in odoo.

sudo apt-get install gcc python-dev mc bzr python-setuptools python-babel python-feedparser python-reportlab-accel python-zsi python-openssl python-egenix-mxdatetime python-jinja2 python-unittest2 python-mock python-docutils lptools make python-psutil python-paramiko poppler-utils python-pdftools python-pypdf python-requests python-decorator python-passlib antiword

6. Install Gdata client if not installed yet! This is specially used for Google related integrations.

wget http://gdata-python-client.googlecode.com/files/gdata-2.0.18.tar.gz
tar zxvf gdata-2.0.18.tar.gz
cd gdata-2.0.18
sudo python setup.py install

7. Create directory for OpenERP(v7) and fetching the same from launchpad. (NOTE: Use /home directory of your user)

sudo mkdir openerp
cd openerp
bzr branch lp:openerp-web/7.0 web
bzr branch lp:openobject-server/7.0 server
bzr branch lp:openobject-addons/7.0 addons

8. Creating User For Postgresql. (NOTE: Replace username with your system User)

sudo -u postgres createuser -s username

9. Alter User Of Postgres. (NOTE: Replace username&password with your System User&password)

sudo su postgres
psql
alter user username with password 'password';
\q
exit

10. Starting OpenERP(v7) Server by going to the server directory of OpenERP.

cd /home/workspace/openerp/server
python openerp-server - -addons-path=../addons/,../web/addons/

11. Create Directory For Cloning OpenERP/Odoo Gnd Go To That Directory.

cd /home/workspace/odoo

12. Cloning the latest code of 8.0(odoo) from GitHub.

git clone https://github.com/odoo/odoo.git

13. Go to odoo directory.

cd odoo

14. Start 8.0(odoo) server.

NOTE: To stop the server press CRTL+C keys and to restart do the same procedure as above.

12:12

Building block & Snippet Editor guideline's

Building block & Snippet Editor

The building blocks appear in the edit bar website. These pre-built html block

allowing the designer to easily generate content on a page (drag and drop).

Options allow snippets to add customizations part html code according to their

selector (jQuery) and javascript object.

How to create content?

Designers can add their own html block in the "snippets" (/website/views/snippets.xml).

The block must be added in one of four menus (structure, content, feature or effect).

Structure:

<div>
   <div class="oe_snippet_thumbnail">
       <img class="oe_snippet_thumbnail_img" src="...image src..."/>
       <span class="oe_snippet_thumbnail_title">...Block Name...</span>
   </div>
   <div class="oe_snippet_body">
       ...
       <!--
           The block with class 'oe_snippet_body' is inserted in the page.
           This class is removed when the block is dropped.
                </div>!
           The block can be made of any html tag and content. -->
   </div>
   </div>

How to create options?

Designers can add their own html block in the "snippet_options" (/website/views/snippets.xml).

Structure:

<div data-snippet-option-id='...' 

    data-selector="..." 


    data-selector-siblings="..."   

    data-selector-children="..."   

    data-selector-vertical-children='...' 
        ...
        <li><a href="#">...</a></li>   

        ...
        <li class="dropdown-submenu" 

            data-required="true" 

            <a tabindex="-1" href="#">...</a> 

            <ul class="dropdown-menu">
                 <li data-value="text_only"><a>...</a></li> 
            </ul>
        </li>
</div>

How to create a javascript object for an options?

openerp.website.snippet.options["...option-id..."] = website.snippet.Option.extend({

// start is called when the user click into a block or when the user drop a block

// into the page (just after the init method).

// start is usually used to bind event.

// this.$target: block html inserted inside the page

// this.$el: html li list of this options

// this.$overlay: html editor overlay who content resize bar, customize menu...

start: function () {},

// onFocus is called when the user click inside the block inserted in page

// and when the user drop on block into the page

onFocus : function () {},

// onBlur is called when the user click outside the block inserted in page, if

// the block is focused

onBlur : function () {},

// on_clone is called when the snippet is duplicate

// @variables: $clone is allready inserted is the page

on_clone: function ($clone) {},

// on_remove is called when the snippet is removed (dom is removing after this tigger)

on_remove: function () {},

// drop_and_build_snippet is called just after that a thumbnail is drag and dropped

// into a drop zone. The content is already inserted in the page.

drop_and_build_snippet: function () {},

// select is called when a user select an item in the li list of options

// By default, if the li item have a data-value attribute, the data-vlue it's apply

// like a class to the html block (this.$target)

// @variables: next_previous = {$next, $prev}

// $next = next item selected or false

// $prev = previous item selected or false

select: function (event, next_previous) {}

// preview is called when a user is on mouse over or mouse out of an item

// variables: next_previous = {$next, $prev}

// $next = next item selected or false

// $prev = previous item selected or false

preview: function (event, next_previous) {}

// clean_for_save

// clean_for_save is called just before to save the vue

// Sometime it's important to remove or add some datas (contentEditable, added

// classes to a running animation...)

clean_for_save: function () {}

});

// 'snippet-dropped' is triggered on '#oe_snippets' whith $target as attribute when a snippet is dropped

// 'snippet-activated' is triggered on '#oe_snippets' (and on snippet) when a snippet is activated

Odoo Require Concept

Odoo web framework come up with new concept of module loading which is almost inherited from RequireJS.

Let me describe how modules are loaded, how dependencies are calculated ?

Everything else is similar in web framework but now It is more modular, each and every component is reusable by just fetching/calling it using require(Its a wrapper to load the object).

Previously modules were loaded using namespace(same name given as module name to JS namespace).

First of all note that now onwards global object openerp is replaced with odoo.

Now onwards if you want to create any module or any widget you can simply define it using odoo.define, lets have example of both style old style as well as new style.

Old Style:

openerp.my_module = function(openerp) {

openerp.web.my_widget1 = openerp.web.widget.extend({

//your widget stuff here

popup = new openerp.web.FormPopup(...);

});

openerp.web.my_widget2 = openerp.web.widget.extend({

//your widget stuff here

});

New Style:

odoo.define('web.my_module', function(require) {

popup = require('form_popup') //Where form_popup is separately defined in another file

web = require('odoo_web');

web.my_widget2 = openerp.web.wdiget.extend({

//your widget stuff here

});

No doubt in both cases we can have re-usability but in later one we can maintain small files for small features and can use that small feature in another file by requiring it, code is more readable and simpler.

Note that, new style you need to define files in proper order because one feature might depends on another and due to dependency issue you module might not be loaded.

Lets have a look how it works in background ?

we having one main file boot.js, boot.js file having anonymous function and it is in closure style which is called when file is loaded in DOM, the responsibility of boot.js is to load module, this file is the file which generates the concept of require method and dependency.

It creates global odoo object which having define method, now note that all other files will have define function called where second parameter will be callback function, whenever each file is loaded, each file will call define method of odoo, now define method of odoo global object checks for the arguments and second argument will have function in which there will be other require calls.

Define method checks for the require calls using Regular Expression, after gathering all require calls it fetches those objects from services object.

Service object is an object which is module's/object's pool.

Say for example if I define one of my widget:

odoo.define('form.digital_signature', function() {....});

Then form.digital_signature is going to register in service pool.

If there is dependency missing then its not going to load that module, if everything is fine, if it finds all dependent module are already loaded in service object pool then it calls function which is second parameter in define and also add that module/feature with name given as a first argument in service pool, if one tries to register service with same name twice then it will raise error that service with same name is already registered.

There are some core methods in boot.js, which you should go through:

define -> Finds require call, generates dependency list, creates wrapper of require

process_jobs -> loads module and add that module in module/object service and factories pool

init -> initializes webclient.

So with this we can simply create small features and use it by calling it another file using require('feature_name').

All your generated module will generally return reference of your object like example given below:

odoo.define('web.ajax', function (require) {

"use strict";

var time = require('web.time');

var Dialog = require('web.dialog');

time.date_to_utc...

var my_dialog = new Dialog(....)

});

where web.dialog is:

odoo.define('web.Dialog', function (require) {

"use strict";

var Dialog = Widget.extend({

//your dialog stuff

});

return Dialog;

});

So here web.dialog returns reference of Dialog and we can then use new Dialog after calling var Dialog require('web.dialog');

Hope this will help, feel free to raise your query by comments.

Install Odoo 11 on Ubuntu 16.04

1. Connect to SSH and Update the Packages

2. Download and Install Yenthe Van Ginneken Script

3. Make Executable File

4. Install Odoo 11

5. Set Master Password

6. Verify Odoo Installation

7. Setting up a Reverse Proxy

Installing and configuring Odoo on DigitalOcean

This guide covers how to install and configure Odoo

Install Odoo 10 on Ubuntu 16.04

Before You Begin

Configure UFW Firewall for Odoo

Install PostgreSQL Database and Server Dependencies

Create a PostgreSQL User

Create an Odoo User

Configure Logs

Install Odoo

Install Dependencies for Odoo Applications

Install Python Dependencies

Install Less CSS via nodejs and npm

Install Stable Wkhtmltopdf Version

Odoo Server Configuration

Create an Odoo Service

Change File Ownership and Permissions

Test the Server

Enable the Odoo Service

Test Odoo

Updating Odoo

Configure UFW Firewall

Create a Separate Database User

Create a Test Odoo User

Configure Logs

Install Odoo Testing Environment

Testing Environment Configuration

Change File Ownership and Permissions

Check your Testing Environment

Prepare your System for Production Tests

Update your Production System

OpenERP V7 and V8(odoo) installation on Ubuntu

Building block & Snippet Editor guideline's

﻿Odoo Require Concept

Odoo web framework come up with new concept of module loading which is almost inherited from RequireJS.

About me

Popular Posts

Labels

Linkedin

Odoo Require Concept