Release: QUIQQER 2.36
Executive summary
QUIQQER 2.36 brings together several changes that make routine work easier to complete and easier to operate. Core 2.36.0 introduces provider-based mobile uploads through QR links, Sign 1.5.0 extends that flow to documents returned from a smartphone, and Contracts 2.11.0 adds a more complete path from contract content and templates to customer signing.
The operational side of the release is equally important. Cron 2.12.3 isolates scheduled jobs with Symfony Process, blocks individual jobs during system updates, and adds structured failure diagnostics. Invoice, Cache, Translator, Contact, SEPA, and ERP receive narrower changes aimed at predictable processing, clearer diagnostics, and fewer edge cases in maintained installations.
This report is based on the available release notes and is intended as orientation. The relevance and risk of an update still depend on the modules, integrations, and operating environment of each project.
What changed
Mobile hand-offs for uploads and signatures
Core 2.36.0 adds provider-based mobile uploads through QR links. A task that starts on a desktop can therefore hand off file capture to a phone without requiring an improvised transfer step. The provider model also gives future upload routes a defined integration point rather than tying the workflow to one implementation.
Sign 1.5.0 builds on the new Core requirement and supports signing returns from a smartphone. Process documents are now visible in the signing settings as well. Together, these changes make document hand-offs more transparent for administrators and more practical for users working across devices.
A fuller contract workflow
Contracts 2.11.0 adds contract content, template management, and a guided editing workflow. It also introduces customer signing, informational PDFs, email-based signing, and manual returns. This moves the module beyond storing contract records toward supporting the actual preparation, exchange, and return of contract documents.
Projects using customized documents or mail flows should treat this as a workflow change, not only an interface update. Templates, generated PDFs, recipient communication, and both digital and manual return paths should be tested together.
Scheduled work with clearer boundaries
Cron 2.12.3 runs scheduled jobs through Symfony Process and adds structured failure diagnostics. Worker output is supported in environments restricted by open_basedir, and individual jobs are blocked while system updates are running. These changes provide better isolation and make failures easier to investigate without allowing background work to interfere with an update.
Deletion of system cron entries is now limited to superusers. That closes an administrative gap around jobs that are part of the platform's operating structure.
Invoice processing and payment state
Invoice 2.15.1 initializes draft contacts from customer defaults, accepts invoice addresses from POST requests, and resolves mail-name placeholders consistently. PDF output can be resolved by UUID, while Imagick and QR-code rendering failures receive explicit handling. Linked invoices are also updated when payment status changes.
The release further improves MCP handling for configurable invoice downloads. For integrations, the practical benefit is a more explicit route to the intended document together with more consistent customer and payment data around it.
Diagnostics and interface refinements
Cache 3.6.0 adds administrative diagnostics for WebP conversion and reports process failures more reliably on PHP 8.2, including cases where no stderr output is available. Resolved converter paths are used consistently, and test environments preserve their PATH. Current quiqqer console names are introduced while legacy aliases remain available.
Contact 2.6.2 stabilizes ContactHub popup loading, sizing, and transitions. The window dimensions and label-left layout are aligned with brick popups, especially around 1000-pixel windows. Translator 2.6.3 batches INI writes during locale creation and caches translator-language schema lookups, reducing repeated work in language maintenance.
What this means for projects
The most visible opportunity is a cleaner cross-device document flow: uploads, signatures, contract templates, signing, and returns now connect more directly. The most important operational work sits underneath that experience. Scheduled jobs have stronger process boundaries, system-update coordination is clearer, and failures in cron, image conversion, QR rendering, and invoice output provide more usable evidence.
SEPA 3.4.3 limits setup migration to legacy bank accounts that actually exist, while ERP 4.3.2 accepts legacy empty optional values. These are deliberately narrow compatibility changes, but they are relevant to older data sets and should be included in migration checks.
Operational notes
- Test QR-based mobile uploads with the providers and device combinations used by the project.
- Run one complete contract cycle: template, editing, PDF, email, customer signature, and manual return.
- Confirm that scheduled jobs pause during a system update and that structured diagnostics reach the expected logs.
- Verify invoice address input, UUID-based PDF retrieval, QR rendering, and linked-invoice payment updates.
- Review WebP converter diagnostics and resolved binary paths on PHP 8.2 hosts.
- Check legacy bank-account and optional ERP values before and after setup migrations.
Looking ahead
QUIQQER 2.36 is not defined by one isolated feature. Its direction is the connection between user-facing document work and dependable platform operation: moving files between devices, preparing and signing contracts, processing invoices, and keeping scheduled tasks observable. Projects should stage the update around those end-to-end workflows rather than validating packages individually.