NoMongo: Error While Loading Events Data in Volunteership Section

[gkbishnoi07]

Describe the bug
The Volunteer section fails to load events data, displaying an error message:
"Error occurred while loading Events data"

To Reproduce
Steps to reproduce the behavior:

1.Open Talawa Admin (develop-postgres branch)
2. Login to the User Portal using [email protected].
3. Join an Organization & Visit an Organization Page
4. Navigate to the Volunteers section.

Expected behavior
The events data should load successfully, displaying upcoming organization events.

Actual behavior
An error message is displayed: "Error occurred while loading Events data".

• The GraphQL API returns a null data response with an error:
  "Cannot query field eventsByOrganizationConnection on type 'Query'"
  This suggests that the queried field does not exist in the GraphQL schema or is incorrectly referenced.

Screenshots

Additional details

• Check if the eventsByOrganizationConnection query exists in the backend schema (talawa-api). If it was renamed or removed, update the frontend accordingly. If missing, define it properly in the GraphQL API or use a similar existing query

Potential internship candidates

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

• Student Internship Programs talawa#359

[MayankJha014]

Assign this to me

[mpdesai90]

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.

[gkbishnoi07]

@mpdesai90 assign me

[Mayankpulse333]

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.

I know but i have one issue that why i asked

[github-actions]

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.

[Cioppolo14]

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

[hkumar1729]

@Cioppolo14 pls assign this issue to me.

[hkumar1729]

Queries and mutations for Event Volunteers/VolunteerGroups don’t exist yet. There’s already an open issue for this, so I think it’s best to wait for that to be implemented.

[github-actions]

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.

[Cioppolo14]

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

[hkumar1729]

@Cioppolo14 pls assign again im already working on it.

[github-actions]

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.

[Cioppolo14]

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue

[github-actions]

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.

[VanshikaSabharwal]

assign

[github-actions]

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.