Tom Barrett

Thanks. To be honest, supporting non-standard ports is probably not going to be a high-priority fix. But it's good to have the issue noted, and we'll work on it when...

Problem with explicit ports starts here in init.php ``` if (strpos(array_get($_SERVER, 'HTTP_HOST', array_get($_SERVER, 'SERVER_NAME', '')).$_SERVER['REQUEST_URI'], str_replace(Array('http://', 'https://'), '', BASE_URL)) !== 0) { $do_redirect = TRUE; } ```

Yeah that'd be one solution, if the listed names were links. But something that takes up less space would be preferable. Or some way to click on the disabled option...

> t may have been 'fixed' in the current version of Jethro but in the version I am running I can search for a person who is absent and just...

One quick thought here: The current sytax is something like [Core.first_name] I think it would be clearer to use something like [person.first_name{status=Core}] This makes it more obvious that it's a...

Not currently available as a docker container, I'm afraid. I'll note this as a feature request.

Could be a property of the roster role. For those with select-multiple=false it could be presented as "required". For those with select-multiple=true it could be presented as "number required" (0+).

Implementing this issue could help with a better implementation of #829. At the top of a run sheet, roles which are "reqiured", but unfilled, could be shown so that their...

Good thought. It's not currently supported.

I don't like the idea of a whole different "visitor" entity. They are persons! Differentiating people with different levels of connection to church is what the "person status" field is...