Skip to content
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

Bug: Managing family properties on Family View page does not work properly #7165

Open
kuba-marek opened this issue Sep 22, 2024 · 5 comments

Comments

@kuba-marek
Copy link

kuba-marek commented Sep 22, 2024

Description
A clear and concise description of what the reported bug is:

  • ChurchCRM version: [5.10.0]
  • PHP version the server running: [PHP 8.2.21 (my install), also tested on PHP 8.2.22 (Softaculous Demo)]
  • DB Server and Version the server is running: [MariaDB 10.11.6 (my install), also tested on MySQL 8.0.39 (Softaculous Demo)]

Steps To Reproduce
Steps to reproduce the behavior:

  1. Run Softaculous Demo / fresh install
  2. Add a Family
  3. Go to Family View of a new Family (/v2/family/1)
  4. On the #Properties pane, click on round + icon
  5. An Assign a New Property dialogue will open with "Single Parent" option in the drop-down menu
  6. Go to People -> Admin -> Family Properties menu
  7. Delete the Single Parent property and
  8. Create some new (other) property
  9. Go to Family View of your new Family (/v2/family/1)
  10. On the #Properties pane, click on round + icon
  11. An Assign a New Property dialogue will open with "Single Parent" option in the drop-down menu

Error no. 1 - Single Parent should not be there (was deleted in step 7)
Error no. 2 - Property created in step 8 should be there instead

  1. Choose Single Parent property from the drop-down menu and try to assign it

Error no. 3 - ERROR dialogue will open:
Error making API Call to: /ChurchCRMjsvxa30s4x/api/people/properties/family/1/2, Error text: Slim Application Error

  1. Refresh the Family View page several times, you should manage to get your new property (added in step 8) on the drop-down menu of the Assign a New Property dialogue eventually
  2. Assign the new property

Error no. 4 - "No data available in table", "Showing 0 to 0 of 0 entries" and "No property assignments" messages are shown, and your new property is not shown in the table on the #Properties pane (but the property is actually properly assigned in the database in the 'record2property_r2p' table)

  1. Refresh the Family View page several times, you should manage to get your new property visible in the table on the #Properties pane. But

Error no. 5 - "No data available in table", "Showing 0 to 0 of 0 entries" and "No property assignments" messages are still shown

  1. Try to delete your new property from the table on #Properties pane.

Error no. 6 - your new property is still visible in the table (but it is actually properly removed from the database in the 'record2property_r2p' table)

  1. Refresh the Family View page several times, you should manage to have your new property removed from the table on the #Properties pane.

Expected behavior

The + Assign A New Property dialogue of the #Properties pane on the Family View should instantly reflect properties added (or removed) on the Family Properties admin menu. Properties assigned using the Assign A New Property dialogue should be instantly visible in the table of the #Properties pane. Entry count below said table should show correct counts when there is some entry in the table. Removing the property from the table on the #Properties pane should remove it from this table instantly. The drop-down menu of the + Assign a New Property dialogue of the #Properties pane should not show non-existent properties.

Screenshots and/or logs

If applicable, please include screenshots or share logs to assist in explaining your issue.

📋 Relevant screenshots:
family-property-bug

Desktop (please complete the following information):

  • OS and Version: [Windows 11]
  • Browser (and Version): [Chrome 128.0.6613.139]

Smartphone (please complete the following information):

  • Device: [Huhlawei P30 Pro]
  • OS: [Android 11]
  • Browser (and Version): [Chrome]

Additional context

It looks like there is some cache for the API calls?

@kuba-marek kuba-marek added the bug label Sep 22, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Oct 25, 2024
@kuba-marek
Copy link
Author

Commenting to remove stale label..

@DAcodedBEAT
Copy link
Contributor

@kuba-marek is this an issue on 5.11.0 ?

@kuba-marek
Copy link
Author

@DAcodedBEAT Yes, both on my installation and Softaculous demo.

@github-actions github-actions bot removed the Stale label Nov 7, 2024
Copy link
Contributor

github-actions bot commented Dec 7, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants