PHP and Laravel website maintenance and fixes

The site already works, but something breaks, slows down or is out of date: the host demands a newer PHP version, emails do not arrive, an update leaves a blank page, and the developer who built it is no longer around. Such a site does not have to be rewritten from scratch — more often it is enough to understand the code and carefully fix exactly what is in the way.

Typical requests

• Errors. A blank page, a 500 error, a form that does not send, a payment that fails, an admin panel that will not open.
• PHP upgrades. Upgrading from old PHP 5.6 or 7.x to PHP 8, upgrading Laravel and libraries — so the host does not switch the site off and known security holes are closed.
• Speed. Slow pages and database queries, heavy images, needless calls to third-party services.
• Site email. Customer emails and enquiries do not arrive or land in spam — sending set-up, SPF, DKIM, DMARC.
• New features. An enquiry form, card payments via WayForPay, a customer area, an admin section, a CRM or Telegram integration.

Typical situations

• The host is switching off an old PHP version. The code is upgraded for PHP 8, outdated functions and libraries are replaced, the site is checked on a copy — and moves to the new version without downtime.
• Pages take 5–10 seconds to open. The slowest database queries and heavy spots in the code are found; after the fixes pages open in a fraction of a second.
• Enquiries from the site stopped arriving. Email sending and the domain’s mail settings are checked; enquiries arrive again and stay out of spam.
• Card payments are needed. WayForPay payments are added to the existing site: a payment page, payment confirmation and an email to the customer.

Working with someone else’s code

• A copy first. The site and database are copied and deployed separately — changes are made on the copy, not on the live site.
• Change history. The code goes under version control: every change is recorded and can be rolled back if needed.
• Safe deployment. A backup of files and database before every deployment, a check of pages and the error log after.
• Minimal intervention. What needs fixing gets fixed, without rewriting everything to taste — you understand what you pay for.
• Notes for next time. What was done and where it lives is briefly written down, so the next change does not start from zero.

How the work goes

1. Task and access. What is wrong or what needs adding; access to hosting, the database and the admin panel.
2. Review and estimate. The code and the cause of the problem are examined; you get a list of work with cost and timing.
3. Changes on a copy. You check the result before it reaches the live site.
4. Deployment. With a backup and a check afterwards.
5. Support. One-off tasks or ongoing maintenance — whichever suits you.

How much it costs

It depends on how tangled the code is and how much has to change. That is why a review and an estimate come first and the work after: you know the cost of each stage in advance and pay for an accepted result.

Frequently asked questions

Does RandomStar take on someone else’s code?

Yes, if the site is written in PHP or Laravel. A code review comes first: after it, it is clear whether to fix what exists or rebuild some part.

Will the site go down during the work?

No: changes are made on a copy and deployed with a backup, so if anything goes wrong the site is quickly returned to its previous state.

What access is needed?

Usually the hosting panel or SSH, the database and the site’s admin panel. Passwords can be changed once the work is done.

How long does a PHP upgrade take?

From a few hours to a few days — depending on the age and size of the code. The exact timing is in the estimate after the review.

Discuss your site