Leaderboard

@Basil - fine suggestion, however here is my humble opinion: - processwire is a developers tool. - actually there already is a resource even better than a book: the forum. - no 2 sites will ever be the same, and consequently these tutorials would have limited value. - shopping carts are a breeze with foxycart, i mean like 5 minutes a breeze (for an initial integration, and then the sky is the limit) - travel agency..sounds like there could already be a purpose built system for this? this sort of thing would be not for the faint of heart.. - i don't think anyone here would gamble the time it would take to write such a book, and maybe your estimates are a bit high. - you can promote good karma by "flattr"-ing those developers who have flattr accounts (Soma, David-Karich).... cheers!

We are using hipchat for constant team chat for some months and it's really great. For video talk we've been using sqwiggle for the last weeks, and for project management we are trying invision with good results.

Just found this gem here https://sublime.wbond.net/packages/ProcessWire%20Snippets%20-%20Basic https://sublime.wbond.net/packages/ProcessWire%20Snippets%20-%20Advanced Installing on SublimeText3

I think the issue is just your single quotes - it is looking for "$answer_text" as a string, rather than "Yes". EDIT: Have a good read through some of these links to get a better understanding of the differences between single and double quotes: https://www.google.com/search?q=php+single+vs+double+quotes

ColorPicker Custom Fieldtype/Inputfield for ProcessWire 2.+ This module gives you a new custom Fieldtype. Let's you select a color using a Colorpicker jQuery Plugin. The color selected will be stored in HEX format uppercase: "EAEAEA"; To use it in your template as a background HEX color, you'd simple output the value and prefix it with a #: echo "background-color: #" . $page->color; When creating a new field in the admin, you can set a default value the field should be prefilled with when creating a new page. The field supports a "reset" button to be able to set it back to the default value. The colorpicker used: ColorPicker jQuery Plugin by Eyecon Since 1.0.6 the colorpicker supports color swatches to add predefined colors for easy selection. Thanks @Rayden for the implementation. How to install: Download the contents of this repository and put the folder renamed as "ColorPicker" into your site/modules/ folder Login to processwire and got to Modules page and click "Check for new modules". You should see a note that two new modules were found. Install the FieldtypeColorPicker module under "Field" section. This will also install the required InputfieldColorPicker at the same time. Done You can now create a new field with the "ColorPicker" Fieldtype. Get it from modules section: http://modules.proce...e-color-picker/

This module integrates Swift Mailer mailing library to ProcessWire, providing support for three different "transports" or methods of sending email: SMTP, Sendmail and Mail (essentially PHP's native mail() function). WireMail is email-related base class for ProcessWire. See this post by Ryan for the details. Important thing to note here is that a) it's brand new, so as of this writing you'll need a fresh dev version of ProcessWire to use this and b) it makes integrating new ways of handling email-related tasks very easy. Getting started You can download or clone the module from GitHub: https://github.com/teppokoivula/WireMailSwiftMailer/. Using this module is as simple as downloading / cloning it to your modules directory and installing it. If you're going to use SMTP or Sendmail features, insert correct SMTP credentials / Sendmail command to module settings first. Third transport, Mail, is included simply because it's a native feature of Swift Mailer; if you're going to use it, I would suggest against installing this module. ProcessWire's native WireMail implementation handles this part just fine. Basic usage Sending emails should be done using wireMail() function -- if you use mail() directly, you're going to bypass ProcessWire's email handling features entirely. Main difference between mail() and wireMail() is the order and number of arguments: $number_of_recipients = wireMail($to, $from, $subject, $body); For more information please take a look at README. This module is released under GPLv2 (just like ProcessWire itself) with the exception of included Swift Mailer library, which is copyright © Fabien Potencier and released under the MIT license.

Before we can repeat, we can slide! ProcessWire2+ RangeSlider Fieldtype This fieldtype let's you create slider input fields in the admin using the built in jQuery UI Slider. You can use it as a regular single value slider, or enable "Range" setting under details of the field edit screen, which gives you two number. In the front-end templates you can use the field as follows: If used as single value slider echo $page->fieldname If ranged slider is enabled echo $page->fieldname->min echo $page->fieldname->max Use in selectors strings With a regular single value slider $pages->find("range=120"); If range slider is enabled $pages->find("range.min>=100, range.max<120"); It comes with various settings. ------------------------------------------------------------------- - range enable - width of slider (%) - default value - min value - max value - step - prefix for displayed value(s) - suffix for displayed value(s) Download ------------------------------------------------------------------- You can download the Module from Github. https://github.com/s...nic/RangeSlider How to install ------------------------------------------------------------------- 1. Download and place the RangeSlider folder in: /site/modules/ 2. In the admin control panel, go to Modules. At the bottom/top of the screen, click the "Check for New Modules" button. 3. Now scroll to the RangeSlider Fieldtype module and click "Install". 4. Create a new Field with the new "RangeSlider" Fieldtype. Once saved you can configure the fieldtype, with various options under "Details" tab. I have made some testing, and installed on different PW installs. But if you find any issue, I'd like to hear. Have fun!

Here's a video of a module we're working on that I thought you guys might like. The module, Lister, provides a different type of Page List than the tree that you usually interact with in ProcessWire. It gives you a table of pages with customizable columns, filters and actions. Rather than try to explain what it does, I figured I'd show you. This module also uses a new (soon to be released) Inputfield invented by Apeisa, developed by me, and sponsored by Avoine, called InputfieldSelector – it's what you see on the configuration screen as well as the Filters tab. I recommend bumping up the size/quality to 720p so that you can properly see everything. The video has no sound... I tried to do one with narration, but that didn't work out.

You could always place the script outside the PW templates folder and bootstrap it to processwire so you still have access to PW pages and fields for grabbing the validation messages. http://processwire.com/api/include/

@3fingers...I think that js is in his .php file

Welcome! Two little questions that have rather large answers, to be honest. First of all, I suggest that you ignore front end for the moment till you get your head round the rest of the process (see what I did there?) The key to ProcessWire is the incredibly powerful APi which allows you to build any functionality - Form Builder is a module that allows you to create front end forms very easily, but they can also be built manually. So, I suggest you do one or other of the tutorials in the Wiki just to get the hang of how the system works and as a very basic introduction to the API http://wiki.processwire.com/index.php/Main_Page Next step is to look at the API (linked on the top menu) and especially the Cheat Sheet. http://cheatsheet.processwire.com/ That will give you a clue to how much is possible with ProcessWire. The point with PW is that it is not quite an out-of-the-box solution like the Drumlapress mob, but it allows you a lot more versatility and does not shoehorn you into one particular way of working. Having said that, it is not a scarily complicated system either - many of us started using it with very little development knowledge, but have found it manageable and we have learned a huge amount. And had fun in the process.(I did it again..!") So, get your hands dirty with the tutorials and then ask any specific questions you need - you will find the people on the forums here are, quite uniquely, rather better than boring old docs!

thank you guys! and apeisa sory i mean 1000 sales! Macrura i think most of cases is similar, for booking site lets say the perfect example is what Ryan has create Villas of Distinction or VillaRental.com allso for catalog searching your creation Ohm Speakers is a good case. Anyway thank you and i love this forum!

Pw book has been discussed many times before and would definitely be worth it. But little math error in your calculation. If 100 people buys 30 euros book, it will give 3000 euros, not 30 000.

No toots yet. BUt we'll be waiting ... and watching ... silently.

Resurrecting this topic. I need to establish an approval process for both publish and edit — it also needs a comparison feature like Pete mentioned. I'm looking into building an in-house module(s) to handle this — perhaps using something like PrettyTextDiff for the comparison. I'm wondering if anyone else has already developed anything that they wouldn't mind sharing. Save myself a little work.

Hey OrganizedFellow, Thanks for bring this to attention I had completely forgotten about it. I'll keep updating with what I've learnt so far! Thanks.

This thread started with tons of great promise of uniquely useful tools and resources, but it has turned to off topic discussion and spam.

I give them to Soma to eat .... he is so underfed, you know.

Thanks, apeisa, this is awesome.

Its still working, some nice folks purchased a copy

thank you adrian for providing support. I can only apologise, I hardly find time to update or work on my published modules. However, they are on Git, so you easily could fork them or do a commit. regards EDIT: The module now needs permission 'analytics-view'

Hi Guys.. Started cleaning up my Mac and thought I would have a look at MAMP and see if there was an update. Looks like there is a whole new version out! New price is 39 Euro. For most of us here, I suspect, the upgrade from Pro 2.x costs 19 Euro Just sharing... Cheers

I found this earlier today! https://sublime.wbond.net/packages/ProcessWire%20Snippets%20-%20Basic https://sublime.wbond.net/packages/ProcessWire%20Snippets%20-%20Advanced

Hi all, I'm a big fan of the Sublime Text 2 text editor and of course of huge fan of ProcessWire, so I went ahead and created a library of PW snippets to be used with the ST2 Snippet system. I followed the PW cheat sheet, and created Advanced and Basic versions. The Advanced version contains only those seen in the advanced mode of the cheat sheet, so if you want the full set, you'll want to get both Basic and Advanced. They are on GitHub here: https://github.com/evanmcd/SublimeProcessWireSnippetsBasic https://github.com/evanmcd/SublimeProcessWireSnippetsAdvanced I've just submitted the Advanced set for inclusion into Package Manager, so hopefully that will be added soon. See the README for more info. Any feedback welcomed

OK I feel like a n00b now! This simple bit of code seems to work anywhere in the front-end: if ($this->modules->isInstalled('ProcessForgotPassword')) echo $this->modules->get("ProcessForgotPassword")->execute(); Obviously it should be attached to a link and used in the same context as in the backend... but It generates the bare unstyled forms, and seems to handle all the functionality perfectly.

Well I can give you the parser for free: Just put the "wp-import" folder in the same directory as "site" and "wire" and add the name of your xml file in the folders "index.php". --- And if you still prefer a real module you can support development via (for example) PayPal mail@nico.is --- Edit: Forgot to add the attachment wp-import.zip

If you add this line at the end of the array in public static function getModuleInfo() { 'permission' => 'page-view' it will give your other users access. You could even give it a new custom permission, like: 'permission' => 'analytics-view' then create that permission and assign it to the role of the users you want to allow access to. Of course these options are hacking the module core code and so hopefully Luis will reply soon with something along these lines. Hope that helps in the meantime.

Hi mlcb, welcome to processwire. A lot of beginners questions, like you are asking now, have already been answered in the forum. Just go through the forum channels to see if your questions are already answered there. http://processwire.com/talk/topic/4173-grouped-forum-posts-links-articles-tutorials-code-snippets/ What makes PW so different from other cms'es is that with PW you can directly use any html, css, php, etc, experience you already have. This is not the case with the other cms'es out there, where you have to learn their rules first before you can use them. In other words, PW can be used by both designers and coders even with little html and css experience. With PW you can make your own templates and fill them with your own api calls. Which brings me to what you have to learn with PW and that is it's powerfull api, http://processwire.com/api/ Feel free to work with wordpress, joomla, drupal, etc, so that you can compare them with PW and make your own conclusions. That is what I have done and made me see the open potential that PW has compared to the others. I wouldn't start with something so ambitious like that. Start with the tutorials first, learn the api and then work your way up.

I just went ahead and did what I wanted to do since a long time. Yesterday at this time there was nothing. Now there's this: http://soma.urlich.ch/ My old portfolio, taking dust, is gone for good! Now I have new shiny blog. Starting with zero, this took a couple hours to setup a complete custom blog. I'm still working out details here and there and adding new stuff I still want to. But what I need and wanted is there now roughly. Some things used in this ProcessWire site: - ModulesManager (of course) - Hanna Code - Repeaters (for the inline code snippets added to content by some Hanna code) - Rainbow JS for the highlighting (http://craig.is/making/rainbows/) - PW Comments Core module - RSS Feed Core module - Markup Twitter Feed (http://modules.processwire.com/modules/markup-twitter-feed/) - Pocketgrid (there's no good grid system other than this http://arnaudleray.github.io/pocketgrid/) - FontAwesome Icon Font No frameworks used except PW. I hope I'll find time to write some things about web dev in general and ProcessWire. Hope you step by now and then.

+1 re the other suggestions, especially config->debug. Check the bottom of this page where it says The advantage of this is that you can have your local setup verbose about errors and your live site not verbose (by setting the config->debug differently in the two files). If you are very new then you may want to come back to look at this later since it's just a nicety (but a very nicety I think ) Another good thing that is sometimes appropriate is to build and test the HTML+CSS+jQ first (ignoring any PW) then gradually introduce PW so for example have PW replace a static TITLE tag with data generated from PW.

Greetings Larry, Excellent discussion! Coming from the world of PHP frameworks, I am also very curious about the most "MVCish" way of working in ProcessWire. An interesting challenge is that a lot of the "M" and "C" necessities in frameworks are handled differently (I would say better) in ProcessWire. And yet, as we develop more complex sites, the templates can get quite involved with material that properly should be abstracted into some sort of classes/functions/controllers. What's great about ProcessWire is that we have the best aspects of frameworks, with the freedom to be creative in how we structure views and functions/classes, and it takes care of many crucial database elements in efficient ways. We then have the potential to develop interesting structures, without being forced to worry about too many conventions. I'd love to see a discussion here where we share creative ideas for structuring ProcessWire sites in MVC ways. Thanks, Matthew

Would be cool to create a project management system using Processwire.. with the help of something like http://dhtmlx.com/ components. What do you think?

While this technic is nice to know it is much easier to enable compression via .htaccess, also because of the reason Ryan mentions. I don't see any reason why to do this via PHP. See the H5BP htaccess for nice technic https://github.com/h5bp/html5-boilerplate/blob/master/.htaccess#L379 and other goodies. Also only while the html served might be 4kb instead of 24kb, this doesn't make the page load that much faster, but using this for all resources along with caching headers you get a ~30% decrease of file sizes. Using PW template cache can have the most impact on page loading, depending on how render intensive the page is, you get a loading time around factor 2-5 times faster just because it doesn't need to render it.

Greetings, I have been working a lot with SVG graphics lately, which is especially interesting when combined with the dynamic nature of ProcessWire. I generally use Adobe Illustrator or Inkscape to create the SVGs. But I really like this: http://code.google.com/p/svg-edit/ It works very nicely as a standalone app, but the exciting part is integrating this with a ProcessWire site. More on that in another post! Thanks. Matthew

Very good topic Vineet Sawant !! Not only discuss with each other coding pw websites but also about marketing websites. My experience is that many website builders consider this a private part of their work and so discussions and answers about this topic stay for the most part private. Of course I can understand that, it would be like asking someone how much money he or she is earning every month, for how many hours and what kind of work and many people would like to keep that private. But it would help a lot of newbies if they could learn something from the pro's about making, negotiating, planning, selling and getting payed for websites. I for example made only 8 or 9 websites that I actually sold. None of them was done with pw that came later on. I charged between 300 and 800 euros because they were simple websites with still a lot of work and I got payed when the website was finished and delivered. Sometimes I got not payed as promised or not payed at all and had to shut down the website. Then on the first page of the website I put in big letters : "This website is for sale - contact me at - - - - - " The next day they called me where to meet and pay me ! Because I am not a pro website developer and know little php (but I am good with html/css/api and photoshop) my rate is 15 euro/hour for html-css-photoshop work and 20 euro/hour for simple php work. I have studied coding rates per hour with google from many internet entrepreneurs and I know my rates are cheap but hey I am not a pro. I am learning everyday and my dream is to become a pro website developer and coder with pw and make a living with websites. That would be a dream come true for me and say goodbye to my work at a rent a car company. And I am sure I am not the only one on this forum with this dream. So people - please reply on this topic. My own experience with selling websites so far: 1. Only give FTP - Admin - Database - CPanel passwords to the client when he has fully payed you !! 2. Don't let your self get payed the total sum at the end but get payed each time you finished a part of the website, lets say in 3 or 4 parts. 3. Make it absolute clear from the very beginning that changes and edits on the website afterwards are going to be charged and for how much. Just too many clients take it for granted that doing changes and edits on their website afterwards are included with the end price they payed you. 4. Offer them from the very beginning a payed course if the client wants to edit the website for him self. By the way - this is also and exactly the reason why it is so important that a cms has an easy front-end for the client so he can edit his website in an easy way. 5. Informing your client about points 3 and 4 at the end makes them angry. Tell them at the very beginning. What I and many others, would like to read from you people is how to find new projects or new clients ? At what point do you hand over the ftp - admin - database and cpanel passwords ? How do you let your self getting payed for your work ? - at the beginning - in parts - at the end And where do you consider risks in the payment ? How many people here do actually make a living with websites and how many do it as a second income ? Ok thanks in advance for your replies.

I eat them.

Sometimes elements of your good design can go to a good home on another website.

Awesome Kongondo! I haven't gone through the whole thing yet, but am printing out so I can read in more detail. But it's clear you've put a lot of great work and thinking into this, Thanks! I can't wait to read it in full.

.. and one more take for the same subject, from slightly different angle: ProcessWire is both CMS and CMF in one package, ie. by installing ProcessWire CMF you also get "admin" which is essentially a CMS built on CMF provided by ProcessWire. The line can be a bit blurry at times Anyway, admin uses API behind the scenes, so it's not really that different from any other application you might build with PW (expect for the fact that it's probably larger.) You'll most likely want to keep it available even if you build something similar yourself -- if not for any other reason, at least to give you a nice way to view and manage templates and fields without having to do everything via API (which is of course possible too!) From my point of view there are two main ways to use ProcessWire as a platform for your applications: Bootstrapping (like Pete explained above) enables you to use it's features from strictly outside PW, ie. you could build whole application yourself and then make PW store (and fetch, sort, sanitize etc.) your data. You could also use more of the framework provided by PW by creating your application as a PW site, using template files for your application / view logic and so on. You don't really have to build modules to use PW (as a framework or a CMS) but they're a handy way to package some feature you need often into one reusable tool you can pull out whenever there's need for it. They also enable you to tweak how PW works out-of-the-box; you can, for an example, add new methods to PW objects such as Pages, without hacking core code (which is unbelievably useful at times.) Process modules (one type of modules you can create for ProcessWire) are a bit different in that they integrate directly with admin tools, providing new features there. These let you extend default admin features a lot and more often than not whatever control panel your custom application needs could also be built this way Generally speaking there are many similarities between PW and various web application frameworks like CodeIgniter and CakePHP, but PW doesn't venture quite as deep in the "generic utility" category and also forces as few restraints on you as possible. It's more focused on handling content and data types than providing you tools for general tasks (strings and numbers, email, FTP, complicated image manipulation etc.) and doesn't force a strict application structure (MVC, MTV etc.) on you (unless you build one yourself, like I've done for my own projects.) I hope this helps understand a bit what PW is, how it relates to other frameworks.. and whether it's the tool you're looking for Extra tip: cheatsheet is good place to start digging in PW. Turn on the advanced mode and you'll get pretty good idea what PW can offer.

Joss, please rename your account to Papabear. Everytime you Post, the forums becomes such a nice athmosphere of a dark forest with a tiny warming fire place, the little ones sitting around the fire, listning to the warm and comfortable voice of Papabear. I really enjoy your posts, well you allready know what I´m thinking about you

Hi Matthew, i´m sorry, but i´m actually not seeking more beta testers. Almost 80% of the core developement has been completed. I´m now in huddle-together-mode and will create a new preview Video by next week. Please take note that this is a commercial project of mine. But I will write a detailed Case-Study after release of v1.0.

You actually can use the 'sort' property, but you'll want to perform the sort after you've assigned it to all your items, because PW will write them out in the order that they appear. For instance, here is how we might reverse the order: $cnt = count($page->images); foreach($page->images as $image) { $image->sort = $cnt; $cnt--; } // now tell it to sort by the field 'sort' $page->images->sort('sort'); // you may not need to do this, but putting it here just in case $page->trackChange('images'); $page->save(); Avoid calling $page->images->remove() just because that will queue an actual file to be removed when the page is saved. Another way you might accomplish reversing the order: $myImages = new Pageimages($page); foreach($page->images as $image) { $myImages->prepend($image); } $page->images = $myImages; $page->save();

diogo, sure $img = $page->images->first(); $page->images->remove($img); $page->images->add($img); $page->save(); and the first image is at last position