Leaderboard

ProcessWire ProFields is new product that will soon be available in the ProcessWire store. It consists of 4 really useful new modules: Textareas (Fieldtype + Inputfield) Multiplier (Fieldtype + Inputfield) Table (Fieldtype + Inputfield) AutoLinks (Textformatter) These modules are currently in beta testing, and I'll be posting screencasts to highlight some of the features of each over the next week or so. To start with, here is a screencast for Textareas: This video includes sound (narration) and I recommend viewing it at a larger size than above (preferably full screen), and bump it up to the 720p resolution so that you can see everything in better detail.

This module is improved and extended successor to Version Control For Text Fields. It handles everything it's predecessor did -- providing basic version control features for page content -- and quite a bit more. Download or clone from GitHub: https://github.com/teppokoivula/VersionControl. This module requires ProcessWire 2.4.1 or later, mostly because of the file features, which require certain Pagefile and Pageimage methods to be hookable. There's no sensible way around this limitation; for those stuck with < 2.4.1, Version Control For Text Fields will remain a viable option. What does it do? While editing pages, fields with old revisions available show up with a new icon in their header bars. By hovering that icon you get a list of available revisions and by clicking any one of those the value of that particular field is reverted to that revision. No changes are made to page until you choose a revision and save the page, which means that you can keep switching between revisions to get an idea what's really changed without inadvertently causing any content to change. The module also adds a History tab to page edit. This tab opens a view to the history of current page in the form of "revisions" -- each of which is a group of changes to page fields processed during one page save (similar to revisions in various source control applications). There are three actions you can perform on these revisions: adding comments, live previewing what the page might've looked in that revision and restoring the page to specific revision. One specific feature that has been a big thing for me personally is support for file (and image) fields, as the original version control module felt rather incomplete without it. I'm hoping to take this a lot further performance, stability and feature wise, but as it stands right now, it's already included here and should be fully functional. Watch the video preview here I prepared a little screencast outlining most of this: http://youtu.be/AkEt3W7meic. Considering that it was my first screencast ever, I'd like to think that it wasn't that bad.. but I might give it another shot at some point, this time planning a bit before hitting "record" Upgrading from Version Control For Text Fields For those already using Version Control For Text Fields, I've added something extra. If you upgrade that module to it's latest version, you should see a new checkbox in it's settings screen saying "Don't drop tables during uninstall". If you check this, uninstall the module and then remove it's files (this is required in order to install Version Control), your old data should be automagically imported to Version Control. Import has only been tested with limited amounts of demo data. Proper tests are yet to come, so please be careful with this feature! Update, 21.6.2015: as of today, this module is no longer in beta. While all the regular warnings still apply (making changes, including installing any new modules, on a production site should always be considered risky) Version Control has gone through pretty extensive testing, and should be as stable as any other module out there.

Hello fellow ProcessWire devs. I recently developed and launched the following site: http://whiteconst.com/ Specs: PW 2.4 Zurb Foundation 5 Full width layout + responsive design; font-scaling in certain situations Ajax page loading; window history pushstate CSS3 based loading animations (page to page, project modal) Heavily animated home page slideshow (built with sequencejs) Developed so that every page is properly indexed by search engines despite used of Ajax (each page has it's own unique URL; canonical meta tags also indicate to search engines what the official URL of a page is to prevent duplicate content cases) Form Builder module Hanna Code module XML Sitemap module Video Embed for YouTube/Vimeo module (don't know about this one? you should!) Custom module to that allows administrators to view all projects in the admin section using a table layout with more metadata screenshot: http://goo.gl/3HfJTW Custom modal to view projects Custom developed news blog (with categories, year archives, recent posts filters) Content is easily manageable by site admins All kinds of frontend coding to make the layouts look great, especially the project pages (image gallery, videos, etc.) This was a challenging project for several reasons. Several requirements and layouts were changed along the way. Also, whenever dealing with Ajax based page loading, that seems to complicate things by a factor of 3 (must take many other things into consideration for it to work properly and lots of edge cases). This was also the first PW site I did that needed a blog / news section. I didn't start with the Blog profile, but this was easy to roll. In fact, I like being able to build out the blog myself because of the greater control it provides. I wanted URLs to be formatted in a particular way. It needed to be Ajax based. I like naming things my own way (Blog or News? Post or Article?... WordPress's defaults are extremely confusing to the end user). At the end of the day, ProcessWire was a perfect fit for this project. - Jonathan

Sure, there are many. Let's be clear: Don't know ProcessWire exists Never had any experience with it and worry about the learning curve Don't see any books about it Don't see lots of themes for it Worry about commercial support for PW Don't know anybody who uses PW Web host doesn't offer pdo_mysql (for example) Plan on blogging and don't see much blogging info for PW Need a website for posting photos and words, and their nephew offered to install WordPress for free PW certainly has an audience that is some subset of, or some small intersection with, the WordPress audience. But comparing CMS to CMS, there are so many differences in the community alone. If your goal is to attract more of the WordPress folks, you'd probably want to identify what type of WordPress folks first, and then provide resources and communication that attract them to PW. I have to explain to about one out of three clients that I did consider WordPress before suggesting ProcessWire. To them there's a bit of a risk with this ProcessWire thing. If I mess up the job, it becomes one more pain point. "And what was this Process thing he suggested? There are ten guys in town who do great WordPress sites!" These clients usually already talked to three or four people who seem pretty savvy, and a few people around the office, and most of them said some variant of, "if somebody could set up a WordPress site for us, we could take it from there." This is because there are a lot of people who work with WordPress, understand what it can do, and who maybe aren't--for various valid reasons--aware of ProcessWire's existence. So there's some fear about ProcessWire when it comes up. Sometimes. Finally, WordPress is not just a CMS; it's a community and a business (well, Automattic is). Automattic might at some point do the equivalent of Facebook buying Instagram. They might pick up or bring on board some other really sharp CMS, and ProcessWire users, the Instagrammers of the CMS world, might start to wonder when PW is going to turn really hard in whatever the new direction is. Or maybe they should start using this new Automattic thing. You never know. But with all that said, yes, ProcessWire is an amazing tool. Fresh off of a WordPress site build myself, I have to say I can see why people are so keen to jump into building their own tools. They want something that fits better. Which is, I guess, how we got ProcessWire. Maybe the cost of the precise fit for us PW users is some chunk of audience that would otherwise come from e.g. the WordPress community.

When we were evaluating CMS solutions a few years ago, the main reason WordPress seemed inviting was the availability of themes and modules, both free and commercial. In a nutshell you can just register to any of those theme sites popping up everywhere and (for a very modest price) get hundreds or thousands of great-looking themes. Grab one, customise it a bit (change the logo and perhaps a few colours) and show it to a client. Congratulations: if the client is happy with that, you've just saved quite a bit of work. That's not what you'll want to do when a client wants really customised look and feel or a set of custom features running behind the scenes for their site (which is exactly where ProcessWire shines) but for those clients that don't care if it's unique and 100% customised to their needs.. well, you get the idea. If the client later decides that he/she needs something more complicated, offer them an upgrade to ProcessWire Custom work, whether it's design or programming, takes time and costs money, period. ProcessWire makes development fun and easy, but won't do it for you. You'll still have to do the work and the client will still have to pay for it. For the record: I'm not saying that one should ever use WordPress (don't get me started on the downsides), but I can definitely see why some folks would prefer it. We've chosen ProcessWire as our main tool and never really looked back. It's working amazingly well for us and our customers.

All the WP sites I did in the past (way too many of them, now I switched entirely to PW, I even redid whole clients simple "brochure" websites pro-bono to save me the hassle) have been ok, but there's always something with the API that doesn't work quite right (future dates in queries, good luck!), maintenance issues, compatibility issues (loading 10 versions of jquery and the like). Some things might work right when developping, but often I need to change the plugins code to improve them, which is a problem. Then when new versions of everything comes out, it's a mess. WP sites don't seem to grow very well either, so as complexity increases, it all falls apart. Speed issues are also a big thing and really hard to optimize to get good load times. All that time waiting for the admin to do stuff is wasted time in billable hours (I charge a minimum of 30 mins for maintenance, most things take less than 15 mins to do, the process is usually much faster in PW I've found so far). Also take into account that when you do full-custom work like I do (I'm a designer AND a programmer), WP always comes with either too many or not enough features. That's time I need to just do configuration to get rid of the unneeded parts, which sometimes isn't really straightforward. I also do a lot of multilingual things, WP can do it with plugins, but the workflow is kinda weird and involves a lot of support calls from clients. Some of the features don't work so well either. So far what I've launched with PW is trouble free. It does everything much better and faster. I can say with big relief that WP's custom post types are a thing of the past. I was able to implement different relatively "complex" things (well, would be in WP) like 100% custom event systems, payment/donation systems, etc (hopefully will be able to package some of them nicely to reuse later and share in modules) in next to no time. Now I'm happier, clients are happier, work is faster, everybody wins.

@Soma, I just setup the whole thing, see: https://github.com/owzim/PWCaptainHookCLI Now the output of the array only has to be integrated into your html.

yes i like wp for.install exploit script , irc bots , pharmz , game servers etc without wp i wolud have.to get my own hosting

I am continuously bombarded with Wordpress this and Wordpress that, from all directions on how it is the best cms and the go to cms out there. It is starting to get a little silly. I can hardly read an article or visit a page without the mention of the holiness of Wordpress. It seems to have become some sort of mantra. Of course i don't agree. But it got me thinking. Are they all wrong? Are there any circumstances or reasons that anyone would use Wordpress over Processwire for a particular project?

How clever do these people sound to you? http://www.blackhatworld.com/blackhat-seo/white-hat-seo/672816-whitch-web-engine-should-i-choose-my-niche.html

I love how this Module is clearly excellent for larger sites, useful for any site but not essential to building brilliant PW sites. Building an income stream for PW is a healthy thing to do and like the rest of PW it's clearly being done with care; thanks for this and the upcoming great new tools Ryan And nice to hear, from the vocal commentary, that not just the Admin i/f has a theme

there is a module: https://processwire.com/talk/topic/4758-release-pagetree-add-new-child-reverse-on-top/ ------ Attention: It is pretty fine to install it before starting a new branch. If you want to install it in a site for an already existing branch, you 1) have to move / rename your existing branch, 2) create a new (empty) branch with the original name 3) move your childpages into the new branch 4) remove the renamed (and now empty) parent page

@darrenc In addition to adrian's remarks above, I've found that Ryan is great at picking up a good idea from a pull request and making whatever adjustments he feels necessary to slip it into the codebase. Don't worry about dotting every 'i' and crossing every 't' at this point; just get used to git and github and then make sure that your proposed changes make sense and have a good rationale and you have a good chance of seeing the code get accepted even if it is modified along the way.

This is awesome Teppo! Of course near the end it looks like many versions are created as adding images saves the page behind the scenes via Ajax so that's one way you'll end up with a lot of revisions (did I remember that correctly or make it up?). I'm wondering if it's worth making it so it only stores revisions when updating image and file fields AFTER the Save button is pressed? Or did you already take that into account? Loving this module and it will be fascinating to see how you handled the image and file fields when I dig into the code

I'll keep it short: no. The longer version is that every time I've dealt with Wordpress it was to upgrade it due to security issues and every time I did that it broke a plugins and updatingthe plugins broke some template or other. Now I don't accept work with Wordpress unless it's to move a site away from Wordpress. The problem is that so many people out who use it are oblivious to the security issues that keep cropping up in their software but if you look at the update history every 2-3 updates fixes some XSS or other big security flaw. I actually used a hint from a website that allows you to check the version of any Wordpress website to highlight the issue to a customer whose WP was about 5 versions behind so you can - if you had the time - let folks know just how out of date and unsecure their sites are. This is almost certainly how hackers target sites too. You can do the same for Joomla easily too (same customer had a Joomla site on the early 1.x branch - some 15 versions behind the latest in the 1.x series and well behind the 3.X branch of course!).

PW is chosen, WP is followed.

If you have little to no web development skills, WordPress is probably best platform for throwing together pre-made themes and plugins to create something resembling a website or blog that is relatively straightforward to manage. But it won't necessarily be "good." Scalability, extensibility, customisation, performance, suitable page size, code quality, upgradability, integration... many things that are an afterthought, difficult to accomplish, or require even more mediocre plugins to address. I can't think of any projects where I would use WordPress over ProcessWire.

The instructions for this module say to use the path relative to your templates directory, eg: styles/mystyles.css or scripts/myscript.js There is a setting in the module config: "Allow Directory Traversal: Enable the directory traversal option to make it possible to add files from outside of the template folders. (../)" which you can use if you need to access css and js files above the templates directory, but otherwise they should all be in subfolders of "templates" and linked to with a path relative to templates. Make sense? EDIT: not relevant to this module, but path vs url - depends on what is being done with the file being linked to. If it's a css or js file, typically you are going to want the url option. The path option is the full server path to the file which is useful for php operations on files, but no good for front-end display/calling of files.

Ok, let's make it really simple for people using chrome to do this If you are using chrome do this to have PW search with google on the omnibox by simply typing "pw [spacebar]" 1. right click on the omnibox and chose "Edit Search Engines" 2. scroll down until you find these input fields 3. Fill them as in the image: third field should be https://www.google.com/search?q=site:processwire.com%2Ftalk++-site:processwire.com%2Ftalk%2Fmembers%2F+-site:processwire.com%2Ftalk%2Fuser%2F+%s This is the equivalent to this search in Google: "site:processwire.com/talk -site:processwire.com/talk/members/ -site:processwire.com/talk/user/ %s" where %s is the query 4. type "pw [spacebar] Edit Search Engines" and see if this thread appears in first PS: I'm sure there is an equivalent way to do this in other browsers, but I'm not going to look for that now. Edit: simplified the url

Hello, I found some code examples to build a frontend user login. I thinking about a little module/ extension for it... but after some searching I've the question what could be the best way to do it... Login and logout already buildin with the following methods $session->login() $session->logout() API pages: http://processwire.com/api/variables/user/ http://processwire.com/api/variables/session/ How to create a new user or set a password found here http://processwire.com/api/variables/user/ So I need custum methods to register a new user, update password/ profile and reset a password. The needed code could be found here at the forum https://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/page-2?hl=%2Bregister+%2Bconfirm#entry50183 https://processwire.com/talk/topic/4066-activate-user-account-via-email/ https://processwire.com/talk/topic/107-custom-login/?p=11290 ... But I think it's not needed to create a new class with all methods and so duplicate/ wrap already existing functions... Should I hook into session or user to add "missing" methods? How to addHook found here: http://processwire.com/api/hooks/#add_new_method https://processwire.com/talk/topic/1186-how-do-i-extend-user/?p=10507 It's my first try to build a pw / php module... so be forgiving my stupid questions

Hi all, today I stumbled upon yeoman and went searching for a PW generator. Larry Botha mentioned in a side not in his thread about MVC template approach that he has put a yeoman generator for PW together. I test installed it and it is working great. Pretty fascinating how quick we can setup a PW project with yeoman. This definitely can be a great timesaver. Larry's generator sets up a pretty opinionated PW install with his MVC structured fixate template and KSS etc. It would be great if we could have an unopinionated version that gives us a clean PW install. We could add options to the generator for installing a choice of boilerplate templates like the blank template, Foundation, Bootstrap, Blog etc. Just wanted to get your opinion on this. If any of you are interested, we could pull something together. Cheers Gerhard

TextformatterThinspace is a trivial text formatter that removes repeated spaces (either ascii or non-breaking) and repeated newlines, replacing them with just a single instance.

I do believe a new standard for screencasts has just been set!

Despite the challenges it looks like you had fun - nice project to work on by the look of the end result

@diogo - nobody asks the guy what he wants to do, but "there's a plugin for that" (paraphrasing Apple of course ).

I have also created a helper some time ago specific for InputfieldTinyMCE to strip non breaking spaces in text on saving. https://gist.github.com/somatonic/10330802

and pump the volume up

Would you choose a premade cake over a selfmade cake?

Just a reminder: above module is only useful if sorting cannot be set based on some field or created date for example.

In fact, I'm not done yet. If you've got Chrome, download this free tool to check for outdated versions of Wordpress, Joomla and many more as you browse the web: http://www.whitefirdesign.com/meta-generator-version-check?pk_campaign=MGVC-Chrome A cursory look at web dev companies in my local area shows an alarming trend not updating Wordpress. One company has their own site running version 3.3.1 which is from January 2012. 30% of their portfolio shows out of date installations (could have been higher but two links were incorrectly linking to other sites in their portfolio and not all are necessarily built in Wordpress). Another agency had more than 50% of their sites running older versions of Wordpress that are vulnerable to attack. *sigh* But it perfectly highlights how complacent people get with updating Wordpress. If you're not going to bother checking for updates for software on client sites, build them solely in HTML and at least they're not at risk.

Huge release! Congratulations Teppo! I love the preview UI, very neat.

I just don't understand how the guys making Wordpress could still have enough XSS and other serious bugs I'm their code that every few updates fixes another one. So if you have a client that's set on Wordpress and doesn't heed warnings about security updates and the fact they'd have to pay you to update is several times a year just to keep it secure then don't take them on. It will only lead to headaches for you in the long run.

Amazing module with impressive ease of use! And really slick and jaw dropping inline-page-version preview!

Very nice and I believe it will be a very useful tool.

adrian, extremely helpful and that completely makes sense. I'll brush up a bit more on git and then go from there. Thank you for following up.

I can't say I use PW for a long time, but I as a basic php coder/designer (newbie) I am definitely sold to PW. Can't tell you enough how painful Wordpress and Joomla are. True there are many plugins available, but none of them are same preferred coding. On top of that they all interfere with CSS because of integration in these plugins. Many times, even if you find a nice theme, you end up searching which part was doing what that you want to modify. In the time I have used PW I never once looked back on other CMS because PW give me the feeling truly anything is possible. Besides, I like the learning curve of it. I also called some payment providers Mollie/iDeal to see if integration is possible, and of course it is. That will be the next fase in my website design. Thinking SEO, layout, coding, security, any kind of website - PW is my favorite!

I do use WP for a couple of blogs, though I probably would not bother now as when it comes to integrate with social media and things like open graph, it is easier to do that in PW, to be honest. Outside of that, I find it cumbersome. Edit: One thing I would add is that because WP has a huge, non technical user base, they have spent a lot more time thinking about usability that some other CMSs like Joomla or Drupal, and I think a lot can be learned from them.

I hear with ravensburger you can have beautiful paintings on your wall too, some people will be satisfied with that. Other people prefer a Dali, da Vinci or van Gogh. I prefer a framework where i can decide how to do the things i want to build, not the other way around. ProcessWire gives me that freedom. Like Craig mentions i wouldnt knwo any project i build in the past two year or so where i would use Wordpress over ProcessWire

I respect Drupal, but strongly dislike using and developing in it. This comes from a couple years of developing sites in it. The problems with Drupal have certainly been a motivation in making ProcessWire happen. Out of the box, ProcessWire is going to be a lot better at the large scale than Drupal. ProcessWire's architecture, foundation and API are far better than Drupal (captain obvious). People may use Drupal at large scale, but I don't believe the product itself was ever truly designed for it. Like with WordPress, being used at the large scale is something that happend to Drupal rather than something it made happen. Drupal is a pig that people have affixed wings to because there wasn't any other way to do it at the time. You see similar things happen with the other big platforms (WordPress, Joomla). As far as pigs go, Drupal is a good one. There are some things to respect (though not necessarily agree with) about Drupal's roots and the original thinking behind it. There's no doubt that it is far better than Joomla, for anyone that cares about this stuff. Beyond that, where it excels is in all the 3rd party stuff written for it, to do just about anything. It's a diesel-powered cuisinart in that respect… whatever you need to blend, it will blend… but it'll be messy. Working at large scale, 3rd parties have built all kinds of caching, CDN and load shifting things to throw on top the pile (and likewise with WordPress). Even a pig can fly if you strap wings on to it. And Drupal has a lot of folks thoroughly invested in it to the point where they are making that pig fly. Drupal is also such a household name that it represents a low-risk position for decision makers (low risk of job loss from choosing Drupal). None of this makes it a good product, just a safe one for people that don't know any better. But for people that do know the difference, we want a panther, not a pig.