EGOCMS 26.1.0

Features

• Frontend administration
  • Forms can be forwarded to the next form after successful submission. Data from fields with the same name is transferred.
  • The EGOCMS supports a new captcha provider: ALTCHA. Similar to Cloudflare, ALTCHA performs a so-called Proof-of-Work (PoW) check instead of entering a character string. All you have to do is activate a checkbox that triggers an intelligent check to determine whether the user of the form is a human or a bot. Unlike Cloudflare, ALTCHA runs entirely in EGOCMS and therefore does not communicate with any external service (so there are no additional costs). ALTCHA is recommended if the classic Captcha is too complicated for you and a pure PoW check is sufficient. If you require additional features, these can be covered by Cloudflare. Please note that Cloudflare requires an account for this. You can find more information on this in our online help.
  • Blocks can be set via the condition parameter so that they may only occur once in the current client, in a list of specific clients or in all clients(details).
  • In global.json, merge=true can be used to specify for certain values that they do not overwrite but extend the previous value. This occurs as a comma-separated list (accordingly, this property only makes sense for options that expect a comma-separated list).
• Live synchronisation
  • When downloading multimedia files from the live server, an MD5 checksum check is carried out beforehand and the files are only downloaded if they do not exist on the editorial server or are not identical. This already happens for the synchronisation of files from the editorial server to the live server and now applies in both directions (both for multimedia and Mediapool).
  • Pages that would not have a path on the live server because all possible paths to the page contain at least one page that may not be transferred to the live server are not created on the live server or are removed on the live server(this corresponds to an automatic intranet flag).
• The name of a page is now validated. This must not be the same as a meta URL if the page is mounted directly under the start page or a page with an area domain. The check is performed via the page method isValidName($name) and can also be extended via a PageExtension if required.
• Input Plugin Validate: The function specified in the func parameter can also supply text to display different error messages. An empty text is not considered an error.
• When integrating page types with design variants via the Dynamic content block, any existing CSS and JavaScript files are also integrated.
• The sitemap.xml does not generate URLs for pages of the redirect type.
• Certain actions in the system service are now deactivated by default and can be activated if required. This is done using the same settings that are used to deactivate actions in the system service. This decision was made because it is not necessary to execute these actions regularly during normal operation; the data is automatically kept up to date. These actions can also have very long execution times. It therefore makes more sense for administrators to execute these actions, or the associated scripts, manually if the need arises.
  • Update URLs
  • Update links
  • Update search index

Compatibility

• Chatbot streaming has been optimised for Safari.
• Rewrite1 and Rewrite2: The local call of index.php URLs in the frontend without login is now allowed.
• The migrate_urls.php script now catches errors, displays the error messages and then continues.
• Input Plugin WYSIWYG Legacy: The dialogue width and height for use in the frontend is now 1440 x 900 pixels.
• The EGOCMS Standard Captcha(Securimage) has been updated to version 4.0.2.

Bug fixes

• The action "Copy to..." (sitemap and menu) must not be used to select the copied page as the target page.
• When recursively inheriting rights to subordinate pages, the checkbox for changing the selection function has been corrected.