Settings and billing

Troubleshooting checklist

Resolve common issues such as tables stuck processing, missing products, stock mismatches, date filters, and SSL warnings.

Back to docs
In this guide
Support and troubleshooting workflow
Support and troubleshooting workflow

Table stuck on processing

A table stuck on Processing usually means the AJAX response failed or the server returned unexpected JSON.

  1. Open browser developer tools and inspect the network request.
  2. Check Laravel logs for the related controller error.
  3. Confirm columns in Blade and controller JSON match.
  4. If counts change between pages, inspect recordsTotal, recordsFiltered, and pagination parameters.

Products not appearing

Product visibility depends on status, stock, location, selling flags, and filters.

  1. Check product active status and Not for selling setting.
  2. Check business location and current stock.
  3. Clear category, brand, and search filters.

Payment provider SSL warning

Local Windows/WAMP setups may need a trusted CA bundle for cURL. Production should keep SSL verification enabled.

  1. Install or point PHP cURL to a valid CA bundle locally.
  2. Do not disable HTTPS or SSL verification in production.
  3. Check payment provider callback URLs after changing the domain.

Detailed operating workflow

Use this checklist when a table, dropdown, form, screenshot, payment provider, or report behaves unexpectedly.

  1. Capture the page URL, user, business, date range, selected location, and exact action that failed.
  2. Check browser console and network response before editing view code.
  3. Check Laravel logs and the relevant controller method for server-side table or AJAX failures.
  4. Reproduce the issue with one controlled record before generalizing a fix across the app.
Check before moving on The failure is not caused by stale filters, hidden columns, or missing permissions. The DataTable column definition matches the JSON keys returned by the controller. Local-only SSL workarounds are not used in production payment flows.

Review signals and troubleshooting

Use these checks when the screen looks correct but the numbers, records, or workflow do not behave as expected.

  1. If a visual change does nothing, inspect whether another shared partial overrides the selector.
  2. If a dropdown style reverts after interaction, patch the initialized Select2/dropdown state, not only the original select.
  3. If a table is blank but counts exist, inspect row rendering and data keys before changing the query.
Practical notes
  • For production issues, capture the exact URL, user, time, network response, and Laravel log line before changing code.
  • Fix one confirmed cause at a time; broad UI or query changes can hide the original failure.