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: Files deleted in new release is still on site after upgrading #7035

Open
romdricks opened this issue May 18, 2024 · 4 comments
Open

Bug: Files deleted in new release is still on site after upgrading #7035

romdricks opened this issue May 18, 2024 · 4 comments
Assignees
Labels

Comments

@romdricks
Copy link
Contributor

romdricks commented May 18, 2024

Description

I upgraded from 5.7.0 to 5.8.0. I was comparing changes made to the files (just for learning) and i realized that some files were deleted and some where moved to a different location. I was curious, so I did a manually checked on my site. Upon doing so, I realized that the files that were deleted in 5.8.0 were still on my site after upgrading.

These are the two files that were deleted for the current release:
src/ChurchCRM/Emails/users/PasswordChangeEmail.php
src/ChurchCRM/Interfaces/SystemCalendar.php
src/views/email/BaseEmail.html

This was deleted for the 5.6.0 release:
src/Menu.php

  • ChurchCRM version: 5.8.0
  • PHP version the server running: PHP 8.1
  • DB Server and Version the server is running: MariaDB 10.11.7

Screenshots and/or logs

Here is a screenshot of one of the files:

Screenshot 2024-05-18 163559

Expected

5.7.0...5.8.0

Screenshot 2024-05-18 164848
@romdricks romdricks added the bug label May 18, 2024
@respencer respencer self-assigned this May 20, 2024
respencer added a commit to respencer/ChurchCRM that referenced this issue May 20, 2024
@respencer respencer linked a pull request May 21, 2024 that will close this issue
12 tasks
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 Jun 25, 2024
@respencer respencer removed the Stale label Jun 25, 2024
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.

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 11, 2024
@DAcodedBEAT DAcodedBEAT removed the Stale label Oct 14, 2024
@DAcodedBEAT DAcodedBEAT removed a link to a pull request Oct 14, 2024
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants