Leaderboard

Is my 100th post I wanted to do something special. I edited a video, hope you like it Just for fun Edited: Now with subtitles

Interesting discussion! I definitely think Processwire could improve its usability but I don't think plugins is the way to do it. I just did a clean install of PW 2.5 and documented each step in the process. Here's a .pdf with 44 slides that covers the scenario of a new user's first contact with PW: http://cl.ly/0e3V2M3w1z1B ​comments appreciated

woop, you hide the best part on the last slide. To quote his PDF: I like ProcessWire the way it is. Clean and minimal. Please, don't tell me how to do things. Instead focus on tutorials, guidelines and articles that explain how to use the tool ProcessWire to build great sites. My first site with ProcessWire was quite easy and not a complex monster. I learned how to use different field types and how to structure content with each project and I'm still impressed, when I find a new way to solve a problem with ProcessWire. That wouldn't be possible, if I had everything finished. Then I would say "Oh thats great but not exactly what I needed". ProcessWire as a clean and minimal CMS/CMF to build a website is great. Ryan should try to improve the system itself and keep bloat away. (In my opinion, the new 2.5 with all it's profiles is even too much to start). There are other areas to improve, beside the system and most of them were mentioned before in this thread: Better onboarding process that guides the users A single place for all the little code snippets and fragments. Tutorials for beginners and experts. Maybe have a look the new Kirby docs More site profiles to start with, but not bundled by default (Download during the installation?)

I've been a member here since July 2012. I have less than 300 posts. If you were to check them all out, I am mostly voicing my opinion. Very very very few of my posts are CODE related. I don't share code with someone in the hopes it works for them because it worked for me. I don't post code issues that are not working on my installation. I AM NOT A CODER. Period! ADHD and OCD make it incredibly tough to piece things together. I don't memorize every CSS3 element or attribute. I rely heavily on http://www.css3.info/ and http://caniuse.com/ I don't dare memorize much PHP either, so I shoot over to http://php.net/ I use Foundation5 for my layouts, but I can NOT memorize those damned classes, so http://foundation.zurb.com/docs/components/grid.html All I know is the basics: git status, git add ., git commit -m'This is my commit message.' For ANYTHING ELSE I Google the hell out of it. For others, I rely on the above bookmarks, or the other 1,000 others I have bookmarked here on the forums of snippets and little code ideas that could come in handy. Have I learned PHP? Yeah! I can create some variables, if and elseif statements, and simple loops. With my limited PHP, HTML5, CSS3, and Foundation5 knowledge. I've put out several websites this year. Made $x,xxx. Made some hardware upgrades. Bought some business cards. Purchased the PW Forms module. Taken my family out to dinner. I've learned that if I want to make ProcessWire do this and that, which it CAN'T do outta the box - I got a little bit of learning to do. AND I AM NOT A CODER! hah!

I haven't done the WEBDESIGN BUSINESS for long. Only a few years. Mostly I have pursued it as a hobby and from time to time, I'd build something for profit. Done tons of reading about freelance, Getting Things Done, design, etc. I used to use ExpressionEngine, back when it had just branched from pMachine. I was an early adopter and fell in love with it. Used it for several sites. Bought four commercial licenses for clients. TONS of extensions/addons/etc. One of my last clients on EE was about two years ago. By far, the greatest, client, ever. I've been a lurker and mild contributor here since July 2012. Taking things in. Bookmarking. Testing things out on various localhost installations. I was delighted to receive an email from him (my old client) a few weeks ago, asking if I would visit with his Father, because he also owns a business and needs a website. Even though we had a major disagreement, we parted ways and I'm thrilled to learn he still thinks very highly of me. So COMING SOON, is my very first, ProcessWire website ANNNNNNNNNNNNND he sends me another email today, stating that he wants needs a redesign on his old site. I looked over the source code and it reveals I used Foundation 2.2.1, hahaha. So this ought to be fun!!! \o/ I'm pretty sure I'll just keep him on EE instead of rebuild it entirely on PW. So most likely a responsive redesign. ** HIGH ** FIVE **

I always thought in your pic you were terrified of being pixellated from the bottom-left corner

Admin Custom Files Admin Custom Files is a simple module that can add custom javascript plug-ins, scripts and styles to the Processwire admin area. Instructions are on github. Download module at GitHub Download at the modules directory

On your page where you would want to see the Foundation Callout, you would have a textarea field (mine is called "body"). In the body field I add the Hanna code: [[wgc-panel-home-bottom-holiday]] I make use of the _init.php file and have the following: $body = $page->body; In the particular template file or better yet in _main.php or header.inc you would have: echo $body;

Maybe I'm overreacting but a few of Woop's comments seem to value seductive sales/outreach style of presentation over efficient transfer of information. We need both but they are not interchangeable. readme.md - "Not a very welcoming start" I don't see it that way at all. When I see a readme file that traces back to a version control repository I feel pretty confident that I'm looking at up to date info that's actively maintained, probably by someone with first hand knowledge of the content. Also, one page of clearly organized text is so much more accessible and easy to grasp than having to slog through whitespace, logos and blather like "we create something beautiful together" to find kernals of truth for my project notes. The thing about all of this documentation and user interface stuff is that it's a huge amount of work to communicate effectively to different audiences and keep it up to date and error free. I hope we can create an environment where glimpses of underlying complexity or unfamiliar terms is not off putting to new or not very technical users and they have the tools to find out what they don't already know. Reference and how-to information about Processwire exists but the fact that it's scattered in different places (including this forum) makes finding it a little tricky. Wouldn't it be great to have a Processwire powered knowledge base kind of thing that we could throw all that into? We already have the API cheatsheet. That kind of drill down treatment could be applied to tutorials and snippets too. Maybe we could work out a clever bot to mine the forum posts and link some of that content in as well. Hard to know where to begin (or end) with that kind of thing.

You could make your own: // a filename array for scripts in the head (make the name you wish) $config->headScripts = new FilenameArray(); // a filename array for scripts in the bottom (make the name you wish) $config->bottomScripts = new FilenameArray(); // add scripts to the head FilenameArray $config->headScripts->append('/your/wished/path/head.js'); // add scripts to the bottom FilenameArray $config->bottomScripts->append('/your/wished/path/bottom.js');

Update time! We've launched lightning.pw over the weekend. I've added more information on the first post. Try it for yourself now and use the coupon code PROCESSWIRE for a free credit. Any feedback is welcome. Please note, that we would still call this a beta version. We are note sure how many ProcessWire sites we can fit on a server so we might have to finetune some settings for better performance later. Also there are still some little optical improvements on our todo list.

Well my idea for snippets.pw was including two different types of "posts": "snippets" and "receipts". Snippets: Snippets would be really short code blocks including maybe 1-2 descriptive lines and inline comments. But mostly the pure code. Receipts: Receipts would be a little more advanced. They would first explain which "ingredients" (fields, templates) are needed. Then show the code with more description. At the end you would see the results as screenshots or as html code. So this post type is more like a tutorial. --- After talking to LostKobrakai and marcus about this it appeared that they had slightly different ideas about this. But I think I would be fine whatever way we go as long as something helpful emerges. And as long as I can put my 2 cents in

public static function getDefaultData() { return array( 'total' => 0, 'limit' => 10, 'anotherDefault' => 'blah blah', ); } public function ___install() { //do stuff here, etc., etc. //save default module configurations on install wire('modules')->saveModuleConfigData($this, self::getDefaultData()); }

My avatar was custom-made by WillyC, hence the unusualness. Been using it proudly ever since

For this specific case you could also add hooks to $sanitizer from an autoload module. So that you could call $sanitizer->specialchars(). See wire/core/sanitizer.php for details. Horst's solution is probably easiest. On a side note: There is already $sanitizer->entities() so maybe it would make sense to add specialchars to Sanitizer core class?

I'm happy if I can contribute to some sort of snippet library and I like the two kind strategy because it fits the "hey I found a cool piece of code" mentality and also the stuff that just needs a little more explanation.

Three words: New. Homepage. Video.

I don't know if this is what you are asking for or talking about: I use Hanna Code for most Foundation specific add-on stuff (Buttons, Panels, Pricing Tables, etc....). It works very nicely and saves an enormous amount of time. I either create an exclusive field (normally textarea) that will render whatever Foundation add-on I need or add it to existing $body (textarea) or text fields.

Ha - thank you all for the suggestions Im going to be boring and just feature my face* *actual face may differ slightly from photo. It gets bigger or smaller depending on the proximity of Christmas and puddings

User-Friendly is very subjective, what's hard for someone is easy for another person. PW requires (and rightly so) that you invest some time in learning the basics (PHP, Jquery, CSS and HTML). These are skills you need anyway to be productive and secure when dealing with a modern day website. Without knowledge of how things work (i.e PHP, Jquery, CSS and HTML), you will never be able to realistically maintain a website. I sincerely hope PW is not "user-friendly" to the cookie-cutter variety out there. They will never take the time to learn the basics, because everything about web development/design is all magic to them. This will most certainly kill this wonderful forum with numerous and countless issues that are entirely based on their refusal to learn simple processes. That would be a shame and will hopefully be resisted. Suggestions on how to improve PW are encouraged and actively discussed on this forum. I enjoy reading the diversity of opinions and concepts. In 2 short years PW has blossomed. I originally had problems understanding why the PW palette was so open, but as time went on and I relearned PHP, Jquery, CSS and HTML I came to respect and appreciate PW. I have read the forum every day for these 2 years. I can say that I never did that with any other software. I hope that we don't inadvertently kill this golden goose on the magical chase for "user friendlyness" and more users. The funny thing is, no matter how "user friendly" PW gets, someone will always think it can be more friendly. That's just human nature at work. To me, PW is already very user friendly and useful. Every client of mine that has seen PW has been happy working with it.

Often times, creating a side project is first and foremost scratching your own itch Or to start differently: Currently, I'm developing a site where I need CKeditor (and later jQueryUI Datepicker) outside of the admin, in frontend. I searched Google and the forums and found an approach to follow - but during the research the site laravel-recipes.com came into my mind (since I'm currently also looking into this framework). It's content consists of small, spot-on bits of information, for example: http://laravel-recipes.com/recipes/269 Just to think out loudly here, wouldn't it be nice to have a ProcessWire counterpart of such a site? processwire-recipes.com for example? Target group: Developers, from beginner to advanced Difference to these forums: Stripping the discussion part, concentrating on the info; and if done properly: bypassing the mediocre forum search, better tagging Difference to the official tutorial section: Focusing on not creating a whole site, but modular parts of it. Single solutions. For example: First child redirects (shameless plug, but this is the format of information pieces I'm having in mind) Difference to the API documentation: Situation-based ("I need this and that") instead of architecture-based Laravel.io (forum), laravel.com (official, and doc) and laravel-recipies.com possibly prove that these type of sites can coexist in a framework ecosystem, so I guess a recipes site would not cannibalize this forum here nor the doc section. A recipe site like this would live and die with its content, of course. I would be ready to share all the small pieces of information I encounter that would make a good "recipe". But that alone wouldn't be enough so this project won't survive without contribution of the community. What's your opinion on this? Yea or nay? Update: ...it just took, erm, nearly three months,... but here it is: https://processwire-recipes.com/

I just discovered FoundationDeck. It's a marketplace SOLELY for Foundation5 templates, NICE! I used to browse ThemeForest and somehow came across this little gem. www.foundationdeck.com I bought a template just a couple of days ago. --------------------- How many of you rely on templates? It eases the design load. Lets us focus on the development and back-end. No need to reinvent the wheel, right? How many of you rely on templates?

I don't think there are any (I am no layer, laws do differ between countries and are utterly confusing to begin with), but the movie references here would definitely go into "quotation usage" here in Finland. You are building something new, using just a small pieces of something existing.

Without intentional searching, I stumbled upon some snippets that would be adequate recipes - if tagged well and accompanied with a short description of problem and solution: https://processwire.com/talk/topic/5578-how-to-use-fancybox/?p=73141 https://processwire.com/talk/topic/7167-server-error-with-latest-dev-build/#entry69041 https://processwire.com/talk/topic/7573-best-way-to-implement-a-global-utility-function/#entry73157 https://processwire.com/talk/topic/3779-use-csrf-in-your-own-forms/ Just to add more examples to my idea of processwire-recipes. Since community attribution would be crucial for such a project, it's also a matter of pragmatism to keep recipes short. The easier it is to contribute the bigger the chances are that anyone does. To not create a parallel structures but to join forces on this topic, Nico and I spoke yesterday and we learned that our approaches differ slightly. We decided to present these both - and are eager to hear your feedback on them. To keep things simple Nico will shortly present the state of his snippets.pw idea so far in this very topic. What connects us nevertheless is the feel that there is need for such a "PW knowledge hub" page.

Damn, I spoiled my 100th on something much less spectacular .

Found it. it was JSON related. Working code: if($this->input->get->render != 'JSON') $event->return = $event->return.'n';

(Have you checked your JSON response, is it notice free ? ) I don't know what you want to accomplice, but mabe you can handle certain parts with Javascript. Your can handle Javascript, after $.ajaxComplete();

At the end of the day it comes down to skills, budget and what the client wants

when it is in the site/config.php it is available everywhere, also in modules, regardless at which time a module is loaded. (I'm speaking of custom modules, especially created just for one site) I can use all my personal utilities in those modules, in templates, in hanna-codes, just every where at every time, - thanks to Ryan who made $config populated first in PW. (so easy and with less writing)

Like this: (Thanks Sugur Lee Hooper)

*pictures Joss in a sparkly dress swaying and singing into a microphone*

If it's just a personal project that I just want to get out there, then sometimes I will use a pre-made template, but for clients I make something different each time. It does depend on skills, budget and timescales as well as whether or not the customer minds if you use a template that could be being used hundreds of times elsewhere. For a head-start I use http://getuikit.com/ (have used Foundation as well) but I tend to have an idea of where I want to take it from those basic starting blocks. I am by no means an awesome designer though

ah - that would be me.... sorry

I use my own utility function files in my site-profiles in a subfolder called for example: 'mylibs' I include them once in the site/config.php file: include_once(dirname(__FILE__) . "/mylibs/myfunctions.php"); This way I can use all what is in my utility files every where, regardless if I run PW in the webserver or if I bootstrap it for CLI operations.

avatar_sparrow.zip

We could make one (don.t lett willy.make u.see _1 4u)

Guys, thanks for all the comments, hints, tips and encouragement to keep on trying. I appreciate that. Reading back I also notice I was rather grumpy last night. Sorry about that, I should not engage in these kind of forum discussions in the middle of the night. Being very tired I have a tendency to be much blunter than I normally am. Some people made the remark that modern website creation often involves some form of coding, more than 5 to 10 years ago. That's true, and indeed at the heart of my frustration. While my general site building skills have improved with the demands of the market, my coding skills lag behind. So the discrepance between what I CAN and what I WANT is becoming bigger. What I want is the more or less ready to use functionality of a CMS like WebsiteBaker, Joomla or Wordpress, combined with the flexibility and power of PW. My first impression was that I would be able to create custom stuff pretty easily, but after trying for a week orso I was disappointed. Partly in myself and my lacking skills, partly in my expectations that turned out to be too high (in relation to my skills), and partly in PW because a number of things are really not user friendly (enough) in my opinion. I do feel that PW could benefit from having ready to use functions/modules/profiles/whatever-you-call-them that can be regarded as absolute core functions of any website: regular pages, blog/news, form, gallery. I'm not talking about time management, full blown ecommerce, forum, or anything fancy like that. No one expects that in a core CMS setup. Just the basic stuff to build any regular informational website, like a typical small business website. It's not important if that would be part of the core, or separate addons, they just need to be readily avaliable without having to heavily edit underlying code. I don't see why that would harm PW as a developers framework. That aside, I do feel I need to PW another go, if I have the time. All comments have given me a new impulse to try again to overcome my own current limitations.

Quick hint: already saved snippets.pw and trying to create a blog/snippet collection so you get easier into pw. But it's only a concept at the moment.

I'm giving my opinion as much as you are, right? I wasn't a coder when I started playing around with pw, I was a graphic designer that knew a little of html, but liked PW because I understood that it was more flexible than other easier systems. All I'm saying is that, from the moment you understand that you have a powerful tool in your hands, either you are willing to learn it or you don't. Both choices are perfectly fine. I'm not looking down to anyone, and I'm sorry if it came out that way. Again, just giving my personal and absolutely independent opinion.

And what else should be in the core? Forum? E-commerce? Local finances tax systems? Should we vote and have in the core the most popular features? Or should we leave the core light and efficient so that even an average developer can quickly create any of those for their clients? Should PW be aimed at the regular Joe that wants a blog like all the others in one day, or should it be aimed at the regular Joe that is willing to pay a competent PRO to create a customised solution? There are dozens of good CMSs made especially for that public, like http://www.couchcms.com/ or http://www.surrealcms.com/ or even http://grabaperch.com/ . These tools don't try to be more than that. They have a focus, they follow it, and they do it well. Pw is actually a very simple system (in the way you mean it), but yes, it is directed at coders and everyone willing to learn a bit of code. But it's not only usable by coders, they are only intermediaries who make it usable by anyone with a business who wants a website. In that context, the potencial users that know HTML/CSS but are not willing to learn a bit of PHP become a much smaller percentage.

What you described here is the opposite of PW. Call it what you want, but if these are your requirements for a tool to call itself a CMS, than PW is not —and won't be— one. This can happen with site profiles though. We only have to wait that they appear, and they will with time.

SUPERBULOUS IDEA! LOVE IT. Where do I sign up?

After some more ideas and a rewrite again... Should be renamed to FormHelper. Module can create forms by 1) page object 2) template (fields) 3) array of field data (new) It's possible to skipFields (array of field names), clearFormValues (field values removed), changeable form and submit button values, take care of jsConfig and also JqueryCore module load. So ckeditor works out of the box (if output order is correct at template...) Example how to build a login form with username and password fields... $fh = $modules->get('FormHelper'); // Create a username form field -- fieldVars 'name' is required to build $field->name $fieldVars = array('name' => 'username', 'label' => 'Username', 'required' => true); $fieldAttr = array('id+name' => 'username'); $field = array('module' => 'InputfieldText', 'vars' => $fieldVars, 'attr' => $fieldAttr); $formFields[] = $field; // Second form field... password $fieldVars = array('name' => 'password', 'label' => 'Password', 'required' => true); $fieldAttr = array('id+name' => 'password', 'type' => 'password'); $field = array('module' => 'InputfieldText', 'vars' => $fieldVars, 'attr' => $fieldAttr); $formFields[] = $field; // Change submit button value from "Submit" to "Login" $formSubmit = array('attr' => array('value' => 'Login')); // Generate the form $fh->createForm(array('formSubmit' => $formSubmit, 'formFields' => $formFields)); // process form $process = $fh->formProcess(); // check result of form process if ($process === NULL) // not send elseif ($process == true) // send, without errors elseif ($process === false) // send, but with errors $form = $fh->render(); // returns rendered form echo '<html><head>'; // jsConfig needed by wysiwyg editors echo $fh->jsConfig() . "\n"; // outpunt needed scripts for inputfield modules, ... foreach ($config->scripts as $file) { echo "<script type='text/javascript' src='$file'></script>\n"; } foreach ($config->styles as $file) { echo "<link type='text/css' href='$file' rel='stylesheet' />\n"; } echo '</head><body>'; echo $form; echo '</body></html>'; Generate form of current page (with ckeditor loaded for body field... jquery is needed) $fh->createForm(array('jquery' => true)); Generate form from given page object $fh->createForm(array('page' => $pages->get('/'))); // or without prefilled form field values $fh->createForm(array('page' => $pages->get('/'), 'clearFormValues' => true)); And form based on template fields $fh->createForm(array('template' => 'sitemap')); Known bug with form generated based on a template instead an existing page! You get an error if a form should be generated from a template with fiel fields (like images)! Because of a fakePage object You'll get this error message. Error: Exception: New page '/pwdev//' must be saved before files can be accessed from it (in /volume1/web/pwdev/wire/core/PagefilesManager.php line 240) #0 /volume1/web/pwdev/wire/core/PagefilesManager.php(211): PagefilesManager->path() #1 /volume1/web/pwdev/wire/core/PagefilesManager.php(67): PagefilesManager->createPath() #2 /volume1/web/pwdev/wire/core/PagefilesManager.php(55): PagefilesManager->init(Object(Page)) #3 /volume1/web/pwdev/wire/core/Page.php(1625): PagefilesManager->__construct(Object(Page)) #4 /volume1/web/pwdev/wire/core/Pagefiles.php(74): Page->filesManager() #5 /volume1/web/pwdev/wire/core/Pagefiles.php(58): Pagefiles->setPage(Object(Page)) #6 /volume1/web/pwdev/wire/modules/Fieldtype/FieldtypeImage.module(33): Pagefiles->__construct(Object(Page)) #7 /volume1/web/pwdev/wire/core/Fieldtype.php(374): FieldtypeImage->getBlankValue(Object(Page), Object(Field)) #8 /volume1/web/pwdev/wire/core/Page.php(760): Fieldtype->getDefaultValue(Object(Page), Object(Field)) #9 /volume1/web/pwdev/wire/core/Page.p To create new pages with FormHelper your module have to create the page first. Maybe there is a solution... but I don't know at the moment. Also it's not a problem for my needs. Editing pages works fine and if a module try to create a new page it simply should saved via api before FormHelper build the form...

Hi Martijn, I think the OP was possibly asking about front-end forms, where the markup is really important, but tying it into the PW admin system is not. Seems that the form builder api can still provide some value there, even though that's not its primary use-case. But yes, I understand how if you are building an admin page that it would be important to hook into the larger PW system so that other people can program against your own module in the future.

a brave or lion-hearted but very eclectic version can be made out of this: http://upload.wikimedia.org/wikipedia/commons/a/af/House_sparrow_chick.jpg

Now.

Yep, thats more or less what I had in mind. Format-wise and compared to the Bolt snippets, I would propose to add more context, since I like the trio "Problem - Solution - Discussion" (see laravel recipes example above). But their tagging is perfect.

Ivan, always happy to oblige:-) The backend is not customized. It uses the Modesta Theme which we felt was a tad better than the default. We were under tight time pressures to launch the site and decided to skip any backend customization. For the time being, permissions are just for backend admin - web, magazine editorial. There was an idea we had mooted with roles for users who submit photos, but because of the launch deadline, we have deferred that bit for Phase 2. I am appending a screenshot of the backend, just to show you what we have done. The Block-System that you see, is for organizing the Home Page content. It has 3 regions [left, middle, right], very similar to Drupal's regions, in the template. Within each region, post excerpts can be added by the admin for control of the Home Page content. Magazines and Web Editorial, are organized by month. Trust that answers your questions.

Hello Peter Knight! I started in the community recently I can only say ... The cms and the community are great Lists are cool Edit by me Because 2 lists Are better than one. Just kidding

I never used MODX, but based on the talks we had here in the forum I'm strongly convinced that this is not true. We have some heavy MODX ex-users here that may confirm—or not—this.As Martijn said, don't count the modules. I think one of the reasons PW doesn't have more modules is because people don't feel the need for them as much as in other system. You can do so much only with the core...