[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

Once you have read the `RQL tutorial`_ and you know the application'`schema`_,
you're ready to define your own views. Just type the RQL query retreiving data
you're interested in in the search field. If the view used to display them
doesn't fit your need, choose another one in the possible views box (this box
isn't displayed by default, but you can activate it in your `user
preferences`_). Once you're satified, add a `bookmark`_ if you want to reuse
this view later.

.. _`RQL tutorial`: doc/tut_rql
.. _`schema`: schema
.. _`user preferences`: myprefs
.. _`bookmark`: doc/bookmarks


Below are some example of what can be acheived...

.. winclude:: custom_view_last_update
.. winclude:: custom_view_rss