d'Hinnisdaël

Can you create an issue on the repo? I'm currently busy with other projects, so i you require a quick fix, a PR is much appreciated. Otherwise I'll see when i get to it.

@Robin S That looks great, thanks! Will take that as a starting point and see where it takes me. Probably make this configurable behind a proper inputfield setting.

Good to know. Makes sense to keep it simple 🙂

Amazing! Thanks for open-sourcing 🙂 My main use case for this would be a nested page tree of categories. So a single template, but nested one or two levels deep, and both parents and children can be selected. Is this currently supported?

Rather late to the party, but congratulations to everybody involved on the website redesign! It's turned out really well. Such a clear and fun design for a CMS, I like it better with every minute. One thing that doesn't quite work yet (I think) are the admin screenshots on the homepage. These could be much more lively and colorful. As in: examples of working with images and other multimedia content in the backend. Sure, the tables and custom fields are important, the search, filter, etc. But it's all rather dry. And I kind of miss the skyscrapers, they lent themselves to integrating images easily. Or maybe it's time for trees or birds. As someone said before, keeping the skyscrapers comes with some free brand recognition. I agree that not of all the animations make actual sense or match the text beside them, but that's... okay? They're fun to look at, and the text is large and easy to read.

SQLite support would be especially great to signal that ProcessWire prioritizes ease of installation. It's a sane, pragmatic default that avoids the hassle of networked databases. I would assume 80% of new sites to just use that over MySQL if it was available. That said, the selector engine and quite a few third-party modules probably do rely a lot on the strongly typed columns of MariaDB, so I'm not sure how feasible this really is. Types in SQLite are very unintuitive, coming from the MySQL world.

@FireWire Sure! Wouldn't say no to a PR implementing this. I think there's a long-standing feature request in the core for disabling modules (as opposed to completely uninstalling them). That would be the ideal solution of course 🙂 But yeah, having it in the module is a close second, I'd say.

I would like to echo the request to get back proper checkboxes. ProcessWire provides distinct inputfields for checkboxes vs. toggles, so I'm confused to find that all of them now look like toggles. It's rather unintuitive and, as Bernhard mentioned, not amazing for module developers. Not sure what problem the global switch to toggles was solving, but I don't think there was a problem to begin with. Checkboxes are great, toggles are great, let's keep them separate 🙂

Separate color pickers for main color (light) and main color (dark) sound like a good solution to allow proper branding while still being accessible. Also, I would like to second the request for adding CSS variables for the border radius. There are some great additions in the new theme to make things more customizable, but to call it truly "customizable", it should offer the possibility of changing the border radius on buttons and inputs. The current look (very round buttons + completely square inputs) is a bit peculiar, but that's okay as long as we get a way of tuning things ourselves 🙂

@Jules Vau The hashes (or in your case, color codes) are stored as filedata. If you have access to the Pageimage object, this should do: $type = $image->filedata("image-placeholder-type"); $hash = $image->filedata("image-placeholder-data");

I've created a fork of the previous version a while ago that adds support for aspect ratios. Been working great for years, and haven't seen a need to update to the newer version. Here's the fork and the git diff in case you're still on v1. The newer v2 seems to be a complete rewrite, so...

Thanks @Noboru for the pointer! I've released version 0.3.1 with your suggested fix.

@FireWire The placeholders are cached and there's no logic for regenerating anything on module refresh, especially not globally, so that'd be a surprise for me at least. Are you sure it's related to this module? Feel free to share the exception stacktrace in case.

@FireWire Thanks for the heads-up! So you're saying it's currently working but will break in a future version of ProcessWire? Is there a specific release that triggers the issue on your end? The module should probably also reset the output formatting state to the value it was before setting it to false, just in case.

@wbmnfktr The ecosystem of available packages and services is definitely one of the major draws of Laravel. It almost parallels the Wordpress ecosystem, but ten times more professional. A lot of Laravel packages are very high quality, actively maintained, well tested, etc. That's probably a result of their somewhat "enterprisey" approach to structuring a project. Dependency injection, containers, service providers, those are all great approaches for professional projects, but they do require some commitment to learning these specific concepts. ProcessWire's approach to extension via hooking is almost the complete opposite of Laravel's container resolution approach. They're both flexible and ergonomic, but ProcessWire's a lot more approachable and easier to grok for newcomers I think. Being able to replace an internal handler in three lines without copy-pasting the whole class is really magical.