Troubleshooting & Common Issues

This WPCoreAI troubleshooting guide covers common problems with customer access, downloads, WordPress installation, licenses, updates, and website display.

For a product that is not a WordPress plugin or theme, follow its own installation, access, and version-management instructions. WordPress menu paths apply only to WordPress software; licensing, updates, integrations, and support depend on the supplied product and purchase terms.

Start with the section that matches your symptoms. For feature behavior, layouts, or supported integrations, use the guide for your product and release in Product-Specific Documentation.

Before You Change Anything

A useful diagnosis starts with a clear record of the problem. Before changing settings:

  1. Record the exact error message and the action that caused it.
  2. Note the product name, installed version, and affected page or administration screen.
  3. Identify recent changes, such as an update, new plugin, hosting migration, or configuration change.
  4. Confirm that you have a current backup before changing files, updating software, or testing a different theme.
  5. Use a staging copy for tests that could affect visitors, purchases, or published content.

Make one change at a time, repeat the same test, and record the result. If a change does not help, restore the previous setting before trying another approach.

1. You Cannot Sign In to WPCoreAI

Check Which Account You Are Using

Your WPCoreAI customer account is separate from the WordPress administrator account on your own website. Use the WPCoreAI sign-in page for purchase-related access.

  1. Check that the email address or username is entered correctly.
  2. Check for accidental spaces when copying your credentials.
  3. If you cannot remember the password, open password recovery.
  4. Enter the email address or username associated with your account.
  5. Check your inbox and spam folder for reset instructions if an account matches.

If you request more than one password reset, use the most recent email. Do not share your password or reset link.

If Sign-In Still Fails

Try signing in through a private browser window to check whether stored browser data or an extension is involved. Private browsing still requires cookies to be permitted for the sign-in session.

If the problem continues, contact WPCoreAI with the error message and the steps you tried. Avoid creating multiple accounts to resolve an existing purchase-access problem.

2. A Purchase or Order Confirmation Is Missing

  1. Check the inbox and spam folder for the email address used during checkout.
  2. Confirm whether the payment provider shows a completed, pending, or unsuccessful transaction.
  3. If you have a WPCoreAI account, sign in and open the customer dashboard to check the purchase information available there.
  4. If the order remains unclear, contact WPCoreAI with the product name, purchase email, approximate purchase date, and order number if available.

A payment record alone may not explain the store’s order status. If payment appears to have been taken, request assistance before attempting another purchase.

Do not include card details, payment-account passwords, or unredacted payment screenshots in your message.

3. A Product Download Is Missing or Fails

The Download Is Not Available in Your Account

Confirm that you are using the intended WPCoreAI account. Keep your purchase email and order number available, then contact WPCoreAI if the purchase or its download cannot be located.

Do not assume that registering another account will transfer an existing purchase.

A Download Link Returns an Error

  1. Record the error text.
  2. Return to the purchase or download area available through your account and retry from there.
  3. Check whether other websites and downloads work on your connection.
  4. If the failure continues, report the product name, order number, approximate time, and error message.

Do not post private download URLs publicly. They may contain access tokens associated with your purchase.

The Downloaded File Appears Incomplete

Wait for the browser to finish downloading before opening or uploading the file. If your connection was interrupted or the archive cannot be opened, download a fresh copy from your available purchase access.

Keep the original filename and confirm that you downloaded the installation package rather than the documentation.

4. WordPress Rejects the Installation ZIP

Check the Package and Installer

A plugin ZIP and a theme ZIP use different WordPress installation screens:

  • Plugin: Plugins → Add New Plugin → Upload Plugin.
  • Theme: Appearance → Themes → Add New Theme → Upload Theme.

Some WordPress versions label the relevant menu entry or button Add New.

Use the installable ZIP identified in the product documentation. Do not upload a documentation HTML file, an unrelated archive, or a complete download bundle when its instructions identify a separate installation ZIP.

“The Theme Is Missing the style.css Stylesheet”

This message can occur when the uploaded archive is not an installable theme package. Check that you are uploading the theme ZIP through the theme installer and that any outer download bundle has been handled according to the supplied instructions.

Do not create an empty stylesheet to bypass the error. If the correct package still fails, report the filename and exact message to WPCoreAI.

“Destination Folder Already Exists”

Check whether the product is already installed. If you intended to update it, follow the documented update procedure and back up the website first.

Do not delete the existing installation simply to bypass the message. Deleting a plugin can trigger its uninstall process and may remove stored data, depending on the product.

Invalid or Damaged Archive

Download a fresh copy and retry with the correct package. If WordPress still rejects it, include the ZIP filename and full installer message when requesting help.

5. Upload Limits, Timeouts, or File-Permission Errors

If installation reports an upload-size limit, timeout, or inability to create or write a directory, the hosting environment may need attention.

  1. Record the error and the installation ZIP size.
  2. Check the maximum upload size displayed by WordPress, if shown.
  3. Ask your hosting provider to check PHP upload and request limits, available storage, temporary-directory access, and WordPress file ownership and permissions.
  4. Retry after the relevant restriction has been corrected.

Do not apply broad writable permissions such as 777 to WordPress folders as a general fix. Ask the hosting provider to correct ownership and permissions for its environment.

If the upload option itself is missing, confirm your administrator permissions and whether the hosting service restricts software installation.

6. WordPress Activation and License Activation Are Confused

WordPress activation enables an installed plugin or theme. Customer license activation, where required, is a separate process.

Follow the instructions for your specific product:

Do not assume that a missing license-entry screen indicates a fault. Products can have different licensing and update workflows.

If a Required License Activation Fails

  1. Confirm that you installed the customer package supplied for the product.
  2. Check that the key belongs to that product and was copied without extra spaces.
  3. Read the exact activation response before retrying.
  4. If the response concerns status or activation limits, contact WPCoreAI rather than changing site records without understanding the effect.
  5. If the response indicates a connection failure, ask your hosting provider to check outbound access and relevant firewall logs.

Do not disable HTTPS certificate verification to make activation succeed. Report connection errors with sensitive values removed, and keep the license key private.

7. An Update Is Missing or Fails

No Update Notice Appears

First confirm which update method your product supports. An available product release does not mean every installation uses an automatic WordPress updater.

Compare your installed version with the release information available for your purchase. Where the documented workflow uses WordPress update checks, open Dashboard → Updates and use Check again if available.

If an expected update remains unavailable, report the installed version, expected version, and update method. Do not rename the product folder to try to trigger detection.

An Update Download or Installation Fails

  1. Record whether the failure happens during the download, unpacking, or installation stage.
  2. Keep the exact error message.
  3. Confirm that a current backup is available.
  4. Check storage and permission errors with your hosting provider.
  5. Contact WPCoreAI if the error concerns package access or the supplied release.

Avoid repeated update attempts on a live site without checking whether the previous attempt completed.

8. A Page Looks Incorrect or Changes Are Not Visible

  1. Confirm that you saved or published the relevant setting.
  2. Open the affected page in a private browser window.
  3. Check whether the issue affects signed-in visitors, signed-out visitors, or both.
  4. If caching is enabled, clear the relevant page cache through your caching plugin, hosting service, or CDN.
  5. Retest the same page and device size.

If the problem remains, record the page URL, browser, device, and whether custom CSS or a child theme changes the affected area.

On a staging site, temporarily disabling CSS or JavaScript optimization can help identify a conflict. Change one option at a time and restore it if the test makes no difference.

Do not use cache clearing as a substitute for checking whether the underlying setting was saved correctly.

9. A Feature Stops Working After Another Change

If a problem begins after installing another plugin, updating software, adding custom code, or changing hosting settings, test the connection on a staging copy.

  1. Reproduce the problem before making changes.
  2. Keep the affected WPCoreAI product and its required dependencies enabled.
  3. Temporarily disable one suspected conflicting plugin or customization.
  4. Repeat the same test and record the result.
  5. Restore the previous state if the change does not help.

Avoid bulk deactivation on a production website. It can interrupt checkout, forms, security controls, or scheduled work.

If disabling a component changes the result, report both components and their versions. This provides useful evidence, but does not by itself establish which component contains the fault.

10. An External Integration or Scheduled Task Fails

For features that depend on an external service, check the provider’s account status, service availability, permissions, and usage limits. A valid credential can still fail if the account lacks access to the requested service.

Record the provider’s error code with credentials and private data removed. Do not repeatedly retry a request that reports an exhausted quota or billing restriction.

If your product implements scheduled tasks, imports, or API connections, follow its documented checks for those features. Confirm the service status, authentication, permissions, and limits only for integrations your installed release supports.

11. The Website Shows a Critical Error or Becomes Unavailable

If the website or WordPress administration area becomes unavailable, prioritize restoring access.

  1. Record the visible error and the change immediately preceding it.
  2. Check the site administrator’s inbox for a WordPress recovery email, if one was sent.
  3. If administration remains accessible, deactivate the newly activated plugin or return to the previously working theme as appropriate.
  4. If you cannot access administration, contact your hosting provider for recovery assistance.
  5. Ask the host to inspect the relevant PHP error log and help restore a known working backup if necessary.

Keep recovery links private. Do not enable public error display on a production website or publish unredacted server logs.

Avoid deleting files or repeatedly switching components without a recovery plan.

When to Contact WPCoreAI

Use the Contact page if the issue remains unresolved, the documentation does not match your package, or the problem concerns purchase access or a supplied product release.

Include:

  • The product name and installed version.
  • Your order number for purchase-related questions, if available.
  • Your WordPress and PHP versions, where known.
  • The affected page or administration screen.
  • The steps needed to reproduce the problem.
  • The expected result and actual result.
  • The exact error text, with sensitive information removed.
  • The checks already completed and their results.

Do not include passwords, payment details, license keys, API credentials, private download links, or unredacted customer records.

If you cannot safely complete a suggested check, explain that in your message. A clear description of what you observed is more useful than making changes you cannot reverse.