// Self-written website under control
Support for self-written websites and old PHP code
I help you understand a website that was written individually: PHP code, database, forms, admin panel, errors, transfer to a new hosting, PHP update and careful modernization without complete rework.
Code
Analysis of PHP files, templates, connections, forms and main functions of the website.
Base
Checking the database structure, errors, backups and connections with the admin panel.
PHP
Compatible with the latest versions of PHP and hosting settings.
Protection
Checking accesses, suspicious files, old libraries and vulnerabilities.
// When the developer disappeared
A self-written website can be maintained if you first understand its structure
The main problem of self-written websites is the lack of documentation and dependence on the old developer. Therefore, the work begins with a careful audit of the code, database, hosting, forms and critical scripts.
Code audit
I look at the project structure, main files, dependencies, forms, admin panel and critical areas.
PHP Errors
White screen, deprecated warnings, errors after changing PHP, problems with the database and forms.
Forms and email
Restoration of sending enquiries, SMTP, checking addresses, antispam and form processing logic.
Backups
Copies of files and database before work, verification of recovery and project portability.
Modernization
Accurate edits without rewriting the entire website: PHP, structure, security and compatibility.
Transfer
Moving to a new hosting or VPS with checking the domain, SSL, database and forms after launch.
// Cautious modernization
Not every old recorder needs to be urgently rewritten from scratch
Sometimes it’s enough to update PHP compatibility, fix forms, close security risks and set up backups. But if the code is too old and expensive to maintain, it’s fairer to plan a migration to a new framework.
// How the work goes
First figure it out, then edit it
A self-written website cannot be repaired like a template CMS. We need a careful approach and an understanding of what affects what.
Audit
Code, base, structure, access, forms, errors and hosting.
Backup
Files, database and rollback capabilities.
Risk map
What breaks, what is critical and what is better not to touch without testing.
Edits
Code, PHP, forms, security and compatibility fixes.
Check
Control of scripts, requests, admin panel, pages and errors.
// When needed
When a self-written website requires attention
- Developer missing
- The website runs on old PHP
- Forms stopped sending enquiries
- No backups
- Hosting asks to update PHP
- Errors appeared
- Website needs to be moved
- Administrator is unstable
- There is a suspicion of hacking
- Any minor edit has become expensive and risky
// Application
It’s better to start with an audit of a self-written website
Send a link to the website and describe what is known: language, hosting, access, admin, database, errors or transfer task.
// FAQ
Frequently asked questions: Support for self-written websites
Is it possible to maintain a website if it is self-written?
Yes, if you have access to files, database and hosting. First you need to understand the project structure and critical functions.
What to do if a developer disappears?
It is necessary to conduct an audit: files, database, access, admin panel, forms, hosting, domain and backups. After this, it will become clear whether the website can be supported.
Is it possible to update PHP without a complete rework?
Sometimes yes. You need to check incompatible code, old functions, libraries and website behavior on a test copy.
Is it possible to transfer a self-written website to a new hosting?
Yes, but it is important to transfer files, database, PHP settings, cron, SSL, domain and check forms after launch.
What if there is no documentation?
This is a common situation. Then the documentation is partially created during the audit: structure, accesses, critical files and dependencies.
Can molds be repaired?
Yes, handlers, SMTP, antispam, fields, sender addresses and server errors are checked.
Can new functions be added?
Yes, if the codebase allows it. Sometimes it's cheaper to add a small module, sometimes it's better to plan for a migration.
How to understand that it is better to rewrite a website?
If the code is very outdated, any changes break other parts, there is no security and the website is difficult to port, a rewrite may be more profitable than a repair.
Do you need access to the database?
For full diagnostics and backups - yes. Without a database, you can only check part of the website.
Can I take a self-written website for maintenance?
Yes, after an audit and understanding of the risks, regular support can be agreed upon.