Recently Updated Topics

Thank you so much, you saved my day.

Yep, I confirm this still works today. However, the website in question is still using an earlier version of ProCache. 😄

I completely agree — keeping CSS variables semantically meaningful and scoped at the right level makes a big difference for long-term maintainability. Using names like --muted-color or --masthead-active-color outside their intended context can lead to confusion down the line, especially as the project grows. Your idea of compiling a starting list of variables with clear usage definitions is an excellent step. It’ll help ensure we separate “color intent” (like --text-muted or --background-accent) from “specific context” (like --masthead-bg). Once that foundation is consistent at the root level, we can easily extend or override in components without breaking semantic meaning. Count me in if you start that list — a collaborative approach could really make the design system more scalable and self-documenting.

@prestoav, thanks for the compliments 🙂 I forked AIOM primarily to fix issues I was facing, and then it somehow developed into the version with the caching options. I don't use minification of CSS/JS. I think it's enough to use simple preg_replace to remove blanks. It's painful to follow and track issues for all libraries now included in the module (voku html_min, simple_html_dom, symphony css selector, lessmin, cssmin, jsmin, ...). Not worth it for those few percentages. But hey, the module works, even on PHP 8.5. Did you try/test caching options? @David Karich, I didn't change the class name as I wanted to preserve its name and your contribution/authorship of the module. Thanks for the module! I'll PM you.

This is great! The filter feature alone is so good! Will save a lot of time. Thank you very much for this fantastic module!

[Update] More flexible access mails (v 1.0.11) Just pushed a small update to the module — a few quality-of-life improvements for access mails. What’s new Custom intro text for access mails – There’s a new field called Access Mail Intro Text (optional) access_mail_addon_txt added to your product templates. Whatever you put in there gets prepended to the access mail’s lead text — great for short intros, personal notes, or product-specific instructions. Hookable mail variables – PLMailService adds the hookable method ___alterAccessMailVars($vars, $mod, $user, $links) You can now easily tweak mail content in your ready.php, for example "first purchase vs. repeat purchase": wire()->addHookAfter('PLMailService::alterAccessMailVars', function(\ProcessWire\HookEvent $event) { $vars = (array) $event->arguments(0); $user = $event->arguments(2); // check if this is the user's first purchase $purchaseCount = ($user->hasField('spl_purchases') && $user->spl_purchases) ? $user->spl_purchases->count() : 0; $isFirstPurchase = ($purchaseCount <= 1); if ($isFirstPurchase) { $vars['preheader'] = 'Welcome! Your new access is ready.'; } else { $vars['preheader'] = 'New access added to your account.'; } // Hand back the modified variables $event->return = $vars; }); As always, feedback, ideas, and real-world use cases are more than welcome — especially if you’ve built custom hooks for your own onboarding or mail flows. Cheers, Mike

Hi, well, all this sounds quite normal, when starting an install process, if the htaccess file is named .htaccess the web site will try to work as if it were installed which is not the case in the contrary, wuen the install process is running/finished this file needs to be renamed as .htaccess with the starting period else it won't work as the server won't find it as a genuine .htaccess file il you have a look à the install.php file code, you'll see when the mutation takes place 🙂 have a nice day

v1.0.2 Bugfix: Fix deprecation warnings in PHP 8.2 (contributed by esszett in #2) Note that the module now extends the WireData class instead of Wire. This is recommended for modules now and shouldn't cause problems, and it gets rid of any warnings because of undeclared property access. If this is causing any unintended side effects, let me know.

With anything new that gets designed (a website, operating system, interface), there's always that initial cringe feeling because it's no longer familiar and comfortable, but after a couple weeks, that goes away. I'm developing a new site and using the new Konkat admin theme, which at first felt totally wrong, but now it feels just right (with 1-2 CSS tweaks, like to make repeaters jump out more). My brain is very picky about adjusting to new fonts... Inter in this case. I like the font a lot, but I just need to adjust to it, get used to the curves. Same thing with new versions of Windows when they change the default font. It's kind of like when Facebook went through a few major design changes at during the 5-10 mark and everyone would complain, then everyone got used to it. Anyway, great work. It's grown on me.

Wow, that was quick. Thanks. Will wait until it goes into main and then update through module interface.

In the “Core” tabs of the “Modules” page, look for the “IMagick Image Sizer” module and check if it’s installed. Is so, try uninstalling it and see if it solves your issue.

Only 4 years later I found the cause for this. It’s an Apache behaviour: Some Apache configurations are just fine with spaces in URL paths. Some force a 404 status code, no matter what you try to do in your PHP. Might have something to do with ModSecurity module, but I’m not sure. Better be safe: If you can avoid spaces or %20 in URLs, do it!

Many thanks @jploch that really helps to start and to find some more orientation how and with what in Page Grid. I have to to dive in...

I just switched to UiKit version 3.24.1 (thanks to RockFrontend to make this easy), and I can reproduce this with the latest version of the Less module... The same errors

Cross linking And also, this v useful module: https://github.com/BitPoet/SaveUserUnpublished

Thanks @jploch for your further explanation.

Thanks @cwsoft for your hints, I'll check them.

I also just stumbled upon the same issue – but with assets built inside of ddev. Adding the assets dir to `upload_dirs` didn't help...

Triggering Custom JS function Hi folks, I'm using Privacywire on a number of sites and it;s working well, thank you! With Microsoft Clarity now moving to requiring a consent signal on cookie acceptance I had hoped to run a signal function for this with the 'Trigger a custom JS function' setting in Privacywire's config (right at the bottom). However, having declared a test function (to just console.log something) higher up in the page script files, and adding the function name into the Custom JS function field in Privacywire, I can't get the function to run when cookies are accepted. I have tried both the function name (e.g. 'myFunction') and with brackets (e.g. 'myFunction()') but neither seems to work. Anyone tried this and got it to work? Thanks for any help!