Leaderboard

I'm proud to share this newly released custom-made website with you. Musikschule Neumünster https://www.musikschule-neumuenster.de/ Design details The design was built from ground up to give every aspect and every detail of the website its very own unique look. We faced the demand to create a visual experience that is up to date but kind of classic at the same time. A fact you can't describe but you will feel and see it when visiting the website. ? Technical details From top to bottom every detail can be managed in the backend - all instruments, tutors, events, and content pages. In order to make life easier some things are automated (for example: archiving older events or managing the relationship between tutor and instrument). Modules and time-savers ProCache Croppable Image 3 PagefieldPairs MarkupSitemap Hanna Code Jumplinks I hope you enjoy the result as much as we* do. * A little side note to reduce confusion: I'm partner and the developer of Muskaat (design and development bureau based in Neumünster, Germany).

In this post we preview a new feature coming in ProcessWire 3.0.108, which is a major upgrade to our live search feature in the admin. In this update, PW’s search becomes a lot more versatile and powerful while remaining just as easy to use. Plus, there are some fun and useful power-user features that we’ll cover here too. https://processwire.com/blog/posts/processwire-3.0.108-preview/

Hi Everyone, Today I am delighted to share my new product that we have created with Processwire. It's a verification system, that binds together a physical address with website. I’m using Processwire nearly from the beginning and I still believe that it is one of the greatest open-source platforms that exist. Being thankful I’m pleased to provide the service of Verikey verification to the Processwire community (and websites that you did) for free. Forever. Visit verikey.com Gift code: ###### (please, request by direct message) Feedback and questions are really appreciated. Many thanks my Mom, @ryan, @soma, @adrian and all Processwire contributors. Cheers, Alexander UPD: While subscription Stripe requires a valid bank card details. It’s a formality by Stripe for all subscriptions. The Verikey service remains 100% free and out of charge with the provided voucher code.

I use one, but haven't released it yet; started documenting it here... https://outflux3.gitbooks.io/markup-theme-engine/content/

This. I think these two statements summ it up pretty well – @Knubbi's post is totally legit imho. Those who argue otherwhise (expect for @bernhard's point of PW becoming more popular not beeing a goal at all) miss the point I guess – yes you can do all things with PW and, yes we don't want a Drupal front-end-hell and for sure no second WP – BUT for people looking into PW there could be better ways to start: I think @joshuag provied a solution that has both worlds – but it involves both Developers and Ryan. A strong Site-Profile market: Profile should have a well visible market where they could also be sold … directly integrated into the PW setup and processwire.com Like Themes (which are often bundling other modules f.e. shopiing funcitonality etc.) they could be very powerfull, within their provided scope of Templates and Fields, as are WP Themes – Site Profiles come with the dependencies they need: for example Blog functionality etc. and provide a fast starting point for those who need what the profile combines. At the same time, they stay true to PW as they are just ready-made implementations of PW, not bloating the core or changing the way PW works One can still start with a blank site I think, what we miss is, that WP does not really work any different – there is a system and then there are some Themes on top of it providing basic functionality – But only well integrated with the Base-System. As soon as you want to add this or that – it requires manual work or it might look goofy or breaks stuff. We have the same situation with PW Profiles: We don't have to change the way PW works, what we need is strong support for readymade Sites, coming together with a few PW-Templates and Fields. Now this is not where most of us work as @joshuag said – but its a totally valid market and could easily life side by side with those crafting sites from the blank slate.

Hey guys, Thought I would share a quick preview of Designme. A module we (Eduardo @elabx and I) are building for visually laying out your templates/edit screens. ? This is a really quick, zero polish screen grab. FYI. Video #2 - UPDATE This new video shows the following features in Designme: Re-arranging fields via Drag & Drop Re-sizing fields via Dragging. Adjusting field settings - with live refresh. Working on "hidden" fields while Designme is active. Creating New fields. Deleting fields. Creating/Deleting Tabs. Dragging fields between tabs. Creating fieldsets. Tagging/Un-tagging fields. Fields without headers expand when hovered (like checkboxes). Live filtering of fields in the sidebar. Ability to adjust (all) Template settings without leaving Designme. Template File Tree Editing Template files source code with ACE Editor. Editing Multiple files with ACE Editor. (New Tabs) Saving files. Techie stuff Fields load their own js/css dependancies. *ready to use on creation (*most fields) Everything happens via Ajax to ProcessPageEdit (via module + hooks). Designme has a JS api that you can use. All actions trigger events. We would love any detailed feedback on what you see so far. If you are interested in testing Designme. Let me know below. ? Video #1.

Thank you, @tooth-paste. The PagefieldPairs module keeps the mapping between tutor:instrument, tutor:ensemble and vice versa in sync. So editors can either add tutors to an instrument/ensemble or add instruments/ensembles to a tutor. This detail seems small at first but it's crucial. Keeping this in sync makes changes much easier and reduces the risk to miss a tutor/instrument/ensemble somewhere and it doesn't matter where this detail gets changed.

I understand the theory behind sticking with labelled master versions and I don't see any harm in advising future superusers to follow that approach, but I guess I don't see why you can't use the latest dev now and still advise them of that for the future. It's not like being on dev forces you to stay on dev. No there isn't - it's really up to Ryan to make this decision and it's not something that is planned for specific date intervals. I think part of the reason for this is that he know that most of us are probably running the dev anyway. I think the key thing here is that starting a new project on the dev branch makes sense because you'll be testing thoroughly as you're using it. Upgrading an existing site to dev maybe the situation that is technically a safer approach. But I have been using PW for 5 years and in that time I think I've only come across 2-3 major bugs introduced in a dev version that affect existing functionality. Typically all you might have to worry about is new features which haven't been fully tested yet. Obviously PW is not perfect (https://github.com/processwire/processwire-issues/issues) and I actually think we need more solving of issues right now than new features, but no software is bug free. But does a "master" label make it more stable? Sometimes, but not always ?

A very nice, beautiful and informative website. Your design skills are outstanding

Well I'm a starter only but it's fun, and knowing you can any time run tests to ensure everything is OK is invaluable.

Thats not practical since the "overrides" would need to be at so many places. With Uikit you've got LESS where you inject your colors etc. at various places. You replace code, not just override it. Simple overrides would be much more complicated and and could potentially break on an updated base theme. Replacing the whole CSS makes sence. BUT, you're suggestion just triggered an idea: Publish it as a propper Module and replace the CSS of the AdminThemeUikit with a hook… This way, AdminThemeUikit would still be technically the Theme, but the CSS (and potentially JS) would be entierly replaced by the "Child" Theme. In this way, one would also not need to change Settings etc… Brilliant! But I think, the required Method is not (yet) hookable… I guess it is hookable, since it's public…

There are many of us running the dev version on live sites - it's typically more stable than master. Of course there are exceptions on occasion, but I tend to look at the changes implemented in each dev commit - if they are significant, I'll hold off for a week, but if not, I'll update right away.

I see where you're coming from, but I would kindly disagree. PW will never really cater to the "click-and-install-my-entire-website-and-then-you-will-have-your-latte-macchiato-ready-for-you" crowd. wix.com and whathaveyou will do that for you, cheaper and faster. Where PW really shines, is: Creating something that lives on the web, and doesn't make any assumptions how you're going to (re-) use that data in your frontend. There are so many trendy buzzwords, that it's hard to keep track of... PW is (e.g.) perfectly suitable as a "Headless CMS", or whatever the mot du jour is... For such scenarios, "modern website presets" just get in the way.

Admin Theme Boss A light and clear theme based on Uikit 3 Features Five unique color options Beautifully redesigned login screens Modern typography using Roboto Condensed Extended breadcrumb with edit links Extends AdminThemeUikit, so you can continue using all current and future AdminThemeUikit features Option to activate theme for all users Compatibility with AdminOnStreoids and other third party modules Updated and Releases There is a shiny new release page where you can subscribe to updates for new releases of AdminThemeBoss. Color Variants: ProcessWire Blue Dark Black Vibrant Blue Happy Pink Smooth Green *new with 0.6.1* Requirements Requires a current ProcessWire version with AdminThemeUikit installed and activated. Installation Make sure AdminThemeUikit is activated Go to “Modules > Site > Add New“ Paste the Module Class Name “AdminThemeBoss“ into the field “Add Module From Directory“ Click “Download And Install“ On the overview, click “Download And Install“ again… On the following screen, click “Install Now“ Manual Installation Make sure the above requirements are met Download the theme files from GitHub or the ProcessWire Modules Repository. Copy all of the files for this module into /site/modules/AdminThemeBoss/ Go to “Modules > Refresh” in your admin Click “Install“ on the “AdminThemeBoss“ Module

DEPRECATED If you are interested in the new version (commercial module launching in 2023) write me a PM --- Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering. WHY? ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue ? Features/Highlights: 100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself) Limitations: While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation. Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme. Download: https://gitlab.com/baumrock/FieldtypeRockGrid Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md Module status: alpha, License: MIT Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation. Contribute: You can contribute to the development of this and other modules or just say thank you by testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM). Use Cases / Examples: Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches: Filters, PW panel links and instant reload on panel close: You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

Since all good things come in threes, here's another responsive blog profile for PW3: Editorial Travel Blog Template Like the previous two, it builds upon @kongondo's Blog module and uses @justb3a's Simple Contact Form. It also makes use of @Pete's XML Sitemap and @ukyo's Font Icon Picker. Features: Responsive Slide-in sidebar Homepage with picks and last posts, 3-column layout Selectable widgets, e.g.: Recent posts Recent comments Current month calendar with links to posts per day User-switchable sort order for lists (ascending/descending) Configurable list pagination An online demonstration can be found here. And again: all feedback is welcome!

Last week I stumbled upon the focus point feature and I love it. There's only one problem: I made a user role “editor“ for my client. And while as a superuser I can work with the focus point feature as much as I want, she can only set a focus point while uploading pictures and before she saves the page the first time. Once the page is saved she can‘t see the three buttons “Crop“, “Focus“ and “Variations“. Her only option is to remove the focus point via the dropdown but after that she can't set a new one. Do I have to give her an extra permission? Which? Additional info: The gallery where this happens is placed inside a repeater matrix. I wouldn't imagine that this could be a problem but who knows … ?

Here you go https://github.com/processwire/processwire/commit/c7dfb37a7ece9d1a2e0369a92263e7c18663502a Looks like it was fixed in 3.0.100

Thank you very much @cstevensjr. I'll forward your compliment to the designer.

Please take this suggestion, based from the view of a decision maker which framework to use: I hear you saying: "Processwire can do everything. It is not limited to web sites." Sure, it's true and we all got it. However, you canot target "everything". You have to market to specific demand. The success of WP and Bootstrap is their totally overwhelming "out-of-the-box" instant gratification. Click.. Click.. AWESOME website. "Done!" Of course, it is not done. However, users are hooked enough to dig deeper, study, try thing out, extend. And bam, they invested additional time and are captured in that ecosystem. While the Processwire installation technically is flawless, it spits out newbies into the desert (or alternatively into nah sort of website template). The gap between the Processwire post-installation situation and something WP provides with their modern templates is too high. We almost skipped Processwire, because we just didn't know how to get to a first success. It is only, that WP exploded after installing two incompatible plugins, that we came back. We now work with a Processwire Pro to do the website for us but not everybody is willing to invest into the blind. Processwire is totally awesome - I felt that with my very first look. It is so clean, fast, tight, professional, secure and flexible, that I want to see it thriving. Please get users hooked with an awesome general startup experience, people can start working on. it doesn't take more than a beautiful modern website template and ideally with a page builder module preset.

But the truth is my tool is more suitable for module or site profile development rather than for site testing, where you would test the specific PW instance.

Oh, now I got it! Setting module autoload and singular to true again and clearing all caches helped... Thanks for this great module!

Nice job @Noel Boss ! Already adopted, modified & installed ! I just tweaked it to get a Google look (controls), removed the transparency on dropdown and reversed the fonts and notes.

Hi @netcarver, Many thanks! You're welcome!

Hello @Noel Boss, Thanks for your message. I have checked Stripe logs. Seems like it may have happened because you tried to use an expired card previously. The Verikey service is completely free for you. However all subscriptions are handled by Stripe, and their system does not accept the form without a valid bank card. I’m sorry for that but unable to amend this formality. Anyway, I’ve created the ticket and waiting for their response. Many thanks for trying.

Hi, @matjazp We use Google Geocoder to verify an address before sending the letter, to avoid wrong recipient. Could you send me your address please and I will double-check it? Thank you!

Добар дан, @dragan! Thanks for your message. At the moment, I have time only for in-house development. Thanks for your report. Yes, it seems like something is wrong with checking URL JS. We are verifying it more precisely and hope to fix it shortly.

Hello there, it is good to hear that someone cares about code testing in PW community. Some time ago I've created a tool which helps you to run your tests against multiple version of PW quite easily. You can check it out there: https://github.com/uiii/tense. It is compatible with any testing framework. I would be really glad if I'm not the only one using it ?

Looks really nice! Just wondering about the approach you've taken - if this module is about styling changes to the core AdminThemeUikit couldn't the module just add a CSS file containing the style overrides and not reproduce all the AdminThemeUikit files?

I'm having the same problem - URL is wrong. After clicking Apply, it says "Can not recognize the mailing address. Please check and try again."

Interesting! So you're saying that's your own business venture, not working for a client-project? Good luck with that project. I can surely see potential for such a verification process. Gonna read more about it when I have more time. I tried to verify one of my sites and came across a bug(?). When I entered my site URL, there was an error message showing up: Wrong URL. (white text on red background, beneath the input field). The URL is most definitely correct though. What's strange: I could actually proceed to the last screen, where I have to enter a password etc.

Make sure you have a filter form that action url is the $page->url. I don't know what the problem is really but it's all getting too complicated for what it really can be (dead simple). Example filter form for a paginated result list : <?php namespace ProcessWire; $filter = ""; $form = $modules->InputfieldForm; $form->attr("action", $page->url); $form->attr("method", "get"); // select with sort options $f = $modules->InputfieldSelect; $f->attr("name", "sort"); $f->label = "Sort"; $f->addOptions(array( "-title" => "descending", "title" => "ascending" )); $form->add($f); // submit button $f = $modules->InputfieldSubmit; $f->attr("name", "filter"); $form->add($f); // process form if(count($input->get)){ // processes and populates form fields $form->processInput($input->get); // if sort is not empty if($form->get("sort")->value) { // build filter and add to whitelist so it gets picked up by pagination $input->whitelist("sort", $sanitizer->selectorValue($form->get("sort")->value)); $filter .= ",sort=" . $input->whitelist("sort"); } } $result = $pages->find("template=basic-page, limit=2{$filter}"); $content .= "<h2>Show Results</h2>"; if(!$result->count) { $content .= "<p>no results</p>"; } else { foreach($result as $res){ $content .= "<p>$res->title<br>$res->url</p>"; } $content .= $result->renderPager(); } $content .= $form->render();

IMHO this is the fundamental element in this discussion. In my first discovering of Processwire I did not understand how it really worked, since I came from more trational CMSs. I have always thought that there is a lack of information on how to do "things" that are easy in other CMSs. I know that the power of Processwire comes from the freedom of doing things "your way", but sometimes someone needs just a functionality. In my case I came from Drupal and from time to time I miss a module like Views in Processwire that makes so easy to build any type of queries from simple list to complex building blocks . Maybe we need more documentation on "how to do common things".

Cool. On a related note: If you need to extract images from an MS-Word file, there's an easy "hack": Copy the Word file rename it to filename.zip. Un-zip it, and you'll see a folder "media" with all the images inside

Wordpress has one thing different than ProcessWire, which enables them to have such a high quality default theme: Just three types of data, where two are quite similar. It‘s post, pages and comments. The rest is wysiwyg content all the way. In Processwire we don‘t have that and the power of it comes from not having that. Wordpress themes are just pretty frontends for a nearly non changing backend structure, which it had for years. In ProcessWire the first thing you probably do is creating your own content types (templates) and that‘s what no default theme can cater for. How should it know how to display that random blob of data you decided is a entity in websites domain? So there‘s not much incentive to spend a great amount of money on a high quality theme, which is unusable for just about any reasonable usage of processwire beyond „first impression“ after installation.

yes, i know, i'm talking about site profiles that require no coding https://modules.processwire.com/categories/site-profile/ and these:

Hi, ProcessWire does not compete with the WordPress market... Thank the lord. ProcessWire is for developers with basic to advanced knowladge who need a tool to make their vision a reality, easier. A framework. Much like jQuery. You must have some knowledge of JavaScript to fully understand jQuery. Just like if you were to develop for WordPress, you'll need PHP knowledge. Well, unless you are looking to sell themes. I don't know why a PHP developer would touch WordPress. ProcessWire's API is so much easier. So to answer your question, in ProcessWire you start here - http://php.net/docs.php then here - https://processwire.com/docs/ In WordPress you start here - https://wordpress.org/plugins/ then here - https://codex.wordpress.org/FAQ_My_site_was_hacked Edit: Notice how the 'My site was hacked' question was in the Frequently Asked Question section... Should it really be a frequently asked question? Because I don't think I've seen it asked once on the ProcessWire forum. Edit2: Most people here just use the blank profile and see the other profiles as bloat.

No doubt. What I mean is, that the gap to get there is too wide for newbies. My apologies for any offense created. I am just enthusiastic and wanted to share my thoughts as someone who had a first contact to PW.

@Knubbi - i think you may be missing the fact that there are already some awesome profiles available that are out-of-the box very usable sites. I haven't done the dare yet, but i **think** if I needed a complete site real quick, like a one pager, or a simple blog, i'd guess it could be completed quickly and easily. Guess I'll have to try it to find out, and take the "how fast can you setup a (preconfigured profile, generic, no additional custom fields) processwire site" challenge. Will report back when done..

That would be perfect! ??

The problem is that the definitions of real data, studies and 3rd parties have a super broad range. I personally understand them like this: real data = comparable numbers or features studies = examples, references, sites built with ProcessWire 3rd parties = ProcessWire experts (long time ProcessWire users, integrators and developers) We are all 3rd parties (experts) that could create any kind of studies (show examples and projects) to show real data (used features, development time). The videos Jonathan created are a super nice look behind the scenes for someone who is already in web development and CMS-things. My clients aren't into this. They ask me to give advice. They trust me. They want me to tell them what they need. I am the 3rd party (expert) that knows about pitfalls. Let's turn things around. We shouldn't compare ProcessWire to another CMS. We should show and tell the benefits of ProcessWire. For example: ProcessWire is easy to extend. ProcessWire is easy to use. ProcessWire manages all kinds of data structures (books, movies, cars, clothing, what, ever, ...) right from the start. ProcessWire generates all kinds of data exchange formats (RSS, XML, JSON, CSV, ...). ProcessWire doesn't need a dedicated or specialized hosting to perform well. ProcessWire is highly customizable. ProcessWire delivers what is needed. [Your statement here] Just my two cents.

Sorry for the late reply; I have been on holiday for a while. This module acts only on changes to a Page Reference field - this is deliberate for reasons of efficiency. If you already have some Page Reference values in place before you start using the module on those fields then you can get things set up with a one-off API operation: // Get all pages where page_field_a is not empty $pgs = $pages->find("page_field_a.count>0"); // Get derefAsPage property of page_field_b to distinguish multiple/single page fields $deref = $fields->get('page_field_b')->derefAsPage; foreach($pgs as $p) { // For this page, get the pages selected in page_field_a $selected_pages = $p->page_field_a; // Standardise $selected_pages to PageArray in case of "single" field if($selected_pages instanceof Page) $selected_pages = $selected_pages->and(); foreach($selected_pages as $selected_page) { // Add this page to page_field_b on the selected page $selected_page->of(false); if($deref) { $selected_page->page_field_b = $p; } else { $selected_page->page_field_b->add($p); } $selected_page->save(); } } You can do a similar operation for page_field_b -> page_field_a if needed. Once you set up the Page Reference field pair in the module config then the module will take care of all changes from that point onwards.

<?php /** * getFieldsetOf * * for ProcessWire * * gets fields inside a fieldset of pages or templates * choose to retrieve values * * @param Template|Page $context the page or template * @param String $fieldsetName name of the fieldset * @param bool|boolean $collectValues want to collect values of the pages fieldset? * @param string $fieldsetCloseIdentifier default: '_END' * @return FieldsArray|WireData returns FieldsArray or if data wanted, WireData */ function getFieldsetOf($context, String $fieldsetName, $collectValues = false, $fieldsetCloseIdentifier = '_END') { if ($collectValues === true && $context instanceof Page) { $collectedItems = new WireData(); } else if($context instanceof Template) { $collectValues = false; $collectedItems = new FieldsArray(); } else { throw new WireException("getPageFieldset: first argument must be of type Page or Template", 1); } if (!$context->fieldgroup->get($fieldsetName . $fieldsetCloseIdentifier)) return NULL; $collecting = false; foreach ($context->fieldgroup as $field) { if ($field->name == $fieldsetName) { $collecting = true; continue; } if ($field->name == $fieldsetName . $fieldsetCloseIdentifier) { break; } if ($collecting) { if ($collectValues) { $collectedItems->set($field->name, $context->get($field->name)); } else { $collectedItems->add($field); } } } return $collectedItems; } Some extension of the above code - works with templates and pages. If thrown at pages you may choose to retrieve the values inside the fieldset as a WireData object. edit: @dragan (below) thanks for the hint! Just removed it.

please not again . . .