Archives
Contributors
-
dms in 18.0 is wow
happy contribution...I am waiting for positive feedback and encouragement.Dear Contributors, I couldn't wait until I share the video of dms module for version 18.0 that I am almost finished with.It will include wow features starting with new odoo design for 18.0 and also a handy security and privacy for managing files and sharing too as well.
https://youtu.be/5z7yPdCnZCo
by Mohamed Alkobrosly - 04:45 - 26 Mar 2025 -
Re: dms security issues solved
Don't worry. There's no problem, but the wording is important. To put "DMS security issues" raises an alarm on something that it's not true. If you want to organize the security in another way, it can be discussed.Let's talk about it on GitHub.Regards.
by Pedro M. Baeza - 05:36 - 25 Mar 2025 -
Re: dms security issues solved
Best regards...Thanks for Pedro for guiding me on best behave.Dear Pedro and community.I am so sorry for causing interruption, I was excited to introduce an extra layer of security for better organization of docs. and ultimate security too.On Tue, Mar 25, 2025 at 10:27 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:Hi, Mohamed, what you (and some others) consider security issues, are conscious decisions about how the DMS work, and they should be discussed separately from the migration to a new version. Please keep the migration clean from these behavior changes and let's discuss any change in GitHub separately.Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Mohamed Alkobrosly - 05:30 - 25 Mar 2025 -
Re: Migrations scripts from MuK DMS to OCA DMS
On 25 Mar 2025, at 15:52, Pedro M. Baeza wrote: > It seems there should be an initial problem that leads to the one you > are including. Please inspect the complete log, and any further thing, > put it on the GitHub repo. > Regards. I’ve opened this issue on the OpenUpgrade github repo with more information including a complete log: https://github.com/OCA/OpenUpgrade/issues/4881 I think this is what you suggested. > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [1] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2] > > > > [1] https://odoo-community.org/groups/contributors-15 > [2] https://odoo-community.org/groups?unsubscribe Regards, Olaf -- Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany Geschäftsführer: Olaf Wagner | Sitz: Berlin Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
by Olaf Wagner - 05:11 - 25 Mar 2025 -
Re: Migrations scripts from MuK DMS to OCA DMS
It seems there should be an initial problem that leads to the one you are including. Please inspect the complete log, and any further thing, put it on the GitHub repo.Regards.
by Pedro M. Baeza - 03:50 - 25 Mar 2025 -
Planned disruption of OCA services on April 7th
Hi everyone,We have been informed by our hosting company that a mainboard replacement needs to be performed on the main OCA server.This means that most OCA services (CI, runboat, weblate, GitHub bot, etc) will be disrupted on 7 April 2025, from 08:00 GMT+2 to 12:00 GMT+2.Please organize accordingly.I'll provide more information as it becomes available.Best regards,-Stéphane--Stéphane Bidoul
by Stéphane Bidoul - 10:31 - 25 Mar 2025 -
Re: Migrations scripts from MuK DMS to OCA DMS
Thank you very much everybody for the information and the great work on openupgrade.
I wasn’t aware that everything is already integrated into the existing scripts.
However, when I run the migration in 13.0, it fails in the postmigration step for the
dms. Im am using the latest versions of the openupgradelib and the 13.0 branch from
openupgrade itself.2025-03-24 16:20:03,420 2372 INFO elego_v13 odoo.modules.migration: module dms: Running migration [13.0.8.1.0>] post-migration 2025-03-24 16:20:03,422 2372 INFO elego_v13 OpenUpgrade: dms: post-migration script called with version 12.0.2.0.1 2025-03-24 16:20:03,579 2372 ERROR elego_v13 OpenUpgrade: dms: error in migration script /opt/odoo/lib/addons/oca-mirror-dms/dms/migrations/13.0.8.1.0/post-migration.py: ('dms.file(3249,).content', None) 2025-03-24 16:20:03,579 2372 ERROR elego_v13 OpenUpgrade: ('dms.file(3249,).content', None) Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/api.py", line 748, in get value = self._data[field][record._ids[0]] KeyError: 3249 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/fields.py", line 1038, in __get__ value = env.cache.get(record, self) File "/opt/odoo/lib/odoo/odoo/api.py", line 754, in get raise CacheMiss(record, field) odoo.exceptions.CacheMiss: ('dms.file(3249,).content', None) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/api.py", line 748, in get value = self._data[field][record._ids[0]] KeyError: 3249 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/dist-packages/openupgradelib/openupgrade.py", line 2331, in wrapped_function version, File "/opt/odoo/lib/addons/oca-mirror-dms/dms/migrations/13.0.8.1.0/post-migration.py", line 9, in migrate env["dms.file"].search([])._compute_mimetype() File "/opt/odoo/lib/addons/oca-mirror-dms/dms/models/dms_file.py", line 379, in _compute_mimetype record.res_mimetype = guess_mimetype(base64.b64decode(record.content or "")) File "/opt/odoo/lib/odoo/odoo/fields.py", line 1065, in __get__ value = env.cache.get(record, self) File "/opt/odoo/lib/odoo/odoo/api.py", line 754, in get raise CacheMiss(record, field) odoo.exceptions.CacheMiss: ('dms.file(3249,).content', None) 2025-03-24 16:20:03,584 2372 ERROR elego_v13 odoo.modules.loading: Error executing post migration script for module dms : ('dms.file(3249,).content', None) 2025-03-24 16:20:03,596 2372 ERROR elego_v13 odoo.modules.registry: Failed to load registry Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/api.py", line 748, in get value = self._data[field][record._ids[0]] KeyError: 3249 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/fields.py", line 1038, in __get__ value = env.cache.get(record, self) File "/opt/odoo/lib/odoo/odoo/api.py", line 754, in get raise CacheMiss(record, field) odoo.exceptions.CacheMiss: ('dms.file(3249,).content', None) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/api.py", line 748, in get value = self._data[field][record._ids[0]] KeyError: 3249 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/modules/registry.py", line 87, in new odoo.modules.load_modules(registry._db, force_demo, status, update_module) File "/opt/odoo/lib/odoo/odoo/modules/loading.py", line 489, in load_modules force, status, report, loaded_modules, update_module, models_to_check, upg_registry) File "/opt/odoo/lib/odoo/odoo/modules/loading.py", line 368, in load_marked_modules upg_registry=upg_registry, File "/opt/odoo/lib/odoo/odoo/modules/loading.py", line 256, in load_module_graph migrations.migrate_module(package, 'post') File "/opt/odoo/lib/odoo/odoo/modules/migration.py", line 191, in migrate_module migrate(self.cr, installed_version) File "/usr/local/lib/python3.7/dist-packages/openupgradelib/openupgrade.py", line 2331, in wrapped_function version, File "/opt/odoo/lib/addons/oca-mirror-dms/dms/migrations/13.0.8.1.0/post-migration.py", line 9, in migrate env["dms.file"].search([])._compute_mimetype() File "/opt/odoo/lib/addons/oca-mirror-dms/dms/models/dms_file.py", line 379, in _compute_mimetype record.res_mimetype = guess_mimetype(base64.b64decode(record.content or "")) File "/opt/odoo/lib/odoo/odoo/fields.py", line 1065, in __get__ value = env.cache.get(record, self) File "/opt/odoo/lib/odoo/odoo/api.py", line 754, in get raise CacheMiss(record, field) odoo.exceptions.CacheMiss: ('dms.file(3249,).content', None) 2025-03-24 16:20:03,597 2372 CRITICAL elego_v13 odoo.service.server: Failed to initialize database `elego_v13`. Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/api.py", line 748, in get value = self._data[field][record._ids[0]] KeyError: 3249 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/fields.py", line 1038, in __get__ value = env.cache.get(record, self) File "/opt/odoo/lib/odoo/odoo/api.py", line 754, in get raise CacheMiss(record, field) odoo.exceptions.CacheMiss: ('dms.file(3249,).content', None) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/api.py", line 748, in get value = self._data[field][record._ids[0]] KeyError: 3249 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/odoo/lib/odoo/odoo/service/server.py", line 1194, in preload_registries registry = Registry.new(dbname, update_module=update_module) File "/opt/odoo/lib/odoo/odoo/modules/registry.py", line 87, in new odoo.modules.load_modules(registry._db, force_demo, status, update_module) File "/opt/odoo/lib/odoo/odoo/modules/loading.py", line 489, in load_modules force, status, report, loaded_modules, update_module, models_to_check, upg_registry) File "/opt/odoo/lib/odoo/odoo/modules/loading.py", line 368, in load_marked_modules upg_registry=upg_registry, File "/opt/odoo/lib/odoo/odoo/modules/loading.py", line 256, in load_module_graph migrations.migrate_module(package, 'post') File "/opt/odoo/lib/odoo/odoo/modules/migration.py", line 191, in migrate_module migrate(self.cr, installed_version) File "/usr/local/lib/python3.7/dist-packages/openupgradelib/openupgrade.py", line 2331, in wrapped_function version, File "/opt/odoo/lib/addons/oca-mirror-dms/dms/migrations/13.0.8.1.0/post-migration.py", line 9, in migrate env["dms.file"].search([])._compute_mimetype() File "/opt/odoo/lib/addons/oca-mirror-dms/dms/models/dms_file.py", line 379, in _compute_mimetype record.res_mimetype = guess_mimetype(base64.b64decode(record.content or "")) File "/opt/odoo/lib/odoo/odoo/fields.py", line 1065, in __get__ value = env.cache.get(record, self) File "/opt/odoo/lib/odoo/odoo/api.py", line 754, in get raise CacheMiss(record, field) odoo.exceptions.CacheMiss: ('dms.file(3249,).content', None) 2025-03-24 16:20:03,599 2372 INFO elego_v13 odoo.service.server: Stopping gracefully openupgrade failedThis may be a subsequent error, as I see some of these error logs before:
2025-03-24 16:20:03,383 2372 ERROR elego_v13 OpenUpgrade: Pass argument 'env_or_cr' as Cursor parameter until 16.0I haven’t been able to isolate the problem further yet.
The actual data — dms.file(3249) — is there and should be correct (at least in the MuK tables); content is
one of the columns that are new or migrated.Looking forward for any hints how best to proceed again.
Olaf
On 24 Mar 2025, at 13:33, Enric Tobella Alomar wrote:
When we ported the module, we made it compatible with MUK DMS. You should need to use OpenUpgrade on the migration and set the rename of the module on the apriori file.Kind regards,El lun, 24 mar 2025 a las 13:17, Radovan Skolnik (<notifications@odoo-community.org>) escribió:Hi,
I believe it is already part of the migration scripts. Check https://github.com/OCA/dms/tree/13.0/dms/migrations/13.0.1 and/or https://github.com/tegin/dms/commits/13.0-dms-migration/
Best regards
Radovan Skolnik
On pondelok 24. marca 2025 12:07:13 CET Olaf Wagner wrote:
> Hello everybody,
> we need to migrate some customers from the original MuK DMS modules to
> the OCA modules. I seem to remember having seen something about ready
> migration scripts several years ago when the DMS modules were first imported
> into the OCA repository, but am not able to find that again.
> Can anybody help?
> Thanks in advance for any hint,
> Olaf
> --
> Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
by Olaf Wagner - 09:11 - 25 Mar 2025 -
Re: odoo CE to OCB
You can try Doodba (https://github.com/Tecnativa/doodba) for using Docker and there, OCB is used by default (but you can also use odoo/odoo if you want).Regards.
by Pedro M. Baeza - 09:06 - 25 Mar 2025 -
Re: odoo CE to OCB
Hi Abdulbasit, Just get the most recent OCA/OCB, that's always the best idea anyway - it's based on the latest odoo/odoo and has the most fixes available. Only thing is that if you were stuck on an older image, you might have to "upgrade base" and in some databases this can overwrite some records. Make sure you test this on a test database first before doing it in production. -Tom On 3/24/25 11:47, Abdulbasit Suleiman wrote: > Dear Contributors, > > We are deploying odoo17 CE with OCA modules. Using docker-compose > However we want to migrate our customers to OCB image without > affecting the persistent volume. > > Kindly recommend the OCB docker image that the docker file is most > similar to odoo CE image. > > Best Regards, > Abdulbasit Suleiman > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe >
by Tom Blauwendraat - 09:01 - 25 Mar 2025 -
Re: dms security issues solved
Hi, Mohamed, what you (and some others) consider security issues, are conscious decisions about how the DMS work, and they should be discussed separately from the migration to a new version. Please keep the migration clean from these behavior changes and let's discuss any change in GitHub separately.Regards.
by Pedro M. Baeza - 08:26 - 25 Mar 2025 -
dms security issues solved
Best Regards...I am waiting for your reviews on our migration, and I am pleased to have the fix merged in older versions too.Only we have to assign any user as a follower to the file in its mixin in form view and those users whether they are internal or portal will access only the files they are following.In brief as portal users can access only their related sales order and invoices, they access only their related files.here is the commit of the solution:Now we could solve the security issue in 18.0 but I guess if some members here are annoyed from these issues in older versions like 17.0 and 18.0 I left the commit of the solution in that PR:I was interested to assign each portal user access to only their related files and by default related directories only.We found that some people have raised them in:Dear OCA community, recently we have been migrating DMS module from 17.0 to 18.0.While migration we encountered some security critical issues.
https://github.com/OCA/dms/issues/381
https://github.com/OCA/dms/issues/386
https://github.com/OCA/dms/pull/385
8db593b4bcb94f772576f7fec33f6c1837bd610f
by Mohamed Alkobrosly - 06:56 - 25 Mar 2025 -
Re: Migrations scripts from MuK DMS to OCA DMS
When we ported the module, we made it compatible with MUK DMS. You should need to use OpenUpgrade on the migration and set the rename of the module on the apriori file.Kind regards,El lun, 24 mar 2025 a las 13:17, Radovan Skolnik (<notifications@odoo-community.org>) escribió:Hi,
I believe it is already part of the migration scripts. Check https://github.com/OCA/dms/tree/13.0/dms/migrations/13.0.1 and/or https://github.com/tegin/dms/commits/13.0-dms-migration/
Best regards
Radovan Skolnik
On pondelok 24. marca 2025 12:07:13 CET Olaf Wagner wrote:
> Hello everybody,
> we need to migrate some customers from the original MuK DMS modules to
> the OCA modules. I seem to remember having seen something about ready
> migration scripts several years ago when the DMS modules were first imported
> into the OCA repository, but am not able to find that again.
> Can anybody help?
> Thanks in advance for any hint,
> Olaf
> --
> Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 01:32 - 24 Mar 2025 -
Re: Migrations scripts from MuK DMS to OCA DMS
Yes, I confirm that's it!
by Pedro M. Baeza - 01:25 - 24 Mar 2025 -
Re: Migrations scripts from MuK DMS to OCA DMS
Hi,
I believe it is already part of the migration scripts. Check https://github.com/OCA/dms/tree/13.0/dms/migrations/13.0.1 and/or https://github.com/tegin/dms/commits/13.0-dms-migration/
Best regards
Radovan Skolnik
On pondelok 24. marca 2025 12:07:13 CET Olaf Wagner wrote:
> Hello everybody,
> we need to migrate some customers from the original MuK DMS modules to
> the OCA modules. I seem to remember having seen something about ready
> migration scripts several years ago when the DMS modules were first imported
> into the OCA repository, but am not able to find that again.
> Can anybody help?
> Thanks in advance for any hint,
> Olaf
> --
> Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 01:16 - 24 Mar 2025 -
Migrations scripts from MuK DMS to OCA DMS
Hello everybody, we need to migrate some customers from the original MuK DMS modules to the OCA modules. I seem to remember having seen something about ready migration scripts several years ago when the DMS modules were first imported into the OCA repository, but am not able to find that again. Can anybody help? Thanks in advance for any hint, Olaf -- Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany Geschäftsführer: Olaf Wagner | Sitz: Berlin Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
by Olaf Wagner - 12:05 - 24 Mar 2025 -
Re: Manage odoo automatic mails with recipients anti spam
Hi David,
We are using an external mailbox via SMTP. Any delivery issues - such as mailinblack - appear in the inbox of the external mailbox. Actual delivery can be managed from the dedicated inbox. We did not find an automated solution yet, probably because that is the intention behind the use of mailinblack 😊.
Set-up of such a mailbox is via Technical > email > outgoing mail servers.Hope this helps.
Kind Regards,
From: David Beal <notifications@odoo-community.org>
Date: Friday, 21 March 2025 at 13:03
To: Contributors <contributors@odoo-community.org>
Subject: Manage odoo automatic mails with recipients anti spamDear OCA contributors,
How do you manage automatic mailings from odoo when the recipient uses an anti-spam solution that requires the sender to be validated by a return mail that requires clicking on a link or filling a captcha ?
I have a customer who uses the https://www.mailinblack.com/en solution.
Mails returned by recipients who have mailinblack are not returned in Odoo in the original mail thread and are invisible in Odoo.
What are the best practices in this case?Thanks a lot
Regards
David BEAL
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Piet Hendriks - 01:21 - 21 Mar 2025
