diogo

Speaking of fortrabbit. I already emailed them telling about the change that has to be done on pw's .htaccess to install it there, and they answered that they will make sure to include pw specific insructions on their new docs.

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.

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

A tip. When you click on the number of each post (upper right corner of the post box) it gives you the direct link of the post so you can share it easily.

chhhhhhh... you will wake up Joss and Mathew

Hello my PHP addicted friends Since I see so many struggling with JS (read: jQuery) in the forums, here is a good learning resource via Cody Lindley's twitter http://superherojs.com/

Looks good chris! Only thing that bothers me is the "go to the top" arrow. It's too present, and you don't really need it because you don't have any long page. Besides, in some screen sizes it covers other elements. I would remove it

and for those who use chrome https://chrome.google.com/webstore/detail/php-ninja-manual/clbhjjdhmgeibgdccjfoliooccomjcab?hl=en

It depends a lot of what your needs are. If you think that the content will be all translated, go for the core approach http://processwire.com/api/multi-language-support/multi-language-fields/ since soon it will have support for different urls. If your site will be very simple, and you need to have different tree content in each language, go for tree approach, since it gives you more flexibility. Edit: I'm not recommending Soma's http://modules.processwire.com/modules/language-localized-url/ because soon there will be a more natural way to do more or less the same in the core.

Just in case this isn't obvious, pwired means that jQuery is used in the admin. PW doesn't enforce any library on the frontend, and you're free to use whatever you want.

If the repeater serves this purpose, I don't think we should be put away by it's name. The only reason I think this should be a new fieldType is because the repeater carries two unnecessary things for this purpose: the serialization numbers, and the extra visual grouping. Of course those could also be removed in case the max would be 1, but with the extra work, why not just have a different kind of field?

You could do something very simple, even if it only pulls your twitter and some marked posts from the forum

Good eye Wanze!

Looking good Luis. But I have to confess that the unity dash always irritates me a bit

Hello Fred, welcome to the forum. ProcessWire is as simple or as complicated as you want it to be, and I doubt that there is any other CMS that allows for extreme simplicity as PW does. When you enter the admin for the first time you are logged in as superuser, and that's why you see the setup and modules links. To give you an idea of how the admin would be for your client follow these steps: Go to Access->Roles and create a new role named "editor". Check the boxes "View pages", "Edit pages" and "Delete pages". Press "Publish". Go to Access->Users and create a new user. Give the user a password, and under "Roles" check the boxes "guest" and "editor". Press "save". Now logout and login with the new user credentials (tip: use incognito mode from your browser, so you don't have to logout). You will notice that the admin is completely stripped of any advanced actions. As for the projects, the Processwire way of doing this is by creating a new page for each project. Have a look at these tutorials to get a feeling of how it works: http://wiki.processwire.com/index.php/Small_Project_Walkthrough http://wiki.processwire.com/index.php/Basic_Website_Tutorial

You could make /site the root of you bibucket repo

I knew I had answered to this before! It wasn't easy but I found it http://processwire.com/talk/topic/1916-another-categories-question/

Rob, this idea is not very different of your previous one of imposing a limit to just one repeater. So, I can imagine that this kind of field would work exactly like a repeater works behind the scenes (creating a repeater page under "admin" and adding the repeater pages to it) but without the need of grouping the fields inside a "field#1" label or the "+add item" button. Edit: Just like with repeaters, this wouldn't be more than a single page field type on steroids

It's because you have $page_sent->save(); also outside the if. Yes, if you will use fields from this page later in the code sequence. If not, you don't need to.

How do you create the $page_sent variable? Did you confirm that it really holds the current page?

Hi lucky, For OR use the pipe | symbol. So, if you want pages that have one of three templates, do this: $location_cat = $pages->find('template=location_category|spot_category|another_category'); This is documented here http://processwire.com/api/selectors/. A great read

Gebäude alles klar gedanken versunken! Tschüüüss

I think your best choice is the Page fieldType holding the users that have visited the page. Add onePage fieldType to the templates of the pages you need to monitor and choose the Users page as parent of selectable pages. Then use the API to start populating it. if(!$page->counter->has($user)) { $page->of(false); $page->counter = $user; $page->save(); } and to get your view count: count($page->counter)

Yeah!! At least until Ryan jumps in and kick our asses with his arguments