Leaderboard

I want to say thanks to all people in the forums for being here and make this place so special and a great place to be. There's some spirit and drive going, I think many other CMS forums can only dream of. It's still small and the quality of people and their support to help in the forums always amazes me. Even newcomers help other newcomers in a manner it's quite unique I think. Not saying there's might other places that are the same, but I don't know of any. Thanks for the nice experience to all of you! Then the biggest thanks would go to Ryan our "Man on the Wire", always sharp and considered helpful, with brilliant ideas and execution. You build something very special here and while maybe some think it's not "sexy" enough, they don't know what's under the hood. I think people are really excited to get direct responses from you and this is what makes them feel at home, which ignited some friendly fire and spread all over the place. Quo vadis? This is for now and I really wonder how it will be when the forums grows to a place, where I hardly will be able to catch up with new posts. Every other day I wonder how long Ryan will still be able to do so for every question in the forum. Don't know how you do it but you do. So then where will ProcessWire be in a couple years from now? How far will this forum grow? Will there be lot's of PW sites spreading across the web and sharing places as with other big CMS'? Hardly think about it but I think it could very well happen. What could the PW web be? How many modules will there be and quantity > quality... While at it, Clouds! I can't hear stand it anymore, STILL we have moving clouds in the new ProcessWire website!!! Hope people don't think we go PW Cloud? Also I would love a horde of crazy new core php developers that help making crazy new stuff with this CMS/CMF. No I'm not drunk but after that post I'm wired. Keep it up, stay healthy and spread the word "ProcessWire". Peace. ( Ahhh, I reached 2000 posts and I didn't even notice yet! Well never used to post that much in a forum ever. Well mostly just BS nobody wants to hear heh )

I have some news about the potential conference in 2013. When I posted about this originally, I didn't know that we had another baby girl on the way, due around May. I am very happy about this, but it would also interfere with my ability to attend a conference. The baby would be too young to travel, and it's too much for me to ask my wife to be alone with a newborn + a 3-year old, while I travel across the world. So I have to put this conference plan on a back-burner while we figure out a better time to do it. Thank you for all of your interest in this conference. I'm really thrilled at all the enthusiasm this conference idea has received, lets plan to reschedule.

I'd welcome the opportunity to do anything that helps move the ProcessWire project forward. I'm cool with interviews so long as I've got at least a rough list of questions ahead of time. I tend to think a lot before I speak so wouldn't want to waste people's time with "Hmm, let me think about that" or "Hmm, let me look up what FLOSS and FOSS means again." Since I don't work in an office with other developers, it's rare that I talk to anyone about webdev topics. But think I can do a good job when prepared.

Is it just me or are processwire designer/developers a classy group of people? All these sites I keep seeing are well designed, expertly executed, all around quality work!

hi ryan, this piece is by former modx fanboys, who converted to pw recently. it's made in interview style and the guy who is mainly talking had pw on his shortlist for a while. since pw was awarded by cmscritics recently, they now decided to publish the interview. their first topic is how easy it is to update pw compared to modx. they continue with their opinion, that modx is more "academic" while pw is made by people who know webdesigner's everyday business. next they praise how responsive the main developer of pw is (do you know him?). good ideas raised in the forum make their way into the core quickly, they state. next they talk about the simplictiy of pw. they raise questions on the roadmap: will pw stay as simple as it is? or will it go the "enterprise road" like modx did? the piece is not at all an introduction to pw. it's more a fireside chat of people who know modx in detail and now compare it to pw. they end with a chat about the api. that everything in pw has to bee done "manually" in pw (with some php knowledge), is a major advantage from their point of view. however, they consider pw as not "sexy" but powerful. the whole thing is a bit like pirate radio (do you say so in english?). i mean independent radio by amateurs. cheers, christoph

Hello folks, The next release of textile (v2.5) is going to see some major changes to the codebase and a few minor additions to its abilities to handle text. The changes outlined here are not yet committed to the dev branch of netcaver/textile but (Now committed) I want to post about this in advance so any developers here can get a feel for what will be changing and see if it impacts them (to track what is already committed to the dev branch for v2.5 you check the changelog.) As I'll be taking over responsibility for maintaining the textile text formatters with this release, I'll also take care of making sure these code changes don't impact end users of the textile in PW. However: if there any devs reading this who use textile in other work they might be interested in the rest of this. To facilitate textile’s uptake in other projects & to make it plain easier to read, I'm moving the code towards PSR-2 compatibility. Although I don't necessarily agree with everything in the PSR-2 standard, I will be adopting it for textile because... textile has used no coding standard to date and has had many contributors who have all used different styles & consequently the coding style (or lack of it) reflects this and needs some sanity restored to it. It gives people who may contribute to textile a standard to work to. I have been advised that a minimum of PSR-1 compatibility is required for textile's uptake in at least one other CMS. So how might these changes bite your installation? Here's a few ways... First potential problem: Are you overriding textile's defines to customize something? As PSR-1 (needed for PSR-2) doesn't particularly like code declarations & side effects (such as the #defines that pepper textile) in the same file, I need to know what use, if any, folks are making of the existing txt_ defines listed here as they will be going. If you are using them, you will need to start calling a new method setSymbol('name', 'value') prior to calling TextileThis() or TextileRestricted() and drop the defines as textile will no longer be using them at all. NB. the 'name' to pass into setSymbol() is as shown in the link above without the leading 'txt_' which is no longer needed as the names will no longer be in global scope. If you are using textile in exactly its default configuration with respect to defines there is nothing to worry about so far. Next: Using a define called 'hu' to make all relative image paths absolute. This is only likely to impact the use of textile in Textpattern CMS (it's original parent project.) Textpattern CMS uses a define called 'hu' to point to its root path and if textile finds a define called hu it uses that to prefix all root-relative image paths turning them into absolute paths. Now that textile is breaking free from its Textpattern CMS heritage, I think it's time to break this hidden coupling between the two and instead replace it with a generic (and explicit) setRelativeImagePrefix() method, allowing other projects to use relative image path prefixing if they need to without resorting to using the 'hu' define and without the possibility of a name conflict if they already happen to be using a define called 'hu' for something else. If your project doesn't use any define called 'hu' the above won't be a problem for you. Finally: Still using PHP4? I thought not, but I have to cover this anyway. Next up is PSR-2's requirement for explicit visibility on all properties and methods. As textile comes from a PHP4 heritage it has never had these. A quick look at my stats for PHP versions across hosts show that ~79% of hosts run PHP of some kind and that ~76% are PHP5 or better. Needless to say, PHP4 support is going. But even if you are running PHP5+ this change to the textile codebase will bite you if... you are calling any methods other than the constructor method, TextileThis() and TextileRestricted(). you are accessing any of the class properties. These will all become either protected or private and most will have no set or get methods. I figure that for most projects using textile there will be no issues but please let me know if you are going to get bitten by any of the above and if you know of other devs who use textile in their projects, please give them a heads-up.

I have just dipped my toe into the large space that is the ProcessWire wiki. At the moment, that just means that I have just logged on and am just creating a couple of templates and some other bits and pieces - nothing complicated, I don't have enough time! Once I have done that, I will start scribbling. For the moment, all I have done is a half complete help page about starting a new article (click on help in the left navigation), and created two categories - Drafts and Pending. Hopefully this will help with anything anyone writes which they want to flag up as not finished or need checking. More info on the help page. Talking of categories - if someone has any good ideas about what categories should be created and how they should be organised - that would be really useful! Joss. (PS: If anyone needs a logon for the Wiki, please ask Ryan, not me!)

First pw site... http://www.stokar.com/ composer's management agency. Processwire was great for this!; took on every challenge and request the client had with ease. Thanks to Ryan, and to everyone on the forum - it was an essential resource for working out all of the code to make this site work. -marc

Nice writing Soma. I agree and I think this is what is happening here:

@ panictree - I really like your work.

Will be definitely in the next update!

Well, now, my background is wonderfully confusing. But out of the many things I have done over the years, one of them was producing radio shows.... Maybe we should do an interview with Ryan via Skype or something ....

@joshuag: That is my impression, too. In fact, I'm really amazed at the overall professional level we have here at Processwire: top designers, top developers and even more importantly, a group of passionate and friendly people eager to help each other. Simply priceless!

I found Janko's FormToWizard code to be one of the simplest ways to implement a multi-page/multi-slide form. Now with the Processwire this just got easier. I tweaked his script a wee bit to work with the API forms described in this thread. PWformToWizard.js bunching your fields into fieldsets just as Ryan described above, each fieldset will become a page/slide. Instead using the <legend> tag that Janko uses, the script now generates a legend based on the label, specifically anything that comes before a colon ':' first add the script: <script type="text/javascript" src="PWformToWizard.js"></script> then use this javascript to initiallize formToWizard: $("#SignupForm").formToWizard(); the default styles are: <style type="text/css"> body { font-family:Lucida Sans, Arial, Helvetica, Sans-Serif; font-size:13px; margin:20px;} #main { width:960px; margin: 0px auto; border:solid 1px #b2b3b5; -moz-border-radius:10px; padding:20px; background-color:#f6f6f6;} #header { text-align:center; border-bottom:solid 1px #b2b3b5; margin: 0 0 20px 0; } fieldset { border:none; width:320px;} legend { font-size:18px; margin:0px; padding:10px 0px; color:#b0232a; font-weight:bold;} label { display:block; margin:15px 0 5px;} input[type=text], input[type=password] { width:300px; padding:5px; border:solid 1px #000;} .prev, .next { background-color:#b0232a; padding:5px 10px; color:#fff; text-decoration:none;} .prev:hover, .next:hover { background-color:#000; text-decoration:none;} .prev { float:left;} .next { float:right;} #steps { list-style:none; width:100%; overflow:hidden; margin:0px; padding:0px;} #steps li {font-size:24px; float:left; padding:10px; color:#b0b1b3;} #steps li span {font-size:11px; display:block;} #steps li.current { color:#000;} #makeWizard { background-color:#b0232a; color:#fff; padding:5px 10px; text-decoration:none; font-size:18px;} #makeWizard:hover { background-color:#000;} </style> <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js"></script> <script type="text/javascript" src="formToWizard.js"></script> <script type="text/javascript"> $(document).ready(function(){ $("#SignupForm").formToWizard({ submitButton: 'SaveAccount' }) }); </script> see janko's page for more info~ Now, just to add some responsive jquery validation to each 'next' button...

The method I often use is very similar to what Martijn posted. I'm thinking about adding a new $config variable where we can specify what files should be automatically included before a template is rendered. That way we don't even have to do remember to do an include("./global.inc"); The result would be kind of like an autoload module, but one wouldn't have to know how to make a module to benefit from it.

It is always interesting to find where processwire is mentioned, so this is the topic to post links to articles, blog posts, discussions, tweets etc which are about or related to ProcessWire. I started with this one, which is well written article about some basic differences between WP and PW: http://www.globi.ca/articles/articles/processwire_vs_wordpress/

Hi, I have a simple question. I need to do additional logic right after a new page has been created/saved, to be more specific I need to call an API with the value of some of its fields, is this possible in process wire? Thank you!

Do you hate dislike TinyMCE and heart Markdown? Or Textile? Or HTML? Do you wish there was better way to create content than textarea? Well there is! Content creation oriented, syntax highlighted and easy on the eyes, that is this new plugin I made. And I know you'll love it! And did I mention it supports HTML, Markdown and Textile? Download/fork/star here: GitHub PW Modules Your local modules manager Features Syntax highlight your text, for easier preparation of content Nice light, readable theme Supports Textile, Markdown & HTML Auto selects mode, based on field's textformatters (last found is used) Works with multiple fields on page, each with different settings Features inspired by iA writer Blue Cursor Focus mode We are still kind-of in beta, so please, test your browsers and let me know… Thank you! <3 PW

The idea behind the jobs forum is for anyone looking for paid development work to post their requirements in one place and for developers to get in touch with them. Any project can be posted, whether it's custom development work, website design, or complete installation and setup of a website. There are a few guidelines that are useful to bear in mind to help things go smoothly: Give a good amount of detail about the project so that prospective developers know roughly what will be involved. If a project requires an NDA for any reason, try and give non-specific details such as the type of development work involved (module development etc). Let people know how to contact you - if no contact details are given, people will most likely PM you on the forums here. If you have a requirement to work with a developer in the same country as you, please mention this to narrow the field of applicants. If you are happy mentioning a budget in the open, this is also fine but not required.

I couldn't agree more with you, Soma. As a newcomer to this forum, I already feel part of the community, part of this family that is ProcessWire. I really can't think of another online forum I've been a part of that is as friendly, open and helpful as this one. I think this might be due to the fact that we are all so passionate about ProcessWire and that we just don't mind to devote some of our time to help others that are as passionate as we are about this system. I would also like to thank Ryan, our man on the wire, for being so kind, patient and helpful. As for the future, well, only time will tell. We might as well just enjoy what we have here and what will be, will be. @apeisa: pretty relevant example, haha.

Thanks Soma this is really nice of you. Thank you also for all the great work that you are doing here! Now I have to logoff for a few days, so this is a great last post to read before I head out. Hope that you all have a great weekend and week! Also please no more Ektron licenses on my credit card.

Just wanna thank Soma for this. Been searching for selector for page references for an hour. This solved my problem.

@joshuag: thank you for the kind words , they mean a lot to me!

Hmmm, think I have it. Got the feeling it was to do with the path part of setcookie, Ryan's tip to have a look in Chrome was a good one, the path was getting set for that page only and just specifying "/" didn't work, I had to add null to the domain part as am on localhost setcookie("InfoBar", $info_bar, time()+3600, "/", null);

London ... has to be the Toucan in Soho street - a tiny, cramped, smelly, basement but the best Guinness in London. They also do an amazing pre 1960 Middleton special whiskey (if they have any left) - as long as you don't mind payout around £30 a shot or so. Me and that Whiskey had a bit of a reputation there about 14 years ago. Had to ware the shades ever since .... I also lived for a while in Cambridge but my liver was having some serious survival issues! (Note, I am now a very sober, peace loving soul living in a small town overlooking a nice green!) Edit: I mean Carlisle street - grief, my memory!

Haven't tested, but adding this, or something like it, to your .htaccess (after RewriteEngine On) might work: # skip over URLs with a period (possible filename) or your admin URL RewriteCond %{REQUEST_URI} !(\.|processwire) # skip over requests to files that physically exist RewriteCond %{REQUEST_FILENAME} !-f # redirect to the same URL with a trailing slash RewriteRule ^(.*)([^/])$ http://%{HTTP_HOST}/$1$2/ [L,R=301]

Ryan, best wishes for a healthy pregnancy and delivery to you & your wife (ok, mainly to her) but congratulations to you both.

That setMaxFileSize is only in the dev branch.

All the users permissions should be now be fixed. Sorry, I didn't realize before I'd broken that.

Hi Adam, thanks for the feedback. Feel free to open an issue on the netcarver/textile repo for any feature requests or ideas you have. Going beyond v2.5 I'm considering adding a plugin system to textile, called "textplugs", and having a textplug specifically for MD compatibility but I don't want to make MD compatibility part of the textile core.

It's quite undocumented and it's rather chaos, but it's here: https://gist.github.com/4233629 • it's temporarily shortened version of WIP full module, so comments may make no sense you input {{ anything:function pw=like, params=1 }} and it will call "function" from inside the class (with parsed $params as parameter, should be array. Do with it whatever you want.

maybe: $options = array( 'has_children_class' => '', 'levels' => false, 'max_levels' => 2, 'show_root' => true, 'outer_tpl' => '<select id="select_mobile">||</select>', 'inner_tpl' => '<optgroup label="¬">||</optgroup>', 'list_tpl' => '||', 'item_tpl' => '<option value="{url}">{title}</option>', 'item_current_tpl' => '<option value="{url}" selected="selected">{title}</option>' );

Hi mcmorry, I've read the howto and the thread.. Point 3 in howto: I want disable it for the default language -> so I don't create "it" page. With "it" page it works.

Thanks all. I have summarized the solution suggested by Soma in two examples (for future reference): Example 1: Simple example that lists your related yourpagefield articles - first pages referred by this page, next pages that refer this page. <ul> <?php foreach($page->yourpagefield as $k=>$p) { echo "<li><a href='{$p->url}'>$p->title</a></li>"; } foreach($pages->find("yourpagefield=$page") as $p){ echo "<li><a href='{$p->url}'>$p->title</a></li>"; } ?> </ul> Example 2: List related pages based on the yourpagefield field (all referring pages are sorted alphabetically, the block is only output when related pages exist). <?php if(count($page->yourpagefield)>0 || count($pages->find("yourpagefield=$page"))>0 ): ?> <h2>Related</h2> <ul> <?php $ref = array(); foreach($page->yourpagefield as $k=>$p) { $ref[$p->url] = $p->title; } foreach($pages->find("yourpagefield=$page") as $p){ $ref[$p->url] = $p->title; } asort($ref); #shuffle($ref); foreach($ref as $url=>$title) { echo "<li><a href='{$url}'>{$title}</a></li>"; } ?> </ul> <?php endif; ?>

I actually did attempt to build something, twice, last time a few years ago. My first attempt was based on lightweight WYSIWYG with very limited capabilities, e.g. h1-h6/bold/italic/links, not much else. It had drag-and-drop reordering of the sections, and a "template" drop-down for each section. It was not much use in practice. My second attempt was based on Markdown, which can be processed on both client and server-side. This had a single, floating (semi-transparent) form for the Markdown, and would render the HTML in the background, on the fly. It would detect placeholders on the Markdown content - so if you entered "{photo}", for example, a "photo" item would show up on a list of all the placeholders in the content. You would then click on a placeholder in that list to edit it, and you could then substitute it with, say, an image, a table, or some other piece of content - each type of content would have it's own editor. I loved that idea, but clients don't understand Markdown, or don't like it. Content-editable is now fairly ubiquitous, so I think something in between those two ideas would soon be feasible - a very simple, lightweight, in-place editor with basic formatting, draggable sections and containers and so forth, some of which would have custom UI for uploading images, populating tables, etc. I'm sure it's not a small can of worms to open up though.

Congrats Ryan!

ok I didn't test it and wasn't sure... you look different suddenly...

Talking too much with the database is not what slows a site down. Reducing queries doesn't necessarily improve performance. You can have a few hundred queries that execute faster than one query. It comes down to good indexing and queries that use those indexes well. When optimized well, MySQL is not likely to be a bottleneck even with a lot of chatter. Now if data isn't indexed well, things get slower as the scale increases. Combine that with more unoptimized queries and it gets even slower. But this isn't ProcessWire. ProcessWire does support the 'autojoin' option for page references, which causes those references to be joined in the page-loading query. This has potential performance benefits if the quantity of joined page references is relatively small. But I don't recommend it unless you plan to use those page references on every single instance of the page. Otherwise, you are joining extra data for the times when you don't actually need it. Using the FieldtypeCache is yet another way you can join more data at once. This particular Fieldtype actually keeps a separate cached copy of the page's data encoded into a one-time-load bundle, bypassing load from the field_* tables. But ProcessWire is pretty fast in the way it works natively, so the situations where one benefits from autojoin and FieldtypeCache are fairly rare. But they are there when you need them.

Yeah, I already did (almost) that. I could post you the code if you wish In my case it's more like {{ figureimage index=2 figindex=1 title="What is this?" }}, but totally simple to adjust. I also has far more robust system for parsing textareas and using shortcodes inside text fields, but that one is far from done… so I'm just bragging here.

christoph, it's like talking about a dream you had. Major thumbs up for your taletelling skills.

I accept the challenge

This isn't specific to ProcessWire, but HTML checkbox fields in general. When it comes to seeing if a checkbox is checked, the presence of the field in $_POST means that it was checked. If a checkbox is unchecked, it doesn't show up in the $_POST. Whatever value you assign to a checkbox field doesn't really matter, as that isn't the indicator of whether it was checked or not. Using some non-zero value in your checkbox does make sense though because a statement like this would indicate whether the checkbox was checked or not: if($input->post->my_checkbox) { // checkbox was checked } else { // checkbox was not checked }

Oh, I forgot to mention one thing: If you guys are curious, you can test the uploading form until the end. The inserted data will be discarded if there's no video upload. edit: very nice site @panictree

Big improvement, glad to see it I know the original design contributed to me initially overlooking PW. The one thing that is driving me nuts right now is the "motor" mono-space font in the documentation, something about it I just find really hard to read, in fact I've gone as far as to use stylish to force it back to courier. Anyway, just my opinion, not really a great idea to get fancy on pre-formatted text used for docs.

I'm new to PW and wanted to say thanks for such an awesome, elegant tool. I'm really looking forward to working with it. I hope to be able to help out and contribute some day. Really, though. I'm just blown away. Great job on your own site as well.

Just experimented also a little and made a little example based on Martjin's code. With some improvements and simpler add image routine. No need to create a new PageImage as the page already has PageImages field. Just add the path to the file and save page. This can also be a remote web url. Also this example shows how error handling can be done. I also used a "/.tmp_upload" folder to upload images first and only add to the page if everything is valid. Since $u->execute() uploads the file to the destination specified, it could be a security issue, if not dealed correctly with it. As far as security goes this folder should be made publicly not accessible via htaccess (in comment). In 2.3 you could maybe use built in restriction to files on pages, but not sure it would be appropriate here. Further, I delete the images uploaded in tmp folder in either case. This is all example code and may even need additional security for real public uploads. (mime types check of files by the WireUpload is sufficient? Ryan?) I've put the code on gist.github: https://gist.github.com/4150974

soundas pdfcompsar have.meinor problemo yo.must edit /site/config.php, changes $config->debug=true; to $config->debug=false;

Works with many to many too. $prs = $pages->find("title=Zoo|Theme park|Museum"); // maybe also use the name or id $poi = $pages->find("template=poi, poi_type=$prs"); EDIT: corrected code. yours doesn't work because "get" will return only 1 page and not page array.

Try this where you output the date: <?php setlocale(LC_TIME, 'es_ES'); // substitute your locale if not es_ES echo strftime('%e de %B de %Y', $page->getUnformatted('date')); // substitute your date field name This should produce the following output for today's date: 8 de noviembre de 2011 We're going to be providing localization support for the date field with ProcessWire 2.2, but the method described here will continue to be backwards compatible. Note you can also put the setlocale() part in your /site/config.php if you prefer. What locale you can use depends somewhat on what are installed on your server. I think that es_ES (or es_ES.UTF-8) is fairly standard, but if you want to get a list of locales you can type this in the unix shell: locale -a