Leaderboard

I've been working nonstop in ProcessWire all week, but for client work. So this week there are just a few updates on the dev branch, mostly attending to minor issue reports from the last week or so. I have another week of client work left, so next week may be similar, though we may be able to bump the version number next week (on dev but maybe also master/main). Following that, I'm looking forward to working on and collaborating on some more substantial core development and upgrades. I hope that you have a great weekend!

Just sent out the October Newsletter and at the moment we're holding at 49 subscribers, one being myself ? and basically stagnating since last month (+1). Not sure if the newsletter is helpful for anybody, but I try my best to provide interesting content. Here are some numbers from the first two issues: If anybody has some ideas, feedback or other input feel free ? The first two issues were basically written by ChatGPT with some minor manual tweaks. The input came from a RockShell script that scans all my repos and then creates a log and lists all commits. ChatGPT did a quite good job in converting these into some nice sentences. This months version I decided to put more manual work into it. There have been less commits and so it was possible to give it a more personal touch. Have a great month! PS: It's not too late ? https://www.baumrock.com/rock-monthly/ ?

Perfect! Thank you.

Hi @Boost, you have to add the attribute "uk-lightbox" on a container and then add a link to open the lightbox: <!-- Video as link --> <div uk-lightbox> <a class="uk-position-cover uk-cover-container" href="<?= $page->block->video_upload->url ?>" data-caption="Caption for the Video"> <video src="<?= $page->block->video_upload->url ?>" loop muted playsinline uk-video="autoplay: inview"></video> </a> </div> <!-- Link over video --> <div uk-lightbox> <video src="<?= $page->block->video_upload->url ?>" loop muted playsinline uk-video="autoplay: inview"></video> <a class="uk-position-cover" href="<?= $page->block->video_upload->url ?>" aria-label="Video-Link" data-caption="Caption for the Video"></a> </div> Regards, Andreas

Content-wise... a great update, as I am not that often around here right now. The moment my latest projects are done, or at least in review, or... short before release I will drop you a message as RockPageBuilder sounds interesting. But right before that I have to try RockMigrations and RepeaterMatrix support - as those are spread around so many projects of mine. ? Besides that... there is one thing you could look into right now: Screenshot: Thunderbird 115.3.1 (Linux) Readability. It's quite hard to read due to those tight line-heights, and maybe the foreground/background contrast could be smoother. Yet, line-height is an real issue for me here. I wanted to read it, so I did. Otherwise I'd probably just ignored the mail (if it wasn't from you). Oh... and you better send a newsletter the moment your new website is ready!

That's so sad and bad at the same time. ? I will do so... I'll let you know on Saturday/Sunday (the day after tomorrow, and the day after that...!

Clients should always have their own accounts! If a features that a client wants or needs that need a 3rd party service, I present the information to the client, explain the pricing, and let them know that the account will be a service that they subscribe to. I like to emphasize that this means that they have ownership of the service and don't have someone in the middle (like me) charging a premium as a reseller. An example besides DeepL is a service called Smarty, which is an API to work with addresses. I am doing work with a client's CRM and explained that their address data isn't high quality enough to complete the work they need. I told them there's a free 30 day trial, and after that it's $54/mo. It sounds steep, but the client understood that it was an important necessity. It's a cost of doing business for them, just like DeepL may be. There are two sets of pricing for DeepL, the price to use their application, and the price to use their API. There are 2 separate pages for subscription plans, and on the "Plans and pricing" page it has both subscription types. It can be confusing due to how they have it presented. Here's where they have that hidden: I looked at the pricing plans and I don't see anything that would prevent a client from using the Free plan, unless 500,000 characters isn't enough. Then it would be €5.49 to sign up for the Pro plan, and then €20.00 for an additional 1,000,000 characters. So 1.5 million characters for €25.49. If it really came to that I would think that in most cases it would be possible to sign up for one month of Pro to translate the initial large amount of content, and then downgrade to the Free plan with 500,000 characters- unless they're publishing a ton of content per month! In Fluency you can switch between Free and Pro accounts without any issues or additional configurations needing to be made. Hope that helps, but if not let me know.

I saw that thread before I wrote this post, but I seemed to have missed the few references to using URL hooks. Thinking this further, I should consider using AppApi first before trying to roll my own solution.

There has been a lot of discussion here ? https://processwire.com/talk/topic/26792-headless-processwire-how-do-you-do-it/ I think this should work: /get-images(/{page})?(/{field})?/ ?

About URL hooks Not sure it has change but once happened to me that I couldn't do optional segments, example: /get-images/{page}/{field}/ Request wouldn't reach if I tried to get to: /get-images/{page}/ Then I think the concept of middleware is not present? So say you want to block unauthenticated calls, check CSRF, etc, you'd have to make that check on every route hook. Probably AppApi is still the way to go, feature wise? Project seems very alive! Edit: Just reading AppApi actually uses path hooks to bootstrap its endpoints.

This week we have ProcessWire 3.0.229 on both the dev and master/main branches. At this moment, both branches are equally up-to-date. Though I've not yet added the 3.0.229 tag just yet, as it is Friday after all. ? So I'll tag it this weekend or Monday. If you are already running the dev branch on version 3.0.228, then this version contains a few issue fixes and is worth the update. If you are running the previous master/main version 3.0.227 then this version has quite a few worthwhile fixes and I'd recommend upgrading, at least once we add the 3.0.229 tag. Here's a link to the current commit log. That's all for today, have a great weekend!

Same here: I usually put those things in a tab on the root page: Rendering the menu is easy: <div> <?= $pages->get(1)->footermenu->implode(" | ", function($p) { return "<a href='{$p->url}'>{$p->title}</a>"; }); ?> </div> Config Settings is a repeater field that populates a custom API variable with site settings: $uk->config->company and branding:

On some sites I actually have a "menus" tab on the homepage and in that tab there are two page reference fields: one for top menu and one for the footer menu. This way the site editors can easily adjust which pages appear where and none are shown anywhere by default.