SiNNuT

I don't think the process field (of type FieldtypeModule) is used that often in selectors. This is actually the first time i see a question about it in the forum. When it's used the above works perfectly fine.

Great, was just digging through the modules class for some deeper understanding. So for a selector on the 'process' field (field_process) you need to pass the process module id. Which you can get by feeding the module classname to $modules->getModuleID("ModuleClassName"); Which is of course better than look it up manually and hard-coding it like i did Have not needed this but great to keep in mind.

Could you try getting the process module by its id? For ProcessHome: $pages->get("template=admin, process=87, include=all"); I suspect you have to get the process by id, not sure though.

Something like this should work <?php $tests = $pages->find("template=detail-testimonial, sort=-date"); foreach ($tests as $test) { $mydate = date("F", $test->getUnformatted("testimonial_date")); echo "{$mydate}<br/><h3>{$test->title}</h3><p>{$test->testimonial_body}</p><hr/>"; } Actually, i'm not sure that setting an extra var ($mydate) would be most efficient. You can also do it directly and then concatenate your stuff together.

Awesome. Thoroughly enjoyed x-men days of future past. Those Marvel movies seem to be getting better every year. Also looking forward to x-men apocalypse, long wait though.

Really like it. Great use of colors and images. Even themed the google map.

You have piqued my interest. I don't really follow the GitHub issue list on a regular basis but is there some kind of list of lingering, quite obscure issues that are not really reproducible? If so it would be nice to bring these together, along with possible work-arounds.

Glad you got it sorted. If you've searched via the native forum search i'm gonna give you a tip: Always use Google to search the forum. Native search is downright useless most of the times and pretty crappy at best. "site:processwire.com/talk set language active api" in Google would have given some results

Damn, there's too much to like in this thread....

If a page is not active for your secondary language there is nothing to find/get in that language. If you create orders via the API you can set a language active via this: https://processwire.com/talk/topic/4383-how-to-set-language-active-via-api/ Pages created via the PW admin should already activate all languages by default.

I updated the title. How are you implementing multi-language? I'm not sure that you would need to synchronize content between your development environment and the live site. If you are using multi-language fields you can simply convert existing fields to multi-language, right within your live site. You could start translating the content in the live environment. The benefit is that you can also create multi language content for newly added pages. You could then use you dev environment to update you templates, and other stuff to correctly display multi-lang. When satisfied you would just put these to the live site. It all depends a bit on how you are working, but in my experience synchronizing content between dev and live can be pain. PS for fields and templates Processwire also has import/export features which can come in quite handy. This goes for fields and templates, not data.

So where do you run into problems? Entering the code on the back-end? Using CKEditor or plain text? Or displaying on the front-end? If you are able to enter your code snippets in the back-end between for example: <pre><code>...</code></pre> You could use something like https://highlightjs.org/ to syntax highlight it on your blog pages in the front-end. Lots of options really, that depend also on your input scenario.

I'm not quite sure what exactly you are after but there is this module: http://modules.processwire.com/modules/page-references-tab/ If this isn't what you are after you can probably at the least get some inspiration from it and/or modify to your needs.

What Joss said. That's some tasty looking food btw.

Did a couple of MODx Evo sites back in the day, and i liked it. Then Revolution came around and i was excited, tried it and was heavily disappointed. Revo was (and probably is) a very capable system but, at least at the time of my experiments, it was also very slow, from the sluggish ExtJS based UI to reduced front-end page rendering performance compared to Evo. It had a security/access system that was powerful but also very complex and complete overkill for my uses-cases. So i went looking for a substitute to Evo and eventually stumbled across PW and i've never looked back.

I not that familiar with Form Builder but this (the review entry part) does sound like something that Form Builder would handle nicely, without requiring you to do a lot of front-end coding. It allows to save the form submission (a review) to PW pages. I'm sure there are ways to store the listing id in a hidden field, so that you could do a pages->find easily to get all the reviews for a specific listing. If you are comfortable doing some coding you could also quite easily make the form and submission logic yourself using some PHP and the PW api. I'm not sure where the comments belong? A comment on a review or a comment on a listing? Anyways, comments are available in PW (core). For ratings there is http://modules.processwire.com/modules/page-ratings/ you could look at.

There needs to be a template that has the 'allowed templates for children' setting set, and a template with allowed template for parent. And the parent holder page needs to be created in the tree. Away from computer, so not quite sure about the terms, but this should get you there.

Ryan, I've got notified in the PW admin (2.5.3 master) that there was an update (0.1.9) available for Hanna Code. I checked GitHub and saw that you added support for hyphenated Hanna names, cool! Unfortunately, updating via Setup->Upgrades did not go as planned. It timed out after 30 seconds and the mentions of TextformatterHannaCode and ProcessHannaCode had dissapeared from the modules list. After that, a '.TextformatterHannaCode' directory was present in the site/modules and a 'ProcessHannaCode' directory with only partial files (the ace stuff) in it. Clearing out these folder and installing from ClassName also did not seem to work anymore, as it also resulted in a timeout. Grabbing the zip from GitHub, extracting it in site/modules and renaming it to 'ProcessHannaCode' and afterwards refreshing the modules section in PW admin seems to have restored everything, and i now have an up to date (0.1.9) Hanna Code Module, with all Hanna Codes i already had working correctly. Maybe it was the initial time-out that got me screwed, but maybe there are some (re)naming issues when upgrading to the latest version of Hanna. Thought i'd mention it anyway.

Lovely site but unlike most i don't particularly like the menu. On mouse hover the expanding works. But on touch devices such as my smart-phone to me it doesn't work that well. Tapping the garbled letters you would maybe expect it to expand, and most of the times it does, but it also takes you to a page you are not even aware you clicked, like contacto or crowdfunding. Sometimes it seems to stop to function altogether. This is on Android 4.4.4 and recent Chrome and Firefox versions. It feels a bit random and unintuitive. I'm not sure a main navigational element should be this 'experimental'.

That would be a shame, cause i really like what this module brings/brought to the table.

Note that if you would want to insert the homepage somewhere else, let's say to center it in a nav (in this case after 'Werk') PW comes with more handy stuff. All (or at least most) available on the http://cheatsheet.processwire.com/ $homepage = $pages->get('/'); $menu_items = $homepage->children; $menu_items->insertAfter($homepage, $menu_items[1]); // insert $homepage after the second homepage child

I think you can get some inspiration from Ryan's example over here: http://processwire.com/api/multi-language-support/multi-language-urls/#language-switcher

Ah ok. Good to know

The module README says that text inputs will ignore the hotkeys? If true, this will not help Joss with his text areas.

I like it, a lot. (those zoomy/wiggely pictures on for example the product page are scary )