SQL query in Odoo
Sql query in Odoo model
Scheduled actions can be set by adding this code in your xml file. This exemple will call the function schedule_action from the model hr.employee and send a notification by email if the boolean enable_send_notification is True. This model inherits hr.employee and defines 1 additional field, and 2 additional functions. send_notification is sending email based on the the template my_module.email_hr_employee_notification, see this post how to create email template with xml, schedule_action is the function called by the scheduler.
Artisan is a Japanese brand that specializes in creating high-quality artisan mousepads. These mousepads are made using premium materials, such as silica gel and cloth, and are known for their smooth and consistent surface that provides an excellent tracking experience for gaming mice. What sets Artisan mousepads apart from other brands is their focus on both form and function. These mousepads are not just functional, but also have a unique and attractive design that adds to the overall aesthetic of a computer setup. They come in a variety of sizes, shapes, and colors, so there is something for everyone.Another notable …
Odoo community is not protected against brute force attack by default, the system is vulnerable over internet, however Odoo store provides auth_brute_force App which can handle this task, it’s available through this link. But it doesn’t work correctly behind a reverse proxy such as Caddy or Nginx. In the second part of this post, i’ll explain the little tip to make it work. Download and install the module Download the file corresponding to your version of Odoo. Unzip the file “auth_brute_force-9.0.1.1.0.zip”. Move the folder “auth_brute_force” to your module folder: “/usr/lib/python2.7/dist-packages/openerp/addons/“. Enable the developper mode through “About” popup. Then go to …
Plugin for displaying code in the front end: http://www.viper007bond.com/wordpress-plugins/syntaxhighlighter/ code to use in the backend: [code lang=”xml”][/code]
Sometimes SpamAssassin scores email as False Positive spam, to avoid incoming emails to get junked, we can define globally in the config file /opt/zimbra/conf/amavisd.conf.in domain with a initial score. To whitelist a domain we add domain with a negative score: To blacklist a domain we add domain with positive score: To apply the modification restart Amavis: Now from the source of incoming emails we can see when it’s coming from mydomain.com the initial score is -3 and spammer.com is 5.
