Forum Replies Created
-
Posts
-
The prayer menu is resolved – you have to have at least one prayer request for this to work!
Any thoughts on the granularity of permissions of details about notifications?
Can I check the details of the notifications. Are the options either all notifications or no notifications? Is it possible to have notifications only for the categories that are enabled or added to the App Menu?
Thanks for the quick response. I’ve found the setting for notifications and now turned this off.
I’ve tried using html tags under the text tab but when I save the page and go back they are stripped out.
I’ve also now discovered that when I access the prayer menu in the app itself I get a spinning flower on the screen which doesn’t resolve to anything.
I’m also looking at the granularity of permissions for seeing other people’s data so we are covered by GDPR. Would it be possible for a user to be able to login and see prayer requests but not to access the address details of others? Not everyone has given permission to be included in our contact list, but it would be helpful if they could still register a prayer request and see other prayer requests.
Just taking another look at this would it be possible to have a flag set in the details of a custom field as to whether the info appears in the list of possible filters or not?
I’ve just take a look at adding a text filed which might include all sorts of random information and this also appears in the list of possible filters which doesn’t make a lot of sense to me.
Hi Andy,
Thanks for the quick reply, glad to know the list won’t be endless!
Yes, we work with a lot of different funeral directors – amazing how many there are. Maybe part of being and Anglican church that we don lots of funerals for people we have little connection otherwise with.
We are still very much in the setup phase in moving from a different database so haven’t edited many of the individual records yet. We do have GDPR permission, we just haven’t listed it on the individual records yet! It’s actually been a good process to go through as the move has forced us to check all the records on our previous database and decide which ones to transfer to the new one.
Thanks for your help,
Sandy
Hi Andy,
I’ve now imported our database into the Church Admin Plugin. After some work with the Custom Fields I decided not to import into these as it’s difficult to import into a Yes/No field.
In the process of setting things up I’ve found a couple of problems with adding a Yes/No custom field.
The first is that when you look at an individual’s record it always defaults to displaying Yes. This can be very misleading, especially if this data hasn’t yet been entered.
The second issue is that even when the value is changed in the person’s record it will still display as Yes even when it has been changed to No. I checked the MySQL database record and this is correct. It is set to 0 for a No and 1 for a Yes, and no record exists if neither have yet been set in the individual’s record.
I’m hoping to get the functionality set up over the next few days so our church administrator can start work on the manual data updates for safeguarding, photo permissions, previous weddings/funerals etc next week.
Many thanks for your help, and for being so great with your support.
Sandy
That’s great! Just wondering when you’ll be able to add this?
We’re ready to do the import and get working with the plugin. We’ve got a good amount of manual changes to do once the import is done so it’s not a huge deal if we have to add this data. It’s also a good opportunity to double check the data, both in the csv file before import and on the data once it’s actually imported.
Hi Andy,
Just returned from the New Wine conference and tested this having seen your last email update, unfortunately it’s still not working having updated to the latest version of the plugin.
After editing the record and clicking save I get the following displayed and the date isn’t saved:
Array
(
[department_id] => Array
(
[0] => 9
[1] => 10
[2] => 11
)[employment_status] => Paid
[start_datex] =>
[start_date] =>
[application_form] => Yes
[reference1] => Yes
[reference2] => Yes
[interview] => 12/6/2017
[status] => DBS Clear
[DBS] => 2349575
[DBS_datex] => 2018-07-30
[DBS_date] =>
[review_datex] =>
[review_date] =>
[save-person] => yes/
[submit] => Save
)
Record Updated
