Issue 1: The user cannot record
- Possible cause: The page is running on HTTP instead of HTTPS.
- Solution: Make sure the page is fully served over HTTPS. Browsers block microphone recording on insecure pages.
- Also check: Browser microphone permissions.
Issue 2: The form records but the upload fails
- Possible cause: The storage folder does not exist or is not writable.
- Solution: Open the settings page, check the Storage check section, and create the storage folder if necessary.
- Also check: PHP write permissions on wp-content.
Issue 3: Premium skins do not work
- Possible cause: The Premium entitlement is not active, expired, or not refreshed on the site.
- Solution: Refresh the license from Pro Radio Admin and verify that the Premium add-on or Pro Radio Plus is active on the current domain.
Issue 4: MP3 conversion is not available or fails
- Possible cause: Premium is not active, or the server cannot complete the conversion request correctly.
- Solution: Confirm Premium activation, check outbound server connectivity, and make sure the server supports the required conversion flow.
- Also check: Storage permissions and general upload health.
Issue 5: Email moderation or notifications do not arrive
- Possible cause: WordPress email delivery is not configured correctly.
- Solution: Use the Email test button from the settings page.
- Also check: The Custom notification email address and your SMTP or hosting mail configuration.
Issue 6: A user is blocked too early
- Possible cause: The cooldown, per-user limit, or global rate limit is too restrictive.
- Solution: Review the waiting time and rate-limit settings, or use the Reset user limits tool if you are testing.
Issue 7: iPhone or Safari behaves differently
- Possible cause: Mobile Safari has stricter media permission behavior than desktop browsers.
- Solution: Test directly on the device, grant microphone access, reload the page, and test again on HTTPS.
Issue 8: Changes are not visible after updates
- Possible cause: Cache or optimization plugins are serving an old static page.
- Solution: Clear all caches and test again, especially after enabling HTTPS, changing widget output, or updating skins.
