Skip to Content
เมนู
คุณต้องลงทะเบียนเพื่อโต้ตอบกับคอมมูนิตี้
คำถามนี้ถูกตั้งค่าสถานะ
1 ตอบกลับ
14270 มุมมอง

tldr;

Odoo is sold as an enterprise solution but in my opinion fails quite miserably in the way it forces developers to work with it.


Hi I'm Martin!

I'm a fairly experienced web developer (10+ years) and have worked with different kinds of  frameworks/languages (drupal, vue, nodejs, wordpress,...). In the last months I worked on a reasonably small project with odoo.

In general I like the idea behind odoo a lot. I also like the commitment to backwards compatibility which makes the maintainers lifes harder. Kudos for that!

That being said I wonder how you guys deal with all the unnecessary obstacles odoo seems to put in our way?


This is my rant on the developer experience working with odoo.
This will hurt a little.


1. Errors in qweb templates

Errors mostly do not give you any hint as to what or where exactly the problem is.


2. Adapting templates

Removing elements from templates causes errors because other modules inherited the same template and expect a certain element in a specific place, or throw errors, which brings you back to 1.


3. Changing template changes made by other modules

As far as I know, removing changes to templates by inheriting them made by other modules is not possible. How do you do this?


4. Updating templates

This needs a server restart and possibly module upgrades.

The collective amount of developer time wasted by not realising that you need to restart or upgrade a module must be huge.

Why not do it like almost any other web technology and allow for quick change cycles?

Even with --dev, changes that literally take seconds to make in php applications often take minutes because some xpath selector did not match.


5. Getting information / community culture

If you search for issues on google you mostly get results from this forum - which could be fine. But quite often the answers there are simply posted code snippets that do not actually answer the question. How are others supposed to get a grasp of best practices?


6. Documentation

The general tenor (by reading 100s of forum issues) seems to be that developers are supposed to check out odoo's code to get a grasp of how things work.

If you really want developers to be able to work with your software, complete and accessible documentation is key in 2021.

Here's an example:

Setting/changing values on a related field. There's a specific way of updating a record with int constants which updates the relation. The official documentation does not (as far as I'm aware) tell you how this actually works. The one place I found that does, is: https://www.odoo.com/forum/help-1/many2many-write-replaces-all-existing-records-in-the-set-by-the-ids-148267


7. Quality/comments of odoo's code

Since developers are kind of supposed to learn how to use odoo from odoo's source it's even more depressing that most code is poorly documented and at the same time unclear in its intentions in many places.


8. General stability/brittleness

I've had several issues that came up on only a single odoo instance (e.g. only on staging) even though all instances where exact copies of one another.

Another example: Pdf generation with whtmltopdf.
Odoo 13 works with a single (and quite outdated) of wkhtmltopdf. If you try to use any other version you will have a bad time.


9. Adding fields to models sometimes throws errors when upgrading the module

Adding fields to models sometimes tells me that the newly defined column does not exist. Before even using the new field in templates.

Either the developer does something wrong and it should never work, or it should always work. But hunting after obscure issues like this is a huge timesink.

Googling (again) for issues like this returns solutions like to reinstall the module, which is a workaround at best if it works at all.


---

Odoo is sold as an enterprise solution but in my opinion fails quite miserably in several aspects in allowing developers to work with it.


So my question is this:

How do you guys deal with all that?
How do you justify the amount of time changes take to your bosses and customers?
In which ways do you improve and speed up the whole development process?

อวตาร
ละทิ้ง

You are free to subscribe to the enterprise edition and have access to Odoo's support. Else you have to spend some efforts to learn Odoo. The documentation has very much improved the last 2-3 years. Anyway, this is a help forum only, for discussions please use the corresponding mailing lists at www.odoo.com/groups

คำตอบที่ดีที่สุด

Disclaimer:  This post is for "behind-the-scenes" Odoo partners and Developers.  End users who have chosen an Odoo Partner wisely will experience NONE of this type of issue because Odoo is designed to be implemented and supported by Odoo partners for a seamless, error-free experience that is customized for their specific client requirement.   ODOO IS A FRAMEWORK to build upon.

Responding to Rant

Reading through your rant, I can identify with nearly all of the issues you raise.  Odoo - from the developer's point-of-view - feels very "alpha".  Even now, I wanted to reply to this post so clicked the "login" button.  Then I was moved back to my account page and had to search - again - for this post in order to view it as a logged in user.  "This is an Alpha" problem.

THAT SAID...  This is not just Odoo.  This is simply modern development.  Python was never designed to be error-checked or debugged and when you layer NODE on top of that, there is very little you can do to debug.  First you run the Odoo console to catch the gibberish Python errors describing a failure chain 30 minutes long (this failed so this failed so this failed so this failed....), or- since the error was in NODE - you need to use the browser's built-in debugger - and then you, finally, have no idea why it failed.  SAP is just as bad.  This is just modern development; we no longer expect things to work and if you do, you are just a whiner. 

Move Fast and Break Things - Mark Zuckerberg

Odoo support is generally not the solution you are going to find success with. Odoo support is for end-users needing answers to simple functionality questions: "how do I login?".  

If you pay for a bank of support hours (not free support) then you can get great solutions - at a high cost. I consider my "Odoo Guy" (for whom I pay using my prepaid bank of hours) to be a crucial member of my team.

Odoo Partners seem to have paid so much for their knowledge that they cannot see value in sharing it with do-it-yourself non-clients or other partners.  

"I paid Odoo $3000 for this answer alone - why should I give it to competitors for free"

And so the answer to your question would be: Find a Gold Partner who has spent a lot investing in building a team and learning the answers and pay THEM for information.  Not just end-users, smaller Ready and Silver partners just cannot possibly support the staff to research every bug that they discover.  So an ecosystem of for-pay support between partners has developed.  It is the very opposite in spirit of "open source", but it is the reality of Odoo.

While this might be disappointing to a developer with an open-source mindset, I cannot say that this is particularly bad; just compare any other ERP of this magnitude and things are worse - MUCH WORSE.  But you are correct if you are saying that Odoo could be better if they focused on removing bugs and documenting..

I think we all feel you pain but we chalk it up to "Growing Pains" at Odoo.  Because in the end, your client gets the product that they need while YOU get the pain (and the paycheque).

อวตาร
ละทิ้ง