c2c-oerpscenario team mailing list archive

[OpenERP Majordomo <675714@xxxxxxxxxxxxxxxxxx>]

**automated message**
Thanks a lot for reporting this bug and contributing to OpenERP. Unfortunately the OpenERP Web Client project is not going to be developed further after the 6.0 series. As of 6.1 a newer and better web frontend known as the OpenERP Web project[1] will be available.
Our R&D developers normally work in Launchpad to fix bugs for the next release, but there will be no next release for the current OpenERP Web Client. As our resources are limited, all further R&D efforts from the Web team are dedicated to finish the new 6.1 OpenERP Web project[1].
This bug will be closed as "Won't Fix" to show that R&D won't be able to work on it.

Bugs affecting customers in production of course continue to be handled via the OpenERP Enterprise (OPW) maintenance service, and this is the recommended way to have them corrected directly in the 6.0 LTS stable branch.
You can find more details about all of this in the FAQ of our Bug Management Policy documentation[2].

If you are interested, you should soon be able to beta-test the new
OpenERP Web 6.1 (this will be announced on OpenERP Community channels).

Thank you for your contributions and for your understanding!

[1] https://launchpad.net/openerp-web
[2] http://bit.ly/openerp-bugs-faq (FAQ #4)

** Changed in: openobject-client-web
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/675714

Title:
  selected_dbs is missing

Status in OpenERP Web Client:
  Won't Fix

Bug description:
  On the same server, I have two instances : one for production and one
  for test. Each instance has its own database and its own code base.
  With version 5, we can filter selectable databases at the login screen
  by specifying a value to selected_dbs in the configuration file. But
  since version 6, this setting has been removed. Can you please put it
  back so the users can see only the corresponding database for each
  instance ? The only workaround I found is to run each instance with
  its own database user. But each time you setup a server, you have to
  create two or more users instead of just one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-client-web/+bug/675714/+subscriptions