SiNNuT

Hi gottberg and welcome to the forums. Searching these forums with the term 'treemenu' will give u 4 or 5 topics which deal with various ways to do multi-level/recursive navigation. Just choose the one which best suits your needs. In one of those topics apeisa mentioned something about a simple navigator module but i don't know if this was ever made. On a side note, and in case Ryan is reading this: These questions about menus and navigation come up a lot. Wouldn't i be a good idea to expand this page: http://processwire.c...art/navigation/ to include some information about approaches to do multi-level stuff. Maybe some common scenarios and corresponding functions?

If you could be a bit more specific about where you are switching from and what you would like to achieve/make it would be easier to advise. PW is a very flexible tool with almost all of the building blocks to create great sites fast. I've seen people migrate from typo3, drupal, wordpress etc., so this is all within the realm of possibilities. If you haven't done so already i would just install PW a give it a spin. Play around with some templates, add a couple fields, do some page relations etc. Regarding your questions: - Not that i'm aware of. PW doesn't dictate how you setup and structure your sites. It's pretty easy to setup blog functionality though. However, if all you want to do is blog there are other systems available that are more geared towards out of the box. - Not sure - You want to use these plugins in the PW backend? - Haven't tried to input PHP code in fields myself, don't know if this is possible. It doesn't really sound like something you would want to do. In general i think this belongs in template files, modules etc.

I really like this functionality and in a lot of situations the implementation based solely on titles will suffice and additionally has the benefit of being able to add/paste in multiple items at a time. But at the same time i gotta agree with Soma: quite often the page(template) you want to reference has more than one field you will want to populate. From a UI- and fast workflow perspective it would be great if this was possible. I guess this would mean some sort of modal popup. As the PW user-base expands i think this would be frequently used and a killer feature, really taking the relational aspect a step further (from UI perspective). So for possible future directions, and to make PW even more awesome than it already is i ask you to take this into consideration.

i'm not entirely sure but i think this might be it: http://processwire.com/talk/topic/5-how-do-i-retrieve-all-pages-within-a-certain-monthyear/page__hl__date__fromsearch__1 Also, this could be useful in relation to the above link: http://processwire.com/talk/topic/263-creating-archives-for-newsblogs-sections/page__hl__archive__fromsearch__1

wow, great looking site!

Biotech, while it is certainly possible to achieve what you want i gotta agree with some of the previous comments; try to avoid multipage articles/tutorials/whatever. If you are dealing with lengthy tutorials why not create some sort of table of contents and work with page anchors? I think this makes much more sense in the web world. You could write some logic in your tutorial template that generates the table of contents for you, depending on your structure and requirements.

I dun gettit

I won't be needing a multi language site anytime soon but it's great to see PW having all the bases covered here. Lot's of options.

Thx for checking that there isn't something unexpected happening.

I haven't actually tried it but judging from the pics another excellent theme. Also a nice touch with the page creation time you show in the footer. Your Moderna template is also ace.

Like i said, apparently wampserver comes bundled with it nowadays, i didn't even know it was doing 'something'. Anyways, i did some further testing. I'm on Win7 HP, 64 bit, Wampserver 2.1 (php 5.3.4, mysql 5.1.53, apache 2.2.17) I'm on a vanilla install of PW running from the dev branch. I've only installed the module ImportPagesCSV. The scenario of when these 'error' messages appear is when i change the template of a page with children an then save that page. For example the default 'About' page with 2 children or my 'News' page which currently has 41 children. The actual saving does seem to take place because when i next visit the page in the admin the template has changed. After playing around with xdebug.max_nesting_level setting it appears that 108 is the last value that gives an error. Setting it to 109 and everything is fine and dandy. Adding extra levels of children doesn't seem to affect anything. From the Xdebug documentation: After putting the site in debug mode i was able to get more detailed info. See the attached self containing htm file for a complete call stack leading to the 'error'. I don't know what to make of it, maybe it's of some use to Ryan. Error: Maximum function nesting level of '100' reached, aborting! (line 95 of E:\wamp\www\wcpw\wire\core\Data.php) This error message was shown because you are logged in as a Superuser. Error has been logged. Error: Maximum function nesting level of '108' reached, aborting! (line 162 of E:\wamp\www\wcpw\wire\core\Wire.php) This error message was shown because you are logged in as a Superuser. Error has been logged. error.zip

I encountered the same when changing the the template of a page and saving it: from the PW log: 2011-12-28 17:36:46: admin:/wcpw/processwire/page/edit/:Error:Maximum function nesting level of '100' reached, aborting! (line 95 of E:\wamp\www\wcpw\wire\core\Data.php) Setting xdebug.max_nesting_level to 200 in php.ini did solve the problem. I'm running a default Wampserver (v2.1) and to be honest i didn't even know xdebug was doing anything. How can i know for sure if xdebug isn't interfering with anything or slowing shit down? Apart from xdebug, does this error have a meaning?

thx ljones, I did test it myself and it seems to be doing exactly as expected. Like is said, i'm not a php/pw expert so maybe someone can confirm that there are no gotcha's with this code before you put it to production. (PW api makes it easy to do stuff like this)

Wow, very slick site! It isn't super fast for me but definitely not slow. I would be very interested in a writeup on how you handled the migration.

I'm not a coder but looking at the API isn't this a possible solution? <?php $bkgimages = $page->parents()->append($page)->filter("bkgimage!=''"); $last = $bkgimages->last(); echo $last->bkgimage->url; ?> What this does (i think;): Grab all parent pages of the current page up to the root, append the current page and filter the array for empty bkgimage fields Grab the last item from the array. If the current page has a non empty bkgimage field it is $last, if it's empty $last will contain the bkgimage from the parent of current. This continues all the way up to the root. I think this should work for single image bkg fields and no need for if else checks.

There is a video that showing the kind of approach Pete describes. http://processwire.com/videos/page-fieldtype/ But i'm guessing you want something a little more 'automated'. A module/class that would allow you define some parameters like which pages and fields you want to search for possible relations, give fields a weight, excludes stopwords, and then searches and calculates a ranking/resultset based on the things you define. You would call this module/class in your template, possibly using MarkupCache to avoid a performance hit. Could you elaborate on what functionality you would like to see in your "Related pages" module?

Nice site. Maybe you could consider adding a favicon.

I can't answer your questions, but it's worth mentioning that a "Page history module" is already on the roadmap. http://processwire.com/about/roadmap/

Heidis is a tad slow for me, but acceptable. DG Creative is so slow that it's practically unusable, it takes 1 to 2 minutes for pages to appear on the screen and even then it just keeps on loading and loading. I'm located in The Netherlands.

I'm not sure how this would fit in the PW code base and philosophy (or maybe there are already things in place) but i think it would be great if there was some sort of validation library that ties into the field UI functionality and is also usable via API. Let's say i'm making a site where eventually a couple of people will be allowed to add riders that will compete in a cycling event. A rider has a license number so i add an integer field to my rider template. Ideally i would want to make this field required but also make sure the number is in a certain range (e.g. between 1000 and 50.000), because i know numbers out of range are invalid. It would be great if i was able to define (multiple) validation rules on my license number field in the UI. These options could go under the any of the existing tabs (details, input, advanced) or a new 'validation' tab. Maybe it could even be possible to define custom error messages for your rules right there. Off course one would have to consider multi-lang issues but i'm just thinking out loud. A user who tried to save a rider page without a license number, or a number outside of the defined range would get to see the error messages upon trying to save. Some examples of different validation rules and options: laravel.com/docs/start/validation http://fuelphp.com/docs/classes/validation/validation.html

Thanks for this thorough overview. I'm not the one to comment on the code side but it seems like a well thought out solution.

Maybe i'm easily fazed but it seems you are trying to do a lot. Is this a hobby project or do you intend to make a serious and dedicated effort? How many users do you hope to attract and what is the added value and/or functionality you offer when you compare to tv.com, imdb.com, rottentomatoes and the like? Not trying to talk you out of it, just curious. If i think of these types of sites, most of the times there's also: (user)comments, reviews, voting/ratings, forum or message board, different types of news items etc. So your core system should be flexible enough to add features without too much of a hassle. Probably a straightforward 1-step approval system won't suffice in the long run so you would need to have/built some more work-flow capabilities. I think your best option is to choose a framework that best suits your needs. This allows you to build from a solid base but you still can control every aspect of your application/site, from routing to the way you design your database(queries), views, caching mechanisms etc. Some well- and lesser known examples: Zend Framework, Symfony, Cake, Kohana, Yii, Lithium......

The following is written in Ryan's topicstart: So i guess you'll have to wait till a future version (dunno if Ryan has this planned anytime soon), or you could have a look at the code and possibly add something yourself.

Processwire is free software released under GPLv2 license. I am no expert on this subject but i think GPLv2 allows you to make both modifications you metioned as long as this 'derived work' remains under the same license terms.

iirc html5-boilerplate started of with those comments and ie classes in the body tag. At some point they decided it was better to put it in the html tag. Some of the reasons are listed here: https://github.com/paulirish/html5-boilerplate/wiki/The-markup Using the boilerplate is a pretty nice way to start of a new project.