openerp-india team mailing list archive

["Nhomar Hernandez \(Vauxoo\)" <nhomar@xxxxxxxxx>]

Gustavo.

If you dont give the correct information to the customer, the customer
will make mistakes.

But BTW i think both are right, and IMHO, it must be configurable not
All in All out.

Just FYI, Just the automation give us the correct answers....

You NEVER update a production enviroment without tests, if you are
doing, in this case you are totally wrong.

If you work as Windows admin "lets try and pray" it is not an "strategy"
it is "suicide".

To our customers, we give strong trainings with good and bad practices
explained, and this thing what you argumented:

>>Go to the customer 30 days after your implementation is completed and
introduce an update in a base module. Any customer introduced change will
be lost and you will have an argument with your customer about who is
responsible for the potential losses.

Do you introduce an update without test enviroment?
Do you make an update without security test survey?

This is really, really dangerous.

We use several methodolgies, but BTW the best one is the "Common Sense"
if you update your DB and don't verify you don't open something by
mistake wao, what kind of services are you offering??....

Please, IMHO we must solve things thinkinig in Quality not in Quantity
of users..

For me it is a BIG regression, at least Im wrong or Im missing some new
point.

THanks Gustavo for your thoughts.

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1084570

Title:
  [trunk] Access rules are not reloading when you update a module.

Status in OpenERP Server:
  New

Bug description:
  Hello.

  things declared in security folder in past version is updated, in
  trunk, it is not happening.

  Why it is necesary:

  In views the core doesn't accept groups not created by code, if i am
  not able to reload res_group.xml of my module and ist respective
  ir.mode.access.csv it is not possible have a security module
  implementation by implementation.

  If this is a design decisition, it should be cool if somebody can
  explain us what is the workaround wiuth this bug, if not this is a
  regression.

  Sol:

  opt1: 1.- Make configurable as always, probably i need to block update permisions.
  opt2: 2.- revert the change in this way it can works as before.

  How do i reproduce.

  1.- Create a module with a group/
  2.- Create an acl on ir.model.access file/
  3.- Install the modules.
  4.- In graphical interace delete the acl/
  5./ Start your server with -u all -d dbname parameters.

  What do i got:

  acl is not reloaded.

  What do i spect:

  acl is reloaded.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1084570/+subscriptions