-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with config "archived" person statuses #1120
Comments
The rationale for having more than one is to be able to distinguish "deceased" from "moved out of area" or "joined another church" etc. But the point you raise about the auto-archiving is worthy of thought... |
And perhaps the config interface could use some tweaking to make it clearer what "is archived" means. |
…s. Make the labelling clearer and explain that the first 'archived' status will be used when auto-archiving persons in an archived family.
I can't replicate this error on PHP Version 8.3.9 ...? |
Commit d4d16f5 prevents the 'Archived Person?' flag from being removed from everyone, which is good! However it doesn't stop people deleting the 'Archived' status altogether, which is the situation we've encountered: |
Try deleting a person, then 'Archive and Cleanse' (e.g. on https://easyjethro.com.au/demo/). I get a stacktrace:
|
THanks, will fix. Different error message to what you mentioned originally. |
In Jethro 2.35.1 and earlier there was a hardcoded
archived
person status, and all was well.In Jethro 2.36.0, person statuses became editable, and the one considered "archived" is configurable:
I'd like to suggest that there should be one and only one 'archived' status:
Because:
jethro-pmm/db_objects/person.class.php
Line 1110 in 91f6f61
(This code is also buggy, giving the error
PHP message: Only variables should be passed by reference
)That is going to give incorrect results if e.g. someone "archives" an existing status (thinking it is equivalent to "in use"):
The above 'archive family' code is going to break.
So IMO having one and only one 'archived' status is the best solution.
The text was updated successfully, but these errors were encountered: