Leaderboard

It's not often I'm impressed, so I only feel that it's right to express my appreciation to those behind the development of PW. I've only been using PW since March this year, but it's been a joy to work with. I knew nothing about PHP beforehand, and now I'm able to achieve my goals without too much stress thanks to the excellent PW API. For my current project, I'm jumping in at the deep end by creating an online community where my members will have a basic forum, comments system, gallery, private messages etc. At first I thought this would be an impossible task, but my custom comments system seems to be coming along nicely, all without any stressful programming. I'm fairly sure I'm doing a few things wrong, and I'm sure there are more efficient ways to deal with my problems, but that's what I love about PW, we can do it our way. For my comments system (which I've started from scratch as a learning exercise) I simply wrote some template code to check for a sub-page called "comments" under the current page, article etc. If it's not there, it will be created when a comment is posted. This comment would then appear as a new page under the comments page, as would all the other comments. I'm not sure if this is a good way to go about it, but it works, and I can keep developing it to allow comment editing, quoting etc. Anyway, thanks again. I look forward to see what the future holds for PW, but as it currently stands, it's exceptional.

Nothing wrong with asking, but the scope of your question here makes it difficult to answer in sensible timeframe. There's also a lot of valuable content floating around here that already answers different parts of your question, but I'm assuming you've browsed through those, considering that you even started a thread about that. Something you said in that thread made me cringe a bit, though: "I need to chat less and read more". As I've been repeatedly told, we all learn in different ways, but IMHO you need to read less and do more. As they say, "the best way to improve at building software is to build software", and that applies to sites too. Build a couple of sites of your own and you'll have a lot better idea about what works for you.. and what doesn't. Nevertheless, this is an interesting subject, so I'll start by trying to answer your questions briefly based on my typical process: I don't "create a database and install PW", I've got a script for that. Repetitive tasks are boring and automating them is fun. I use a previously created site as my starting point. This base site includes common templates, template files organised exactly as I like (something derived from Zend Framework file structure and an implementation of the front controller pattern), various include files (functions.php with common and usually render-related functions etc.) and modules I often end up installing. I don't know what a "base template code system" is, but if you're talking about template engines (Twig, Smarty etc.) the answer is "never". Those things are are horrible and wrong. If you're referring to something like partials (as in "not full template files but files you'll include within your template files") and helper functions, then yes -- both are useful in their own ways. The projects we've built before are my "code clip folder". I could go on and on about this and probably will at some point post something about the directory structure, template logic etc. but don't really have time for that now. If you'd like to know something more specific, please don't hesitate to ask. You'll definitely get more (and more helpful) answers if you limit the scope of your questions a bit.. though don't be offended if people point you to existing threads either, as that's just the way things work around here. In some ways this forum serves as our collective data bank and the more discussions about same subject are grouped together the easier it is to dig into that subject later

Great to have you here Guru and I think you summed up perfectly why we all love ProcessWire - it's just an incredible tool that allows us to do what we want and in many different ways. Your appreciation for what Ryan (and contributors) have created here will grow as you realise its true potential

Good for? Why add another language on top of an already existing capable language (PHP?)...Yes, I know I used MODx and its templating language and loved it..but that was before I decided to take the plunge and learn PHP.......Anyway, this is like mermite...some people love smarty and similar while others don't. I like Ryan's summary here: http://processwire.com/api/why-php-syntax/. If you know PHP I suggest to forget template engines like smarty. They are just another layer of complexity you don't need...

Hi Max, I'm still making my way around PW so I'm nowhere near a power user, but here's my process for now: 1. First plan the site out and try to get a conceptual idea of what its components will be - templates, users, user roles, custom functions, modules, etc. 2. I'm not a front end dev, so I get a design done and coded into HTML/CSS for me, or I purchase one, or a client hands me one. 3. Create the database and install PW on a staging server 4. Create a template and page with fields just for the site configuration stuff - site name, site slogan (if needed), admin email, etc. and other things that the site owner might want to edit later from one central place. 5. Create the fields, templates, user roles, etc that I came up with in the planning stage, install modules 6. Port in the HTML/CSS, create pages, get the basic site skeleton done. I have a cheat sheet I'm slowly creating for myself as well as a collection of code snippets I reuse from project to project to make my work faster (because I understand things better when I simplify them for myself) and these help me to port templates into PW fast. 7. After I've done the simple template porting in I then code in any custom functions I need that I planned out before. 8. Fix any glitches I then test the site and move it from staging to production. This varies from project to project and sometimes I do things completely differently but this is my general process. Hope this helps somewhat

Not needed in PW so leave them out of the way Outside PW, though, Savant looks interesting since it also uses pure PHP http://phpsavant.com/ -- Edit: :D just realised that Savant was first written by the guy that wrote that article you linked to.

My dog appreciates that approach - she attempts it regularly with the cat from next door.....

Martijn, try to keep the pieces on the ground. Trap them (edit: the big ones) in a corner if you can

Stupid game.... (can't stand I still didn't reached 2048)

I had the same question last year =) https://processwire.com/talk/topic/3044-why-is-there-no-user-title/

I start with a piece of paper and draw out the site. Then I work out what templates and fields I need Then I work out what framework (or none) that I will use. After that, I install PW with either a blank profile or something useful I might have kicking around and start creating fields, creating blank template files and whatever templates are on my list. By that point the site is really half created - I just need to make it play nice!

I've been playing in my phone for relaxing and (no screenshot, sorry) i've seen the black square of 4096

@GuruMeditationi it's worth looking at the source code for the module. it is 410 lines of code. It's pretty bare bare bones as far as forum's go, but the essentials are there to build something awesome if you have the time. "Private messages" You would have to create this feature but, this page makes it seem pretty simple. "Profiles, with the ability to add extra fields etc." Supported through processwire. All users are pages and can have custom fields. "An option that allows comments on articles/pages etc to create a new forum topic, so that users can reply in the forum, or on the actual article/page etc." I'm wondering about the "best" way to do it myself. But certainly looks possible. "Moderation tools, copy, move, close, pin, ban etc." copy, move, delete are all possible through the admin interface. Ban, close and pin would require some simple changes to module i think. Does not look like there is email notification/topic watching support yet either. Forgiveness in for any wrong information, I hope some one can correct me as I am still pretty new to all this as well.

In that case, one way is to only allow them to delete the pages that they have created. I'll let others more knowledgeable chime in here The property $page->createdUser will get you the user In a selector you can search using created_users_id

Bash, mostly Kongondo explained the main reasons already and the rest was pretty much summed up by Paul M. Jones in his 2008 blog post titled "Another Smarty Emigrant": To be fair templating engines do have valid use cases, but those are almost entirely related to keeping things secure if you need to allow external or otherwise untrusted users (however limited) access to your codebase.

I am not touching this with a 10-foot pole!!! Seems so addictive...

Hi Alan, I would go with a bootstraped script that checks session settings (URL like: http://example.com/yourpdf.php). You need to keep security entry and the infos which pdf / page regards to this session. If it can create pdf on the fly you only need to secure your session settings (limited to a browser / fingerprint or somethnig that like for a limited timeperiod)

Thanks for the quick reply! URL Rewrite 2.0 is actually installed and working quite well. As a matter of fact the root directory that the ProcessWire install is to be a subdirectory in is also a PHP Application using URL Rewrite 2. Also confirming that ProcessWire works fine when it's in a standalone IIS site. However it has issues once placed in a subdirectory in another IIS Site. Come to think of it, im beginning to suspect it may be the root Application's rewrite rules in it's web.config file. I'll investigate and advise.

For the template files you can use the alternative syntax http://cl1.php.net/manual/en/control-structures.alternative-syntax.php <?php if($something): ?> <!-- Html --> <p>My content inside an if </p> <?php endif ?> You can use them with foreach, for, while, switch, etc.

Greetings, I've transplanted most of my Seblod plants to new ProcessWire beds. It's amazing how the nutrients in the soil are depleted in those Seblod beds. Can't really grow anything there. Thanks, Matthew

The last one was not very complicated, so I have just done it for them for nothing - I know that is not great business, but I did not want the liability of it lying around.

Hi Joss, I wish I could do that also. There's plenty of space in my garden but unfortunately the clients are not willing to pay for transition to PW :-(

I am currently digging a hole in the garden for the last of my Seblod projects.