![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 8 weeks ago
Last modified 8 weeks ago
#65295 new defect (bug)
Checksum error when trying to upgrade from 6.9.4 to 7.0 with fr_FR package
| Reported by: | jsmansart | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | General | Version: | |
| Severity: | normal | Keywords: | reporter-feedback |
| Cc: | Focuses: |
Description
I've got this error :
Mettre à jour WordPress Téléchargement de la mise à jour depuis https://downloads.wordpress.org/release/fr_FR/wordpress-7.0.zip… Le téléchargement a échoué.: L'empreinte de contrôle (ou checksum) de votre fichier (efc0790dd3d6320a6e41d0152d2df7a3) ne correspond pas à la valeur de l'empreinte attendue (c195686bfedd394984d8cd19d75a37fa). Échec de l'installation
Seems related to the fr_FR package.
It works if I choose to upgrade to the en_US version
Environment
- WordPress: 7.0 (after upgrading with en_US)
- Subdirectory: No
- PHP: 8.2.14
- Server: Apache
- Database: mysqli (Server: 5.7.18-16-log / Client: mysqlnd 8.2.14)
- Browser: Firefox 151.0
- OS: macOS
- Theme: Bayard Service 1.0.0
- MU Plugins: None activated
- Plugins:
- Advanced Custom Fields 6.8.1
- BSW Blocks 2.15.0
- Bulk image resizer 2.0.1
- Carousel Slider Block 2.1.3
- Contact Form 7 6.1.6
- Custom Post Type UI 1.19.2
- Gravity Forms 2.10.2
- GTM4WP - A Google Tag Manager (GTM) plugin for WordPress 1.22.3
- hCaptcha for WP 4.26.0
- MainWP Child 6.0.11
- MainWP Child Reports 2.3.1
- Members 3.2.21
- Redirection 5.7.5
- SEOPress 9.8.5
- SEOPress PRO 9.8.4
- Test Reports 1.3.0
- WP Mail SMTP 4.8.0
- WP Sync DB 1.5
- WP Sync DB Media Files 1.1.4b1
Change History (2)
Note:
See TracTickets
for help on using tickets.
I just tried updating from 6.9.3 -> 7.0 using the French version and did not encounter any issues. I also don't see any of those checksums when looking at https://api.wordpress.org/core/checksums/1.0/?version=7.0&local=fr_fr
Are you still able to replicate this issue or are there any additional steps to replicate this?