FIXES & TROUBLESHOOTING
Something Broke? We’ll Help Find the Cause and Fix the Right Problem
One-time technical troubleshooting for websites, ecommerce, software, apps, integrations and digital systems when something is broken, unreliable or suddenly behaving differently.
You do not need an ongoing maintenance plan to request a fix. We first diagnose the issue, confirm what we can reasonably repair, then define the work before making larger changes.
Common Problems We Review
- Broken pages
- Form failures
- Checkout problems
- Plugin conflicts
- Login / account errors
- API failures
- Deployment issues
- Mobile display bugs
- Unexpected slowdowns
- Broken integrations
What We Troubleshoot
The goal is to identify the actual cause rather than repeatedly patching the visible symptom.
Website Errors
Broken pages, layout problems, PHP errors, page-builder issues and unexpected frontend behavior.
Forms & Email
Forms that do not submit, notifications that do not arrive or email-delivery configuration problems.
Ecommerce & Checkout
Cart, checkout, payment, shipping, tax or WooCommerce problems that interrupt purchases.
Login & Account Issues
Authentication, password, session, role or account-access problems.
Plugin / Dependency Conflicts
Conflicts after updates, incompatible extensions or broken dependencies.
API & Integration Failures
Third-party services, webhooks or API connections that stop working correctly.
Deployment & Environment
Build failures, environment variables, server configuration or release problems.
Mobile / Responsive Bugs
Layouts or interactions that break on phones, tablets or specific viewport sizes.
Performance Problems
Sudden slowness, heavy queries, overloaded plugins, caching issues or expensive API calls.
Diagnosis Comes Before the Fix
The same visible problem can have very different causes. A failed form might be email configuration, spam filtering, JavaScript, plugin conflict or server-side failure.
- Reproduce the problem
- Identify when it started
- Review recent changes
- Check logs or errors
- Test likely dependencies
- Isolate the failing component
- Confirm a safe repair path
Avoid Random Changes on Production
When possible, troubleshooting should minimise unnecessary changes to a live system. Backups, staging, logs or controlled tests can reduce the risk of fixing one problem while creating another.
The appropriate approach depends on the system and available access.
WordPress & WooCommerce Troubleshooting
Common WordPress issues can come from themes, page builders, plugins, caching, PHP versions, hosting limits, database problems or conflicting settings.
- Plugin conflicts
- Elementor / builder problems
- WooCommerce checkout issues
- Broken forms
- White screens / PHP errors
- Update failures
- Redirect / permalink issues
- Slow admin or frontend
Sometimes the Problem Is the Stack
If a site relies on many overlapping, abandoned or incompatible plugins, fixing one visible bug may not make the overall setup stable.
When the underlying stack is the real problem, we may recommend cleanup, replacement of problematic components or broader maintenance rather than endless one-off patches.
Software, SaaS & App Troubleshooting
Custom applications may fail because of code regressions, data problems, dependencies, API changes, authentication, background jobs, deployment or infrastructure.
Useful evidence includes reproduction steps, screenshots, console errors, server logs, affected accounts, recent releases and API/provider changes.
Production Bugs Need Context
A screenshot alone is often not enough for software issues. The faster we can reproduce the bug and access the relevant logs or code, the faster we can narrow down the root cause.
The Better the Bug Report, the Faster the Diagnosis
Clear reproduction information saves time and reduces guesswork.
Exact URL or Screen
Show where the problem happens instead of only describing the system generally.
What You Expected
Explain what should happen when the flow is working correctly.
What Actually Happens
Share the visible error, wrong result or broken behavior.
Steps to Reproduce
List the clicks, inputs or actions needed to trigger the issue.
When It Started
Mention recent updates, migrations, provider changes or deployments if known.
Screenshots / Errors
Send screenshots, error messages, console output or logs when available.
A Fix Can Reveal a Bigger Problem
Troubleshooting begins with the reported issue, but the diagnosis may show that the real problem is larger than a one-line repair.
Good One-Time Fix
The cause is identifiable, the repair is reasonably contained, and fixing it does not require rebuilding a large part of the system.
Stabilisation Work
The reported bug sits inside a fragile or outdated system that needs several related repairs before it becomes dependable again.
Rebuild / Migration
The underlying platform or architecture is no longer practical to repair safely, so a broader replacement may be the better business decision.
What Determines the Troubleshooting Quote?
We quote against the actual issue and the effort needed to diagnose and repair it, not against a generic ‘bug fix’ label.
Reproducibility
A consistent bug is usually easier to diagnose than an intermittent problem with no clear trigger.
System Access
Admin, hosting, repository, logs or provider access may be required to investigate the root cause.
System Complexity
A simple website issue and a multi-service SaaS failure are different troubleshooting tasks.
Third-Party Services
Payments, email, APIs, AI, hosting and external providers can introduce issues outside the core codebase.
Current Condition
Outdated, modified or poorly documented systems can require more discovery before a safe repair is possible.
Urgency
Routine troubleshooting and urgent production incidents have different response expectations and workload.
Diagnosis May Be the First Scope
For unclear or complex issues, the first paid step may be diagnosis and investigation. Once the cause is understood, we can confirm whether the repair is small, requires stabilisation or should become a larger project.
A Written-First Troubleshooting Workflow
Screenshots, URLs, logs, reproduction steps, test links, progress updates and approvals can all be handled asynchronously in writing. Meetings are optional.
01
Describe the Problem
Send the URL, screenshots, exact error and steps needed to reproduce the issue.
02
Reproduce & Investigate
We review the relevant system, recent changes, logs, configuration and likely dependencies.
03
Confirm the Repair Path
We explain what appears to be wrong and whether the issue is a contained fix or larger scope.
04
Fix & Test
The agreed repair is implemented and the affected workflow is tested again.
05
Recommend Next Steps
If the issue reveals deeper risks, we explain what should be stabilised, maintained or rebuilt next.
Need Only the Fix?
That is fine. Once the specific issue is resolved and tested, the project can end without requiring an ongoing maintenance plan.
Keep Getting Similar Problems?
If the same site or application keeps breaking, ongoing maintenance may be more efficient than treating every incident as a separate emergency.
Fixes & Troubleshooting Questions
Do I need a monthly maintenance plan before you fix something?
No. Fixes & Troubleshooting is designed for one-time problems as well as issues that later lead to ongoing maintenance.
Can you fix WordPress and WooCommerce problems?
Yes, many common WordPress, plugin, page-builder, form and WooCommerce issues can be investigated and repaired.
Can you troubleshoot custom software or SaaS?
Yes, depending on the codebase, technology and access available. Custom software issues may require repository, environment or log access.
What if you cannot reproduce the problem?
Intermittent issues may require more logs, examples, affected accounts or monitoring before the cause can be identified.
Will you make changes before telling me the cost?
For larger or unclear issues, we define the diagnosis/repair scope before substantial work. Some issues may require a paid investigation phase first.
What if the issue was caused by a third-party provider?
We can diagnose the integration and adjust your side where possible, but outages or restrictions controlled by the provider may need to be resolved by that provider.
Can you guarantee every broken system can be repaired?
No. Some systems are too outdated, inaccessible or fundamentally unstable for a sensible one-time repair. In those cases we explain the realistic alternatives.
Can you handle urgent problems?
Potentially, depending on availability and scope. Urgent response expectations should be stated clearly because they differ from routine troubleshooting.
Do we need meetings?
No. SiteLumo uses a written-first process. Clear reproduction steps, screenshots and logs are usually more useful than meetings.
What should I send first?
Send the exact URL or screen, what should happen, what actually happens, reproduction steps, screenshots/errors and anything that changed recently.
Something Broken Right Now?
Send the exact problem, URL or screen, what should happen, what actually happens and any screenshots or error messages. We’ll reply in writing with the next step for diagnosis.