| irc.libera.chat #tryton log beginning Wed Dec 29 12:00:01 AM CET 2021 | ||
| -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 00:45 | |
| -!- ChanServ changed mode/#tryton -> +o cedk | 00:45 | |
| -!- springwurm(~springwur@5.104.149.54) has joined #tryton | 06:20 | |
| -!- acaubet(~Thunderbi@194.224.31.235) has joined #tryton | 08:16 | |
| -!- mrichez(~Maxime@2a02:a03f:c2e8:f900:ed77:85ea:af2b:ba6e) has joined #tryton | 08:50 | |
| -!- LordVan(~lordvan@gentoo/developer/lordvan) has joined #tryton | 08:53 | |
| LordVan | hi. hmm what is the best way to figure out which permissions I need to give a user for a certain action (in this case set a Sale to processing state) | 08:55 |
|---|---|---|
| -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 09:14 | |
| -!- ChanServ changed mode/#tryton -> +o cedk | 09:14 | |
| LordVan | cedk, quick question.. I've been trying to figure out why a normal user (as oppsed to the admin account) cannot "process" a Sale .. All the groups are there that are non-admin... with the admin account itself I can process sales without a problem. do you know what I could've missed? | 10:03 |
| -!- acaubet(~Thunderbi@194.224.31.235) has joined #tryton | 10:04 | |
| udono | LordVan: Maybe there are also accounting/invoice or stock/shippment groups needed to process the sale? | 10:10 |
| LordVan | udono, to test that I made the user part of *all* non admin groups -- even has article admin alreadxy too .. so apart from that accounting, accounting party, stock, force stock reservation, sale | 10:14 |
| LordVan | which is why I 'm a bit at a loss as to what the problem is | 10:14 |
| cedk | LordVan: because there is no need for normal user to process sales, they are processed automatically | 10:31 |
| cedk | only admin has the right in case of issue | 10:31 |
| LordVan | ah | 10:38 |
| LordVan | cedk, can this be changed, or would that be a bad idea? | 10:41 |
| LordVan | (I have some internal workflow related reasons for this so ideally I'd prefer to keep it in confirmed until processing is started manually) | 10:42 |
| cedk | LordVan: I think you should not prevent the processing but plug to the workflow so the next step happens when you want like sale_advance_payment does | 10:45 |
| LordVan | let me have a look at that module. I haven't checked it yet as it is not something we need atm | 10:48 |
| LordVan | the thing is though that I am not automatically processing sales because quite often we have to go back to the 'Draft' state to make some amendments even after confirming (unfortunately that happens frequently with some of our usual customers taht they change their mind,..) | 10:51 |
| LordVan | talking like the customer ringing up last minute saying "I need X more of pos Y" ,.. | 10:53 |
| LordVan | or is there a better way to deal with things like that? | 10:53 |
| cedk | LordVan: so use sale_amendment | 10:54 |
| LordVan | ah good point I had forgotten about that | 10:55 |
| LordVan | I forgot what the reason was I haven'T used it before [like a year ago] but I will test it | 10:56 |
| LordVan | hmm it is quite a lot complexer than just going back to a draft and editing there, but it would work after I add the custom fields I have on the sale lines I guess | 11:03 |
| cedk | LordVan: this is for when the processing of the sale as started so we have an history to understand later what happened | 11:05 |
| LordVan | yes i understand that and I do think it is a good way to keep track of changes | 11:05 |
| cedk | but you can also put a delay between confirmation and processing so you can fix sale in case of early mistake | 11:05 |
| LordVan | maybe a slightly inconvenient workflow will encourage people to make less mistakes :D | 11:05 |
| LordVan | cedk, yes i'd been considering that but I am unsure what value would make sense | 11:06 |
| LordVan | "make less mistakes" meaning "check more carefully the first time" | 11:06 |
| cedk | LordVan: usually we put few hours because it is to fix the case "I click the button and just realize few seconds later the error" | 11:07 |
| LordVan | cedk, true it would solve that issue. not so much the "the customer changed his mind" but that is best in an amendment anyway i guess | 11:09 |
| LordVan | i think I will do both in the end | 11:10 |
| LordVan | just wondering if i still have much use for sale_history now anymore .. but nto like i can disable that easily in the running system can't i? ;) | 11:11 |
| LordVan | then I just need to add my own custom fields to the views for the amendment forms and I should be good .. I like that. thanks | 11:14 |
| cedk | LordVan: sale_amendment activate sale_history | 11:14 |
| LordVan | cedk, ah yes ..didn't see that .. makes sense I guess ^^ | 11:15 |
| acaubet | I'm trying to make sale.number readonly false when it's draft | 11:44 |
| acaubet | bug after declaring in __setup__() like cls.number.states['readonly'] = (Eval('state') != 'draft') and cls.number.depends.append('state') | 11:44 |
| acaubet | but* | 11:45 |
| acaubet | the client keep showing as readonly | 11:45 |
| acaubet | any idea about what I'm missing? | 11:47 |
| cedk | acaubet: readonly attribute has precedence over states (I think) | 11:48 |
| acaubet | true, after adding cls.number.readonly = False before the code lines above works as expected | 11:53 |
| cedk | acaubet: if it is not in the doc, it will be good to add it | 12:37 |
| LordVan | anyone know what causes this error?: https://dpaste.org/pJcU | 13:06 |
| LordVan | (included the xml) | 13:06 |
| LordVan | (2nd xpath only to test sth) | 13:07 |
| -!- springwurm(~springwur@5.104.149.54) has joined #tryton | 13:18 | |
| udono | LordVan: it seems you re-define the view type, which is not allowed. | 13:30 |
| LordVan | udono, not sure what you mean (to be honest my knowledge of those XML files is still not as good as I'd like it to be) | 13:56 |
| LordVan | in fact I even took that data section straight from sale_product_customer module sale.xml to make sure i get the inherit,.. correctly | 13:59 |
| -!- semarie(~semarie@user/semarie) has joined #tryton | 15:30 | |
| semarie | I have a migration question: from tip september (6.1) to tip of today, I have some warnings about column migration type change | 15:40 |
| semarie | 88922 7447557392584 [2021-12-29 15:32:09,460] WARNING trytond.backend.postgresql.table Unable to migrate column data on table ir_queue from text to jsonb. | 15:41 |
| semarie | 88922 7447557392584 [2021-12-29 15:33:06,934] WARNING trytond.backend.postgresql.table Unable to migrate column information on table account_statement_origin from text to jsonb. | 15:41 |
| semarie | 88922 7447557392584 [2021-12-29 15:33:15,180] WARNING trytond.backend.postgresql.table Unable to migrate column information on table account_statement_origin from text to jsonb. | 15:41 |
| semarie | 88922 7447557392584 [2021-12-29 15:33:15,181] WARNING trytond.backend.postgresql.table Unable to migrate column keywords on table account_statement_origin from text to jsonb. | 15:41 |
| cedk | semarie: you can do it manually if you want to benefit from JSONB | 16:12 |
| semarie | I tend to avoid 'free' warnings in trytond-admin output when updating, to keep aware of potential problem | 16:18 |
| semarie | I will look to alter the table | 16:18 |
| semarie | cedk: thanks | 16:19 |
| cedk | semarie: we can not make the alter automatically because we have no guarantee that the text content is a valid JSONB | 16:23 |
| -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton | 16:29 | |
| -!- ChanServ changed mode/#tryton -> +o cedk | 16:29 | |
| SISalp | hello, do you know if there are some controls on new passwords ? seems someone tried a diceware pass phrase and got a "character repeated too many times" message | 17:15 |
| cedk | SISalp: yes a minimal entropy is required: https://docs.tryton.org/projects/server/en/latest/topics/configuration.html#entropy | 17:19 |
| SISalp | cedk: so I think diceware passwords may fail to meet this requirement. Thank you for the quick and precise answer. | 17:23 |
| cedk | but I was never comfortable with this constraint and it seems to be wrong: https://security.stackexchange.com/a/193182 | 18:16 |
| -!- rpit(~rpit@p4ffb7b8a.dip0.t-ipconnect.de) has joined #tryton | 18:25 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!