Leaderboard

I'll share my youtube videos in this thread and if you have questions this is the place to ask. You can also subscribe to this thread to get notified when I post new videos ? Here is the link to my channel: baumrock.com/youtube --- Hey! I've just published my very first ProcessWire video. It's about RockFrontend: https://processwire.com/talk/topic/27417-rockfrontend-??-take-your-processwire-frontend-development-to-the-next-level/#comment-225666 Here is the video: What do you think? Do you understand what I'm trying to explain (despite the many ääähms und öööhms...)? ? What about the length?? I really didn't plan do get to 40mins... Did anybody even watch it till the end? ? Would it be easier to follow when having a small thumbnail in the bottom corner when working on the code? Or better without? Is it worth the effort of creating a video or would a readme be just as good? ? Any tips for better sound/lighting? I'm not really knowing what I do, so any ideas for improvements are very welcome ? Better with or without background music? So many questions... So much to learn... ? But it's fun and I'm a bit proud ?

In this post we cover the details of a new module (ProcessLanguageFieldExportImport) that enables export and import capabilities for multi-language fields in ProcessWire— https://processwire.com/blog/posts/language-field-export-import/

I hope that you all are having a great week! This week I've been working on some updates to the User Activity module and have released version 5 in the ProDevTools board. This version focuses on adding several new requested features, including the following: New options to also detect when you (yourself) are editing the same page in 2+ windows and when you have modified a page in a different window. These are the “collide-self” and “modify-self” options in module config. The module now keeps track of what fields have changed in the page editor and stores them with the activity so that they can be shown in the activity viewer or in page edit alerts. When a page has been modified that is also open to another user it now presents them with a dialog giving the option to reload the page or keep editing. A new “lock” option has been added that blocks a user from editing a page when it is already being edited by another. This is an alternative to just warning them with a pop-up, and it literally prevents them from being able to open the page in the page editor. This can be enabled in the module config and can also be optionally disabled for superuser. A new configuration setting has been added that lets you configure the refresh time in the page list (previously it was not editable). Added feature to limit the “you've been idle for awhile…” to the page editor only. When enabled, idle is still tracked for other admin processes, but idle alerts don't appear. Improvements to ProcessUserActivity (the included activity viewer module), including: 1) visible vs. hidden states are now more obvious. 2) Changes made in page editor are now included in the activity information. 3) The ajax drop-down navigation summary has been improved to include more information. Large portions of the module have been refactored into separate classes for better maintainability and other related improvements. This week there have also been a few commits to the core, but mostly just small fixes and phpdoc improvements, so not enough to write about here, but there likely will be next week. Thanks for reading and have a great weekend!

Haven’t thoroughly tested it or anything, but this hook seems to work: wire()->addHookBefore('ProcessPageEdit::execute', function(HookEvent $event) { /** @var Page $page */ $page = $event->object->getPage(); //ProcessPageEdit does roughly this to figure out if it’s dealing with a save request. if it isn’t, we don’t care if (!count($_POST) || (int)input()->post('id') !== $page->id) return; //if the page isn’t locked -> don’t care if (!$page->isLocked()) return; //if it’s locked and we’re a superuser, unlock if (user()->isSuperuser()) { $page->removeStatus(Page::statusLocked); wire()->message('leet hax, you just edited a locked page.'); //You don’t need to re-lock the page here, because the Locked checkbox is //sent with the page edit form, so saving will set it to the desired value } }); I would have hooked processSave directly, but it’s not hookable. Bonus tip: You can change the warning that says “This page is locked for edits” if you put this in the hook: if (user()->isSuperuser()) $event->object->noticeLocked .= ', but I’ll make an exception for you because you’re such a pleasure to be around'; Btw, you can always edit locked pages from the API as a superuser.

Big thanks also to @elabx, really great! I'll stop posting about new sponsors now but I still appreciate your contributions!! ?

Big thanks to @Pixrael for being my first github sponsor ? This is exciting and I really appreciate the appreciation ?