Releases: municipio-se/municipio-deployment
Municipio 4.2.4 Release Notes
We are excited to announce the release of Municipio 4.2.4. This update has been rigorously tested for full compatibility with PHP 8.3, which we now recommend as the preferred PHP version for Municipio.
By upgrading to PHP 8.3 from the previously recommended PHP 8.2, you can experience up to a 40% faster page load time when the object cache is primed.
General
- The devcontainer now runs PHP 8.3, reflecting modern hosting environments and new default requirements for Municipio (we are still backwards compatible with PHP 8.2).
Municipio Theme (5.11.3)
- Related posts functionality is now simplified. It only searches within the current post type and includes a
rand
in the query to generate more diverse results. - View transitions are now implemented by default. We intend to further explore this feature in the coming months to enhance the user experience.
- New header type: Flexible. This header aims to replace the old "Business" and "Casual" headers by providing a drag-and-drop interface to build your own header layout.
- Bug fix: Resolved an issue where post content was displayed on draft or private pages, even if the header response was sent as a 404.
- Resolved: An issue where Kirki CSS rendering would stop functioning after applying new settings.
4.2.3
Municipio Theme (5.8.11):
- Changes the filter to apply a default value of the icon type, to be able to explicitly set a overriding value locally where components are used.
- Enqueues instantpage.js later on, so that the document has been fully loaded before init. This will enshure that instant page can work properly.
- A fix has been made, to enable users to disable "posts" in the Theme Options.
- Get related posts only runs on place templates. This may be changed in the future, when more types support this feature.
Component library(4.15.1):
- Adds support of default fill mode in the icon component.
Modaularity (6.19.0):
- Resolves an issue with like functionality for visit sites (main menu counter)
4.2.2
We’re excited to announce the release of Municipio 4.2.1, which focuses on addressing key bugs and improving performance. Below are the highlights of this update:
Municipio Theme (5.8.6):
- Icon Translation Optimization: Improved the efficiency of icon translation handling.
- Navigation Class Enhancement: Optimized the navigation class to retrieve pre-processed objects directly from the runtime cache, enhancing performance.
- Upgrade: Introduced a script that clears all oEmbed caches due to updates in the HTML output for icons.
- Customizer Fix: Resolved an issue where changes made in the Customizer were not reflected on the frontend.
- Body Class Correction: Fixed a bug where the body class was not correctly applied across all templates.
- Schema Object Handler: Addressed a warning issue in the schema object handler.
Open Street Map (2.3.7):
- Corrected an issue where pins were not displaying correctly in the map component.
Styleguide (0.11.1088):
- Hero Component: The Hero component now respects the "Reduce Motion" accessibility preference.
- Grid Objects Fix: Resolved an issue where grid objects were not respecting gutter sizes on smaller devices.
Modularity Like posts (2.6.0):
- The "heart" symbol is now compatible with the default "filled" icons in municipio.
Deployment:
- The deployment script now includes functionality to send a ping to New Relic and Sentry after each deployment.
Other:
- The sentry plugin has now been removed from the deploy due to bad performance.
4.2.1
- Component Library (4.14.6): resolve issues where some data attributes where NaN or incorrectly handled.
4.2.0
This update is primarily focused on simplifying the implementation of schema data configuration an presentation.
- Municipio Theme (5.8.0): Add feature for assigning schema type for post types as well as populating posts with values matching the selected schema type. Remove Content Type feature in favor of the new functionality available in schema types.
- Modularity Open Street Map (2.3.6): Adapt to use Schema Type from Municipio instead of Content Type.
- Component Library (4.14.5): Fix issue with "0" as a string not being allowed to pass as value to attributeList property on components.
Release 4.1.2
A new maintenance release addresses issues caused by optimization actions in the previous release. This update includes the following corrections and improvements.
Municipio Theme (5.7.1):
- Customizer: Fixed an issue where dynamic theme settings were not properly loading in the customizer. This ensures that imported settings from the design library are correctly applied in the customizer context.
- Favicons: Removes the custom favicon implementation, and migrates it to be done natively in WordPress using the "site identity" section in the customizer.
- Icons: A optimization on the icon rendering has been made. This reduces the size of the material icons bundle up to 85%. This change also brings settings for choosing font style and weight.
- General: Minor adjustments to correct an issue where the width settings were not being applied.
4.1.0
Introducing Version 4.1.0! This update is designed to optimize performance for frontend tasks, offering significant improvements. It includes several fixes aimed at boosting site performance in both cached and uncached environments. Expect up to a 60% reduction in Time to First Byte (TTFB) on large sites, even when object caching is not enabled.
- Municipio (5.5.2): Upgraded to statically render Applicators (generated css, component data and modifiers) reducing rendering time and unnecessary workloads. This change also enhances security by eliminating the use of eval for calculating conditionals.
- Modularity (6.19.0): Multiple queries used to detect a page’s available modules have been optimized to run more efficiently by reducing the amount of data searched in.
- Open Street Map (2.2.2)*: The plugin has been completely rewritten to offload the initial request size using asynchronous data fetching.
- Like posts (2.5.0)*: The functionality for determining where the liked posts list appears has been updated to execute only during the save_post action. This change reduces runtime calculations on the frontend, improving overall performance.
- Items marked with (*) are breaking changes. These components may have to be configured, in order to work properly.