Updates
Drupal core, modules, theme, Composer, PHP and post-change review.
// Drupal under control
Maintenance of Drupal websites without risk to structure and content
Support for Drupal websites: core and module updates, security, PHP, content types, forms, multilingualism, user rights, transfer to new hosting and regular technical checks.
Structure
Content types, fields, views, menus, forms and multilingual materials.
Security
Checking security updates, roles, users and suspicious changes.
Hosting
PHP, database, cron, cache, file permissions, SSL and transfer to a new server.
// Drupal requires care
Drupal often relies on a structure that cannot be updated blindly
Content types, views, modules, roles, fields and multilingualism make Drupal powerful, but risky for chaotic updates. Therefore, compatibility is first checked and a backup is made.
Core and modules
Updates of Drupal and contrib modules with compatibility control and website check after work.
Content types
Fields, content types, views, taxonomies, menus and content display structure.
Roles and accesses
Checking users, access rights, administrative roles and admin panel security.
Multilingual
Language versions, translations, menus, materials and careful maintenance of the structure.
Bugs and compatibility
Errors after updating PHP, modules, themes, cache or transferring to a new hosting.
Backups and transfers
Copies of files and database, transfer to hosting/VPS, checking cron, SSL and forms after launch.
// Drupal support
Drupal needs to be served through dependency checking, not random clicks
Especially if the website was made a long time ago, runs on old PHP, or uses a set of modules that no one has tested for a long time.
✓Versions of Drupal, PHP, modules, themes and Composer dependencies are checked before updates.
✓After work, forms, roles, materials, menus, views, languages and visible pages are checked.
✓If the update is risky, it is better to work on a copy of the website and transfer the result after verification.
DrupalModulesViewsFieldsTaxonomyMultilingualComposerPHPCron
// How the work goes
Drupal is best updated according to plan
This way there is less risk of breaking the structure, roles, forms or content pages.
Audit
Drupal version, modules, theme, PHP, errors, roles, forms and hosting.
Backup
Files, database and rollback capabilities.
Compatibility
Check modules, theme, dependencies and update risk.
Works
Updates, edits, transfers, forms, content and server settings.
Check
Pages, roles, forms, views, languages, menus and errors.
// When needed
When a Drupal website needs to be checked
- Drupal has not been updated for a long time
- Security updates available
- PHP is deprecated
- Modules are no longer supported
- Forms broke
- Problems with roles
- Website needs to be moved
- The website is slow
- Multilingual available
- No fresh backups
// Application
It’s better to start with a Drupal audit
Send a link to the website and describe the task: update, module, form, content, language, PHP, hosting or transfer.
// FAQ
Frequently asked questions: Drupal maintenance
Is it possible to safely update Drupal?
Yes, but first you need to check the version of the core, modules, theme, PHP and dependencies. For risky updates, it is better to use a copy of the website.
Do you work with Drupal modules?
Yes, you can check, update, replace or configure modules if you have access and understand the website structure.
What to do if the website is on old PHP?
You need to check the compatibility of Drupal, modules and themes with the new version of PHP, and then update step by step.
Can you help with content types and views?
Yes, you can edit fields, views, menus, taxonomies, material output and content structure.
Is it possible to support multilingual Drupal?
Yes, but you need to carefully check the language versions, menus, materials, URLs and translations.
Do I need access to hosting?
For updates, backups, transfers and error corrections, access to hosting/SFTP and database is usually required.
Is it possible to transfer Drupal to a new hosting?
Yes, with transfer of files, database, PHP settings, cron, SSL and checking the website after launch.
What to do if there are errors after updating?
You need to look at logs, module compatibility, cache, PHP and database. Therefore, a backup is important before work.
Can I take Drupal for regular maintenance?
Yes, after the audit you can agree on regular updates, backups, security and minor changes.
Is it better to keep Drupal or move it?
It depends on the state of the website and tasks. Sometimes Drupal makes sense, sometimes it's cheaper to move the content to a simpler framework.