Soma

$partnerTitle = $pages->find("parent=1004,partnerID=$partnerID")->title; Will not work cause find() returns a page array and not a single page. Rather use $partnerTitle = $pages->get("parent=1004,partnerID=$partnerID")->title; Or even $partnerPage = $pages->get("parent=1004,partnerID=$partnerID"); $partnerTitle = $partnerPage->id ? $partnerPage->title : "PartnerPageNotFound"; But why you need a function for that is beyond me. And also why there's obviously an ID you enter manually to then get a page? Why not use a page field to select the partner page?

Nice we now moved from a plain module list (PW2.1) to sections for sake of overview, now you make it flat again with this module I think while it's nice to have all these steroids, it's something I'm trying to keep away from doing too much admin tweaking. Some of these should be considered in core and not via such an module. It's prone to errors and confusions once core admin changes stuff around. Not trying to drag you down. Just my 2 cents.

http://buildinternet.com/project/supersized/

It says 500. https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/core/Selectors.php#L24

Then it seems your server doesn't allow Directory listings +Indexes. Nothing to do with PW.

FilenameArray is just a helper class not a Wire class like Page or Pages.

It's the Options -Indexes In the .htaccess that prevents directory listing.

No need for a extra Process page. Just send a ajax POST/GET request with a special key you recognize in your module's init(), do the work and send back an result.

I just updated the module to support also href='mailto

I think actually the problem is in the details. The module's regex doesn't seem to account for href=' only for href=" So this should be: if($l->adr_email) $out .= "<a href=\"mailto:$l->adr_email\" class='link_mail'>$l->adr_email</a> <br>";

No it's powerful and fast and dangerous ... With one "L"? It's more efficient... No I don't know your obsession. Well I don't know what MenuBuilder contents are. Why? Does MenuBuilder not have any render functions? Aligator and MSN only work with Pages.

Aligator (wip) Processwire Module to render a nested tree starting from a single root or an array of pages. Aligator is similar to MarkupSimpleNavigation but has a different approach of how to define the markup for your menu. It doesn't assume any markup or classes. It's up to you to define them where needed. It's less plug and play and requires some more advanced knowledge of ProcessWire, as some additional setup and coding is needed. But allows for powerful and easier customization without using hooks. Aligator uses callback functions to achieve this. Additionally a selector can be used to filter the children for your navigation. Note: This module is a fun project trying to find simple configurable method to render navigations. It's a work in progress and there might be major changes to how the module works. See further infos and examples on the repository: https://github.com/somatonic/Aligator

Or add a checkbox to the template and when saving a page check for date and if empty set the checkbox. Then use "sort=hasdate_checkbox, sort=training_start, sort=id"

Repeaters are located in /admin so access protected too. So I guess for a not logged in user you wouldn't be able to $pages->find(selector) the repeater pages. I think then you'd need a "check_access=0" or a "include=all". Since they're in /admin you could also consider implicit "has_parent=RepeaterParentID" or "has_parent=2" ($config->adminRootPageID) instead of exluding trash somehow.

It has happened in the past 2 times already and will happen again sooner or later. Looking back I still liked the first forum the most in terms of overview and browsing. I got annoyed by the changes to something I used everyday and was used to it. Always takes some time to adapt and we all know it can be frustrating. Sometimes it's just the styling that's so different your brain has to adapt. But after a while you'll maybe even appreciate it or forget about it. But then it has to be done and I appreciate all the work put into it, as it's a tedious work done in Pete's spare time. I'm also surprised to how much has changed in the new version as it's completely a new thing, and I it took me a while to see where I find what. I think the "why" isn't the problem it's the how you wrote it with the uppercase and the 4 (edit: oh 5!) exclamation marks!!!!.

Are they active for the alternate languages even?

PW doesn't allow for multidimensional post arrays. https://processwire.com/talk/topic/691-wireinput-only-allows-one-dimensional-arrays-why/

I think this is possible like this. There's no fields PW sees and knows about, just custom markup. I think you'd have to use inputfields or maybe save the values yourself.

Well I think we'll have to stick with this bug still for a long time since Ryan can't reproduce it. I just installed again a vanilla PW locally and same scenario once SessionHandlerDB is installed.

Oh really? Lots of headaches for something that simple to find out? Here's your 3000th like!

I just wanted to know if anyone can reproduce this behaviour: https://github.com/ryancramerdesign/ProcessWire/issues/1871 Install SessionHandlerDB and upload a bunch of jpg to an images field. They upload fine and show but after saving the page some images are not saved and wont show anymore. They're still in the assets folder but orphaned. Thanks

This is like this since a long time already. I'm surprized this has never been addressed.

For the simple minded this would be the foreach version that does the same. $colors = array(); $childrenByColor = array(); foreach($children as $child) $colors[$child->color][] = $child; foreach($colors as $color => $items) { $childrenByColor[] = "$color (" . $items->implode(",", "title") . ")"; } $line = implode(", ", $childrenByColor);

The reason you would have to look for is why the homepage has output formatting turned off, because it's not usual at all. Output formatting is always turned on in front-end templates.