Leaderboard

Here is the text, in a gitbook; hopefully nothing too controversial... https://outflux3.gitbooks.io/why-choose-processwire/content/ If anyone wants to edit, feel free; Also, i want to add some images – screenshots of admin, some gtmetrix scores of really fast sites, and icons here and there (that are in the original but didn't make it to the gitbook).

Cheers! Yeah, I guess I should have posted the link here, too. I've been developing with ProcessWire for a few years now (and bugging the community here with whatever issues I ran into -- which so far have always been my own fault!). I just wanted a place where I could explain how and why I picked ProcessWire as my CMF of choice, and to sort of explain a bit how this particular website gets made. I plan to add more to the blog about how some of the stuff works, what my rationale is behind some things, etc. Might not always deal exclusively with ProcessWire, but some upcoming topics will deal with how I handled the watermark branding on social media images (with the great PageImageManipulator module and some creative switcheroo in the PHP code of templates) and how I went about to create the structure and code for a timeline (which isn't online yet due solely to the fact that it has too little content yet). I always like reading patch notes, so I figured I'd add a changelog to the website to keep those who are interested in these kinds of things to keep track of changes that I implement. The roadmap is there to sort of explain where we're going with the website, even if one or two things that are a bit more experimental are kept under wraps (since they may never lead to anything); it also helps remind me what I'm supposed to be working on.

I have read some good posts here that make a lot of sense to leave pw with it's api, php and jquery. It was then the main reason why so many moved from evo to processwire. The forum was vibrant and newbies came in every week for the no nonsense, making so much sense functionality of processwire. To me it is always the same story: people just can't leave their hands from something that is working perfectly good. It just has to be stuffed, cranked, pimped or changed in some way or another. Oh "it is evolution" I hear you say "we have to go with the latest stuff that is going around". We'll why not change the use of php for ruby on rails then, that would be something cool, right ? Not ! Please don't crank the core and leave the back end with jquery. Instead we should put our energy in processwire marketing it's - no nonsense, making so much sense functionality.

I needed the same thing so i used Selectize inputfield single for the master select and then a select multiple on the dependent select, then i initialized the 2nd one using Selectize JS; the JS is not so hard, but you do need to have a custom select multiple that has a data-parent attribute on each option; those are filtered to match the selected option in the 'parent' select. Eventually this will make it into InputfieldSelectize somehow, but for now it's just done by adding JS, courtesy of AdminCustomFiles.. In the screen capture, you will see the left select, which may or may not have child pages; if it does, then the right one shows the children:

I went "crazy" quite a few times over all frontend churn as well, FOMO, etc. At the end of the day, use the best tool for the job. Right now, practically all of my needs are met with the following stack: ProcessWire UIkit3 (it's so good; but, but the horror of using UIkits classes in your HTML!) Some PW premium modules: ListerPro ProCache (it's become my build process tool; you can build UIkit3 with it perfectly fine; I'm dumping Node, Webpack, and whatever the "latest" way to do things is) FormBuilder Pulling in whatever packages I need via composer VueJS if needed (loading it via CDN, oh my god the horror!) Digital Ocean for hosting (manually configuring their Ubuntu LAMP 16.04 droplet... takes only a few minutes) If your clients want to use some crappy shared host, switch them to DigitalOcean; it's practically the same price. I develop all my sites on Windows (but technically it's Linux thanks to WSL). No VMs, no Docker (again, the horror of what happens if my server ends up being PHP v7.0.23 and my local machine is 7.0.22!). Simple and reliable 99.99999999999999% of the time. I deploy with a simple shell script (horror! not using Capistrano, Ansible, whatever the latest tool is). Sure, your site won't be able to handle all of earth's traffic if everyone were to visit your site at the same moment, but it'll be fine for 85.7% of the sites you most likely take on. I've built very complex sites with just those tools and I move extremely rapidly while keeping the site client-maintainable! Even if you became Mr. Expert on the latest frontend tools, it's going to change significantly by this time next year and the year after that. Perhaps sit on the sidelines for a bit. End rant.

Module updated to version 1.1.6, I fixed what we discussed here and included various small fix in ProcessDuplicator and GoogleDrive.

Lately I saw a documentation in german TV. They let people do some creative brain work that used the people highly to concentrate and focus on it. A few parts (3-4), where every part was no longer than 10 to 15 minutes. Another group has done the same, but after 1 or 2 creative parts, they had to do some repetitive or "stupid" or "dumb" work for 10 to 15 minutes, before they continue with the creative work. All people from the second group were much more effective in the later creative parts than the people from the first group. I personally would not call those intermediate parts "stupid" or "dumb". I call them activities with meditative character. ?

We relaunched the website for the famous Opernhaus Zürich https://www.opernhaus.ch with ProcessWire. Lots of stuff going on on the front-end. The "design" was made by an inhouse designer that also does their print work and previous website designs. We used patternlab node with mustache template engine as the design/prototype system. Building elements and component as kind of modules (mustache, css, js) which then are 1:1 imported into PW, which then can be rendered using mustache (php version) via a custom "controller" system.

Yep, ignore it! Bunch of google ass. My sites load well fast enough, google says otherwise of course. But my target audience is usually in the UK where people have quickish internet.

Add Image URLs A module for ProcessWire CMS/CMF. Allows images/files to be added to Image/File fields by pasting URLs or using the API. Installation Install the Add Image URLs module. Configuration You can add MIME type > file extension mappings in the module config. These mappings are used when validating URLs to files that do not have file extensions. Usage A "Paste URLs" button will be added to all Image and File fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved. A Pagefiles::addFromUrl method is also added to the API to achieve the same result. The argument of this method is expected to be either: a URL: "https://domain.com/image.jpg" an array of URLs: ["https://domain.com/image1.jpg", "https://domain.com/image2.jpg"] Example: // Get unformatted value of File/Image field to be sure that it's an instance of Pagefiles $page->getUnformatted('file_field')->addFromUrl("https://domain.com/path-to-file.ext"); // No need to call $page->save() as it's already done in the method Should you have an issue using the method, please have a look at the "errors" log to check if something was wrong with your URL(s). WebP conversion The core InputfieldImage does not support images in WebP format. But if you have the WebP To Jpg module installed (v0.2.0 or newer) then any WebP images you add via Add Image URLs will be automatically converted to JPG format. https://github.com/Toutouwai/AddImageUrls https://modules.processwire.com/modules/add-image-urls/

This week I've been back in the office and enjoying working on the core. Big thanks to Bernhard Baumrock for his great post last week about Process modules. I was offline for about 10 days, so version 3.0.85 of ProcessWire on the dev branch has been largely focused on getting caught up with and resolving issue reports (at GitHub). Though there are a couple new things too, which are covered in this week's post: https://processwire.com/blog/posts/pw-3.0.85/

ProCache is an awesome product with lots of features and Ryan's touch of mastership but for the less/sass compiling you can roll your own with the right PHP libraries, did it once myself with https://github.com/oyejorge/less.php Yes indeed! Actually working a lot on one a lot provided by LiquidWeb.

No way! That's sounds insane. You mean I could throw out all the JS config gibberish and actually make some websites? (and make a process module instead of sodding around with webpack which is teaching me absolutely nothing) Saying that, haven't got the £££ for procache right now. Bah!

And there are the so called "managed VPS" services where you get a preconfigured VPS, regular system updates, technical support and some other extras depending on the provider's actual offering.

VPS services give you a blank linux machine where you have to configure Apache/MySQL/PHP. Sometimes they include panel tools to automate some tasks, I have only used Amazon EC2 which gives you nothing but the empty Linux machine. I think small/medium clients who look for a "all-in-one" solution will prefer a 'normal' hosting. As it enables them instantly ftp accounts, mail accounts, etc. From what I've seen from @Jonathan Lahijani 's projects posted around here is that they are more resource demanding and complex from your average website, so a VPS feels like a perfect fit to achieve performance and simplicity/customization in the server setup. E.g. You need to install a particular php extension, need to use composer, etc. Yes my friend! As beautiful as you depict it. I don't know the specifics but probably checks for changes in the file on it's own, rerenders and caches it. I hope the AdminUIkit had a way to be hooked on ProCache to leverage the in-server compiling.

you mean this? http://modules.processwire.com/modules/fieldtype-fields/

I will try to find the time this week @szabesz Also, if you got 5 minutes and you still have the 1&1 host account, could you test duplicator on it ? I just built a package successfully on 1&1

https://www.pwtuts.com/processwire-tutorials/changing-the-default-admin-theme/ Came to the party too late though

Any news on this? A beta version maybe under the Christmas tree?

If you want a non-default theme, I would recommend setting the config variable in your config.php file. $config->defaultAdminTheme = 'AdminThemeReno';

Interesting read and a very nice PW site: https://www.ancientworldmagazine.com/dev/blog/built-using-processwire/

JQuery simplifies things for JS, just like PW does for PHP cms. You could use vanilla JS or another framework that would make things harder for devs. Would you use PW if it were more complicated to use or so basic like pure PHP? I think jQuery is still the right tool for PW admin, or at least I don't see any real advantages using another (or using none).

Just my opinion, but I don't quite understand whats the benefit to get rid of one dependency to immediately replace it with another dependency. I have no experience with VueJS or Angular yet, but as far as I can see, you would be completely dependent on one of those frameworks. In this case I'm maybe a little bit old school, but I like jQuery and also don't understand, why everybody wants to get rid of it as fast as possible. Also the comparison of ProcessWires API with jQuery was on of the first things, that got me interested. Luckily it is not our decision to decide.

Hi Everyone, all around the Internet i see developers advice to not depend on jQuery anymore, (Frameworks & CMS's ) for example: Bootstrap Bootstrap 4 Without jQuery UiKit Uikit 3 Beta-31-released Silverstripe CMS - Silverstripe and many more .. I wanna know what is the situation gonna be with (ProcessWire + jQuery)? Any RoadMaps related to it? The current included version in "wire" directory is jQuery v1.11.1 .. is it possible to use PW with Vuejs or React (I'm Talking about the core not the frond-end development)

REMOVED Free Processwire Template

Great! Thank you!

Very flashy Yeah that's a bit of a problem we had with the design concept being delivered to us, but you know how it goes. I think it's trying to solve the different ratio of the images they'd like to use, so it's a feature kind of (one of which I'm not very fond of) Homepage is on the logo. (I know)

Hi dragan, unfortunately not. I need to do a complete rewrite of the module. As i need it for all my projects it is on top of my todolist for the next year. I'm still not sure if I should release it free or as a pro module... But I hope I can release something around march 2018...

would be awesome if core natively supported dependent selects in repeaters!

Awesome! Looks like a great tool (features, UI) to work with.

Try ProCache and HTTP/2 https://caniuse.com/#search=http2

So true all what you've said @horst It is insane that we are sort of forced to adhere to google standards and not to common sense. However, I still find that content is king, so I do not push it too far optimizing things to google's liking. Instead, I tell my clients to write frequent news/blog posts. That works

Are, you are having a problem after upgrading to PW 3.0.85? If so, please provide some additional information that will help us help you. Thanks.

Depending on how complex your needs are, the core does offer some support. Use something like this for the selector value for a page field: parent=page.otherpagefield That allows for ajax population of one select based on the selected value of the otherpagefield

There's a commercial module for that:

Yep @ryan's method working perfect. $config->imageSizerOptions('cropping', 'north'); $config->imageSizerOptions('sharpening', 'none'); $config->imageSizerOptions('quality', 80); $config->imageSizerOptions('defaultGamma', -1);

THanks a lot the gamma setting solved the issue!

this is really a bad idea! with this, you wibes out all other properties of the imgaeSizerOptions: before your correction, the imageSizerOptions array contain items for sharpening, quality gamma etc. After your correction, the defaultGamma is the only one item. All others are wiped out! PLEASE, repeat all other items with there respective values, or use array_merge() !! $config->imageSizerOptions = array_merge( $config->imageSizerOptions, // all items from wire/config array( // overwrite specific items 'defaultGamma' => -1, 'sharpening' => 'medium' ) ); -------- But in @dreerr s case, I can't think of that this is the issue / solution. Disabling "defaultGamma" is usefull if you gets clippings in dark to black regions. According to what @dreerr describes, my first question is: "How does the original image looks like?" If this already has arctefacts, you ever will get artefacts also in quality 100. Where does the source- or master image comes from? What processes gets it passed through before the upload to PW? Any restrictions on upload? (max size?) Maybe you can provide a link to that image online, or via PM to me?

@dreerr I had a similar problem in the past and I fixed it by disabling the gamma correction. On your site/config.php add this: $config->imageSizerOptions = array( 'defaultGamma' => -1, // defaultGamma: 0.5 to 4.0 or -1 to disable gamma correction (default=2.0) );

I also listen to music when doing graphic design but only sometimes ( when getting bored a bit ). If I want to be creative I need silence. When doing routine work music is okay, however, when being creative or trying to innovate and/or develop I think any distraction has an effect, that is why I prefer silence in these scenarios.

There's a story from Richard WIlliams (Animators Survival Kit), asking Milt Kahl (greatest Animator who ever lived) if he also listens to classical music during work. Milt responded, that this is the most stupid question ever, and that he's too stupid to do more than one thing at a time. Richard became a better animator instantly not listening to music anymore. He educated many animators working on computer, very addicted to music, to stop it and they all improved in their work a lot. Since I stopped listening to music (which is hard at first) while programming or painting I noticed a lot of improvement in my work.

I learned with ProcessWire that the Internet could work just fine before single page applications I'd love some parts of PW to work as a SPA module, for example, a kind of template-field creator where you can create in a very agile way template-field relationships and the template context overrides. A kind of "template designer".

Good to see I'm not the only one scratching my head over the current jQuery-is-bad movement. To me, wiring in a full-fledged MVsomething framework only makes sense if the complete data exchange is abstracted away, otherwise backend code and frontend (speak backend UI) logic will get even tighter bundled (or bungled?). This would mean that all backend calls would need to be some kind of RESTful using JSON, XML or something along these lines, and plainly, PW isn't at that point right now and getting there would need quite a bit of work. I'm not a real wiz when it comes to MVC/MVVM frameworks, but I do have some experience building complex RIAs, starting by building everything on top of ExtJS (2 and 3) in the good old days and later rolling my own two-way bindings for nested data structures. I've recently delved a bit into the currently trending frameworks, and I was utterly appalled by the unnecessary complexity, semantic mumbojumbo and lack of essential features each of those exhibited in varying degrees. Don't get me started on the massive breaking changes introduced in major frameworks I see every year. I've got one really complex app that needs a larger overhaul next year (warranted after 8 years, I feel), and I've come to the conclusion that it will be simpler, faster and more concise to build everything without any framework besides a lean CSS library and perhaps jQuery, especially if I want it to run the following 5+ years without finding myself using an orphaned framework. If the PW backend could be completely JSONified, I'd be all for that, but even then, I'd currently prefer a framework-less default interface. Any MV* solution could then be an alternative, just like current admin themes.

Cool JS frameworks will become history just because sooner than later someone releases just another even cooler JS framework rendering the previous ones obsolete. BTW, the WordPress guys have been debating for months or maybe for more than a year which one to pick... On the other hand, jQuery is still going strong as others have also pointed it out above.

I'm very interested why foremost it's age is a good reason to turn away from jQuery. It's no new cool kid on the block, but it is matured, very well documented and wide spread. It was no "dead end" like some of the other "cool" JS frameworks have been. It feels like a good ol' companion. It's not the right tool for every job nor a holy grail, but in pretty much use cases it works well and affordable in a sense that there is no steep learning curve.

I'm not strictly against ditching jQuery in favour of Vue / React / whatever it is that all the hip developers use right now, but it's true that this would be a major change, and I'm not sure how much sense it would really make. "That's what others are doing" is not a very good reason in itself, but if it would enable us to do something that we currently can't, I'm all ears (Note: in the end this decision is obviously up to Ryan, and as far as I know there are currently no plans for ditching jQuery / jQuery UI.) Personally I'm still somewhat fond of jQuery. It simplifies a lot of stuff, deals with browser incompatibilities, and provides polyfills for some missing features. It's not the best tool for massive JavaScript applications, but that's not what the admin is all about either. Also, minified and gzipped jQuery 3.x is 32Kb, so anyone calling it "huge" could use a reality check. Sure, it is huge if you're only using it to implement a simple slider or menu or something along those lines, but that's a rather limited use case. That being said, it is true that the core is currently using a relatively old version of jQuery, so going up a couple of major versions could be a good first step? --- On a related note: at least a couple of third party modules already use Angular, and back in the day Antti even released a module that automatically loads it. For third party stuff it could make sense to build a set of modules for loading common frameworks and then require those as needed. That won't solve the problem of having to load jQuery and it won't make the entire admin a Vue/React/whatever app, of course.

For me, the reality is that when I use "vanilla" scripts, each one coming from different developers with its own code for dom traversal and manipulation, yes they are in plain js without dependencies ... but with a tons of redundant code for the same tasks ... so when I finally managed to finish a complex website with sliders, accordions, calendar, date selectors, drop-down menus, parallax, forms and looong, etc. each has its own code to select nodes, add/remove classes and looong, etc. I have a lot of repetitive code, for what? For a trend? yes it's true jQuery 1x is obsolete and fat due to the support of old browsers, but jQuery 3x is as slim as you need. The reality is that we need a library for common tasks (give it the name you want). For today jQuery allows me to do simple tasks on a regular website without additional efforts (ie a website like processwire.com, not a web application, or a project for Córdoba).. well.. if someone create that library, pleeeease use an API similar to PW/JQUERY.. it's so easy to use and learn for us, the non pro developers!!

If Jquery is removed i'd like to see plain vanilla js and no framework in between. Just like like there is no PHP framework in PW.

What do you do with this — I'm dense today.

Use the dev branch of ImageExtra - it is supposed to be fixed there: https://github.com/justonestep/processwire-imageextra/issues/18