web/wdoc/userprefs_en.rst
author Vladimir Popescu <vladimir.popescu@logilab.fr>
Thu, 04 Apr 2013 11:58:41 +0200
changeset 8926 336e4971dc50
parent 6177 76aaca285e07
child 10218 5ebbaf713caf
permissions -rw-r--r--
[dataimport] backout 6947201033be (related to #2788402) (and add a try: except to cache the intended error) The problem actually comes from the ``MassiveObjectStore`` in the ``dataio`` cube, so it should be corrected there. Here, we only protect it with a ``RuntimeWarning`` so that the user can see the problem. ``value`` is set to ``None`` (whence to ``NULL`` from a database standpoint), so that the data can be nevertheless inserted in the database. However, only the keys present in ``row`` are actually non-'``NULL``'. The real solution is to work out the issue in ``MassiveObjectStore`` directly. The current try/except should only be a temporary hack.

The personal information describing a User can be modified using the edit form
of the user. You can access it through the dropdown-menu under the link on the
top-right of the window, labeled by your login. In this menu, click the
"profile" link to go to this form.

Each user can as well customize the site appearance using the "user's
preferences" link in this menu. This will show you a form to configure which
boxes are displayed, in which order, etc...

.. image:: doc/images/userprefs