Leaderboard

@zilli If you are using the new AdminThemeUikit design, which bugs or aspects not fully addressed are you personally running into? Much of what I’ve seen so far have been ideas and suggestions, many of which have been addressed and will continue to be (though I will leave to the designers to decide which). When it comes to bugs, of course there will be bugs with anything as new and significant as this. But the bugs I’ve seen are relatively small and simple things, or with modules outside the core, all of which is very much expected at this stage. The amount of issues is extremely small relative to the scale here, so I've been impressed at how few issues there actually are so far. I disagree. I think Google says it well, so I’ll quote: "Design by committee" [or community] refers to a project where a large group of people, often with varying expertise and perspectives, are involved in the design process, leading to a lack of a clear, unified vision and potentially a diluted or mediocre final product. It's a negative term often used to describe a situation where too many opinions are being considered, hindering progress and resulting in a compromise that doesn't satisfy anyone. Quality comes from finding a professional you trust and letting them apply their expertise towards a solution. Diogo and Jan have been using PW longer than most here, they are at the top of their game and I have a huge amount of trust in their work. BETA TESTING is exactly what we are doing right now. That’s what the dev branch is for. If there are issues personally affecting you, I’d encourage you to open an issue report (none have been reported yet on GitHub). Earlier you implied it was released too early, but "keeping under wraps" implies releasing too late. So I'm confused. But to be clear, nothing is under wraps, it is all available for testing and feedback on the dev branch. That is the stage we we are in. I don’t understand this statement, especially in the context of this conversation. Tight control is not a term I’ve had attributed to me before, in any area. If I think about where I would value control being tight, it would be with matters of security or avoiding scope creep. Wonder no more. This is why we are here typing to each other and why the new admin design exists. It's the reason why we’ve come up with a fresh look for the admin, and shortly will be launching the new website as well. These are some of the most important changes for growth in the history of PW. The old admin and website are about a decade old, and were designed by me – I haven’t been a professional designer in about 20 years, and I think that was increasingly becoming apparent in PW’s appearance both in the admin and on the website. Long time users may be used to it, and some may prefer to keep using the Original design for AdminThemeUikit, which is fine… it will always be there. But we’re focused in getting new users. @jploch and @diogo do this for a living, are at the top of their craft, know what they are doing, and I’m extremely happy with and thankful for their work. My opinion is that what they’ve come up with is exactly what was needed. I don't expect everyone to agree, as we are a diverse crowed here and that's a good thing. @nbcommunication As I understand it, it is frowned upon to create a “Christmas tree” with design elements like this, especially where user input is involved. @cst989 Design is always subjective and it’s perfectly fine to have opinions and preferences. I think the new design speaks very much to what ProcessWire is conceptually and presents it is a way that is more modern, clear and customizable. Even if it is old, I do still like the Original design too (and it’ll always be there) but I think it had more to do with what I found attractive at the time, over what was right for the application. Whatever one feels about what's pretty or attractive is not the point. This is for an application that people use all day, not a cake to decorate. I think the new design reflects PW’s concept and framework better. And it has real systems design thinking behind it rather than just being pretty (though I think it's pretty too). Diogo and Jan know very well how to appeal to our target audience, as well as how to expand and diversify our audience. They are pros and this is what they know how to do far better than me. Having used the new admin for quite some time now, I feel I'm benefitting from it a lot. It's far more then just a pretty face and really grows on you the more you use it.

So annoying when the web host updates the PHP version and you start getting a strange error in the logs. Google search revealed a [solved] answer in the PW forums that YOU posted 3yrs ago 🤦‍♀️ In case anyone else is getting the same error: class='TypeError', code='0', message='count(): Argument #1 ($value) must be of type Countable|array, string given', location='/wire/core/PagesLoader.php', line='972' Here's the solution: The line number may vary according to your PW version.

In my opinion this would be bad for usability. 😉

Hello, The collaborative efforts of @diogo and @jploch are truly commendable, and the new admin theme brings a fresh look to the ProcessWire interface. That said, it feels like some aspects weren’t fully addressed. The theme includes certain design choices that have sparked debate and a few bugs that slipped through. In my view, this isn’t a reflection of any lack of competence from @ryan, @diogo, or @jploch—far from it. Rather, it highlights how the project was managed, which, to me, mirrors how ProcessWire itself has historically been managed under Ryan’s leadership. A project like a new admin theme could really benefit from being more community-driven. A simple round of beta testing with some of the most active and experienced members of this forum could have prevented many of these issues before release. Keeping it under wraps usually doesn’t work as well as we hope, especially considering how diverse the use cases for ProcessWire are. And this does reflect on ProcessWire itself. I sometimes wonder whether Ryan truly wants PW to grow bigger, gain more visibility, and capture a larger market share. If he does, some of the actions we see don’t seem fully aligned with that goal. As for why Ryan continues to keep such tight control, I honestly don’t know—whether it’s a matter of personality, or perhaps he hasn’t yet found people he fully trusts on the technical side. That being said, none of this discussion would even be possible without Ryan’s incredible work on ProcessWire. Regardless of what the future holds, we’ll always be grateful for that. I’m simply sharing my thoughts with the hope of contributing to its improvement. That’s all.

Hello everyone, I'm excited to announce that Version 1.0 of ProcessTranslatePage is now available on GitHub: https://github.com/robertweiss/ProcessTranslatePage Please note that there are some breaking changes in this update. I recommend uninstalling and then reinstalling the module to ensure everything works smoothly. You can use the same DeepL API key that you use with Fluency. After installation, you will (hopefully) see two new fields for the language template. However, only the ⁠'translate_locale' field is required for the module to function properly. Thanks for your patience, I hope you find this update useful!

I’ve been following this ping pong match for a few days. 😁. Gotta say, I loved it and @nbcommunication, you are awesome. Great developer. Thank you for your contributions to the PW community.

Hi @Stefanowitsch, That's great, delighted to hear that! This is been a really useful exercise, I've pushed three bug fixes for the module so I'm happy 🙂 I'll update the README with a note that the module isn't compatible with DelayedImageVariations, and if I ever get around to it will try and figure out what the compatibility issue is. It isn't something I've used before. Cheers, Chris

I can't help but agree!

@bernhardThanks for your suggestions. Will try the get Fresh call for sure. Fun fact is that my $cachedPage was named this way only in this example code. I used $dbPage and finally $oldPage for my own code. I indeed revert back up to four fields (page select, select option, textfield and datetime) on two different templates split in two separate saveReady hooks via saveReady(template=xy). In addition I overwrite page name and page title to some unique values using parts of some input fields and take care of setting a draft value for the page title when a page is newly created but not yet saved (my page title is an auto field not directly set by the user). So early returns are not always possible in this special case. I usally tend to use short circuit returns instead of nested ifs, whenever possible, which however isn‘t possible in my scenario, as the page name and the final title needs to be set last once all fields which may be part of it where sanitized and maybe reverted back to it‘s previous state.

What a twist!!!

I'm clearly in a minority but I personally feel like the redesign is not very attractive.... To me, completely flat single colour panels with single relatively high contrast borders does not look clean and I don't enjoy the use of a mid grey as a base colour for light mode at all. The new font looks bold and blocky to me and again too intense in its contrast. I'm sorry to say this because I can tell a lot of work has gone into it, but I personally hope the Uikit theme doesn't go anywhere, if I put them side by side the Uikit one looks like the more modern and finished one to me. Also to add to the bug reports I'm getting white text on a white input when filling out the db details on a fresh install of the new dev version (dark mode/Chrome/Windows) which made installation quite difficult

I manage to configure the HTMLPurifier. In site/ready.php, I put this: $wire->addHookAfter('MarkupHTMLPurifier::initConfig', function (HookEvent $event) { $config = $event->arguments(0); $def = $event->arguments(1); $def->addElement('details', 'Flow', 'Flow', 'Common'); $def->addElement('summary', 'Flow', 'Flow', 'Common'); }); I got that addElement method from there: https://github.com/processwire/processwire-requests/issues/226 Don’t ask me about the three other arguments (Flow, Flow, Common). 😅 That + a config.json file for this specific field where you specify the accordion plugin and the accordion button in the toolbar, as you mentioned above, and it works fine.