Community mailing list archives
Re: Benevolent Record Dictatorby
David Arnold BA HSG / Analista
315 304 13 68/ email@example.com
devCO - empresa de consultoría de sistemas (en fundación)
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. devCO is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
No JS needed. Just group security.
The edit button needs to be restricted to a certain security group, ideally a group congruent with the users who have write access on the.Chico VenancioCEO e Diretor de Criação
VM TECH - (98) 9 8800 27432015-11-03 21:22 GMT-03:00 David Arnold <firstname.lastname@example.org>:HiI doublechecked, and yes, the edit button is "available" on the tax record which was protected by:[('create_uid','!=',1)] permissions: write, unlinkIs there any elegant way to disable the create button? I reference the html for what I mean...<button accesskey="E" class="oe_form_button_edit btn btn-default btn-sm" type="button">Edit</button>I have a hard time to imagine that I'm the first person stumbling over this behavior...Christian, where you referring to the same? This would imply that there has been a js script that made this magic in v8, which has gone in v9... Frankly, I doubt that.