Leaderboard

I don't consider myself an advanced programmer, neither am I a beginner. As I said in <a href="https://processwire.com/talk/topic/2311-processwire-on-the-web/page-17#entry99587">this</a> post, I balked at PW at first. The first articles I read referred to 'templates'. I wasn't looking for another app with a template engine, so I passed on digging deeper, and continued on with my search. It was the term 'template' that initially turned me away. After looking at all the cms and framework files, I thought, "Great, another idea for a better mouse trap. ...Again." Each and every one of those cms and framewoork apps do not come anywhere close to processwire. Don't get me wrong, I've been using many of them for years, and I am not putting them down. They serve a purpose -- Just not my purpose. From what I have been reading on this forum over the past few days, there is a great group ready and willing to help, and the development is heading in a direction that will support us newer members becoming a more integral part in the future. I don't see PW living between casual and advanced users at all. I see PW as it being what you need it to be. If you need casual, it fits. If you need advanced, it fits. </ .02

I am new to ProcessWire. I am not new, however, to programming (started with assembly back in the '70s). I'm not writing a marketing speel here -- I simply want you (the developers and community) to know how I arrived at ProcessWire as my solution. I have specific requirements for a numer of projects that I will be starting (hopefully) in the next few days, and had been researching various CMSs and frameworks the past few weeks to find a 'one-size-fits-all' toolbox. I have currently forty-four cms installs (from academic to zikula) and thirteen different frameworks ( from akelos to zoop). They all have their merits, and are fine solutions for many users and developers. ProcessWire is one of the original 44 installs, but at first 'glance' didn't seem to fit what I was looking for. Later, after searching the web for a solution to one particular issue, a link back to a PW solution emerged. I clicked the link, and low and behold, ProcessWire *was* what I had been searching for all this time. On a related note, google has sent me a nasty-gram about the reactor they had to fire up because of my queries. The primary strength of ProcessWire that I have discovered so far, is that I (as a developer) am not limited in the tools I can use, or the tools I can create. ProcessWire is sleek and efficient. It is a toolbox full of tools that allow me to build a fine watch, a multi-story office complex, or a fishing pole. The other applications suffer from either bloatware or limited tool availability, or worse, both. I could very well accomplish my project goals using any of these other applications but with much head-banging, hair-pulling, and cosumption of scotch. The biggest 'selling' factor to me for ProcessWire, however, was it's efficient engieering in the construction of built-in tools I will require now, and the ability to create my own tools for use in the future.

Would anyone else like to see the ability to make use of PW variables to build up dynamic descriptions and notes for fields? This is a very simplistic example and not that useful, but I do have some use cases where the ability to do something like this would be very handy: $f->description = __('Please make sure you fill out this field based on the content of the {page.parent.title} summary field.'); As I said - a bad example, but I think this could be a powerful addition in some scenarios.

Hello all! I'm not sure if this is the correct forum to post an introduction, but I didn't want to clutter a specific topic elsewhere. I've been reading various forum topics, wiki, and docs, for the past twenty or so hours and decided to sign up last night. I just want to say that I am impressed with Processwire itself, as well as the community's eagerness to assist us newbies. I'll most likely have a number of questions later. As of now, I suffer from information overload due to the amount of reasearch over the past few weeks. I'm sure some of you old-timers, like myself, are familiar with *Tilt*, which is currently emblazoned on the back of my eyeballs. I look forward to learning and working with PW on a number of up-coming projects, and eventually become a contributing member of this community. Thanks for having me. Best regards, Rick

The advantage to plain includes it that you can edit the prepend/append settings from any module running before the actual page rendering. If you don't need that flexibility there's not really a difference.

Hey, a lot of times I create a role called "editor" and give all of the page-* permissions to it. No problems so far. But I normally forget to go to "home" template afterwards to set the permissions for the template, too. So my idea is to show a list of templates (maybe only the once you have selected as "Manage access individually") in a list like the following in the role edit screen: I think this would be a huge performance improvement and could save a lot of confusion and clicks.

Hi folks! I'm about to add my new module FieldtypeAssistedURL to the repository. You find the source code on github and hopefully in the modules repository soon. Here an extract from the README.md: This module offers you a new field type AssistedURL Field, providing and input field for storing absolute and relative URLs. The field type adds a button to open the URL chooser dialog known from the CKEditor link feature without the tab navigation bar for specifying link attributes. Using the URL chooser dialog the editor may select URLs from internal pages or uploaded files via a search field with auto-completion, a page tree control, and a file selector control. Please feel free to post suggestions and any form of feedback here in the forums or on github. Wumbo

I'm not very familiar with the details of phpdoc but this sounds like it would fit your question (look at the answers): http://stackoverflow.com/questions/6395737/how-do-i-make-my-php-ide-understand-dependency-injection-containers

You can link by using markdown [my-link](http://processwire.com). But be aware, it's not a full-blown markdown parser, which does this job, so other syntax might or might not work. About the overhead. Ryan did mention somewhere, when someone asked about better markdown support, that that would be a performance hit, so I'm not sure if it's wise to back notes/descriptions with features. It's really one of those "called everywhere and often" things.

It is interesting that you say that. What I like about ProcessWire is what I like about my choice in OS. This opinion is based solely on my developer-centric view, and not from the view of my clients. ProcessWire to me is akin to the *NIX of operating systems. Other so called CMSs, especially the more popular ones (wordpress, drupal, et al.), are the windows wrapper versions, whereas the MVCs (and Smartys/Twigs impementations) are the mutated CP/Ms. Everyone believes they have a better mouse-trap. And Yes. You can use their self-proclaimed turbo-charged, lemon-fresh, automatic-transmission mouse trap to kill a mouse, but at exorbitant cost for the supporting systems and learning curves of the end-user. ProcessWire is well architected, particularly so for us 'geeks', as is Unix. And that is where the trumpeted "User Friendly" rears it's ugly head. I'm not knocking the opinion of others. This is, after all, only my opinion. I don't mind so much the Gnome [x-windows, etc.] attempts to make *nix more user-friendly, but please, please, don't bastardize ProcessWire into Windows98.

I have tried them and never saw that purpose. I think it is more about history, who came first and used strong marketing.

Yes Sir. I have used quite a few of them for small-ish projects over the years, and wrote a few plug-ins along the way. I must say that I am more impressed with processwire than I thought I would be considering all I had for a reference was those 'other' apps. I can see PW being my goto tool for all of the "greater than one-page site" projects. That in itself is exciting.

I'm really much more keen on using semantic values in my code, as it's much more readable. 0=hide|Hide 1=article|Article 2=else|Whatever if($page->is("article_options.value=hide"){ //the hide option is ticked, clear markup $out = ""; }

Only if you need to use "limit" in those selectors as well.

@rick: Check out the thread kyle mentions in the op: https://processwire.com/talk/topic/2089-create-simple-forms-using-api/?p=19547

If you're running the dev version (which I like to do since so many amazing features make it into PW each Friday), then reading the blog is a must: http://processwire.com/blog/ I'd say read at least the last 10 posts (better yet, all of them) and continue reading every Friday. They get straight to the point and have nuggets of information that aren't in the Docs section. My opinion is the Docs are great and will get you far, but is missing other nuggets of specific information. For example, you would never know there's a function called wireIncludeFile unless (a) you read it in the blog, (b) you somehow found a mention to it in the forums or © explored the source code a bit.

@Soma: I've been trying to remember the specific issue I was researching -- Happens a lot when I walk into the kitchen too. I will post it when I eventually think of it, though.

Welcome aboard, Rick. Looking forward to seeing the work you come up with.

Hello all, Is it at all possible to use the new InputFieldIcon field in my own templates? I don't see the option to select it when creating a new field. Thanks,

This turns out more complex than it seems, but it is usually something not used that often or ever at all. Even with my experience took some time to get all pages, unpublished , published, hidden, not in trash and not under admin. This is with superuser logged in as I think as editor or guest user you won't get pages from trash anyway. But something like this is needed currently Unless I'm missing something. $pa = $pages->find("has_parent!=2,id!=2|7,status<".Page::statusTrash.",include=all"); foreach ($pa as $p) { echo "<li>$p->path</li>"; } Note that as soon as you got a few hundred or thousand pages you will get a problem Edit: id = 2 // is the /processwire/ admin parent id = 7 // is the trash include=all // to get all pages unpublished and hidden