Leaderboard

This latest version on the dev branch continues resolving GitHub issue reports as the last few versions have done. A new page finding capability has been added as well, and that's what we'll focus on in this post: https://processwire.com/blog/posts/processwire-3.0.91-core-updates/

What I would really like to see is more expanded multilanguage support in the core as 95% of my sites is ML. Very often I need to have some pages available only in non-default languages and every time I have to reinvent the wheel with custom logic. Almost in all modern CMSs (Statamic, Craft, October ..) you can separately publish or unpublish pages for every language even default. There are @adrian's module and request which intended to solve this issue via a module, but as I said, I think that it should be in core.

Here's a document I've been working on https://docs.google.com/document/d/1peY-FUpevKgy87cKOxIVz8jwcv2-3c61zbiJr3QKO6c/edit?pli=1# Flexible Page Layouts in Processwire. It's still rough, but I've been using it to help collect all my thoughts/notes on all the ways to achieve flexible layouts in Processwire. I love hearing about other ways people are structuring their websites. Here is another document that helps me wrap my head around some of the different field types in Processwire. (all on one page) https://docs.google.com/document/d/1VcSluQyjl9AhMBcJA3R4-uZb9IUYdKXGSh7Phclf34Y/edit?pli=1#heading=h.ysvx3k7ssuw7 Hope it helps someone.

Hi and welcome! Advice: Definitely stay in the admin! I had exactly the same thoughts before I created my CRM because modifying the admin seemed totally complex and out of my scope. But once you get the concept it is REALLY simple and you get all the benefits that the pw backend offers (all fields, all functionality like login, sanitization, field collapsing, hooks etc). That's why I created the blogpost that Robin linked to (thx btw ). The ROI (return on invest) of digging into the PW admin is huge and it will help you a lot to improve all your pw related work, because you will understand everything a lot better. I wish you good luck and a lot of fun

Here we go .. The basic idea is an textarea fieldtype with a function somewhat similar to an website blocks builder, I know that currently this can be achieved using a Repeater, Repeater Matrix or Hanna Code, but perhaps this way would be easier for the developer/user and more flexible. The idea came after seeing this plug-in: https://formbuilder.online/ ... and the implementation could be based on these modules: https://github.com/blynx/TextformatterFunkyFunctions from @blynx https://github.com/outflux3/SettingsFactory from @Macrura https://github.com/Toutouwai/HannaCodeDialog from @Robin S Based on TextformatterFunkyFunctions we would have a folder for this type of field with the design blocks that we want to make available to the user: These block files would have main three sections: The Settings section for the Block UI could be based on the SettingsFactory code. A mockup of the user interface of the field would be: It would have drag and drop to add and sort the blocks, and display the generated Form by each block in order to enter the block data The field will have three display modes in the backend: BUILD - the first where field content is configured in visual and interactive mode: CODE - The second is the "real" configuration of the field as required by TextformatterFunkyFunctions and is the data that is stored in the Processwire DB. This mode could be hidden for some users: PREVIEW - The third one is the visualization of the field output, it could be done using Ajax requests to the module into an iframe or inserting the response in a DIV using jquery. Maybe some code of this module will work: http://modules.processwire.com/modules/fieldtype-runtime-markup/ from @kongondo I hope that I have been able to explain the idea correctly, but I can not wait for it to be inspired to make a perfect explanation, .. waiting for that moment and it has been in my trunk for a long time .. It's just an idea to debate, maybe it will be an inspiration for other things, or for someone who wants to develop it (as a commercial module or not)

@geekpete, Welcome to ProcessWire and the forums. In addition to what has been said, especially the comment about roles and permissions, just remember to test your work/module as both a superuser and a normal user. Some stuff will not be viewable, editable, etc, by default for non-superusers.

Thanks again all, I am sold Just setup a dev install so I can start to understand how I can use the PW admin in more detail.

Preview of upcoming Media Manager Version 012 Better, cleaner, ProcessWire 3 UI! Custom columns (add custom fields to media templates; frontend access via API: e.g. $m->email; $m->body, etc) Edit media page directly Ajax update of Media Manager field on a page Disable media views centrally (e.g. manage only image media) Add extra images to image media field (e.g. front, back, top, side views, etc of an image) Better media previews More..... ETA: 3 - 5 weeks Early screenshots (some stuff subject to change)

Download the plugin from the site and uncompress it. Upload the plugin folder under site/modules/IputfieldCKEditor/plugins, activate the plugin in the field configuration in PW (at the very bottom you will see a group of checkboxes that already includes the PW CKEditor plugins for image upload and links, you should see the uploaded plugin now). Check it. As stated above, add the correct option in the toolbar configuration. and you should see it in the editor now.

Markup Regions are a godsend if you want to code HTML directly rather than adding it as strings to PHP variables. Alternatively you can use output buffering (which is what I preferred before Markup Regions were introduced). <?php ob_start(); // $main_content ?> <div>Your markup</div> <?php $main_content = ob_get_clean(); ?> For a project like yours I would be inclined to try building it within the PW admin as a first approach - you can do a lot with the admin (it's just an application built using the PW API) and it's pretty easy to tweak it with hooks and custom CSS. I think it would be much quicker that way. @bernhard has written a helpful blog post for getting started with Process modules, and check out his Showcase topic for the kinds of things that are possible:

Hi All, First post here so wanted to start by saying how much I'm liking ProcessWire. Come from an ExpressionEngine / CraftCMS background I'm building a backend type service website where I have about 10 'admin' pages to view orders, upload orders (as well as a few other entities) extract data etc. We are not talking about millions of records, thousands a month top so I thought I could use the 'page for everything' approach. Initially I was just going to use the PW 'backend' and let the end users onto it i.e. The part you log into by default at /processwire and write some modules but having things like the settings tab on pages and some of the other bits an end user might not understand made me feel my own frontend would be a better idea. I've got things up and running with a custom login that uses the PW authentication system and am building a nav no problem, using selectors for data etc (which by the way are awesome!). So now I've settled in a bit I've come to structure my template files better and have read here.... https://processwire.com/docs/tutorials/how-to-structure-your-template-files/ Delayed output looked like the most flexible strategies (and easy enough to implement). However, bear in mind each of the pages are unique in their functions so essentially I have a header / nav etc, then the page specific block and then a footer. The page specific stuff is quite large and a lot of the time HTML with a sprinkle of PW / PHP bits. I didn't want to do this.... $main content="<div><ul>.........." ($main_content gets used in main.inc as per 'structuring' link above) Its gets quite cumbersome with a large block not to mention I lose some nice features in PHPStorm as it just sees it as a string. So what I've been doing is this.... <?php require("./includes/login.inc"); require("./includes/init.inc"); $main_content = $page->render("partials/" . $page->template->name .".inc"); require("./includes/main.inc"); ?> I now need to keep creating the matching .inc files. Is there a way I can use just the one template file file to set $main_content in some cunning way that enables me not to manage the string building? Am I approaching things right? I know I can just include a header, splurg the content and then include a footer but I liked the 'Delayed Output' approach for the flexibility. Sorry if its a silly question everyone, still learning, only a few days in and I'm no PHP demon, no giggling at the back hahaha

https://thesmartgroup.ie/ We launched this earlier in the year, I'm only just getting round to sharing it. This is the 4th iteration design wise in the past 5 years and personally my favourite in terms of design. The old site was PW based so we had a lot of the content in there but undertook a major re-write and claw back to make everything cleaner and more succinct - relying on more visuals to promote the work we do rather than verbose copy. The site is not using anything out of the ordinary, just standard modules I tend to use for all PW sites: AIOM SEO Markup Sitemap XML AutoSmush MenuBuilder: Markup The site loads pretty darn quick considering it's using a lot of images and many of them are 96DPI for better display on Retina.

I don't think it needs to be automatic, but perhaps the instructions could be expanded. Currently all they say is: "Create your processes then enter a path to the json or php definition of the fields in the path field." and that didn't initially make sense to me. I think spell it out: 1. Create a page under Admin (at the top level or under Setup if you prefer) 2. Save the page and then choose the ProcessSettingsFactory process from the dropdown. 3. Enter the path to youre settings file. Not sure using a placeholder is good the way you did - I actually thought it was already filled out with: settings/site-settings.php I also think you should say included "samples", not examples, because of the folder they are stored in. Hope that helps.

Hi @WebMaster As far as I know, current only ImageExtra module adds support for additional fields for images. Native support for additional properties in image/files fields is on the roadmap for 2018. For now, the most flexible route for you is to create a page for every image, in that way you will get all PW features. There is module that can help with this approach https://github.com/mr-fan/AutoImagePages Do you mean that you can't sort and search by custom ImageExtra fields?

For me it's a mix. I really like a GUI for visually reviewing the code changes in all files before committing. But for checking out and pulling updates from other (not my) repos, I use the command line.

This, every day of the week! Always keep in mind that the PW admin is basically a blank page with a masthead (or sidebar haha), everything else is optional through roles and permissions.

Love the UI update,I think it's something that is really going to round up the module, congrats @kongondo you rock, aweome work!

I make the field non required - it is the most simple way

Keep in mind that the regular processInput method is still called afterwards, so any assignments to the page's fields will be overwritten by the submitted data. You need to fetch the $input argument from $event->arguments(0), read the submitted value from there and assign your computed value to $input["reservationdeadline"] (peek into the POST data in the developer console if you're unsure what date format to use). Don't modify $page, let the regular PW logic handle that part. Though you'd probably find it easier to remove the "required" option and run your logic in a saveReady hook.

Hi @Juergen SchedulePages module has similar functionality and it's done via hook to after page save https://github.com/formmailer/SchedulePages/blob/master/SchedulePages.module#L105 https://github.com/formmailer/SchedulePages/blob/master/SchedulePages.module#L138

Yeah, the "user-admin-all" is very strangely named I think: https://processwire.com/api/user-access/permissions/#user-admin-permissions The description says that it reduces the user's rights to guest users only and then you build up from there with the user-admin-[role] option. All that said, I still think we need a way to let a user with some user-admin permission create another user also with this ability. Otherwise you can't let a client handle the creation of new users in their organization who can also do user management.

@Gideon So You have to increase the memory_limit, post_max_size & upload_max_filesize via cPanel's "Select PHP Version" by clicking on "Switch to PHP Options".

Bravo!!!! Very very beautiful; i have buyed the module a year ago.... and it work very well. The new ProcessWire 3 UI seems perfect.... Do you release a beta?

It's in vogue at the moment I used the vue.js component for it but here is the script for the plugin: https://mattboldt.com/demos/typed-js/

Thanks Adrian! I can understand the decision about it. The problem is that is not clear. If you add a permission "user-admin-all" you expect that the user will be able to add to all users any roles BUT the superuser's. That's why I got confused.

Hi @geekpete, welcome to the forums. As Robin S. said, there are better alternatives. I'd like to suggest @tpr's module Template Latte Replace This is a great template engine that I'm truly happy to use on more complex websites.

I just came across this also. I think that even though this is clearly intentional: https://github.com/processwire/processwire/blob/bafe3d4a1289f6d225c657c4206c27c7a27a5b14/wire/modules/Process/ProcessUser/ProcessUser.module#L211 it is problematic if you want to give a user the ability to create other users with the ability to also create users. I think this should be a Github issue - anyone else have any thoughts? If you need a quick fix, you could comment out the line shown above.

@Robin S You are my hero. Works like a charm and I learn something new about Processwire everyday with the help of all the great community here. Gideon

The idea is get something simple to setup and simple to use.. the Matrix usually is complex to setup and fine tuned, and sometimes complex to the user, mainly when have depth.. and near to impossible to reuse it in other projects.. ah! and is not cheap too.. I was thinking in something simple and useful for build basic landing pages, ..easy to copy to another projects.. sometimes when we have many pages with crazy designs that not fit the regular "basic-page" (main+sidebar) or similar, we start to fill the site folder with several templates files.. but it's only and idea to refresh.. for me make sense.. or perhaps having a Textarea that store unrestricted HTML and can be edited with something like this http://grapesjs.com/

Community wise... I would like to see more examples of **How** people built their Processwire websites. It would be awesome if ever so often we could some how host a Google Hangout or use https://www.crowdcast.io/ to pick volunteers from the community to showcase their Processwire websites and do a site walk through. Here's an example of something similar https://zendev.com/2017/08/31/grids-grids-and-more-grids.html where they talk about Zurb's Foundation CSS/Javascript Framework. They called it Foundation Open Chat https://zendev.com/category/foundation-open-chat.html As you can see they can be embedded into a blog post as well. Well I just saw there is a cost to using crowdcast.io. That might not work, but maybe Google Hangouts or YouTube Live would? I believe they do something similar with CraftCms https://straightupcraft.com/hangouts During those sessions we could: ask questions about the site or Processwire? get to know more about a person behind the avatar? talk about the site's pain points and how the developer was able to work around it? cool module walk throughs or new module showcase? talk about how the site is output? does it use a template engine? Twig, Latte, Mustache, PHP, Processwire's Delay Output Method, etc.. talk about the site's tree structure? talk about the site's hosting environment? ...Just some thoughts I had

I think this is the new current feed

Just recently set it up on my VPS - not particularly tricky but there's a potential gotcha in that Apache mpm prefork (whatever the heck that is) doesn't support http/2 so you need a different kind of prefork. https://http2.pro/doc/Apache got me through it. BTW if you have that kind of control over the server, mod_PageSpeed can help by at least serving webp instead of jpeg to supporting browsers. (There's much more to it as well, but the jpeg to webp thing is out of the box.)

Not totally sure what you mean - you just want to save having to click "Add Filter" to add an email address row? You can use a hook in /site/ready.php: $wire->addHookBefore('ProcessPageLister::execute', function(HookEvent $event) { if($this->config->ajax) return; $process = $event->object; // Just for the Users lister... if($this->page->name === 'users') { // Add to existing defaultSelector (or alternatively you could overwrite defaultSelector) $process->defaultSelector .= ', email%='; } });

Nice site @patricktsg Good to see another Irish user of PW here. BTW love the 404 page