Leaderboard

For my first steps with PW, I found this Youtube playlist by Henning Heyne. He builds step by step a simple blog, but by doing that, you get to grasp some concepts of PW that maybe a bit not intuitive but prove afterward to be extremely powerful (like a simple post category being a page in itself). Hope that will help.

I think ProcessWire's opinions are very worth it. The ones that I feel are right at hand are the selector API and the concepts associated with a Page. This allows you to reduce the amount of decisions you have to take and later execute, letting you go straight into making that real estate/portfolio/etc you want to build. I'd say that with very little backend experience you can build something nice and fast in ProcessWire, with a very advanced and minimalistic and powerful admin backend out of the box. I'd encourage you to give it a try, at least a couple days of work. Give ddev a try to setup your development environment. If you find yourself at trouble don't hesitate to write back, it's an awesome community!

I quote myself here (source) Probably the best way to start is: Read the docs: https://processwire.com/docs/ Get familiar with the selectors: https://processwire.com/docs/selectors/ Try the tutorials: https://processwire.com/docs/tutorials/ Search the forums for common questions with google like this: https://www.google.com/search?q=site%3Aprocesswire.com%2Ftalk+how+to+resize+images And give yourself a weekend or two The moment you installed and broke your 10-20th installation of ProcessWire you will feel at home. And you should break* as many installations as possible to learn the foundation of pages, templates, fields, and go from there. Use DDEV (all platforms) or Laragon (Windows) for an easy start. Best way to start with ProcessWire locally. Install the Skyscraper profile and take it apart - or try another site profile. That way you will learn how to use profiles and can build a routine to install ProcessWire. Maybe even creating a few instances with different profiles could help. * have fun with the code, bend and twist every single part of everything to understand. ProcessWire will give you a headstart, great UI to enter content, manage the site and modules, ProcessWire takes care of routing, permissions, and user management. ProcessWire is probably the easiest way to start learning a bit about PHP. if/else/foreach/echo is everything you need to know to start.

Some first steps: Have you gotten a working PW instance installed and running in a dev environment? Once that's done, install Ryan's "Skyscrapers" site profile and study that. Maybe add some features or use it to setup an instance for a personal project. And of course, there's PW community which is very helpful.

I really like the idea with a tweaks pluggable collection. But I would prefer its usage was separated from the RockMigration module, so one could use tweaks without the more developer-centric migration tool. I thought that @bernhardstarted a dedicated module for that, but not sure if it is still alive.

All we need now is a community library of tweaks and macros. Perhaps it could be called "The Rock Pool" :)

Since I had to update more and more projects lately and also the PHP version of some of these projects was set to >=8 in the meantime I created a fork of the module and updated mPDF to version 8.1.3. With only some small changes in the WirePDF module I can now continue to use Pages2PDF without any restrictions. Maybe this is helpful for someone. https://github.com/markusthomas/Pages2Pdf

The module provides a list of PageTable based content elements. It enables the backend user to easily create, publish, move, delete, copy and paste content elements. The rendering logic of the module is detached from the ProcessWire backend scope via Shadow DOM and allows the elements rendering identical to the front end. It ships with some helper functions that simplify the handling of content elements. Download/Install Github: https://github.com/neuerituale/PageTableNext Module directory: https://processwire.com/modules/page-table-next/ Composer: composer require nr/pagetablenext

https://github.com/baumrock/RockAdminTweaks

Great, thanks very much all. I guess I just need to get stuck in and give it a go - I've been going round in circles for some time wandering what to learn, so really just getting stuck in to something, anything, will be a good idea! You've given me some good pointers so I'll get on with it, thank you.

Hi, And thx for a quick reply. I've manage to accomplish what I wanted with following code: <?php namespace ProcessWire; if( $pagegrid->isBackend() ) { // render things only for the backend $content = ""; $content .= $pagegrid->styles($page); } else { // render things only for the frontend $content = ""; } $content .= "Example content"; if( $pagegrid->isBackend() ) { // render things only for the backend $content .= $pagegrid->scripts($page); echo $content; die; } Thank @jploch for pointing me to right direction :)

Ok, if anyone wants to explore this, and has RockMigrations installed, here's a slightly improved version of the above, packaged as a Tweak. QuickWebAuthnLogin.php

Thanks, That actually works, but I think it might be for the wrong reason. There can't actually be any slowdowns because of permissions, I suppose? It has to be something else. Not sure what exactly yet, but I'll see if i can find out.

@ColtNikolaus No need to ask for permission, doing so adds noise to the forum, creates work for other people, and delays possible answers. What is your actual question?

@Jonathan Lahijani I'm not surprised, but still shocked. I have heard of people not adopting Gutenberg but couldn't tell if it was just a preference to not adopt. This is some critical stuff. The amount of CSS that WP stores in the database has always been problematic. I was asked to make some adjustments on a site, so logically I went to the theme CSS, nope. Then went to the page builder plugin because you can bump around a lot of values for CSS properties in different units- struck out again. Then went to the in-admin theme editor where I found a bunch of styles in a text box, most of them had '!important' to overcome the styles in the other two places. The fact that this got even worse, is feature incomplete, breaking, and seemingly underengineered is just wow. Everyone get in the time machine... <!--include /text/header.html--> <!--getenv HTTP_USER_AGENT--> <!--ifsubstr $exec_result Mozilla--> Hey, you are using Netscape!<p> <!--endif--> <!--sql database select * from table where user='$username'--> <!--ifless $numentries 1--> Sorry, that record does not exist<p> <!--endif exit--> Welcome <!--$user-->!<p> You have <!--$index:0--> credits left in your account.<p> <!--include /text/footer.html--> That's PHP 1.0 WordPress has adopted the syntax of PHP 1.0 I, for one, am truly inspired.

Yes, that's right. I use maybe 5 or so features from AoS and figured porting those over would be a good way to learn both how AoS does it, and how your tweaks work. I'll add as PRs, with attribution to tpr, as I go. Updated to add: First four tweaks from AoS done and in as a pull request. Show extra actions by default. Show template name as a link to the template edit page. "Bypass trash" adds the Delete button to the page action list and also allows permanent deletion from the delete tab when editing pages. Prev/Next page edit links.

What @dotneticsaid. And when trying out things. Snapshot - add fields/templates/dummy pages etc. Like it -> keep it. Don't like it -> rollback to last snapshot.

Why don't you look into the code of those modules or ask the module authors how they did it?

@Entil`zha Hi. By default PAGEGRID renders the whole template inside the backend/fontend. But you can easily customize that. <?php if(!$pagegrid->isBackend() ) { // render things only for the frontend // Eg. Header, Sidebar } // render pagegrid $pagegrid->styles($page); $pagegrid->renderGrid($page); ?> If you are using markup regions you can have the check from above inside your _main.php file. To quickly disable ProcessWire’s automatic append/prepend of file “_init.php” and “_main.php” for a template, you can put this function at the top of your template file. $pagegrid->noAppendFile($page); Note that this will disable the append and prepend files from this template also for the frontend. You can also do it the other way around and disable it globally by uncommenting the lines $config->prependTemplateFile and $config->appendTemplateFile in the config.php file off your site folder and include the files manually on the templates where you want them..

Is it possible to have a thumbnail for the buttons instead of the name with the + icon?

Thanks Brendon. Happy to know that I’m not blind. I will give a thanks trophy anyway. People in this forum are so friendly, if I can boost their ego, it will be my pleasure... ?

The "Thanks" trophy is nice in that it provides reputation points back to members, but aside from a little ego boosting, I don't think it has any terribly high value or merit -- with perhaps the exception of visually providing a means to let other visitors know what replies are worth reading carefully? The "mark as solution" feature is not enabled, or is at least hidden. I'm not sure why the email notifications are still worded that way, but you won't be able to find that button. ?

Hi @Neue Rituale Seems like a useful plugin. Thanks for sharing your work with the community. If there is a video to show how it works would be very useful. Gideon

I was addressing your first question This is a different question Have you read the Processwire Documentation ? Your answers are here: https://processwire.com/docs/start/variables/templates/ --------------------------------------------------------------------- Creating a new template with api <?php namespace ProcessWire; $fieldgroup = new Fieldgroup(); $fieldgroup->name = "something"; $fieldgroup->add("title"); // add some fields $fieldgroup->add("body"); $fieldgroup->add("summary"); $fieldgroup->save(); $template = new Template(); $template->name = "something"; // must be same name as the fieldgroup $template->fieldgroup = $fieldgroup; $template->save(); --------------------------------------------------------------------- Adding fields to a template with api <?php namespace ProcessWire; $template = $templates->get("some_template"); $template->fields->add("body"); // add some fields $template->fields->add("summary"); $template->fields->add("images"); $template->fields->save(); --------------------------------------------------------------------- Forum https://processwire.com/talk/topic/4921-how-to-create-template-file-using-api-under-a-module/ https://processwire.com/talk/topic/352-creating-pages-via-api/ Examples https://processwire-recipes.com/recipes/add-fields-to-template/ Beginner mistakes https://processwire.com/talk/topic/19415-trying-to-create-field-using-api/

Oh, not sure if that is possible. You can always create a separate field for description and make that required (then set the existing description field to 0 rows so it does not show).