What’s new and cool in Odoo 9
From the Odoo Experience 2015.
From the Odoo Experience 2015.
Odoo 9 community vs. enterprise features. Document is still in draft.
Services | Odoo 8 | Odoo 9 Community | Odoo 9 Enterprise |
Community Forum | X | X | X |
Upgrades to future versions | / | / | X |
Bugfixes Guarantee | / | / | X |
Support | / | / | X |
Features | Odoo 9 Community | Odoo 9 Enterprise | |
Accounting | |||
Basic Accounting | X | Improved | Improved |
Accounting Reports | static | static | dynamic |
Statement Import: Coda | X | Improved | Improved |
Accounting Dashboard | / | X | X |
Bank Interfaces (U.S., NZ, Canada) | / | / | X |
Statement Import: OFX, QIF | / | X | X |
Check Printing & Deposit | / | / | X |
Customer Follow-ups | basic | basic | Improved |
User Interface | |||
Desktop | X | Improved | Improved |
Android CRM | / | X | X |
Mobile UI | / | / | X |
New Design | / | / | X |
Project Management | |||
Tasks | X | Improved | Improved |
Issues | X | Improved | Improved |
Timesheets | Former version | Improved | Improved |
Timesheet Chrome plugin & mobile app | / | / | X |
Forecasts | / | / | X |
Sales Management | |||
CRM | X | Improved | Improved |
Sales | X | Improved | Improved |
Contracts | Former version | Improved | Improved |
Customer Portal | X | X | Improved |
eSignature | / | / | X |
Subscriptions | / | / | X |
Digital products | / | X | X |
Human Resources | |||
Holidays | X | Improved | Improved |
Employee Directory | X | Improved | Improved |
Recruitments | X | Improved | Improved |
Appraisals | Former version | Improved | Improved |
Departments Dashboard | / | X | X |
WMS | |||
Inventory Management | X | Improved | Improved |
Barcode support | Former version | Improved | Improved |
Integration with UPS, Fedex, DHL, USPS | / | / | X |
Inter-company rules | / | X | X |
Website Builder | |||
Website Builder | X | Improved | Improved |
Blog | X | Improved | Improved |
Form builder | / | / | X |
Call-to-Actions Blocks | / | / | X |
Versioning | / | X | X |
A/B Testing | / | X | X |
eCommerce | |||
Full eCommerce | X | Improved | Improved |
Authorize.net integration | / | X | X |
Shipping Integration | / | / | X |
eBay Connector | / | / | X |
Amazon Connector | / | / | X |
Coupons | / | / | X |
Point of Sale | |||
Point of Sale | X | X | X |
Point of Sale for Restaurants | / | X | X |
Loyalty cards | / | / | X |
Marketing | |||
Events | X | Improved | Improved |
Expenses | X | Improved | Improved |
Mass mailing | X | Improved | Improved |
Mass Mailing Templates | / | / | X |
Live Chat | X | Improved | Improved |
Misc | |||
Usability improvements | / | X | X |
Google Spreadsheet | X | X | X |
Document Management (slides) | / | X | X |
Planner (first weeks onboarding) | / | X | X |
Reporting | X | Improved | Improved |
Odoo 9 Feature Split – OpenCore pdf version.
How to create your own squid proxy server on CentOS
Squid is a proxy server for caching and filtering web content .
Squid proxy service will cache the requested web-content and re-using it for the further request of the same content.
You can also hide your real IP with squid and access content usually forbidden for your country or IP address.
Requirement is that you have already installed your CentOS server.
1.) Connect with putty to install and configure squid
yum update yum install squid cd /etc/squid3
Make backup of default configuration just in case…
cp squid.conf squid.conf.bak
Remove default configuration
rm -rf squid.conf
Create and open new configuration in nano (you can use any other editor)
nano squid.conf
Paste this 2 lines of code into your new configuration file
http_access allow all http_port 20000
Save configuration
6.) Start squid service
service squid start
7.) To check your connection use telnet IP on port defined in your squid configuration.
In this case 20000
telnet IP 20000
Your proxy server is ready if your connection was successiful.
Setup your OS to use this proxy server and go to http://whatsmyip.org to check your new IP address.
Don’t forget to open port 20000 on your server firewall.
Check this article to configure squid on Ubuntu:
http://netjunky.net/how-to-create-your-own-squid-proxy-server-with-azure/
Cloudflare is a great set of services for its community and their websites. It can provide you with high quality tools that any webmaster could ever wish for. Your sites are much safer with these services, and you can easily grasp what is really happening out there around your little Internet web corner.
You can get your free Cloudflare account in couple of minutes, and with it, you get your brand new name servers. All the benefits of moving your domains to Cloudflare is subject to the completely new post. Here, I just want to show three easy little steps on how to activate subdomain filtering to your odoo server (Ubuntu 14.04).
Subdomain filtering? Well, would you like that web address http://base.yourdomain.com/ automagically opens odoo instance and web site with database named base ? Thats it.
Did I mention that Cloudflare would also create ssl certificates for all your domains? For free? Yes and all your odoo sites will be ssl green and trusted worldwide.
First step is really just following this post -> http://netjunky.net/run-odoo-on-port-80-instead-of-8069/
It will reroute all incoming port 80 traffic to odoo default 8069.
On our odoo server, we need to modify odoo daemon script. Usually, you want to setup your production odoo server with odoo daemon/service script. Script is more or less standard and usually placed here -> /etc/init.d/odoo-server (odoo-server name is optional).
Here is the part you need to modify:
# Additional options that are passed to the Daemon. DAEMON_OPTS="-c $CONFIGFILE"
And after the editing, DAEMON_OPTS line should look like this:
# Additional options that are passed to the Daemon. DAEMON_OPTS="-c $CONFIGFILE --db-filter=^%d$"
Save changes to the script and then restart service:
user@server:~$ sudo service odoo-server restart
On your cloudflare dashboard select your domain, and then DNS tool for managing your Domain Name System settings.
Add a new A record which points to your odoo server IP address -> example: A databasename points to 173.25.53.33
Open your browser with new address -> http://databasename.yourdomain.com/
Create new odoo database with name -> databasename (Note: it must be same as the subdomain name in the A record)
Repeate this step for every new subdomain you want to add.
And do you know what else? It works for all your different Cloudflare domains just as well, one odoo server with multiple domains and subdomains.
Obviously, you don’t want and can’t have two or more databases with the same name. So if you need to have something like erp.domain1.com and erp.domain2.com on the same server, you will need to use slightly different regular expression for database filtering -> instead of ^%d$ you should use ^%h$ .
In short, if you decide to go with regular expression ^%h$ , database name in the 3rd step should be hostname-domain-com (we need to switch dots with dashes).
This is solution when you want to host larger number of databases on one odoo server and you need to have even more flexible domain name choices.
Enjoy your brand new odoo nicely named instances!
Hey what about SSL stuff?
Well ask netjunky, maybe he can write something about that.
How to create your own squid proxy server with Azure and Ubuntu OS.
Squid is a proxy server for caching and filtering web content .
Squid proxy service will cache the requested web-content and re-using it for the further request of the same content.You can also hide your real IP with squid and access content usually forbidden for your country or IP address.
1.) Sign in to your Azure Portal and create VM
2.) Choose Ubuntu Server 14.04 LTS
3.) Configure your VM
4.) Create endpoint higher then 1024 for example 20000
5.) Connect with putty to install and configure squid
sudo apt-get install squid -y cd /etc/squid3
Make backup of default configuration just in case…
sudo cp squid.conf squid.conf.bak
Remove default configuration
sudo rm -rf squid.conf
Create and open new configuration in nano (you can use any other editor)
sudo nano squid.conf
Paste this 2 lines of code into your new configuration file
http_access allow all http_port 20000
Save configuration
6.) Restart squid service
sudo service squid3 restart
7.) To check your connection use telnet IP on port defined in your squid configuration.
In this case 20000
telnet IP 20000
Your proxy server is ready if your connection was successiful.
Setup your OS to use this proxy server and go to http://whatsmyip.org to check your new IP address.
Recent Comments