Leaderboard

Finally, a blog post this time ? — ProcessWire 3.0.159 brings some useful and time-saving upgrades to the core two-factor authentication system: https://processwire.com/blog/posts/pw-3.0.159/

That line wants to execute ProcessPageView. The error means that line 53 returned null: $process = $wire->modules->get('ProcessPageView'); /** @var ProcessPageView $process */ My guess is that files were either not transferred correctly, or fully or were corrupted. FTP can be notorious for converting files on route! (ASCII vs Binary) I'd suggests this: Upload a zip of ProcessWire Unzip the files when they are on the server Install ProcessWire Upload a zip with the file assets Unzip the assets Do the database import Alternatively Install ProcessWire on the server using this script by Soma (you might need to edit it first) Follow steps #3 - 6 above Later, you can sort out your FTP file transfer settings.

Forgot to put a note on what is currently supported : Features Auto-save Medias upload support HannaCode support Blocks Implemented Heading Image Paragraph Embed Quote Code Link Table (beta) Block Delimiter Raw HTML Note (custom block markup)

Hey @jonatan! Good points regarding Kirby. Just wanted to drop a couple of comments ? Since you asked: Personally I find ProcessWire's current admin more appealing than the one in Kirby. I get that this is opinionated, of course, but from my point of view Kirby's GUI is the one that looks dated. For starters everything is tiny and stuffed, the icons and typography are rather mundane (in the lack of a better word), colour theme feels unimaginative (basically just black, gray, and then — gasp — a bit more black) and contrasts are pretty bad. I may be primarily a developer, but I'm saying this also as a designer and author: Kirby's GUI does not feel appealing to me, and it's definitely not something that would, in any way, inspire me. In a way it's nice and simple, yet at the same time it's "the wrong type of simple". Kind of like someone skipped most of the design phase and instead converted an initial wireframe into a final product ? (Again: this is highly opinionated. I get that different things appeal to different people — there's no universal truth when it comes to something like design. I'm also not trying to dismiss Kirby; I'm sure they have their strong points, but my humble opinion is that the GUI is not one of those.) I won't claim to know what the future has in store for this part of the ProcessWire core, but it's worth noting that a lot of what the core currently does depends on an actual database. Ryan has also stated on various occasions that features like full-text index are a must. I'm not very familiar with Kirby myself, so perhaps they've devised equally flexible and performant ways to perform complex queries, but I'd imagine that being much trickier to implement when you're missing all the nice database features — and without the ability to perform even complex queries, ProcessWire wouldn't really be ProcessWire. ... and, that being said, my understanding is that the flat file thing is one of the biggest — if not the biggest — selling point of Kirby. I bet it's a great tool for a lot of use cases, but one could say that it's really competing in a somewhat different category compared to ProcessWire ?

In terms of making the core smaller, can the old admin system (ie, the contents of /wire/templates-admin/ I believe it is) be done away with? The admin that looks like this: https://i.ytimg.com/vi/eq-9GQCT0lw/maxresdefault.jpg

Thanks for the update @ryan! Could you please take a look at what might be causing the main download button for the dev version to be stuck on 3.0.153? It's been this way for several weeks. I know that the button always links to the current state of the dev branch but it's potentially confusing to users having the version number out of sync like this. Thanks ?

Thanks @teppo for your insight, as always highly appreciated. I got what you mean. I think that there is a part of question of taste but also depending on the task on which the user is involved/focused. In first instance, while discussing with the colleague, I started to insist that he could use the CKEditor to write his articles; The point is here, he is specialised in content creation. I also suggested MS Word as tool - but no, the UI is not soft as Gutenberg. Then I abdicated and told him to write his articles on Gutenberg and a local install of Wordpress, after all, I will not touch at it, and I can import the content of a Wordpress page to ProcessWire. I don't know if you guys are used to write content, but this guy showed me also the editor that was crafted for the big site Medium. It's something similar, polished, the editor contain an inline toolbar and some blocks. I understood then that it's like an "new" category of users, they are used to write content in a modern environment. I was not even aware of those type of editor / blocks approach ? . So yes, I can understand that it can be "intimidating". Yes! First mission that was to bring back this guy to use ProcessWire is almost done ?? @Pixrael Yes it could. The module you would like to see was already mentioned and I remember that Theo, Elabx and Joshua worked on something. It was not grapejs but the idea remain the same. If you really want to give a try and invest some time the community will help you ! @bernhard wrote nice tutorials on modules creation you could begin with, then start a new thread here in the modules/dev forum. There are some hard works in perspective and I think that a module like that should be taken by a group with dev and designers ?

This module lets you restrict users to a certain branch of the page tree - it can limit editing permissions, as well as the page list view to this branch. http://modules.processwire.com/modules/admin-restrict-branch/ https://github.com/adrianbj/AdminRestrictBranch Restricted View Non-restricted View Note that this module does not add permissions (unlike how PageEditPerUser and PageEditPerRole work), so the user must have template level permissions to edit the pages in the restricted branch. What this does allow though is giving all users/roles editing access for the home template and allowing that to inherit all the way through the page tree and let this module restrict to specific branches. As you can see from the screenshots you can specify how to determine the branch to restrict the user to - either via a matched role name, or via a dedicated page select field on the user's profile. The match role name works like this - if you have a series of branches called: Branch One, Branch Two, etc, users with a role named: branch-one will only have access to Branch One. You can also decide whether to restrict page tree viewing as well and editing privileges (default) or just editing privileges. The Branch Exclusions option is important for things like external PageTable parent branches etc. Main module config settings User specific branch setting on user profile page This module came out of my personal needs as well as this discussion: https://processwire.com/talk/topic/11428-project-design-main-shop-hundreds-of-affiliates/ As always, feedback is very welcome.

I thought it might be good to have a place where we can post other good CMSs and transparently talk about their positive aspects and, why not, compare them to PW. This might help PW grow by learning with the others, and hopefully, could even bring those tools devs to explain them to us. This idea came up to me after this discussion, and from realizing that after discovering PW I'm not as curious about finding other CMSs as I was before. I can Imagine that this has also happened to others here, and can never be good to stay in ignorance I almost stopped looking for other CMSs, but there are two that I would like to share for starting: The Secretary -> http://www.secretarycms.com/ (this is a free self hosted portfolios CMS. For a portfolios tool it's quite flexible. The user interface is also nice) Webpop -> http://www.webpop.com/ (It's a cloud CMS that gives complete control over the markup. This one is not free)

Hello, I would like to present you a new module which aim to facilitate the productivity of your editors/publishers when working on ProcessWire. The idea begun when my co-worker told me that when typing in ProcessWire CkEditor field he was feeling "loosing motivation" when writing big wall of text and/or inspiration. So he opened his web-browser and show me a site looking to Wordpress - feel free to put your preferred emoji here - then he opened Gutenberg... typed some text and moving some "blocks". I understood immediately why he got this feeling with CkEditor. If you or your client feel like this guy, then you will love this module ! What is currently supported ? Features Auto-save Medias upload support HannaCode support Blocks Implemented Heading Image Paragraph Embed Quote Code Link Table (beta) Block Delimiter Raw HTML Note (custom block markup) Feature Request Frontend Edition And there you go for the preview - sorry I am to lazy and bad at typing text so I had a copy/pasta moment : Module featured in the ProcessWire Weekly #317 - Thanks @teppo

I don't think we've ever gotten to grips with this bug. It bites some people every now and then. Excellent! Glad you got it sorted ?

I've now implemented a multi-site and multi-instance setup and it mostly works. For some reason, the 2nd site cannot access select options fields on pages on the 1st site - I changed these to page reference fields and that works. The only major problem so far is with runtime markup fields, which are pretty crucial to my app (great module btw @kongondo ? ). These don't seem to be accessible by the 2nd site at all - either directly or via $page->render(). Curiously, I had no problem accessing them from a non-PW site (on the same server).

This looks great, thanks for open-sourcing! Am I right in assuming that the callbacks will only get invoked if the matching placeholder is found in the server response?

Interesting, I was thinking that ProcessWire could do with a couple of alternatives to the dated CK Editor. EditorJS is one of those 'modern' editors (I was also looking at Quill), I definitely like the block-based output in JSON format. In the end I think it would be nice to be able to change the editor implementation library for textarea fields on the fly – like having a textarea field where you can select between CK Editor, EditorJS, TinyMCE etc. and being able to easily add other editors through a hook or something. Edit: Obviously this should be changed in the field settings per site, not configurable by editors themselves!

Intrigued! As it happens, I have InputfieldEditorJS + FieldtypeEditorJS proof-of-concept sitting on one of my own sites as well. Mostly functional, though your module looks way more polished. I never got to implement media uploads, for one. It was intended as a test to see if our team would prefer that over Repeater Matrix, and since it wasn't a massive success, I never fully completed it. Very much looking forward to seeing your module in action ?

You already know that you might have to backup and upgrade your site to the new master. Since this version (3.0.62) there have been a number of various fix including repeater.

You can also configure your CKEditor field to insert <br> tags instead of <p> tags on Enter. https://ckeditor.com/docs/ckeditor4/latest/api/CKEDITOR.html#property-ENTER_BR

// not tested class TextformatterP2BR extends Textformatter { public static function getModuleInfo() { return [ 'title' => 'P2BR', 'version' => '1.0.0', 'summary' => 'Textformatter that strips all <p> and replaces </p> by <br>', ]; } public function format(&$str) { $str = str_replace("<p>", "", $str); $str = str_replace("</p>", "<br>", $str); } }

@horst Thank to Corona there are smart people who have time to answer to my stupid questions! ?

have you tried to double click one trash icon? Should do the trick. (since PW version 2.2?)

New showcase entry, for Rum Doodle Digital Marketing Agency https://rumdoodle.at/ Features On-Page SEO in full. Auto json and rich snippets Ajax contact form Bootstrap 4 Fontawesome (will be removed) Modules used Auto Smush Email Obfuscation (EMO) Markup Cookie Consent ConfigForm Fieldtype I love the part when I am not using too many fields and modules.

Hello everyone, Recently I spent some time researching how I can update my workflow. I really enjoy working with TailwindCSS however, when it comes to Javascript, I often find myself having to search around to find a good package. Often I find myself having a package for lazy loading, a package for sliders, a package for animation, a package for parallax and a package for ajax. Before you know it, you are worrying about dependicies, conflicts and vunrabilities for many different packages. Since the push is to get rid of jQuery and use native javascript, often each will have their own utility classes, some of which do the same thing. This adds a lot of bulk to the website. This is what I love about UIKit, it provides plenty of functionality for a small ~130KB unminified. Not many know this, but the UIKit helper classes are exposed via the API too. So it means you will not have to worry about your javascript working cross-browser (https://github.com/uikit/uikit-site/blob/feature/js-utils/docs/pages/javascript-utilities.md). The perfect thing would be to combine UIKit and TailwindCSS, but the best way to achieve this is up for grabs. I personally use TailwindCSS base and implement components from UIKit. I then use PurgeCSS on the CSS file to make sure anything unused by either UIKit or Tailwind isn't making it to production. I do this using Parcel JS. I have used Webpack and Gulp previously, but I find Parcel is a simple and easy way to get a project started (and it's fast!). The next thing I've found is UIKit is not always the answer. There are now more than ever better ways of achieving things in browser. Such as CSS Grid, `position: sticky`, and `object-fit` try to use these CSS alternatives where possible. Purge will always make sure that you get the smallest possible file size, so avoid using the uk-grid element where possible and use CSS Grid. I have setup a github starter template (https://github.com/TomS-/UIKit-TailwindCSS/tree/master) if you want to have a look at it. CSS Grid will introduce intrinsic design (https://www.youtube.com/watch?v=lZ2JX_6SGNI - Great series) Next will be to use WebP, there is plenty going around on the blogs now about this, but this will make a massive improvement to your Google Page Insight rating (https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.tikari.co.uk%2F&tab=desktop). I would love to hear your web manifesto - and ask me anything about mine ?

Hello folks! Recently we published a new website for Brightline, a Project Management Institute (PMI) initiative together with leading global organizations dedicated to helping executives bridge the expensive and unproductive gap between strategy design and delivery. The previous website was made in Hugo as in the beginning it was a very simple website, but as the business needs changed, I decided to build this version in ProcessWire. Nothing fancy occurs behind the curtains, the need was more on getting some data in a way that makes it easier to create reports and to give access to PW's great admin to another team member. For the other website, that you can see here, I didn't implement a CMS on top of Hugo because for me it was quicker to edit the files and push to the repository. Some content is still being copied but 98% is done. A quick list of modules used: - ProCache, FormBuilder, ProFields, SeoMaestro, PageHits, TracyDebugger, MenuBuilder, AutoSmush, and other custom ones. I'm biased, but there a lot of good and useful content created by us and also by partners and all is free to download. :)

I have written tutorials here and various tutorials before, it's fun for me however I think starting small is a good idea. I will create a thread for this today or tomorrow where we can deliberate on table of contents and all.

This is a cool idea. I will start creating a course, but it has no the contents, but in the following weeks I will start uploading videos.

This is now available:

Hi Adam, sorry the question wasn't very clear. I was just wondering how you deal practically with images. I mean on most sites I build there will be different sizes, thumbnails etc. Perhaps multiple images for an area. I guess in a general way, I'm not sure as to the benefits of using these sort of systems once one knows how to use a system like PW. Certain parts of them do appeal to me (the configuration files) but when I download any of these projects and peep through the code, they don't really seem any simpler to me than to using a fully-featured CMS. I totally get the appeal to someone who just wants to load up a theme and then manage their content in Markdown files but once you get beyond that and want to start editing template files and working with more complex structures, isn't that initial simplicity then lost? At which point you might begin to resent the lack of certain features that fuller systems like PW offer. Think these sort of tools go in the "I really want to like them but I don't quite get it" category... Anyway sorry, just my ramblings on the matter

One thing I do like about CMS like Kirby and Bolt are the configuration files in YAML. As I haven't really used these before extensively I couldn't say if they reach a natural sort of breaking point where things get difficult but there are times with PW when I would prefer to do more work in the text editor than clickety-click. (Never thought I'd say that )

I mostly use Kirby, which is a lot like ProcessWire, just smaller and flat file. I remember experimenting with outputting PHP files from Middleman during build process, but do not remember if I was successful or not. Also, some contact forms were originally requested "just because people use them", so those are discarded, if not meaningful.

Been trying out Middleman recently too, but I figured if I can generate a static site with ProCache and have all the power of PW if needed, why bother (that and nobody else at work knows Ruby..), and with Middleman clients absolutely need to go through us to update. I like static sites, but I got bit by them a few times, when the client eventually decides they need something dynamic added. PW looks kind of the best of both worlds there to me.

A couple I have been messing about with lately. OctoberCMS - Laravel based, currently in beta, but looks like it has a lot of potential. Bolt - Nice lightweight CMS.

Other possibility: [[page rendered]] <--- actual $page (wrapper) // child page, 2 rows in repeater [col-50]txt[/col-50] - [col50]txt[/col50] // child page, 3 rows in repeater [col-33]txt[/col-33] - [col-33]txt[/col-33] - [col33]txt[/col33] // child page, 1 row in repeater [col-100]txt[/col-100] // child page, 4 rows in repeater [col-25]txt[/col-25] - [col-25]txt[/col-25] - [col-25]txt[/col-25] - [col-25]txt[/col-25] [[/page rendered]]

https://www.contentful.com/ This is still in beta and I just asked for an invitation, so I don't know how it is. But the concept sounds good. Edit: just want to add that something like this would be really easy to do with a PW site

Greetings Everyone, I was involved in Joomla for about four years before coming to ProcessWire. I also did a fair amount of work with ModX, ExpressionEngine, Drupal, WordPress, and Concrete5. For frameworks, I got involved with CodeIgniter, then with Laravel. I can honestly say that -- in my experience -- ProcessWire allows the smoothest, cleanest path to the development of my concepts. I feel that with ProcessWire there is a shorter distance between what I am imagining for a site and how to get there. As diogo explains, that does not mean that ProcessWire has nothing to learn from other systems. And a positive discussion like this could be amazing if ProcessWire can gain from it. I've taken some time to look at my work with the CMSs, and I actually don't see anything ProcessWire can learn from them. Looking at Laravel and CodeIgniter, I see some potential for comparison (but nothing too major here): 1. Validation. Using the API to build forms in ProcessWire is an effective way to add validation. But it would be great to have more validation in the admin forms. 2. Form Creation. Again, we can create forms using the ProcessWire API. But when you want to build forms that lead to creating or editing new pages, I wonder if a more obvious "form helper" might be good (for example, something like CodeIgniter's: http://ellislab.com/codeigniter/user-guide/helpers/form_helper.html). These are the only two I can come up with at the moment. And again, in both cases, there are ways to achieve it in ProcessWire. It's more a question of whether there might be an even easier way. Thanks, Matthew

There is other CMS'???