Publii 0.46.5 Released: Smarter Post Prefix Handling, Plugin Asset Improvements, and More

Publii continues its evolution, bringing sharper tools and smarter workflows to static site creation. Version 0.46.5 introduces expanded post prefix support, improved asset management for plugins, or significant refinements to metadata handling. This release also delivers a wide range of stability improvements and bug fixes that enhance both the user experience and development flexibility. Whether you are building complex sites or simple blogs, Publii now provides an even stronger foundation for your projects.

Improvements

Several improvements have been introduced to enhance site flexibility, simplify development workflows, and improve overall performance.

• Added post prefix page support to the Simple theme: The base Simple theme now includes a dedicated posts.hbs template. When a post prefix path (e.g., /blog/) is used, Publii will display a separate listing page using posts.hbs instead of falling back to the homepage index.hbs. This improves theme consistency and separation between homepage and post prefix listings.
• Improved post prefix handling: When a post prefix (e.g., /blog/) is used, Publii now automatically renders the prefix path using the posts.hbs template if available, or falls back to index.hbs. There is no longer a requirement to set a page as the homepage to display content at the prefix URL. This makes prefix handling more flexible and eliminates empty folders at post prefixes.
• Subfolder support for plugin assets: Publii now allows plugin developers to organize their assets within subdirectories. During rendering, files located in nested folders are correctly copied, enabling better asset organization and plugin structure.
• Removed trailing slashes in meta tags: The meta tag generation logic for canonical and Open Graph URLs has been updated to remove redundant trailing slashes, resulting in cleaner and more SEO-friendly metadata. (ref. GitHub Discussion)

Bug fixes

This update also brings a range of important fixes that improve stability, consistency, and reliability across the platform.

• Fixed saving of custom images for tags and authors: Resolved an issue where the custom image control for tags and authors did not save images correctly. Previously, saving changes could fail or canceling edits could unintentionally remove images. (ref. GitHub Issue #2150)
• Fixed Sharp library issues on Linux: Resolved problems related to the Sharp image processing library on Linux systems, which previously caused errors during site generation or image optimization. (ref. GitHub Issue #2128)
• Fixed Jimp library issues with enabled crop option: Resolved a problem where using the crop option in the theme images configuration caused errors or incorrect image processing due to issues with the Jimp library. (ref. GitHub Comment)
• Fixed cookie banner JavaScript errors without stored state: Resolved an issue where the cookie banner would throw JavaScript errors if no prior consent state was saved in localStorage. (ref. GitHub Comment)
• Fixed cache buster parameter timing issue during rendering: Resolved a major issue where the cache buster parameter (?v=X) for CSS and JS files was not updated correctly during the first site generation after changes. Previously, HTML files were generated before the updated CSS/JS assets were available, causing the {{ css }} and {{ js }} helpers to load outdated checksums. This could result in browsers serving cached versions of styles and scripts even after synchronization. (ref. GitHub Discussion)
• Fixed S3 synchronization issues when files are missing in the bucket: Resolved a problem where synchronization to S3 storage could fail if some expected files were missing from the target bucket. The sync process is now more robust and can handle incomplete bucket states without errors. (ref. GitHub Pull Request #2144)
• Fixed GitLab repository synchronization issues: Resolved problems with synchronizing sites to GitLab repositories. Previous issues caused errors during the sync process, especially when working with private repositories or specific GitLab configurations. (ref. GitHub Issue, GitHub Discussion)
• Fixed WordPress WXR import issues with featured images: Resolved a problem where importing pages from a WordPress WXR export file failed if a featured image was attached. The import process has been updated to correctly handle and assign featured images for pages during migration. (ref. GitHub Discussion)
• Fixed invalid canonical URL for post prefix page: Resolved an issue where the canonical tag for post prefix page (e.g., /blog/) incorrectly pointed to the root URL (/) instead of the correct prefix URL. 
• Blocked duplication of repeater elements after reaching maximum limit: Resolved an issue where users could duplicate existing repeater items even after reaching the configured maxCount limit. Duplication is now correctly blocked once the maximum number of entries is reached. Additionally, the duplicate button is visually disabled when the limit is exceeded. (ref. GitHub Issue #2085)
• Fixed disabled state handling for text inputs and textareas under tabbed settings: Resolved an issue where the disabled state for text inputs and textarea fields did not apply correctly when displayed inside tabbed plugin settings. 
• Various minor improvements: Introduced small refinements across the application, such as correcting typos in language files and improving overall text consistency.

Final Thoughts

With every update, Publii advances further in making static site management easier, faster, and more reliable. The improvements and fixes introduced in this release focus on flexibility, stability, and better user experience, building a stronger foundation for future developments.

We encourage you to join the Publii Community to share your ideas, feedback, and suggestions. Your input plays a vital role in shaping Publii into the most powerful and intuitive static CMS available.

Ready to explore the latest features? Download the newest version and take your site to the next level.

Download Publii