Features
- The password entered can be shown or hidden in the standard EGOCMS login screen.
- Tab with calendar: A calendar tab can be displayed via "navigation.ini", which can be filled with the page method "getCalendarItems"(details).
- Superusers receive a "Didyou know?" dialogue at the first login of the day if there are unread tips & tricks. This dialogue can also be opened at any time via the "Help" menu.
- In future, EGOCMS blog articles will be presented in this dialogue to highlight new functions or describe existing functions in more detail.
- AI
- The chatbot can now optionally allow file uploads and obtain the context for the conversation from the content of the uploaded files.
- The prompt for handling uploaded files can be set individually for the chatbot.
- Mediapool files can also automatically generate the short description with AI.
- Synonyms for keywords can also be generated automatically with AI.
- JSON/REST API
- Customised methods are possible(details).
- GET calls to page methods are also possible for the login process.
- Frontend administration
- The "Dynamic Content" block shows the editor a message on which page they can edit the content (if the editor is authorised to edit the included page).
- In the "Insert/edit link" dialogue, the target of the link is automatically set to "New window" when selecting an internal page on another client or when entering an external URL. This can of course be changed later if required.
- As soon as the selected layout contains at least one form, a "Form" toolbar button is displayed, which can also be used to access the general form settings. These general form settings can also be accessed via each individual form block.
- The data saved in a form can now also be exported as XLSX (Excel) in addition to CSV.
- Field validation
- New test: keyword. The system checks whether at least one keyword has been assigned to the page.
- The status of all field validations of the page type can be viewed via the toolbar button "Check".
Performance
- Live synchronisation
- If possible, the standard EGOCMS tables are not transferred to the same live server more than once if they have already been transferred and there have been no changes to these tables in the meantime. This is particularly useful for live synchronisations that synchronise several clients (e.g. via a shared service).
- The cache on the editorial server is only deleted after the synchronisation if there were also changes on the editorial server during the synchronisation.