search

PalisadoesFoundation / talawa-admin

Admin portal for the Talawa Mobile App. Click on the link below to see our documentation
https://docs.talawa.io/
GNU General Public License v3.0
137 stars 565 forks source link

Error when editing Super Admin profile #1924

Open palisadoes opened 6 months ago

palisadoes commented 6 months ago

Describe the bug Error when editing Super Admin profile

To Reproduce

Steps to reproduce the behavior:

  1. Start at the Super Admin organization screen:
  2. Navigate to the view profile screen
  3. Error is visible:

Expected behavior

  1. No visible error
  2. Tests must be created for this fix. All tests must be valid and pass

Actual behavior

Screenshots

  1. Start at the Super Admin organization screen:

    image

  2. Navigate to the view profile screen

    image

  3. Error is visible:

    image

Additional details

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

pranshugupta54 commented 6 months ago

@palisadoes, do you mean the error on the left side for Org not found? or email address coming out on the right side?

We have designed this page to be Organization specific, where the user profile will have options related to Org.

palisadoes commented 6 months ago

The loading organization error in the top left hand corner

pranshugupta54 commented 6 months ago

It's going to be same for Admin profile or direct member profile bcuz the side left panel is same for Organization options hence causing error when directly going to Member screen without selecting Org first.

github-actions[bot] commented 5 months ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

coderpawan commented 3 months ago

Ohhh I also faced the same error when i tried to logout but that time i didnot notice this raised issue in the repo. I have solved the issue by putting conditional statement . Actually the error was in the LoginPage.tsx file where org.address was used to access the city but there was nothing to handle if org.address would get null which was the root of the error. So After adding the conditional statement I have solved it. Now tell me what to do next?

palisadoes commented 3 months ago

Our playlists explain your next steps

  1. https://www.youtube.com/watch?v=iYdyBfXdV2w&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF&index=7&pp=gAQBiAQB
  2. https://www.youtube.com/watch?v=lmNeydX_0sQ&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF&index=9&pp=gAQBiAQB
  3. https://www.youtube.com/watch?v=dQuEKpsy1vM&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF&index=10&pp=gAQBiAQB
github-actions[bot] commented 2 months ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

AnshulKahar2729 commented 2 months ago

@palisadoes please assign me the issue, I would like to work on this.

AnshulKahar2729 commented 2 months ago

I would like to work on this issue, is this issue still a priority?

palisadoes commented 1 month ago

@AnshulKahar2729

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

AnshulKahar2729 commented 1 month ago

@palisadoes now you can assign me, previous issue assigned to me is now resolved.

palisadoes commented 1 month ago

@AnshulKahar2729

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

AnshulKahar2729 commented 1 month ago

@AnshulKahar2729

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

Yeah but I have only one issue assign.

Cioppolo14 commented 1 month ago

@AnshulKahar2729 It looks like you have 2 issues assigned. The total is counted across all 3 repositories.

ARYANSHAH1567 commented 1 month ago

@palisadoes Can you please assign it to me?

ARYANSHAH1567 commented 1 month ago

I have solved the issue, Can anyone please assign it to me so that i can create a pr

ARYANSHAH1567 commented 1 month ago

The error was that for the organizations creator id was being passed to the api and it was treating it to be as orgId so i have to also change a file in the talawa-api so will i have to create a issue in api and link it here to fix it?

github-actions[bot] commented 3 weeks ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

ARYANSHAH1567 commented 3 days ago

I tried Solving the issue, identified the thing that was causing the issue but there were some tests that were still failing that i couldnt fix so i am unassigning myself this issue

sethdivyansh commented 3 days ago

Please assign me