[#37382] - Fix wrong update SQL file names
- Fixed in Code Base
- 26 Mar 2022
- Medium
- Build: 3.10-dev
- # 37382
- Diff
- richard67:3.10-dev-fix-wrong-update-sql-file-names
User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Summary of Changes
Fix wrong update SQL file names caused by commit a73ee45 .
Testing Instructions
Code review.
Actual result BEFORE applying this Pull Request
Wrong file name "3.10.7-2022-02-20.sql.sql" for the postgresql and the sqlazure files.
Expected result AFTER applying this Pull Request
Right file name "3.10.7-2022-02-20.sql" for the postgresql and the sqlazure files like it is already for the mysql file.
Documentation Changes Required
None.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Postgresql SQL Administration com_admin MS SQL |
Setting the release blocker label because we should not ship with wrong file names. Even if that will not cause problems at the update, it will later require to delete both the files with the wrong and with the right name when updating to 4.1 or 4.2, and that would simply be silly.
| Labels |
Added:
Release Blocker
?
|
||
@zero-24 It has been release only as release candidate. Does this justify to keep the deletion of the files with the wrong names in script.php on 4.1-dev and 4.2-dev? I think we should keep it to be safe. Otherwise in case if someone updates from 3.10.7 RC 1 to 4.1 or 4.2, there might be a problem.
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-03-26 19:05:37 |
| Closed_By | ⇒ | zero-24 |
merged thanks
it has bever been released right?