[testlib] call init_config once the config has been properly bootstraped This should be done right after repository instantiation and as such involves giving CWTC.init_config as a callback to the test database handler (which will itself gives it to the repository initialization function). This unfortunatly requires to pass the init_config method to the server.init_repository function because it has to be called after the config has been initialized (which is done in Repository.__init__) but before the migration handler is instantiated (which will call 'server_maintainance' hook, hence may require the proper config). Another way to fix this would be to change the initialization sequence, but this is another story. Closes #3749378

     1

action box

     2

    Area visible in the upper left column. You have a list of available actions on the entity. The most frequently used entry is `modify`.

     3

     4

object

     5

    All element created in the application

     6

    Example: project, ticket, user, ...

     7

     8

relation editing module

     9

    HTML widget that let you define new relations amongst objects.

    10

    11

relation

    12

    It's a kind of 'smart' link between 2 objets of the application. It has a specific sense that determine dynamic behaviour and add a new logic of the content.

    13

    14