On Nov 7, 2018, at 6:18 AM, Zoltán Kócsi <zol...@bendor.com.au> wrote: > > For some projects we used colour-coding of the Timeline entries, for > example releases were coloured differently from developers-only commits > and so on. That all seems to have gone.
If you upgraded your central repository server from 1.29 to 2.7 to fix the problem suggested by drh — someone’s been checking in SHA3-hashed artifacts — then you also have to update your skin. If you were using the stock skin before, just go into Admin > Skins and select the Default skin again. You might have to switch to some other skin and back to get it to overwrite your outdated skin files. If you made changes to your local skin, you’ll have to merge the changes made to the default version of the skin you started with into your local version. In versions 2.5 and 2.7, there were a lot of changes to the default skin, some of which were done to track changes made to the HTML emitted by “fossil server” in support of newer features. Outdated skins won’t style the new HTML properly. _______________________________________________ fossil-users mailing list firstname.lastname@example.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users