Leaderboard

Happy to announce the launch of the completely rebuilt San Francisco Contemporary Music Players website, using ProcessWire. https://sfcmp.org/ The previous website was a hornet's nest of disorganized content, dozens of 3rd party plugins, duct taped together within WordPress... difficult to use, time consuming and confusing to manage. And didn't look so good either. Lot of fun to rebuild this, though took several months. YOOtheme Pro and UiKit were a dream for me to work with, just love those. Made it so possible to create all of the custom sections, widgets, sliders, cards, mega menus, and so on. Don't consider myself a front-end focused web dev, so have a deep appreciation for the time, care and effort that Yoo has put into both UiKit and YOOtheme Pro. Almost no additonal CSS was needed to be written for this; the stock UiKit classes and attributes make it possible to just build things in HTML and not have to fiddle with CSS. Ryan's commercial modules played a major role in the build. ProFields, ListerPro, ProCache, and FormBuilder were all important. FormBuilder+Stripe allowed me to confidently migrate their need for a stripe checkout from some WP plugin to the clean and simple setup now using FB. ( https://sfcmp.org/donate/print-for-sale-dirge-by-hung-liu/ ) Some libraries also were of great use and value, namely PLYR for audio, and tabulator for some table display type of stuff. As always, the API was a dream to work with, many custom import scripts were created along the way to import legacy Press, Albums, Repertoire works, Program Booklets library, Players etc.. The image API is doing wonders with SRC sets, and webp images. The PW documentation site was a daily companion. This forum likewise was always a most valuable and enjoyable resource to search and rely on for solving the occasional conundrum. There is such a wealth of info here that i never found it necessary to post a question. Lastly, to underscore just how unparalleled, flexible and user-friendly the PW backend is, we had the backend training session a couple of weeks after the site was launched, and within 30 minutes, the person who will be managing the content was able to know how to create and manage concerts, blog posts, albums, press articles and more.

yes!!! Thank you, this works now You've been v helpful, thanks so much ?

I love ProcessWire and I've been using it almost exclusively for the last 8 years. One thing that has never improved though is how the page loading is blocked while waiting for ALL images to be resized in the frontend. This is ok for a basic page with a single hero image and another 2-3 in the content but is seriously problematic for gallery pages or sites with loads of images. First page load can be incredibly long, or potentially time out. Would it not be much more user friendly if the page would display and images would appear when they are available in the requested size? I came from Drupal 7 where this was the normal behaviour, it was a shock with ProcessWire and unfortunately this is still the case. Is there a technical reason why it MUST be like this? While ideally this would be a feature in the core, what workaround do you all use to display the html/css/javascript while images are getting resized? Is there a module I've missed before?

Finally I got some time to check out RockPageBuilder. I have great hopes! I got 2 fields that depend on the the state of a SELECT as radio buttons called button_linktype: The selectable options: 1=interne Seite 2=externe Website Outside of RPB I am able to do Show this field only if button_linktype=1 or button_linktype=2 to show or hide the depending field. In a RPB block this doesn't work! Neither PW backend nor frontend edit. I suspect this has something to do with the problem that I also cannot access a select option(->title) in my viewfile of a block: // 1=blue 2=black // Outside RPB this works as expected // Inside RPB this results in the PW Pagetitle instead of blue $some_var = $block->button_style->title; Tracy shows that all vars are there. It's a problem of accessing them. PW 3.0.226 | RPB 4.8.0

@Klenkes thx, I already found the source of the problem. Repeater fields have to be renamed because we can have many fields "foo" on one page, so they are named "foo_repeater123" and "foo_repeater456" and such. This conflicts with the showif condition, which would still be "foo=something". I'm wondering though why it does not work on the frontend when using ALFRED. Are you sure? For me it works in two senarios: 1) If I edit one block in a separate window: 2) In an ALFRED modal opened from the frontend It does not work on the backend view: Because in that last case we have fieldnames with the _repeaterXXX suffix. In the first 2 cases we open only the single page, so we don't have these suffixes. Can you confirm that it is the same for you?

Hi Bernhard. No rush! I have no current project ? and just checking the module out. So far I like it and will use it if a fitting project comes up. Then of course I will purchase the next bigger licence.

that's right ?

Ohhhhhhhhhhhhhhhhhhhhhhhhhhhhh yeah I understand, we are all forgetting something tiny but quite important: the property to use on User is "name" instead of "title". ? $playerChampionships = $pages->find("template=Championship_results, winner_home_club={$page->id}"); foreach($playerChampionships as $championship) { echo "<li><a href='$championship->url'> $championship->title - {$championship->winner_name->name}</a></li>"; } Property "winner_name" should be renamed to "winner" since it's a User instance and not a string. ?

Really nice work @Macrura. I love the repertoire list table that is searchable. Fabulous. UIKit really coming through once again.

it's like a hotrod type of setup... i have a YT dev subscription, and a sort of process to be able to use the files in my PW front end, and have the wordpress install on local to work with the settings and sometimes do some designs...

Thanks @szabesz, I'm aware that it's possible but I don't want to pre-generate all image sizes for all images automatically. For example Drupal 7 resizes images on the fly too, based on image presets, yet the page displays and images load as they are generated. I am just hoping that it's possible to achieve something like this in template files.