This summarizes the procedure for updating Drupal from 10.1.5 to 10.6.1 on Sakura Rental Server.
Environment
- Server: Sakura Rental Server
- Drupal: 10.1.5 → 10.6.1
- Installation type: Traditional (tarball, no
web/directory)
Preparation
Creating a Working Directory
Backups are saved outside www (to prevent web access).
File Backup
Database Backup
On Sakura Rental Server, the --no-tablespaces option is required.
Drupal Core Update
Changing Permissions
The sites/default directory is often write-protected, so temporarily change it.
Updating with Composer
Since the composer command is not available on Sakura Rental Server, use composer.phar.
Database Update and Cache Clear
Restoring Permissions
Troubleshooting
Rules Module Compatibility Error
If the following error appears after updating:
The Rules module may be incompatible with the new Drupal core. Temporarily disable it:
Recommended Settings
Setting trusted_host_patterns
Add the following to settings.php:
Enabling state_cache
As preparation for Drupal 11, add to settings.php:
0
Disabling Deprecated Modules
Disable modules scheduled for removal in Drupal 11:
1
Module Updates
For Composer-managed Drupal, update via Composer rather than from the admin panel.
2
Note: Drupal Configuration Types
Drupal has two types of configurations.
| Configuration | Features | Symlink Separation |
|---|---|---|
| Traditional (tarball) | index.php at the root | Not effective |
| Composer recommended | Has web/ directory | Effective |
For the traditional type, vendor/ and composer.json become web-accessible, so protection with .htaccess is important.
Summary
- Always take backups (files and database)
- Update via Composer (not from the admin panel)
- Don’t forget temporary permission changes
- Run drush updatedb and cache:rebuild
- Temporarily disable incompatible modules