The old TUBAF website was based on the Drupal content management system (CMS) version 6.x from 2014. This technical basis was outdated, so after the cyberattack in January 2023, the rectorate decided not to put the website back online for security reasons. Instead, the cyberattack was taken as an opportunity to implement long-standing plans to revamp the website. An external service provider was commissioned to support the TUBAF project team. In a short time, a completely revised website was created, both technically and visually, with Drupal 10 as the underlying CMS.

At the start of the web relaunch project in April, the priority was to create content relevant to prospective students and students. In order to be able to put this content online quickly, some technical-infrastructural issues had to be pushed back - especially the implementation of the group module. This module makes it possible to organize editors into groups and to grant them access rights only to their own group content (e.g. content from a specific institute). Without this group module with its associated authorization model and media directory, there is only a so-called "central area" where each individual editor can edit all content of the website. It is therefore understandable that the editorial team here had to be kept as small as possible.

By the editorial team of the central area, the most important content for the above-mentioned target groups as well as important basic information on the structural units were created (e.g. contacts, references to blogs). However, the complete development of the Internet presence can only be carried out by the structural units themselves. It can be assumed that with the rollout of the system, the amount of content will increase by leaps and bounds.

No. Many important milestones have been achieved in recent months and the visibility of TUBAF has been successively restored after the cyber attack. However, there are still numerous open tasks and potential for optimization. So there will continue to be technical and visual innovations on a regular basis.

The old TUBAF website will be maintained until further notice to give the editors the opportunity to move their content to the new website. In addition, the old website will temporarily function as an intranet, which means that it should be used for pages that should only be accessible internally. We anticipate a period of at least one year before the old web presence can be shut down.

The complexity of revising the intranet is likely to exceed that of the web relaunch by far - especially if added value is actually to be created in the form of an employee portal with personalized information and access to relevant applications and functions. The project team is continuously collecting ideas for this project and also examining initial variants for implementation. However, the current priority is to revise the external web presence. Accordingly, a start date for the "Intranet" project has not yet been set and still requires some preliminary conceptual work.

Accounts must currently still be created manually by the administrators. The connection to Shibboleth is in progress, so that soon the login with the central user data will be possible. The group admins will then assign corresponding editorial rights to the users.

There will soon be a form available for group administrators to apply for their "old" groups again, i.e. independent areas in the new website. You will find the link on this page.

The processing of applications to set up groups will be based on a defined prioritization list, e.g. faculties will receive their own area again first, then institutes, then professorships and then other areas. In the old system there were about 300 groups. So please understand if it takes some time to set up your group.

As a rule, the request to create a group is made by the person who was the group admin in the corresponding group in the legacy system. A corresponding list is available. However, since there can always be a change of responsibility (age-related departure of persons from the service, job change,...) this list is not binding, so that applications can also be made by other persons of the relevant structural unit.

Currently, the creation of password-protected areas in the new Drupal system is not yet possible. The old website can be used as an alternative for a transitional period, since it is only accessible internally, and the content can be uploaded there and linked accordingly.

Yes, in the glossary you will find the matched translations.

Go to the glossary

Please first read the current version of the editorial guide as well as the information on this page. If possible, seek advice from a key user with advanced web knowledge in your environment. If this does not resolve your questions, we will offer web consultations several times a week as the rollout begins. In exceptional cases, please contact the web team at webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de) (redirected to the ticket system).

The new CMS is, despite intensive testing, not yet free of bugs. Therefore, we welcome your support in discovering bugs/errors. Please report them with as meaningful description as possible and screenshot or link to a sample page to webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de).

Note: If something does not work as you were used to in the old Drupal, it is not necessarily a bug. So please check if it is really a bug that makes working in the system much more difficult or impossible, or if it is just a change for the user. It is not possible in the short project duration and also due to the big jump from Drupal 6 to Drupal 10 to map the old system, which has grown for years, back 1:1.

Currently it is not yet possible to make entries yourself. We are working on making it possible to make entries yourself again.

Please send us the event data to webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de), and the editorial team will enter it. Also remember to indicate if registration is required and who the contact person is for the event, if applicable.

In the future, the contact details of contact persons are to be maintained centrally, so that, for example, when the phone number changes, the contact box is automatically updated on all pages on which it is included. Contact persons can currently only be created by admins and super editors. Please send requests to create contact persons to webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de).

Please send an email to webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de) indicating which contact information should be changed. The contact boxes on the website will then update automatically when the change is made in the central database.