tiagoroldao

I've been trying to use the PageAutoComplete fieldtype to connect some autors (teachers and students) to a particular work, but allowing to set unpublished (or hidden) student and teacher pages as well. For that, I've established a filter:

template=teacher|student, include=all
or
return $pages->filter("template=teacher|student, include=all")

In any other compatible fieldtype, it works just as it should, using php code or just the selector, showing me every teacher/student. But using the PageAutoComplete, it never finds the hidden or unpublished pages.

Is it a bug? Or am I doing something wrong?

I've been working on a medium-to-large scale project using pw (browsable alumni works and news repository, for a multimedia design school).
I assume this kind of project is just what PW was written for: loads of information that can be cross-searched, etc.. And for it to work smoothly, sharing fields is the way to go, of course (do correct me if I'm wrong..)

The "problem": some fields acquire diferent roles in different templates ("title" can be a Title or a student name on a student Template), and may benefit from independent descriptions (for setting protocols - specially important on a repository)

Multiple field descriptions would be awesome (specific to each template), but I imagine the work that such a change could mean may not be worth it... I haven't explored the DB very deeply, but I assume the description is in a field entry, and would have to be in the field-to-template entry... Or maybe I'm reading it all wrong

Any thoughs? Am I completely off the ball park?

First of all, my congratulations to Ryan on this amazing piece of software! This is my first post in these forums, but I have been a silent noob for a few months, learning while using processwire for every web project in the Multimedia Design course I'm currently finishing!

On to the bug/problem (is this the right place for this post?) :
When I try to sort a PageArray object using the $a->sort() method on a string field, say, the title, the API places the ones starting with uppercase first, and the lowercase last, like so: A,B,C,D,a,b,c,d...

Am I doing something wrong/missing something?

Cheers,

Tiago