Leaderboard

I'm still using class constant everywhere with great success. Another benefit is that if you remove a field during development your IDE will show you all references that have to be removed. Here I have removed the field "field_eventname" because I don't need it any more. So I removed the constant definition on top of the file and immediately I get proper warnings from the IDE:

Hello @Boost, have you seen this page: https://processwire.com/about/wordpress-vs-processwire/ ? 😉 Regards, Andreas

Hi @franciccio-ITALIANO, it seems, that you always have the same ID "block01" for all your modals, so only one modal will always be opened? You should make the ID dynamic. <?php foreach($page->box_ripetitore as $b => $boxrip):?> <!-- INIZIO BLOCCO RIPETUTO --> <div class="<?php echo $boxrip->box_ripetitore_colore?>"> <div class="uk-tile" id="op31h2"> <a href="#block<?=$b?>" uk-toggle> <h2 style="font-family: Anton; font-size: 3em; color: white;"><?php echo $boxrip->box_ripetitore_tit?></h2> </a> <div style="font-family: Oswald; color: gold; font-size: 1.5rem;"><?php echo $boxrip->box_ripetitore_sottotitolo?></div> <!-- SEZIONI FOGLIA --> <div id="block<?=$b?>" class="uk-modal-container" uk-modal> Regards, Andreas

I've just released a new version with a ton of updates 😎 https://github.com/baumrock/RockMigrations/releases/tag/v3.25.0 I started to adopt a new workflow, because I often heard that "it's hard to keep track". That's why from now on I'll push updates to the dev branch and then merge them to main from time to time. Highlights: I improved the deployment log a lot, made everything a lot cleaner and tried to catch all the warnings that where just written to the log before. Old: New: We also have a new tweak to show page ids in the page tree (1) and a helper method to add labels in the page list (2) and also the template name (not in the screenshot) Check out https://github.com/baumrock/RockMigrations/releases/tag/v3.25.0 for all updates!

Yesterday I received a mail from Vercel about the successor of Webpack, Turbopack. It seem the adventure will continue.. the only bad news (at least for me) is that the tool is coded in Rust, I can't swallow this language... but in term of features it look really promising.

@kongondo on multilang installs, when the title field is set to TextLanguage, MM pages that are creted for each image under Admin->Media Manager->Media Manager: image are published in the default language only. Other languages are disabled. This poses a problem with $pages->find operations, e.g. $this->wire->pages->findIDs("template=media-manager-image, image_gallery=1, products.id={$this->id}"); this return 0 pages for non-default languages. I had to change the selector to $this->wire->pages->findIDs("template=media-manager-image, image_gallery=1, products.id={$this->id}, include=all, status!=" . Page::statusUnpublished . ', status<' . Page::statusTrash); in order to get results. It might be good to have these pages published in all languages by default.

Don't mind, come back as many times with as many doubts as you have. Yes there are amazing modules put out by the community!

If by "featured" you mean "linked to within a CKEditor field" then it's pretty easy. You just upload the file to the first page it will be used on (Page A), and on any of the other pages you use the CKE link dialog to select Page A and then select the file.

Hey, it seems to me that there is a wrong thinking or understanding to the whole subject that leads to the confusion. (?) If your comparison are between the compressed image from a third party tool, e.g. photoshop or others, and ONLY the webP output from GD or imagick, then this is comparing apples with bananas. If that's the fact, please read on. If that's not true, please excuse my post and my misunderstanding and forget / don't read the rest of the post. ? EDIT: maybe of additional interest:

Check /wire/core/ProcessWire.php. Version number is split into major, minor, and revision properties.