AR Logo
AR LogoAli Rehman
Let's Work Together
alirehmandev.comAvailable for work

A symptom-first guide library

WordPress troubleshooting: find the right fix

Start with what is failing, not a plugin to install. Match your symptom to an existing guide, make the first safe check and know when to stop before changing a live site.

Find my symptomUse the blank incident note
By Hub updated

Impact labels help prioritise a symptom; they are not measured severity for your site. If payments, access or data are at risk, pause changes and involve your host or developer.

Access & errors

Start here when sign-in fails, the site loops between addresses or an error replaces the page.

  • High impact

    WordPress login fails or returns to the login screen

    First safe check
    Open your known login address in a private window. Note whether you see a password error, a redirect or an access-denied message before trying more resets.
    Stop and get help if
    You cannot verify account ownership, recovery email or two-factor access, or notice an unfamiliar administrator. Contact the site owner or host; do not bypass login protection.
    Read the guideWordPress Login Not Working? Get Back Into wp-admin Safely (2026)
  • High impact

    A critical error replaces the website or dashboard

    First safe check
    Record which pages fail and the last known update. Check the administrator inbox for a WordPress recovery email without sharing its private sign-in link.
    Stop and get help if
    Recovery access or a usable backup is missing, or the error involves custom code you cannot identify. Ask the host or developer to review the error before replacing files.
    Read the guide“There Has Been a Critical Error on This Website”: How to Fix WordPress (2026)
  • High impact

    The recovery email link says Recovery Mode not initialized

    First safe check
    Stop reopening older recovery links. Note when the newest recovery email arrived and which plugin or theme it names, without forwarding or sharing the private link.
    Stop and get help if
    No usable recovery email arrives, the error names custom code or a must-use plugin, or you have no hosting or file access. Ask the host or developer to deactivate only the named extension.
    Read the guideWordPress Recovery Mode Not Initialized? Fix the Link and Email
  • High impact

    The browser reports too many redirects

    First safe check
    Note whether the loop affects one page, login or the whole site. Record the public addresses involved, including HTTPS and www differences, without changing URL settings.
    Stop and get help if
    The loop crosses hosting, proxy or HTTPS rules and you do not know which layer owns them. Get the host to confirm the configuration; do not switch off HTTPS to hide the loop.
    Read the guideWordPress Too Many Redirects? Fix URL and HTTPS Loops
  • High impact

    The briefly unavailable maintenance message stays on screen

    First safe check
    Check the hosting or update panel to establish whether an update is still running and which component started it. A maintenance message alone does not prove the update has finished.
    Stop and get help if
    The update is still active, its state is unknown or files appear incomplete. Ask the host to check the update before removing the maintenance marker or retrying it.
    Read the guideWordPress Stuck in Maintenance Mode? Fix the Briefly Unavailable Message

Editing & media

Find the difference between an editor problem, a missing file, an old page and a broken URL.

  • Workflow impact

    Elementor stays on its loading screen

    First safe check
    Preserve unsaved work, then compare the affected page with another page and a private browser window. Separate an editor-only problem from a broken public website.
    Stop and get help if
    The next step would disable live plugins, replace a theme or risk losing the page. Move conflict testing to protected staging with a recoverable copy.
    Read the guideElementor Editor Not Loading? Fix a Stuck Loading Screen (2026)
  • Display issue

    Saved changes do not appear on the live page

    First safe check
    Confirm the change is published on the intended page or template. Compare that exact public URL in a private window before clearing any cache.
    Stop and get help if
    You cannot identify the cache layer, or a proposed change affects cart, checkout or signed-in pages. Avoid blanket cache changes and ask for a targeted check.
    Read the guideWordPress Changes Not Showing? Find the Cache That Is Hiding Them (2026)
  • Display issue

    An image is missing or appears as a broken file

    First safe check
    Compare one broken image address with a working image. Check whether the image itself opens and whether the problem is in the media library, page or both.
    Stop and get help if
    Files are missing, access is denied or mixed-content warnings appear. Ask the host before bulk replacement or permission changes; do not make upload folders publicly writable.
    Read the guideWordPress Images Not Showing? Find the Broken Link Between File and Page (2026)
  • High impact
    First safe check
    Compare the homepage, one affected URL and one known working page. Note whether one address or all inner pages fail; keep the current slugs and permalink structure unchanged.
    Stop and get help if
    The repair needs server rewrite rules, a database edit or redirects whose purpose is unclear. Preserve existing URLs and have the host or developer review the routing layer.
    Read the guideWordPress Permalinks Not Working? Fix 404s Without Changing Your URLs
  • Workflow impact

    Publishing or updating fails with an invalid JSON response

    First safe check
    Preserve the unsaved draft and inspect the failed save request's status and response. Check a fresh view of the saved post before retrying or changing settings.
    Stop and get help if
    The next step would disable security, replace routing rules or risk live content. Ask the host or developer to review the exact request and a redacted matching log.
    Read the guideWordPress Invalid JSON Response: Fix Publishing and Updates

Store, email & publishing

Follow the affected order, notification, product image or scheduled post before changing settings.

  • Workflow impact

    The contact form says sent, but no email arrives

    First safe check
    Review the notification recipient and sender alongside an existing saved submission or mail log, if available. A form success message is not proof of inbox delivery.
    Stop and get help if
    Logs show a rejection, sender authentication is unclear or the next step would resend real enquiries. Arrange a controlled test with the mailbox owner before changing DNS or resending messages.
    Read the guideWordPress Contact Form Not Sending Email? 7 Checks and Fixes (2026)
  • Workflow impact

    WooCommerce order emails are missing

    First safe check
    Inspect the existing order status, the matching notification setting and its intended recipient. Follow that order's mail log if available without changing the order status.
    Stop and get help if
    Payment status is uncertain or a retry would notify real customers. Confirm the transaction first; do not cycle order statuses or bulk-resend queued notifications.
    Read the guideWooCommerce Emails Not Sending? Follow the Order Before Changing SMTP (2026)
  • High impact

    Checkout spins, errors or cannot place an order

    First safe check
    For an existing failed attempt, compare the visible error with the order record and payment-provider status. Record the affected checkout method before making another attempt.
    Stop and get help if
    A payment is pending, charged or unknown. Do not retry the customer payment; confirm it with the provider and isolate further testing from live payments and fulfilment.
    Read the guideWooCommerce Checkout Not Working? 6 Checks to Find the Cause (2026)
  • Display issue

    Product photos look blurry, cropped or stretched

    First safe check
    Compare one original image's pixel dimensions with its displayed size. Check whether the issue affects the product grid, main product photo or zoom before regenerating anything.
    Stop and get help if
    The source image is too small, originals are unavailable or a bulk regeneration would change the live catalogue without a rollback. Preserve the originals and agree a limited test first.
    Read the guideWooCommerce Product Images Blurry? Fix Size, Crop and Quality
  • Workflow impact

    A scheduled post shows Missed schedule

    First safe check
    Compare the post's scheduled time with the site's time zone. If dashboard access works, review Site Health for scheduled-event or loopback warnings before running any jobs.
    Stop and get help if
    Other jobs, orders or notifications are also delayed, or a replacement scheduler is not verified. Ask the host to check scheduling; do not run every job or disable the existing scheduler blindly.
    Read the guideWordPress Missed Schedule? Fix Scheduled Posts Not Publishing

Read before making changes

Keep the repair smaller than the problem.

Only work on a site you own or are authorised to maintain. A first check can be read-only; a repair needs a recovery plan and a way to confirm the result.

Protect a recoverable copy

Before changing files, plugins, URL settings or the database, confirm you have the matching files and database backup, access to restore them and an agreed rollback plan.

  • A backup existing is not proof that restoration works. Test recovery separately where possible.
  • Keep new orders, enquiries and content in mind: an older database restore can overwrite them.
  • Without recovery access, stop at observation and ask the host or developer for help.
Isolate store, email and scheduled-job tests

A staging URL or payment sandbox does not automatically block customer email, shipping labels, fulfilment or other integrations. Agree test data, recipients and side-effect controls first.

  • Confirm an uncertain payment with the provider before another attempt.
  • Do not bulk-resend mail, cycle real order statuses or run all scheduled jobs to see what happens.
  • After a controlled change, verify the original journey and record what was not tested.
Recognise when this is an incident, not a routine fix

Unfamiliar administrators, unexpected payment changes or exposed customer data need an incident response from the site owner, host or a security specialist.

  • Preserve relevant records privately; avoid wiping files or logs before they can be reviewed.
  • Do not disable authentication, security checks or HTTPS as a shortcut.
  • Do not paste passwords, recovery links, customer records or full unredacted logs into a support brief.

A useful handover

Describe the problem once.

Select the blank text and copy it into your own note. Nothing is entered, saved or submitted through this template.

Keep passwords, tokens, recovery links and customer information out. Use a public page path and redact screenshots or errors before sharing.

WordPress incident note

Public page path (no query strings or private links):
Expected behaviour:
Actual behaviour or redacted error:
First noticed (date, time and time zone):
Affected area and scope:
Last known working time:
Recent change and when:
Checks already made and their results:
Backup date and restore readiness (no backup links):
Live orders or submissions that must be preserved:
Help needed:

Need implementation help?

Choose the right kind of support.

An investigation is not a promised fix. Agree the scope, access, price and acceptance checks before work begins; emergency response and ongoing care are not assumed.

WordPress development

For a defined theme, Elementor, WooCommerce or custom-functionality change, including a repair that needs development work.

Explore WordPress development

Website maintenance

For a scoped one-off issue or agreed ongoing updates, backup readiness and routine website checks. Coverage is confirmed in writing.

Explore website maintenance

This hub organises existing guides; it does not inspect your website or establish the cause of a fault. The update date applies to this hub, not a fresh test of every linked guide.

About Ali Rehman's experience