Release 1.25.4
About
This is a version not yet released.
List
New
- DokuWiki Docker - A new way to develop and publish ComboStrap WebSite with Docker
- ComboStrap WebSite - A ComboStrap WebSite permits to develop and publish website collaboratively (locally or remotely)
- A new utility: the page bundler. It may be handy when you want to create a single document (pdf) from multiples pages.
Bug
- Bug reported by jkiser99dev: base rewrite was messing up with the CDN url.
- Bug - the dismiss on popover was preventing any link to work. We took over and have implemented our own dismiss with a mousedown event. The impacted elements were:
- ComboStrap - Request Router: Infinite Redirect because the ID was not cleaned when retrieving it.
- Nice URL: When Nice URL is on, the configuration useSlash should also be enabled otherwise the static resource returns an internal error. Dokuwiki breaks if the file path returned a file that does not exist
- Database Sync: the database sync uses a lock that is deleted at the end by a shutdown function. In php 8.3, this function should not print any debug statement otherwise the TaskRunner returns no response (ie gif) even if successfull.
- Ban was not working. We checked at the very first event but as in the last DokuWiki, the Authorization is handled by a class, the new checks were not working and gave no permissions to see the home page. We make now the ban check at the dokuwiki_init_done event.
- The hamburger template was missing the title
- DokuWiki Docker got a second image pool with better default sizing to avoid OOM error
- ComboStrap\ExceptionNotFound: No database row found for the page: An exception was not caught in the router. Commit
- Error: No mime found for path: An exception was thrown when a mime could not be found. It has been set to binary by default. Commit
- Binary was not set as mime but as string, resulting to Error: Call to a member function toString() on string Commit
- The router has been completely rewritten to catch TOO_MANY_REDIRECT browser error. Commit
- The database row collision detection was throwing an error stopping the sync. We known report an error in the log. c0705265c76e59176d9f02515cf7dcf68d9c4862