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: error after clicking event on calendar #7061

Closed
yeison08 opened this issue Jun 3, 2024 · 3 comments · Fixed by #7153
Closed

Bug: error after clicking event on calendar #7061

yeison08 opened this issue Jun 3, 2024 · 3 comments · Fixed by #7153
Labels
bug good first issue Indicates a good issue for first-time contributors
Milestone

Comments

@yeison08
Copy link

yeison08 commented Jun 3, 2024

Description

**Error after clicking event in calendar.

Go to calendar and click an already existing ever to recreate. Error also presento on Demo.**
erro calendar

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

  • ChurchCRM version: [e.g. 5.4.3]
  • PHP version the server running: [e.g. PHP 8.2.13]
  • DB Server and Version the server is running: [e.g. MariaDB 11.4, MySQL 8.2]

Steps To Reproduce

Steps to reproduce the behavior:

ℹ️ As a bug reporter, the preferred mechanism to record steps is to download Cypress Recorder from https://chromewebstore.google.com/detail/cypress-recorder/glcapdcacdfkokcmicllhcjigeodacab?pli=1, record your interaction and copy the results here.

📋 Cypress Recorder Results:

<please replace this section with the results from Cypress Recorder>

⚠️ If you cannot do this for some reason, please document the steps to reproduce below.

(note: this flow is not recommend and will make it more difficult on the maintainers of ChurchCRM)

  1. Go to '...' (if possible, please provide the URL path e.g. /v2/dashboard)
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots and/or logs

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

📋 Relevant screenshots:

<please insert your screenshots here>

📋 Logs:

<please replace this section with the relevant logs>

Debugging Steps

ℹ️ If you need help debugging, please refer to the wiki for guidance: https://github.com/ChurchCRM/CRM/wiki/Logging-and-Diagnostics.

  • What has been done to debug the issue so far?
  • Have you looked at the browser's developer tools to see if an error is thrown / network request failed?
  • Are there any associated error logs on the backend that get emitted when you attempt to do this action?

Desktop (please complete the following information):

  • OS and Version: [e.g. Windows 11, macOS Sonoma 14.0]
  • Browser (and Version): [e.g. Chrome 120.0.6099.216, Safari]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone15 Pro Max]
  • OS: [e.g. iOS 17.2.1]
  • Browser (and Version): [e.g. stock browser, Safari]

Additional context

Add any other context about the problem here.

@yeison08 yeison08 added the bug label Jun 3, 2024
@DAcodedBEAT DAcodedBEAT added the good first issue Indicates a good issue for first-time contributors label Jun 3, 2024
@respencer
Copy link
Contributor

Confirmed.

Copy link
Contributor

github-actions bot commented Aug 8, 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 Aug 8, 2024
@DAcodedBEAT DAcodedBEAT removed the Stale label Aug 8, 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 Sep 10, 2024
@DAcodedBEAT DAcodedBEAT removed the Stale label Sep 10, 2024
@bigtigerku bigtigerku mentioned this issue Sep 20, 2024
12 tasks
@DAcodedBEAT DAcodedBEAT added this to the vNext (5.10.1) milestone Sep 21, 2024
@DAcodedBEAT DAcodedBEAT linked a pull request Sep 21, 2024 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug good first issue Indicates a good issue for first-time contributors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants