PHP version compatibility fix
A site broken by a PHP version change, traced to the specific incompatible code.
Nothing here is broken. This is the work a site accumulates while it is running normally — content that needs updating, an integration that needs building, a report someone has asked for, hosting that needs moving or documenting.
Showing 177–192 of 248 fixes
A site broken by a PHP version change, traced to the specific incompatible code.
Every plugin and theme documented with its actual purpose, including anything that looks unused.
Plugin dependencies mapped before you remove or replace one.
A bug report prepared for a plugin vendor with the reproduction detail their support team needs.
A custom post type's archive using the wrong template, traced to the actual template hierarchy.
A post type slug conflicting with an existing page or another type, resolved with redirects.
A pre-launch checklist run on staging — redirects, indexing, forms, SSL, and more.
A pricing table built to your final spec — tiers, prices, and features — not your pricing strategy decided.
Product descriptions you've already written, imported from a CSV at scale.
Titles and descriptions rewritten for up to 100 SKUs, grounded in your existing product data.
Titles and descriptions rewritten for up to 500 SKUs — a full catalogue pass.
Publish dates and scheduling corrected or set in bulk across many posts at once.
A formal, checklist-style publishing procedure, so quality checks don't get skipped under time pressure.
reCAPTCHA or Turnstile failing to load or blocking real visitors — the key or domain mismatch found.
A recorded walkthrough video of key admin tasks, for a team that learns better by watching.
A redirect map generated from your old and new URL structures — a deliverable, not the live redirects.
Nothing here is broken. This is the work a site accumulates while it is running normally — content that needs updating, an integration that needs building, a report someone has asked for, hosting that needs moving or documenting.
It is priced the same way as the fixes and for the same reason: each one is a defined piece of work with a known shape, so the page can say what it costs and when it will be done rather than quoting for it.
What differs is how you arrive. Nobody lands here from an error message. You come with a task you have already decided you want, and the only open questions are the price and the date. If you are not sure whether what you need is a fault or a task, describe it and we will point you at the right one.