Leaderboard

Imagine a hotel website. Done? Yeah, most of them look the same ;-) In this project I took another approach. The client is - thank PW - able to (re)create the whole look of his website by changing tiles (images, sizes, texts). The size adapts to the screen size, so on nearly every device the look is different. But not the user experience. After one week online I can say: It works. Thanks to a lot(!) of image material and an engaged client it is one of the biggest sites I've ever made. There is a lot to discover (only german yet, english is due in May). So click around... Der Blaue Reiter - Design Hotel Karlsruhe

Mark, I think the source of your confusion here is that you still don't understand how PHP works. Unlike other programming languages, PHP can integrate with HTML in two ways: by integrating it, or by being integrated inside it (ok, strange sentence, but I hope it delivers the point). these two do the same thing: <?php echo "<h2>" . $page->title . "</h2>"; ?> <h2><?php echo $page->title; ?><h2> The difference is that, in the first code you are telling PHP to output all the content, while in the second example, you are using it to output only the dynamic content between static content. The important thing to understand (and this was your mistake), is that you start the file outside PHP, and then you can enter it with "<?php" and leave it with "?>". You can never open a PHP tag, when you are already inside another, like here: <?php <-- we opened PHP include("./TUT_header.inc"); echo "<h2>" . $page->title . "</h2>"; <?php echo $page->body; ?> <-- and we opened it again without having closed it before You should read an introduction to PHP to learn all these concepts, and you will see that PW will be much easier then.

Absolutely fantastic work!

Glad to help. I hardly ever feel the need to use a custom menu. If that's the case my Information Architecture is probably bad. I really like the idea of ProcessWire that your pages reflect your menu and thus your url structure.

Hi Mark, You're too kind. I am not a PHP bod by any means. Coming from tag-based cms's like EE and Textpattern has been a bit of a struggle but oh so worth it. If it wasn't for the patience and help of everyone on these forums I would probably still be struggling. The first site I worked on was my own and the code has gone through a few revisions as I learn new things. You're right, I learned from things not working, asking questions and a little perseverance. I still have much to learn. I can't exactly remember how I started learning the code - it was probably trial and error for sure. The same principles apply to PW as they do to other systems when it comes to getting lists of entries/pages. It time permitted I'd could bang on about how much more flexible PW is compared to anything else I've used. Building a site in PW is second nature to me now to the point where I don't even look at any other system. I just know what I have to do to make it work - most of my sites a pretty straight-forward though. If you want to know about anything I've built - as in how it works - just let me know. @diogo: Send me a duck post card Regards Marty

My twitter wall doesn't stop showing me nice things to link to http://discover-devtools.codeschool.com/ I watched the first two videos and, even if they are very basic, I already learned something that wasn't aware of.

Hey Friends of Webanalytics, I've finished the main work on porting Wanzes GA into a PiwikAnalytics Module. Just uploaded it to the modules directory. It does pretty much the same like GAModule So take a look at the module post: http://processwire.com/talk/topic/1609-processgoogleanalytics/ You could download the module in the directory or directly from my site: http://misterui.de/site/assets/files/1087/piwikanalytics.zip Cheerio

Custom Page List lets you easily customize the page list (tree) in the admin section. I wanted something more (easily) configurable than the existing solutions, so I tried to add some new functionality with an easy to use interface. This is my first module for ProcessWire, so don't hesitate to let me know how to make it better Based on the work of Philipp Urlich (somatonic): PageListImageLabel https://github.com/somatonic/PageListImageLabel Adam Spruijt (adamspruijt): PageListBetterLabels https://github.com/adamspruijt/PageListBetterLabels Features Customize styles and separators used in the page list Display custom labels for each field Display image thumbnails Display formatted dates Display info from related models (e.g. title field of related pages) Display on/off checkbox as "Yes/No" (ready for translation) Define output filter(s) for each field Configuration See the README that comes with the download. Download Source code is available at https://github.com/hgassen/custom-page-list.

Module: MinifyHTML Simple module, didn't even plan to add it to the forum untill owzim asked me to. Description: This module takes the HTML output and then minifies it, and removes all comments from it but leaving the conditional comments in place. Usage: Just install, nothing to configure, works automatically. URL: http://modules.processwire.com/modules/minify-html/

<?=$page->prev->id ? 'previous' : 'first'?> means: if there is a page before this (this isn't the first), the class is "previous", if there isn't, the class is "first". But I don't know what you want to do exactly. You have to adjust to your intention. You could also simply not print the link at all for the first page: if($page->prev->id) { echo "<li><a class='previous' href='{$page->prev->path}'>prev</a></li>"; }

I'm amazed by the PW community. Thank you so much everyone, I really appreciate your help. Diogo, yes, it's the PHP that was confusing me. I will have to get back to basics and understand the rules of PHP. Thanks for your clear explanation. Totoff, thanks for help with the code plus adding the style.

it would be cool if there were a searchable and tagged repository of PW code snippets; each code sample could include the commented code, tags (like menu, gallery, user, forms, search etc.) and maybe a description field where you could put in what the context was. i'm always bringing up previous sites that I solved a problem on to see what the code I used was, and then copying/modding it to the new project.. edit: i just installed CodeBox and looks good. can also send snippets to gist

Well, it's only a two letters difference I get called Diego a lot by foreigners. I'm glad there isn't one in the forum...

Thanks for sharing the list--It's neat that he points out ways people have found to implement similar features. That sort of content deserves a better website I get PHP Classes emails but can barely stand to read them.

echo "<p class='alert'>Direction: <span class='noalert'>" . $page->direction . "</span></p>"; // Working! .alert {color: red;} .noalert {color:blue;}

huh, what an huge amount of work for you. really amazing website and - as you said - very unusual for a hotel. only the logo looks a bit old fashioned now compared to the rest of the appearance. assume they didn't want a redesign? i definitely would love to learn a bit more about how you did this. did i understand you right, they can control the size and content of the tiles from the admin? please give us - at least a mini - case study if you have time.

Very nice Marc! I like how the content is organized, looks like it's very flexible.

Thx apeisa: The whole approach wouldn't have made much sense without your thumbnail module

Teppo, that error seems to be other way around. Mine was that it didn't work without ckeditor, now it seems to require tinymce Not looked at the code yet though.

Thanks Soma and arjen for that suggestion, I'll implement something like that ASAP.. simplest solutions are often best ones too

I have to say when I first installed it also took a time to realize to change text and save before seeing an icon. But if I remember correctly I had to save and change 2 times to get it show up, is that intended? I think it would be better to show the icon from beginning to avoid confusion, and show a little text edit: too slow...

An option would be to always show the icon. If a user clicks a field with no history a simple message like "There are no earlier versions of this field" would be sufficient. I will look into the version tonight and I will report back.

@arjen: current behavior was supposed to be an improvement compared to how it used to work (show one version, which was always active, right after first save) but now I'm starting to think that perhaps it was a mistake. I'll have to think about this a bit more. There are quite a few possible solutions for improving this, I'm just not quite sure (yet) which one would work best here.. About this error, are you already using latest version, 1.0.2? This issue was reported by @apeisa earlier (not in this thread though) and should be fixed now. If it still exists, I'll have to take another look at that one too.

Mark, I don't know where you are having trouble, but PW is really easy to grasp. I can tell you that my first step was to print all the docs from the API and read them in one of my favorite places (on a coffee table by the river looking at the ducks). Once you understand the API everything will seem possible to achieve

Oops... sorry Alan.

Ehi who the hell is adam?

Adam Alan, my ST2 suggests text-decoration out of the box.

http://www.fillmurray.com/

Suggestions are very much welcome and I'd like to hear what Ryan thinks about this too. On the other hand, like @WillyC pointed out above, PW does many - if not all - of the things you've mentioned here very well and still has a lot of potential to grow and evolve. The way I see it, being geared towards slightly more specific needs than other popular frameworks (namely content management) allows PW to focus on what's really important there instead of trying to become everything for everyone. Don't get me wrong, though - I'm not saying that all other frameworks are somehow chaotic. I'm sure they all have their strong points and specialties, my point is that so does PW. Anyway, there have been discussions about integrating other libraries with PW around here and some people still use things like Flourish for certain tasks. I've personally used parts of Zend Framework in the past, but these days I seem to find very few reasons for that anymore, except for certain very specific things. PW is flexible enough to let you work exactly how you prefer and if you prefer to use other tools for some tasks there's nothing stopping you (even if those aren't bundled with PW code.) Last but not least I'd like to point out that unit tests for core code are on their way. Don't worry, we'll get there Edit: Forgot to mention that I'm not (yet) familiar with Composer, though it does sound interesting. Will have to take a closer look. Thanks for the tip!

I have, of course, seen Ryan's excellent "Blog Profile" for ProcessWire. As I understand it, this package serves as a replacement to the default site and assumes blogging is the main purpose of any PW site it's applied to. Great. But at our shop, blogging is almost always just a *part* of what a client site is intended to do. A blog is merely a *section* in a larger site. So, that brings me to my likely need to put together more of a drop-in addition for PW to make it easy to *add* a blog to an existing ProcessWire site. As it happens, I'd really like to do some work in the PW community to help expand PW's overall appeal. Seems to me, a drop-in blog module would be a great place to start. Has anyone else gone this route or had ideas they might want to share? I'm not so much looking for code here. This would be more of a discussion about approach, feasibility, and a wish list for such a module.

I haven't given up on this, and I came quite far. It's been a couple of months since I worked on it - last couple of months have been kind of hectic for me, so I haven't made any recent progress. I do want to work on this, and still believe it's possible - since I gave up on using $trackChanges, the approach I'm using should be pretty safe. Probably a couple of weeks of work left on this at least though, and not sure when I'll get back to it...

Willy, except for "and so on ..", depending of what it means

hi fred, yes, pw is perfect for that. i have a site up and running which does (nearly) that and can help you if you have more specific questions. in short, the pw admin area for your client requires an access managed template as diogo described that holds the necessary fields (more on fields and field types and templates here and here). each project than is a "page" (which in pw doesn't necessarily mean a visible frontend site) that contains the data for this project - and that's it. dead simple. feel free to ask if you would like to give it a try.

Yes, I merged it to master yesterday. I just don't think there's any reason for new users (especially) to be starting with 2.2.9 at this point. The dev branch is more stable than 2.2.9. Now we can go back to letting the dev branch be a dev branch. I'll send out a 2.3 announcement later this week. While there are always more issues to resolve, there haven't been any major problems since people started testing. Nearly all issues that have come up have been related to needing a modules cache clear, or needing to start with a fresh /wire/ dir–things that people should do for any ProcessWire upgrade. I have now added these items to the upgrade instructions in the new README file included with ProcessWire. People upgrading from 2.2 to 2.3 should still follow all upgrade instructions exactly, backup, use caution and test thoroughly. Here are the upgrade instructions as they appear in that readme file: Best Practices Before Upgrading Backup your database and backup all the files in your site. When possible, test the upgrade on a development/staging site before performing the upgrade on a live/production site. If you have 3rd party modules installed, confirm that they are compatible with the ProcessWire version you are upgrading to. If you cannot confirm compatibility, uninstall the 3rd party modules before upgrading, when possible. You can attempt to re-install them after upgrading. General Upgrade Process If you are upgrading from a version of ProcessWire earlier than 2.3, see the sections below for version-specific details before completing the general upgrade process. Upgrading from one version of ProcessWire to another is a matter of replacing these files from your old version with those from the new: /wire/ /index.php /.htaccess Replacing the above directory/files is typically the only thing you need to do in order to upgrade. But please see below for more specific details about each of these: Replacing the /wire/ directory When you replace the /wire/ directory, make sure that you remove or rename the old one first. If you just copy or FTP changed files into the existing /wire/ directory, you will end up with both old and new files, which will cause an error. Note that the /wire/ directory does not contain any files specific to your site, only to ProcessWire. All the files specific to your site are stored in /site/ and you would leave that directory alone during an upgrade. Replacing the /index.php file This file doesn't change often between minor versions. As a result, you don't need to replace this file unless it has changed. Replacing the .htaccess file Like the index.php file, this doesn't always change between minor upgrades, so the same applies. This file is initially named htaccess.txt in the ProcessWire source. You will want to remove your existing .htaccess file and rename the new htaccess.txt to .htaccess. Sometimes people have made changes to the .htaccess file. If this is the case for your site, remember to migrate those changes to the new .htaccess file. Upgrading from ProcessWire 2.2 Follow the general upgrade process above. You will want to replace your /index.php and .htaccess file as well. Clear your modules cache. To do this, remove all of these files: /site/assets/cache/Modules.* Login to ProcessWire admin. You may get an error on the first web request you try, but that should only happen once, so just reload the page. Upgrading from ProcessWire 2.1 First upgrade to ProcessWire 2.2. (side note: I'm not positive this is necessary, you may be able to go straight to 2.3, but I didn't have any 2.1 sites to test). Follow the instructions above to upgrade from ProcessWire 2.2. Upgrading from ProcessWire 2.0 Download ProcessWire 2.2 and follow the upgrade instructions in that version's README file to upgrade from 2.0 to 2.2. After successfully upgrading to 2.2, follow the general upgrade process above. Troubleshooting an Upgrade If your site is not working after performing an upgrade, clear your modules cache. You can do this by removing all of these files: /site/assets/cache/Modules.* If your site still doesn't work, remove the /wire/ directory completely. Then upload a fresh copy of the /wire/ directory. If your site still doesn't work, view the latest entries in your error log file to see if it clarifies anything. The error log can be found in: /site/assets/logs/errors.txt If your site still doesn't work, please post in the ProcessWire support forums.

Georgson, I'm sorry I never answered to this, somehow I din't see your tip. And now I came back to this to help here and saw it. I will check it out, thanks!

gorgious tipp. großartig. Super.

I also have a site hosted on Strato and in the beginning was veeery slow. I talked about this on this forum thread http://processwire.com/talk/topic/847-max-cafe-bar/, Check Georgson's answer at the end, might be useful.

Slightly out of topic, just to say that this evening there is no programming. Just this https://www.youtube.com/watch?v=RVJUJF6Rg1Q

That should be fine Mark as you can set the PHP ones in your PHP.ini, but -indexes is there for security really so it doesn't list files in folders ny default if you type in a directory name so I'd question the security of a host that doesn't let you do that to be honest... assuming I got all that right The main thing is you're up and running and the fun starts NOW!

Hi, I had a similar issue with one.com. Support suggested to comment out the following within the .htaccess file: #Options -Indexes #Options +FollowSymLinks Also: #<IfModule mod_php5.c> #php_flag magic_quotes_gpc off #php_flag magic_quotes_sybase off #php_flag register_globals off #</IfModule> That worked for me but I am concerned it may cause issues down the road! Big thanks for all the hard work you guys have put into processwire. I've spent a day running through the tuts and It already feels like a great piece of kit, plus real friendly community.

So why am I posting a profile in the pub? Well, it is currently so drunken that this is where is belongs. Also, it is a long way off being finished.... Sooooo The Bootwire Blog (of course) is a bootstrap / processwire blog profile that I have started from scratch, more as a learning exersise as anything. And it has certainly given Soma a good work out so far! It is sort of gone a bit beyond a blog, to be honest, and is rapidly turning into a magazine site. It has some interesting features: Categories Topics Tags Post types Authors Choose side bar items globally, or for all category pages, or for all topic pages Choose side bar items (widgets) for any single post Choose themes for posts Posts can have simple galleries added Choose themes for the site (very limited themes to be honest) Centrally control things like headers/footers, number of recent posts to list, lost of other things Posts can be featured on the front page and/or on their own category. Lots of other things. My basic premise that I started from is: 1. Everything is a post 2. Every post belongs to one category 3. Every post can belong to multiple topics 4. Every post can have multiple tags 5. Posts types are based on different templates 6. Themes can be applied to any template 7. Post are also listed by template type. Post types will include: Standard Blog Video Blog Reviews Recipes Photo Blog and so on. The way the categorisation works is quite complicated. But dont worry - here is a huge piece about it! The blog uses five sets of criteria to organise information: Categories Tags Topics Post Types Authors CategoriesThese are the most obvious form of organisation as they make up the main menu hierarchy. On this particular "hover" menu, all categories can accept posts. However, the click-to-open menu version cannot have posts associated with the top level since the top levels will no longer link anywhere. Consequently, it is difficult to switch from one version of the site to another without causing a lot of headaches! Generally it is best to organise the categories into obvious trees: Politics, Sport, Media and so on. Each category can have more than one child creating multiple branches from one top level category. However, making this too complicated or the categories too many layered could be problematical. (note, if this is for touch devises such as phones, too many levels will make it frustrating to navigate. TagsTags are very much what you would expect - single keywords or short phrases that can be associated with posts on a many-to-many basis. Clicking on a keyword creates a seach of keywords on the database.. There is no limit to the amount of keywords that can be created, but it makes sense to re-use keywords as much as possible! TopicsThis is a departure from the normal way a blog or news site works. Topics are broad subject areas that might be related to one particular category, but can be used by any post in any category. For instance, a topic might be created that explores the politics surrounding what we eat. That topic would be of possible use in both the Politics category and the Food category, depending on the post. Topics are far more detailed than tags, but they are limited in number. Unlike tags, they cannot be created on the fly, but are created centrally by the site editors to reflect the nature of the site. A post can be associated with more than one topic, though this may be unusual. Topics will often have long titles and could have long descriptions. A post can optionally display the full topic details in the side bar. Post TypePosts are separated into templates. The most common template is the standard blog which is similar to a Blogger or Wordpress blog. However, further templates are available for perhaps a photo blog featuring a single blog, a full blown gallery blog, a video blog, a review blog, a recipe blog and so on. These Post Types have different layouts and fields that suit their particular subject matter and bring the subject of the post to the forefront. Posts can be sorted by post type. AuthorsObviously, posts have authors. And posts can also be sorted by their author! Well, that is about it at the moment. I have got as far as getting the standard posts, the categories the widget system and the tag system working together with search. I am starting on topics (which I need to think carefully about - not from the tech view, but from the librarian point of view) and will then wonder onto comments. I am going to try and put both the normal system of comments on, but allow for disqus to be used instead. It currently looks like the following (sorry, it hasn't got enough posts in yet, so it is full of holes!) More to come over the next week or so. Joss

Hi Jan ProcessWire is hugely more flexible that Wordpress and you don't need to know much php at all - in fact, the ability to copy and paste is probably more important! (Especially with all the help round here). There is no strict theming system for ProcessWire in the way you would think of for Drumlapress (!) - basically because that would limit the creation of bespoke websites far too much. The system as it works now means that as long as you can write good HTML and CSS, you can create a brilliant site, without having to learn a templating system. You can more or less approach it in the same way as you would a static site - though, of course, you can get a lot more clever too. If you are looking to integrate it with a framework, then that is as easy as it is with a static site. But, so you get the idea, here is is a veyr stripped back basic profile using Bootstrap: http://modules.processwire.com/modules/bootwire-starter-profile/ As for things like galleries and other plugins, because of the way the site is constructed you can integrate ANY plugin without worrying about it having to fit in with the way the system works. Since there is NO JQuery or anything else for the front end until you actually put it there, you wont run into any conflict trouble with anything supplied by ProcessWire. You simply go and install the plugin in the way the developer says and then learn some very basic php and PW syntax to encorporate your data. Galleries are so simple that it is a joke. As for things like blogs - if you want something very simple (a basic "post some news" sort of thing) then it is so easy to create your own system to work the way you want it to. So, all in all, although it would not be of instest to the average Wordpress user, for any designers out there, it is the perfect way for them not only to design what they want, but in the process learn some basic development skills, which never goes amiss! I am a prime example - I am a copywriter, composer and advertising guru, and yet I am creating my own, very complex blog profile, have created several complex brochure site systems and am learning like mad. I strongly suggest you read the following: Showcase: http://processwire.com/talk/forum/9-showcase/ Detailed beginners tutorial: http://wiki.processwire.com/index.php/Basic_Website_Tutorial (written by me who is not a dev) Explanation of Pages: http://wiki.processwire.com/index.php/Pages You will also find that although there is some serious knowledge amongst the community here, not all of us are developers - but all of us have been surprised how much we have learned. Stay and enjoy! Joss

Really all you need is a few template files and a module would simply serve to create the relevant fields and install the comments module for you. Technically that's pretty simple to achieve, but on a brand new site you could just start with the blog profile and add other pages. It's no different than a normal install except it has blog functionality out of the box - it's really easy to add other pages to it as there's nothing preventing anyone from doing that. I can't remember the layout of the blog profile off the top of my head, bit assuming the homepage template lists blog posts you would just set up a /blog page with it's own template, move the code from the homepage template into it and you have successfully moved the blog into its own section.