[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

  <table class="attributeForm" style="width:100%;"

     2

	 tal:attributes="id tab_id | nothing;

     3

			 class tab_class | nothing;">

     4

    <tr tal:iter="widget lines">

     5

      <th class="labelCol" tal:content="structure python:widget.render_label(entity)">attrname</th>

     6

      <td tal:define="error python:widget.render_error(entity)" style="width:100%;"

     7

          tal:attributes="class python:error and 'error' or nothing">

     8

	<div tal:replace="structure error">error message if any</div>

     9

	<div tal:replace="structure python:widget.edit_render(entity)" >widget (input, textarea, etc.)</div>

    10

	<div tal:replace="structure python:widget.render_help(entity)">format help if any</div>

    11

      </td>

    12

    </tr>

    13

  </table>