cst989

Dang you quoted me before I had chance to made my post nicer 😝

Well, I was trying to be polite, but since you decided to call me out like this... by attractive I meant a nice UX, easy to use, clear to see how and where things are interactable, clean, well spaced out, nice inputs that look interactive and are reactive etc etc etc. I have been in this industry for 20+ years, so you don't have to tell me what's important in a UI. A system people have to use every day has to be enjoyable to use, but it should inspire a feeling of using a professional, high end product. Again to reiterate I was not trying to be dismissive of the hard work here and I will continue to use the product and pay for the excellent pro features etc, maybe a few of us devs will get together and just maintain the UIKit theme if it will not be used for new features in the future by default. But I didn't really appreciate the suggestion that I missed the point, while admittedly that was on me and my own poor choice of words.

Config migrations seems very cool, is it meant to be an approach you can use on its own or alongside regular migrations? I guess you can't delete a field from a template just by taking its entry out of the array so you still have to write a migration to do that?

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

Ran into a little bit of an odd issue with this, but not sure if this module is to blame, or PW. I've found when saving blank values in php 8.3 - which includes the initial save that happens when making a new page - you hit this error with a core PW file Fatal Error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in wire/core/FieldtypeMulti.php:257 This happens even though the field I've made is a single "select" type This is a pretty common php 8 issue I believe, which could presumably be changed by fixing if(!count($values)) { to if(empty($values)) { but I wouldn't say I was a php expert enough to be confident in the potential repercussions of this, nor whether this is something that should even be changed in PW since it only seems to get tripped up by this module.

One thing I've found is that most environments will show php warnings when using $config->debug = true but ddev will not. Does anyone worry/do anything about this?

I have a catalogue of DVDs in ProcessWire. Sometimes I know the exact date, sometimes I only know the month and year, or just the year. I'm migrating from a system that allowed me to put in the date like 00-00-1995, but PW's date fields will always default to 01-01-1995. Even if you use the date option that says "separate inputs for year, month and day" and only save year, it will still set the month and date to Jan 1st. Ideally I want it to still behave like a date field, maybe with a calendar, but at least limiting the format to correct dates, and being able to sort by it on the front end. I can think of workarounds, like having 3 separate fields and perhaps joining them together in a hidden field or in my template. But I wondered if anyone had a go-to approach that they've used for this in the past. Thanks in advance! 🙂

The first post of this thread points to this area for defining custom classes, albeit predating TinyMCE being in the core, but am I missing something, I can't find this anywhere... [deleted] Sorry, I realised there's settings against the module as well as settings against the field, this trips me up more often than I should admit...

Just checked and yeah, it's fixed in 3.0.239 ?

I solved this by creating a new field and saving it with a hook, essentially... if($page->template == "news-post") { $page->set('has_media', $page->image->count || $page->slideshow->count || !empty($page->video_embed)); } now I can just check if has_media=1 But I'm still curious why my old approach stopped working

We have just updated a ProcessWire site from 3.0.184 to 3.0.229 and the following selector has stopped working: template=news-post,image|slideshow|video_embed!='',sort=-created In other words, I'm trying to grab the latest articles for featuring on my homepage, as long as they have at least an image, slideshow or video - if not, they're not suitable for the location. Is there an obvious reason this should've stopped working in the latest version, and/or an alternative approach?

Hello, following various guides on here in years past, I've always had a css file in the admin by editing /site/templates/admin.php and adding: $config->styles->add("/site/assets/css/dist/admin.css"); Now suddenly I find that this call is aggressively cached with a v=3.0.227 on the end. Even if I add my own cache-busting variable to the end, it's ignored in favour of this. Does anyone know how to get it to clear? Or never be cached? In the end, 3 commits later, I had to rename the whole file.

Bump! Nobody know if this is possible? Am I explaining the question badly? Edit: revisiting this so much later, I had a brainwave, I can simply target the field with some custom CSS: .ProcessPageEdit-template-hotel .Inputfield_gallery .Inputfield_map { display: none; }

That's correct yeah and it did kick me out as expected. Clearing my cookies seems to have worked, thanks!

I changed the name of "Admin", which worked as expected, and I've done many times before. However, internal links, like Setup > Templates are not updating Is there something I could do - a cache I could clear perhaps (tried object cache, procache and browser cache) - to try and solve this? This happens locally on a ddev site and in staging which is an apache/cpanel site