Leaderboard

Hi all, The forums have just had a fairly major upgrade - everything seems brighter and cleaner though as always if you spot any areas we may have missed that don't look quite right (broken rather than different), please comment here.

They had added this as a new setting and, somewhat bizarrely, not set it to the most useful setting by default. I've changed it so the default is now what we were all used to so you shouldn't need to go and set that setting.

The Architekturforum Freiburg sees itself as a regional platform for information and exchange about architecture, urban planning, landscape architecture and building culture. On the website you can register for events, view presentations or become a member. The website uses UIkit as framework and Workbox for the PWA. architekturforum-freiburg.de Features: Dynamic primary color Structured data Dynamic primary color The events are grouped in programs and every program can have its own color. For this I used the awesome module Color. I defined a fixed color palette, so that no ugly colors could be selected and I worked for the first time with CSS variables. With CSS variables you are more flexible than with f.e. SCSS variables and can change the primary color for the whole website on the fly. This is used on the detail page of events with a different primary color. Structured data It was important for me to provide the correct structured data for the events. Since the pandemic they have been enhanced for online, offline and mixed events. Modules used: Repeater Matrix Form Builder Functional Fields Map Marker ProCache Upgrades TOTP two-factor authentication Tracy Debugger Color Sitemap Email Obfuscation (EMO) Regards, Andreas

We add support for ProcessGraphQL with the additional module GraphQLFieldtypeOembed.

Thanks, I found the setting to turn off topic stats - not sure why anyone thought that was a useful feature but it seemed to be a global setting that triggered under certain scenarios ? I won't be able to change things like scroll wheel without digging into the JS so that's not something I'll be able to solve unfortunately. Their code is a little impenetrable (to me at least) whenever I try to read it so I try and stick to simple template updates in this software. I'm a bit of a JS noob in that I'm happy with jQuery but I don't fully understand JS classes yet and am rusty with vanilla JS - though it's definitely time I learned. The RTE as far as I'm aware is a modded CKEditor. They did used to use their own a few years back but it was a big project on its own just to manage it, but yes there is room for improvement in some areas I agree.

Another new feature - you can also switch to a card view (less useful) and this "fluid view" which may be more useful to those of you who use the activity feed in that you can select forums to filter by on the main forum homepage and have all the topics appear in a list. I've not used it so I'm not sure how useful it really is, but it's an option.

Today I had this informational E-Mail in my inbox and simply want to share: ---------------------------------------- Hello from the staff at Let's Encrypt. On September 30, there will be a change in how older browsers and devices trust Let's Encrypt certificates, resulting in a minor decrease in compatibility. If you run a typical website, you won't notice a difference. Devices and browsers running up-to-date software will continue working fine, and we've taken steps to make sure the vast majority of older devices will too. If you run a large website, or need to support less common software (particularly non-browser software), you'll want to read about the details at: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ In either case, no action is required from you. We're letting you know so you can provide answers to any questions your site visitors may have. Since 2015 we've served the world with 1.6 billion free certificates, each one providing security and privacy to people on the Web. It's work that's 100% funded by charitable donations since we are a nonprofit. If your company is interested in sponsorship, please email sponsor@letsencrypt.org. If you can make a donation, we ask that you consider supporting our work today: https://letsencrypt.org/donate/ Thank you. - The Let's Encrypt team ----------------------------------------

I found this in Account Settings (click the user dropdown in the forum header):

Store, collect and update oembed data from external sources. This module uses the great PHP Library Essence by Félix Girault and adds some processwire magic. It is inspired by Ryan's example module FieldtypeEvents and the TextformatterOEmbed module by felixwahner. Thanks! Download & Install Github: https://github.com/neuerituale/FieldtypeOembed Modules directory: https://processwire.com/modules/fieldtype-oembed/ Composer: composer require nr/fieldtypeoembed

The issue occurs because both InputfieldURL and FieldtypeURL put the value through $sanitizer->url(), and by default the "convertEncoded" option is true. It would be good if this option was configurable for InputfieldURL/FieldtypeURL. As a quick fix you could copy the modules to /site/modules/ and edit usages of $santizer->url() to set convertEncoded false, and maybe open a GitHub issue/request to have that added as a configurable option.

Thanks! Yes, the first option sets the URL to the same one as the URL of the XYZ hour ago link. Thank you very much, Pete! Some examples for the "right column" feature: https://processwire.com/talk/topic/17068-markupsitemap/page/7/ https://processwire.com/talk/topic/12208-tracy-debugger/page/1 screenshots: Looks like it is the long topics which get these stats feature added automatically perhaps? I am not sure how useful these stats are. This is more of a social media like feature you talked about, which is kinda irrelevant in our case, I think too. It just takes up space. I vote for turning it off, if possible. Thanks in advance, Pete! EDIT: It is not possible to use the scroll wheel of the mouse to get to "under" the spoiler, I had to position the cursor in the text above and use the arrow keys of the keyboard to edit anything below. I wish the forum's developers spent more time on improving the RTE instead of anything else. Using the RTE is still a pita sometimes. I know that a JavaScript based RTE in the browser is the hardest thing to implement ever, but still... ?

@szabesz can you link to an example of this right column? I can't see it though I wonder if Ryan or one of the moderators was perhaps playing with the block manager yesterday without realising it shows for all users (we had that happen a few years back accidentally too and I've not found a setting to turn if off yet ? ). My one complaint with forum software (most big forum software really) is that they need to stay relevant in a world where social media dominates so they add new features and don't always think about what the default setting should be (see my previous post - hopefully that one is sorted) and they do like to move the settings around in the admin so we spend a little while every year or so learning where things are. Mostly though the improvements are usually good, but we don't have the luxury we have with ProcessWire of not upgrading so there will always be these little pain points every so often.

Looks and works great, thanks @Pete!

Fantastic, thank you. You have been a huge help!

Yes, $config->ajax will be true if the current request is AJAX.

I think I found it, the XYZ minutes/hours ago link might lead there. I just cannot test it currently 'cos I have run out of unread posts ?

I usually keep an eye on unread posts: https://processwire.com/talk/discover/unread/ Previously, when I clicked on the title of the topic, I was taken to the last unread post and that was very convenient. However, the new version just links to the first post, which is not very useful. Currently the closest thing to do is to click on the "number of replies" link, but that takes me to the last post, and I need to scroll up to find the where the "Unread replies" begin. Is there still a link that leads directly to the beginning of "Unread replies"? I need it badly ? Also, some topics (maybe module support sections?) have a new "stats section" laid out as a new right column. This is a waste of space because the main column is narrower than full width, so a long topic has become even longer than before. This means a lot of extra scrolling from now on, which does not make me happy at all ? Code in this new narrow main column is mostly need horizontal scrolling just to see the content, and that is annoying. I also saw some fixed-width code text sticking out of the main column it for some reason. I am not pleased with these changes at all, they are definitely not welcome. I hope Pete can sort these issues out.

I'm on MacOS using Firefox. I know Firefox has its way of doing when it comes to some cases with margin-bottom... Regarding colors: maybe a suggestion would be to set the blue for buttons / nav bar to a be a bit more blue-ish. Here I took the color from the (invisible) background of thumbnails (32, 115, 206) : Edit: wouldn't mind as well to have the left and right paddings to match the ones on the header (40px left/right). And sorry for throwing you css details !

Thanks @monollonom - I think it might be a bit of a fluke but the new default colours in the software mostly match the ProcessWire site with just some minor tweaks anyway. What browser/OS are you seeing that white space on? It seems alright on Windows+Chrome.

Tiny detail but the margin-bottom on the footer creates a white space I was surprised at first seeing the new colors but it looks good !

Fixed, thank you.

It's worth noting that there are now TFA options on your account for added security if you go to Account Settings > Security & Privacy. Likely not required for most people but if you want to add a little extra security to your account you now can.

i would say the name on a profile page lacks a bit of contrast

Fixed, thanks.

Thanks - I'll check that out. Just pushed a fix for mobile as the user menu was missing - I guess we need to keep that ?

Thanks for your work on this @Pete One thing I noticed is pink on dark grey doesn't really work, eg: Otherwise, looks great!

There's no simple way to do this because when a page is moved the page list is updated via AJAX, whereas the core message() / warning() / error() methods require a normal page load in order to appear. But I had fun exploring some workarounds. Maybe one of these will suit or maybe not. In these examples a message is shown whenever a page is moved but of course you would add your own logic show your message more selectively. Option 1: queue a warning() to appear at the next page load via $session->warning(), and use some JS to automatically reload ProcessPageList whenever a page is sorted or moved. In some custom admin JS (you can add this with a hook or by using AdminOnSteroids): // When a page is moved in ProcessPageList $(document).on('pageMoved', '.PageListItem', function() { // Reload location.reload(); }); In /site/ready.php // When a page is moved $wire->addHookAfter('Pages::moved', function(HookEvent $event) { $page = $event->arguments(0); // Show a warning $event->wire()->session->warning("Page '{$page->title}' was moved to parent '{$page->parent->title}'."); }); Result: Option 2: Make use of the fact that when an exception is thrown ProcessPageList will show this as an alert. The below assumes that you only want to show a warning when a page is moved to a new parent and not when it is sorted within its existing parent. If that distinction doesn't matter then you could simplify this by only hooking after ProcessPageSort::execute(). In /site/ready.php // Optional: use Vex for nicer alerts in ProcessPageList $wire->addHookBefore('ProcessPageList::execute', function(HookEvent $event) { $event->wire()->modules->get('JqueryUI')->use('vex'); }); // Before ProcessPageSort::execute $wire->addHookBefore('ProcessPageSort::execute', function(HookEvent $event) { $pps = $event->object; $move_id = (int) $event->wire()->input->post->id; $moved = $event->wire()->pages->get($move_id); // Store original parent ID on the ProcessPageSort object $pps->original_parent_id = $moved->parent->id; }); // After ProcessPageSort::execute $wire->addHookAfter('ProcessPageSort::execute', function(HookEvent $event) { $pps = $event->object; $input = $event->wire()->input; $pages = $event->wire()->pages; $parent_id = (int) $input->post->parent_id; $move_id = (int) $input->post->id; $parent = $pages->get($parent_id); $moved = $pages->get($move_id); // Check if the parent ID has changed from the original (i.e. the page has moved) if($parent->id !== $pps->original_parent_id) { // Show an alert by making use of how exceptions are handled in ProcessPageList throw new WireException("Page '{$moved->title}' was moved to parent '{$parent->title}'."); } }); Result: Option 3: do it all in JavaScript. Whether this is viable depends on what sort of logic you need. With a bit of extra faffing around (not shown here) you can get things like the page IDs and template names from the class names of the page list items which might help. Optionally add the Vex library as in option 2. And then in some custom admin JS: // When a page is moved in ProcessPageList $(document).on('pageMoved', '.PageListItem', function() { var moved_title = $(this).find('.label_title').text(); var $parent = $(this).parent('.PageList').prev('.PageListItem'); var parent_title = $parent.find('.label_title').text(); var $from = $('#PageListMoveFrom').prev('.PageListItem'); if($from.length) { // Page was moved to a different parent var from_title = $from.find('.label_title').text(); ProcessWire.alert('Page "' + moved_title + '" was moved to parent "' + parent_title + '" from parent "' + from_title + '"'); } else { // Page was sorted within its existing parent ProcessWire.alert('Page "' + moved_title + '" was sorted within parent "' + parent_title + '"'); } }); Result:

Great to see pull requests merged. This will help community and pw greatly!

i was having trouble getting this – i had these as attributes underline__type=radios underline__options=None|Top|Bottom|Both underline__description=Please select your border options. but not working, so i tried this: underline underline__type=radios underline__options=None|Top|Bottom|Both underline__description=Please select your border options. and it works; i don't think this is clear from the instructions – would be great if there were more working examples to copy/paste, in the cheatsheet