Release: QUIQQER 2.33
Executive summary
QUIQQER 2.33 is a broad operational release. Core 2.33.0 makes password-reset automation and process locking easier to control, while Bricks, Contracts, CMS Import, OAuth Server, Tags, Purchasing, ERP, Dashboard, and Guest Orders refine the workflows around day-to-day project work.
The common thread is not one headline feature, but fewer manual steps and clearer system behaviour. Administrators gain better console and locking controls, editors receive more predictable content windows and search tools, and business modules add filters and interfaces that make routine work easier to verify.
This report is based on the available release notes and is intended as orientation. The effect on a specific installation still depends on its modules, customizations, and operating environment.
What changed
More controlled Core administration
Core 2.33.0 extends the password-reset console command so an account identifier can be passed as an argument, the new password can be read from standard input, and confirmation prompts can be skipped when appropriate. This makes controlled recovery procedures and scripted administration easier without changing the underlying account model.
Core also introduces configurable process locks and corresponding system settings. These controls help projects coordinate long-running or mutually exclusive processes more explicitly. A new search field in the site-selection popup reduces friction when administrators work with larger project trees.
Editing and accessibility in Bricks
Bricks 2.37.2 improves prepared brick windows: they can start at their calculated height, support automatic height handling, and receive parameters from the button that opens them. The changes are small individually, but together they make editing dialogs behave more consistently for content teams.
BoxContentAdvanced now supplies the missing aria-level information for entry headings. Locale files and dialog translations were also reorganized so Bricks uses the current Core locale group more consistently.
Clearer contract and purchasing workflows
Contracts 2.10.0 adds due-date and period filters to the overview and APIs, including totals calculated for the filtered result. The analysis window and action controls were modernized as well. Teams can therefore narrow reporting to the relevant period and reconcile the displayed totals with less manual work.
Purchasing 2.12.0 redesigns document and line-item editing and improves MCP handling when purchasing documents are downloaded as PDF files. ERP 4.2.1 adopts the updated Core user interface, while Dashboard and Guest Orders receive smaller consistency and cleanup changes.
Safer imports, authentication, and tag maintenance
CMS Import 2.1.1 now creates imported groups with UUID references, applies Core permission checks to imported media, inherits permissions from canonical parent sites, and respects the console system-cleanup check. These changes reduce the chance that imported structures diverge from the permission and maintenance rules of the target project.
OAuth Server 3.11.1 adds SQLite-compatible refresh-token locking and removes a redundant permission check. Tags 2.3.0 adds search to tag management and supports broader, batched cache rebuilding, which is useful when large sets of tagged pages need to be synchronized.
What this means for projects
Projects with automated administration should review the new Core console options and decide whether non-interactive password resets belong in their operating procedures. Installations using Contracts, Purchasing, CMS Import, OAuth Server, or Tags have the most visible module-level changes and should test the affected workflows against their own permissions and integrations.
For editorial teams, the Bricks and site-selection changes should mainly appear as calmer, more predictable interactions rather than a changed publishing model.
Operational notes
- Review configured process locks before introducing them into scheduled or parallel jobs.
- Test imported media and inherited site permissions with representative roles.
- For OAuth installations on SQLite, verify refresh-token behaviour under concurrent requests.
- After a tag-cache rebuild, check a representative set of tagged listings and detail pages.
Looking ahead
QUIQQER 2.33 continues the recent focus on making the platform easier to operate across different project sizes and module combinations. The practical next step is a project-specific test that concentrates on account recovery, process coordination, permissions, and the business workflows actually enabled in the installation.