szabesz

I would not say a "rollback" is desirable, it is just that the new theme needs some more work because it is rough around the edges. Eg. when selecting pages in a Lister, the "label" showing the number of selections makes the list jump, which is bad UX but can be fixed with a display:"inline-block". Also, used to be shaded inputfield groups can have their background color back, etc... So while I agree that it is sort of half-baked, it can surely be made better.

Awesome! Just what I will need in the near future. Thanks @Mikel for sharing!

News: "...npm got rocked by a record-breaking exploit..." https://youtu.be/QVqIx-Y8s-s And self-driving cars, AI agents, refrigerators, cat feeders, and who knows what else are and will be based on code written by who knows who...

Great new features, thanks a lot!

+1 Is it possible to bring it back?

Hello, This is the closest but also not being maintained: https://processwire.com/talk/topic/22665-module-imagereference-pick-images-from-various-sources/ Not a media manager, but it can fulfill certain requirements: https://processwire.com/modules/process-media-lister/ and "combined" with this https://processwire.com/talk/topic/29985-file-mover/ they can fulfill even more requirements. Not being overly complex, Robin will probably be able to update these whenever needed. That's an advantage....

I think both developers and clients should be the target audience and I cannot see why it would not be possible to target both. Anyway, in my opinion, the new design "targets typographers". To me, it looks like solution to a school assignment for students studying typography. BTW, I found an error in the following href:

I second that. While I completely appreciate all the work that has been put into the redesign, but I think the "brand spirit" is off. I feel like I've arrived at a typographer's portfolio site. To me, the new design conveys no message other than bold typography. All the messages are explicitly spelled out in writing, which is fine, but aside from that, we have plain, rounded boxes, practically no colors, no images and that is all there is to it.

Hi, I do not know it this has been reported or not, but there is at lease one "This video is private": https://processwire.com/docs/multi-language-support/multi-language-fields/ see:

Thanks @Robin S I love tools like this as often there is no need to do the same task again in the future.

Thanks @gmclelland! Pretty useful service for getting high-level overviews. I tried this prompt: Explain how ProcessWire handles locales. And got this: # How ProcessWire Handles Locales ProcessWire provides comprehensive locale support through its **LanguageSupport module system**, which manages internationalization (i18n) and localization functionality across the entire framework. ## Core Locale Management ProcessWire's locale handling is primarily managed through the **Languages class**, which extends WireArray and provides centralized locale management functionality [1](#0-0) . This class contains the main `setLocale()` and `getLocale()` methods that handle locale settings throughout the system [2](#0-1) . The system uses PHP's native `setlocale()` function as its foundation, with extensive wrapper functionality to support multi-language environments [3](#0-2) . The locale settings affect various categories including `LC_ALL` and `LC_NUMERIC` for proper formatting of numbers, dates, and other locale-specific content. ## Individual Language Objects Each language in ProcessWire is represented by a **Language object** that includes its own locale management methods [4](#0-3) . These objects provide wrapper methods that allow setting locales on a per-language basis, enabling fine-grained control over locale settings for different languages in multilingual sites. ## Translation Functions ProcessWire implements a GetText-like translation system with three core functions that work with the locale system [5](#0-4) : - `__()` for basic string translation - `_x()` for contextual translation with additional context - `_n()` for plural form handling These functions are available both globally and as methods in Wire-derived classes [6](#0-5) . ## System Integration The locale system is initialized during system startup through the **LanguageSupport module** [7](#0-6) . This ensures that proper locale settings are established early in the request lifecycle. Locale settings also integrate with other core components: - **Number formatting** through WireNumberTools, which uses locale information for proper numeric display [8](#0-7) - **Page name localization** for multilingual URLs through LanguageSupportPageNames [9](#0-8) - **Field value management** for multilingual content through specialized field types [10](#0-9) ## Locale Validation and Maintenance ProcessWire includes system checks to ensure locale settings are properly configured and functional [11](#0-10) . These checks help identify and resolve locale-related issues during system updates and maintenance. ## Notes ProcessWire's locale handling system is designed to be flexible and comprehensive, supporting both simple single-language sites and complex multilingual installations. The system builds on PHP's native locale functionality while providing ProcessWire-specific enhancements for content management scenarios. The modular architecture allows locale functionality to be enabled or disabled as needed, making it suitable for sites that may not require internationalization features.

I installed it on MAMP Pro and also on its own cPanel account, as it does not support shared hosting. I also tested the Docker option back then and it worked as well, but I am not fluent with Docker so I abandoned that project for a while. But I might get back to it as the idea was to run it it on a QNAP NAS. And it worked but I did not find the time to finish the task to setup automatic backup for it.

First of all, thank you for all your heroic efforts! And I am not exaggerating. Please consider https://www.bookstackapp.com/ Free, open source, and contributors do not have to set up anything. I've used it, it's great, stable, and its developer is actively working on it, improving it regularly.

Back or not, having only one lone icon/image among non-skeuomorph icons/images is, at the very least, questionable.

https://www.youtube.com/watch?v=EoEeRWHJ8xs A checkbox is a checkbox and should not be confused with a toggle, I think. A toggle is not a skin for a checkbox. https://infyom.com/blog/user-interface-design-tips-checkbox-vs-toggle-switch/ https://uxdesign.cc/the-good-the-bad-and-the-toggle-2abc0fbbd099 Quotes: A toggle switch requires two steps: selection and execution, whereas a checkbox requires only the selection of an option, and the execution/saving action is normally required later or at a different area. Usage recommendations Do not use toggles in forms. Use checkboxes or radio buttons instead. Do not use toggles in filters or multiple selections of elements. Inhale. Use toggles for settings and changes that have an immediate effect on the UI (same applies for the segmented control). Avoid mixing toggle button groups and segmented controls. Exhale. Avoid using switches with multiple options.