monollonom

I just pushed a tiny update to make adjustements to the CSS for the new Konkat theme. It’s just some spacing details and it now uses the --pw-border-color CSS var (and falls back to the original theme color if not set).

I just tried on a test setup to install the FieldtypeOptions module and add it as an image’s custom field but it is not displayed when editing an image, nor is it available to toggle on in the FieldtypeFile’s module settings: And it's actually normal behavior as this Fieldtype is basically blacklisted as a FieldtypeFile’s custom field. @tires your best bet is to use a Page field instead and have your options stored as pages somewhere:

How are you switching languages? Using javascript? I tried on a test setup and I can indeed reproduce your issue by changing the URL in the browser the way you described but maybe you should instead rely on something like $page->localUrl to create your language switcher? You can also raise your issue on Github, ideally by mentioning from which PW version you updated.

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.

There are quite a few topics with this issue but maybe this specific answer from @Robin S could help? Also, since it seems to be an issue with AJAX, are you seeing any difference if you toggle on (or off) this option?

Small update following a small issue I had: when saving a template the module now makes sure "sortfield_reverse" is unset, in case the user was previously sorting using a reversed sort direction

(I forgot to update the download link on the PW modules website, it should be good now!)

I just published an update that might be of interest to some: the ability to transpile any MJML code without it being part of a template. From the release note: This new release extracts the transpiling of MJML to HTML into its own public method allowing you to call it for any arbitrary piece of MJML code, instead of having to have the code in a template file: $mjml = "<mjml></mjml>"; /** @var PageMjmlToHtml $pmh */ $pmh = $modules->get("PageMjmlToHtml"); $result = $pmh->transpile($mjml); if($result->code === 200 && empty($result->errors)) { echo $result->html; } By default the options’ values are the ones set in the module’s settings. This new method is also hookable, which means you can for example set different options depending on the template: $wire->addHookBefore("PageMjmlToHtml::transpile", function(HookEvent $event) { $mjml = $event->arguments(0); /** @var Page $page */ $page = $event->arguments(1); $options = $event->arguments(2); if(!$page->id || $page->template != "specific-template") return; $options["relativeLinksParams"] = "utm_campaign=new-campaign-title"; $event->arguments(2, $options); });

Hi @Laksone, Sorry but somehow I forgot to have a look at it. I managed to update the QR code generation to accomodate for bigger content but there is still a limit to this so I added a note in the README and in the fieldtype’s "Details" tab. I also took on the opportunity to do some code cleanup and add the option to set the (interesting) error correction level. Please update the module and let me know if you’re facing any issues.

The blur animation is very laggy for me and impacts the slideshow as well: Screen Recording 2025-08-17 at 20.16.11.mov Most likely it’s because of the blur(0.6px) coupled with the svg filter. I understand why you went for this visually but I think it's unfortunately too heavy...

Quick css fix for the misaligned "Project" button: Add <button> to your css selector: .pw-module-primary-actions a, .pw-module-primary-actions button { } Another note: on the homepage you should add the width and height attributes on the slideshow’s images (maybe even a background-color?) so there’s no layout shift when loading the page: Also I think you could echo the logo’s svgs using file_get_contents to avoid the empty spot like in my screenshot. Lastly I would also advice to respect "prefers-reduced-motion: reduce" for the lottie animations (and have a fallback svg image in case there’s no javascript). It’s quite easy to do by setting the autoplay option using "window.matchMedia('(prefers-reduced-motion: reduce)').matches".

This is the css you want to counter when hovering .uk-card > .uk-card-body > a 🧐

Congrats on the launch @ryan and @jploch 🤝 @diogo for the design. I think it’s a great update! Two small things I noticed regarding the cards: This has to do with the width of .uk-card-body being 100% combined with a padding. I saw you added a max-width but it would be best to use "box-sizing: border-box" instead, so the padding is included within the 100% width. Also re:cards, I noticed there was some js to allow to click anywhere on a card to open its link. A nice css trick I learned is to use ::before on the <a> tag to "cover" its parent. In your case you could use this css: .uk-card .uk-card-body a::before { content: ""; position: absolute; inset: 0; } This way the <a> covers the card and makes the whole card clickable: (btw some external link are not working, e.g. Processwire Weekly, there seems to be a slash wrongly added at the beginning of the href)

This issue has been raised by @adrian as well in the new admin theme thread and aknowledged by @ryan:

Thanks for sharing @ryan. Do the CSS selectors need to be this specific? Or is it because we have to overwrite styles written with less that tend to produce these (thanks to the nested selectors)? For example: .PageListActions a { } /* instead of */ .PageList .PageListItem .PageListActions > li > a { } /* or */ .InputfieldRepeaterItem > .InputfieldHeader { } /* instead of */ .pw .Inputfields .InputfieldRepeater .InputfieldContent .InputfieldRepeaterItem > .InputfieldHeader { }