Release: QUIQQER 2.18
QUIQQER 2.18 brings this week's CMS work into focus: 18 package updates were filtered down to the changes that matter most for live projects, editors, integrations, and everyday maintenance.
This overview is based on the available release information. It is useful for orientation, but not a replacement for a project-specific update decision; with sparse details alone, no reliable decision should be made.
Core 2.18.1
Core lands at 2.18.1 after a fast sequence of release work. The same window also included 2.18.0, 2.17.2, and 2.17.1, so this is more than a single isolated patch. The clearest gain is better day-to-day stability across the platform. For customers, editors, and development teams, this means fewer rough edges in the CMS core and a calmer foundation for live projects.
What this means in practice
- Several fixes focused on preventing edge-case errors and improving overall stability.
Gallery 2.2.0
Gallery lands at 2.2.0 after a fast sequence of release work. The same window also included 2.1.5 and 2.1.6, so this is more than a single isolated patch. The clearest gain is faster maintenance work and easier platform upkeep. In practice, Gallery gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Maintenance and migration-related tasks were streamlined for more efficient project upkeep.
Cache 3.2.1
Cache lands at 3.2.1 after a fast sequence of release work. The same window also included 3.2.0, so this is more than a single isolated patch. The update reads as a practical mix of more reliable account, permission, and sign-in handling, faster maintenance work and easier platform upkeep, and cleaner integration points for connected tools and automations. In practice, Cache gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Account access, permissions, and authentication handling were made more dependable.
- Maintenance and migration-related tasks were streamlined for more efficient project upkeep.
- Integration and automation touchpoints were cleaned up to behave more predictably.
quiqqer/bricks 2.25.0
Bricks lands at 2.25.0 after a fast sequence of release work. The same window also included 2.24.0, so this is more than a single isolated patch. The update reads as a practical mix of a smoother editing and content experience, more reliable account, permission, and sign-in handling, and cleaner integration points for connected tools and automations. For editors and content teams, Bricks should feel a little closer to the way daily publishing work actually happens.
What this means in practice
- Editing and content workflows were refined to make daily work feel smoother.
- Account access, permissions, and authentication handling were made more dependable.
- Integration and automation touchpoints were cleaned up to behave more predictably.
- Smaller interface improvements make the system easier to use in everyday project work.
Pace 2.0.4
Pace lands at 2.0.4 after a fast sequence of release work. The same window also included 2.0.3 and 2.0.2, so this is more than a single isolated patch. The clearest gain is better day-to-day stability across the platform. In practice, Pace gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Several fixes focused on preventing edge-case errors and improving overall stability.
Menu 3.7.1
Menu lands at 3.7.1 after a fast sequence of release work. The same window also included 3.7.0, so this is more than a single isolated patch. The update reads as a practical mix of a smoother editing and content experience and small but noticeable interface refinements. In practice, Menu gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Editing and content workflows were refined to make daily work feel smoother.
- Smaller interface improvements make the system easier to use in everyday project work.
Browser Extension 1.0.1
Browser Extension lands at 1.0.1 after a fast sequence of release work. The same window also included 1.0.0, so this is more than a single isolated patch. The clearest gain is a smoother editing and content experience. In practice, Browser Extension gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Editing and content workflows were refined to make daily work feel smoother.
Translator 2.3.0
Translator moves to 2.3.0 with a focused update for active QUIQQER projects. The clearest gain is faster maintenance work and easier platform upkeep. In practice, Translator gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Maintenance and migration-related tasks were streamlined for more efficient project upkeep.
Gdpr 2.8.1
Gdpr lands at 2.8.1 after a fast sequence of release work. The same window also included 2.8.0, so this is more than a single isolated patch. The clearest gain is a smoother editing and content experience. In practice, Gdpr gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Editing and content workflows were refined to make daily work feel smoother.
Install 1.5.1
Install lands at 1.5.1 after a fast sequence of release work. The same window also included 1.5.0, so this is more than a single isolated patch. The update reads as a practical mix of better day-to-day stability across the platform and cleaner integration points for connected tools and automations. In practice, Install gets another useful step toward smoother operation in maintained QUIQQER installations.
What this means in practice
- Several fixes focused on preventing edge-case errors and improving overall stability.
- Integration and automation touchpoints were cleaned up to behave more predictably.
Highlights at a glance
- Core: Several fixes focused on preventing edge-case errors and improving overall stability.
- Gallery: Maintenance and migration-related tasks were streamlined for more efficient project upkeep.
- Cache: Account access, permissions, and authentication handling were made more dependable.
- Bricks: Editing and content workflows were refined to make daily work feel smoother.
- Menu: Smaller interface improvements make the system easier to use in everyday project work.
- Install: Integration and automation touchpoints were cleaned up to behave more predictably.