Leaderboard

Merry Christmas/Happy Holidays and Happy New Year! This week we take a look at two new modules released this week: LoginRegisterPro and FileValidatorImage. Plus discussion of upcoming plans for new FileValidator modules and how they are useful in PW. Then a brief highlight of two great new ProcessWire-powered websites— https://processwire.com/blog/posts/new-modules-and-great-websites/

Thanks a lot for your suggestions @szabesz @bernhard I really like ImageSorcerer and ImageReference. The former for its creativity, the latter for its clarity and reference to the page reference field. The more I think about it the more I tend towards ImageReference. It says it all clear what this fieldtype and inputfield are doing: allowing you to store a reference to an image that lives elsewhere in the system. I had that thought, too. But I decided to leave them as separate options mainly because the 'select image from page' allows to setup a dedicated page with a set of images to choose from and to categorize them by using child pages. If I made this a flexible option it might not be obvious for developers and editors what is really happening here. What I'm currently working on is having the PageListSelect remember the page that the image was selected from. Will release this feature before end of this year.

What about ImageReference like the PageReference we already have? Thx for that preview. What came to my mind instantly was that it would be great to have an option to define a default. This would then be very similar to the "select image from page" option - so maybe these could be combined? Maybe that would be overengineering. Not sure ? Thx for your great work! I will definitely use your module a lot in the future.

What keeps me trying out Wireframe is the lack of templating support, so I would welcome this addition for sure. Currently, I do not use any templating engine for PHP so I cannot recommend based on experience, but would like to raise my points of view on this: Twig 3.x: needs at least PHP 7.2.0 to run Blade: PHP >= 7.1.3 Latte: v2.5 requires PHP 7.1 (supports 7.4). v2.4 requires PHP 5.4 (supports 7.4 too). What I prefer is not being forced to update PHP too often. In this regard Latte looks like a good choice. Another factor is how solid the development community behind the library is. I would never use something like a "one man show Blade offspring", as even though one can rely on the parent project for years to come, what happens when the developer of the offspring abandons his project? The reason I am still sticking to plain php for templating is that it needs no updating nor maintenance, which is a timesaver in the long run. Regarding others: https://www.dunebook.com/best-php-template-engine/ BTW, have you taken a look at utilizing Markup Regions somehow?

sure, here is the page table; the fields on any given section are just like title, headline, body, images, page select, section options etc, plus "section type". Some sections have no configuration. The slider section allows the user to select which slides to show; the slides themselves are stored in a central media library, and the settings for any slide are stored with the media item. Sections with images have a field to select the media item to use for the image, or upload an image. For a site like this, every image needs to be cleared and licensed, so the media library provides that functionality, with fields for license type, photopgrapher, sources etc. I'm not using the MicroContexts on this site; that module is now called "Page Field Contexts", and it enables template contexts based on Page Field values. It's a super simple, yet effective module and I'm using it on several sites. https://github.com/outflux3/PageFieldContexts

New showcase entry, for Aaron Copland, composer. https://www.aaroncopland.com/ Features Filterable/Searchable Works Listing with category, publisher, instrument, tag, keyword, or year range filtering Each work has a page showing meta data, as well as related media like audio, images, video, and related events & news. Works are cross related at various levels, as Copland would sometimes use sections of one work in other works Microdata (json-ld) for site, person, works, images, news and some events Ability to display embedded media like Spotify, Youtube/Vimeo, Getty Images, Archive.org etc. Fast autocomplete site & works search Modules used Admin Custom Files AOS Page Field Edit Links Auto Smush Batch Child Editor Custom Inputfield Dependencies Admin Comments* Secure Files Font Awesome Pro Import External Images Autocomplete for CK Editor Inputfield Selectize Simple MDE Visual Page Selector Font Icon Picker Page Field Info Page Table Extra Actions Pages 2 PDF Changelog Dashboards Process Documentation Settings Factory Restrict Tab View Selectize Template & Field Tags Prev/Next Tabs Text Input Awesomplete Get Video Thumbnails Ion Rangeslider Runtime Markup Config Form Inputfield Color Inputfield Field Descriptions Extended Cookie Management Banner ProCache Lister Pro Profields (Table mostly) FormBuilder Various custom modules *Admin Comments is a module in development that enables site admins/editors/managers to add comments to pages in the backend and to optionally notify other site admins/editors/managers. Possibly to be released in directory soon.

We recently relaunched DOMiD, the Documentation center and Museum of Migration in Germany. Concept, design and implementation by schwarzdesign. Features Bilingual site with German and English A section-based design focusing on flexibility and ease-of-use for editors Multiple forms built with FormBuilder that can be placed on any page Separate feeds for news & press releases Lightning fast page loads with almost perfect ratings in Lighthouse Completely accessible and SEO-friendly Notable tech decisions Forms and form placement There are multiple forms for different services that DOMiD offers. Those are built with the FormBuilder. The editors don't have access to the FormBuilder itself, but we still wanted to allow them to control which form is displayed on what page. For this purpose, every page has a select field to select which form to include (if any). Additionally, the form placement has additional fields for a headline and a description, so a generic contact form can be reused in different contexts. Section-based design Most pages are built through Repeater Matrix sections. There are multiple section types available, for example: A generic text / image column with up to three columns of text and images An accordion (rendered as <details> elements). An image gallery Downloads (for files and images, displayed as a list of downloads) External Embed (e.g. YouTube) All sections have an optional headline and a selection of three different background colours. In addition, text columns may be rendered as a coloured block with some padding. This allows for interesting and diverse layouts. Testimonial database One of the available sections is for testimonials or statements (you can see one at the bottom of the homepage). Because one testimonial may be displayed on multiple pages and the client wanted to be able to switch the displayed testimonial on the fly, there's a separate content type for statements. The statement content type has fields for the statement text, author, and author image. The testimonial section only has a page reference field to select which statement to show. This way, the testimonial definition is separate from the placement on a page. Modules used Form Builder Pro Fields (Repeater Matrix in particular) Unique Image Variations ALIF - Admin Links in Frontend Sitemap Wire Mail SMTP Developer Tools: Tracy Debugger, Duplicator, ProcesWire Upgrade Migration museum As a sidenote for anyone living in Germany, this month the German Bundestag has approved funding for DOMiD's first Migration Museum ("Haus der Einwanderungsgesellschaft")! The museum will be build in Cologne and is scheduled to be finished by 2023. We're looking forward to it! Check out this page if you want to learn more, or find out what people are saying about it here.

Hey folks! I've been thinking of adding templating engine support for Wireframe, preferably in a way that supports multiple templating engines (module per engine, or some other way to set up the preferred engine), but realise that I don't really have the foggiest which engines folks prefer these days. I'm sure some of you are way more knowledgeable than me in this regard, so I'd lie to ask for your suggestions and/or opinions first ? My current list looks like this – loosely ordered by how much weight I'm thinking it should have: Blade (part of Laravel – standalone from https://github.com/jenssegers/blade) Twig (https://twig.symfony.com/) Latte (https://latte.nette.org/) (Dust PHP) * Anything I'm missing? What about the order, does it make sense? ? * Dust lingers on the list mainly because it's the last templating language I've used. It's a JS thingy ported to PHP, not very popular as far as I know, and not very well maintained, so not sure if it's really worth the trouble.

Hi @ryan, I'm considering purchasing the LoginRegisterPro module and I'm asking: will you develop support for viewing and/or editing ProFields fields on the front-end (files, repeaters, richtext, combination fields, etc.)? If so, when can we expect it to be developed?

Twig would definitely be number one on my list, I've been using it for every project for a while and it feels waaaay cleaner than native PHP or Blades. See my tutorials (part one - part two) regarding the Twig integration ? Part two has some examples of connecting Twig to the ProcessWire API, it's a natural fit.

Nice idea. If you have sth like template engine factory module in mind, people could add their own engine modules. Two more engines, that are quite popular and not on your list: Mustache and Smarty.

@theqbap Then add the string "JSON" before the config : JSON{ "name": "Testing the import", "input": { "type": "csv", "delimiter": ",", "header": 1, "limit": 10 }, "fieldmappings": { "title": 1 }, "pages": { "template": "Data", "selector": "title=@title" } }

These ones popped into my mind: AnyImagePicker GlobalPickerForImages GlobalImagePicker GlobalImages GlobalImageSource PickAnyPicture PicturePicker And some creative ones too: ImagineGlobally ImageOutsorcerer (not misspelled but intentional ? ) ImageSorcerer ImageOutsourcing

Great, thank you ? Would be great if you could add an option to set markup of some popular css frameworks easily on your todo list as well ? eg $config->MarkupMenu = 'UIkit3'; // $config->MarkupMenu = 'Bootstrap4'; // ...