New 24/7 monitoring and daily cloud backups now included in every Shield Pro plan.

Help Centre

BugShield Knowledge Base

Guides, walkthroughs, and answers for getting the most out of your account.

Submitting a Fix Request

A fix request is a request for developer help with a specific WordPress problem on one site. BugShield keeps the request, payment state, developer conversation, attachments and result together.

Before submitting

  • Choose the website that needs help. If you have more than one, use the workspace selector to switch sites.
  • Describe what you were doing, what you expected to happen and what happened instead.
  • Tell us when you first noticed the problem and whether anything on the site had recently changed.
  • Save any login details in the Password Vault rather than including passwords in your request.

Create the request

  1. Open Fix Requests, then select Create fix request at the top of the dashboard.
  2. Select the closest issue category, or describe the problem manually.
  3. Provide a short summary and describe the problem clearly. Include a page URL if the issue affects a specific page.
  4. If helpful, add screenshots that show the problem, taking care to hide any customer or payment details before uploading.
  5. Review the request, its priority and the plan coverage shown before submitting.
  6. Submit for developer review.

Plan coverage and one-off payment

Shield Light includes two eligible fixes per billing month, while Shield Pro includes eligible fixes without a monthly count. Compare the maintenance plans for more detail. If payment is required, the estimated price is shown before you submit. You must review and accept that price before the amount is authorised on your card. A developer reviews the request before work begins, and the charge is captured when the request is accepted. If BugShield cannot accept the request, the authorisation is released.

What happens next

The request begins as Requested. Learn what happens at each stage in Fix Request Statuses. You will receive an update when the request is accepted or if a developer has questions or needs credentials. Reply in the request chat so the complete decision trail stays attached to the job.

Common questions

Frequently Asked Questions

What counts as one fix?

One fix is one clearly defined reported issue with a clear resolution. Unrelated problems should be submitted separately.

When is a one-off payment charged?

The estimated amount is authorised when you submit and captured after a developer accepts the request. The review screen shows the current payment state before submission.

Can I attach screenshots?

Yes. Attach images that demonstrate the problem, but remove personal, customer and payment data first.

Should I put passwords in the request?

No. Store credentials in the site-specific Password Vault so access can be controlled and logged.

Still need help?

Can’t find what you need? Our team is here to help.

Contact us