Troubleshooting

Common issues and solutions for API Mapper

Troubleshooting

This guide covers common issues and their solutions.

Installation Issues

Plugin Not Appearing

Symptoms: After installation, API Mapper doesn't show in the admin menu.

Solutions:

  1. Clear all caches:
    • WordPress/Joomla cache
    • YOOtheme cache
    • Browser cache
  2. Check PHP error logs for fatal errors
  3. Verify YOOtheme Pro is version 3.0 or higher
  4. Deactivate and reactivate the plugin

Installation Errors

WordPress

"Plugin could not be activated"

Cause: PHP error during activation.

Solutions:

  1. Check PHP version (requires 7.4+)
  2. Check WordPress error logs
  3. Temporarily switch to a default theme
  4. Deactivate other plugins to find conflicts

License Issues

"Invalid license key"

Solutions:

  1. Check for typos or extra spaces
  2. Ensure you're using the correct product's license
  3. Try copy-pasting the key again from your account

"License already in use"

Cause: License is active on another domain.

Solutions:

  1. Deactivate on the other domain first
  2. Log into wootsup.com and deactivate from your account
  3. Contact support if you can't access the other domain

"License server unreachable"

Cause: Your server can't connect to our license server.

Solutions:

  1. Check if api.wootsup.com is blocked by firewall
  2. Verify outgoing HTTPS connections work
  3. Try again later (temporary server issue)

Connection Issues

"Connection failed" or Timeout

Possible causes:

  • API URL is incorrect
  • API is down or unreachable
  • Server blocks outgoing requests

Solutions:

  1. Verify the API URL is correct
  2. Test the API URL in your browser
  3. Check if your hosting blocks external requests
  4. Try increasing the timeout value
  5. Contact your host about firewall rules

"401 Unauthorized"

Cause: Authentication credentials are invalid.

Solutions:

  1. Verify API key or credentials are correct
  2. Check if credentials have expired
  3. Ensure the auth type matches API requirements
  4. Check API documentation for correct header format

"403 Forbidden"

Cause: Access denied by the API.

Solutions:

  1. Verify API key has required permissions
  2. Check if IP restrictions apply
  3. Verify rate limits haven't been exceeded
  4. Check if the endpoint requires additional scopes

"404 Not Found"

Cause: Endpoint doesn't exist.

Solutions:

  1. Verify the endpoint path is correct
  2. Check API documentation for current endpoints
  3. API version may have changed

"500 Internal Server Error"

Cause: Error on the external API's server.

Solutions:

  1. Check API status page
  2. Verify request parameters are valid
  3. Try again later
  4. Contact API provider if persistent

Data Issues

Fields Show Empty in YOOtheme

Cause: Field path doesn't match API response.

Solutions:

  1. Use the connection tester to see actual response
  2. Verify JSON path is correct
  3. Check for typos in field paths
  4. Ensure data exists in the response

Wrong Data Displayed

Cause: Incorrect field mapping.

Solutions:

  1. Check the JSON path matches your expected data
  2. Verify you're not accessing wrong array index
  3. Clear YOOtheme cache after changes

Data Not Updating

Cause: Caching is active.

Solutions:

  1. Check cache duration settings
  2. Clear API Mapper cache
  3. Clear YOOtheme cache
  4. Wait for cache to expire

Performance Issues

Page Loads Slowly

Cause: API requests are slow or blocking page load.

Solutions:

  1. Increase cache duration
  2. Reduce number of fields fetched
  3. Use pagination to limit data
  4. Check if API itself is slow

Too Many API Requests

Cause: Cache settings too short or disabled.

Solutions:

  1. Enable caching
  2. Increase cache duration
  3. Check if multiple elements use same connection
  4. Verify cache is working correctly

YOOtheme Integration

Source Not Appearing in Customizer

Symptoms: API Mapper connection doesn't show in dynamic content dropdown.

Solutions:

  1. Save the connection first
  2. Clear YOOtheme cache
  3. Refresh the Customizer
  4. Check PHP error logs
  5. Verify connection is active/enabled

"Invalid source" Error

Cause: Connection configuration issue.

Solutions:

  1. Re-save the connection
  2. Check for PHP errors
  3. Clear all caches
  4. Verify field mappings are valid

Getting Help

If you can't resolve your issue:

  1. Check Documentation - Search these docs for your specific error
  2. Collect Information:
    • WordPress/Joomla version
    • YOOtheme Pro version
    • PHP version
    • Error messages (exact text)
    • Steps to reproduce
  3. Contact Support - Email support@wootsup.com

Debug Mode

To enable detailed error logging:

WordPress

Add to wp-config.php:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);

Check logs at: wp-content/debug.log

Was this page helpful?