Troubleshooting
Troubleshooting
Section titled “Troubleshooting”When the GIF picker cannot reach the active provider, it shows an error in place of the GIF grid. The rest of the post form keeps working: members can still post text without a GIF.
The GIF button does not appear
Section titled “The GIF button does not appear”Work through these in order:
- API key. A valid key must be saved for the active provider on General. A green “API key is valid and working” message next to the field confirms it.
- Area toggle. The area in use must be enabled: Profile activity, Group activity, Private messages, or (bbPress) Forum topics and replies. Check the Overview tab for the count of enabled areas.
- Dependency. BuddyPress (or bbPress for forums) must be active. Under BuddyBoss the plugin deactivates itself.
- Messages and forums need the visual editor. In private messages and bbPress, the button is added to the TinyMCE toolbar, so it only appears when the visual (rich text) editor is active. A member with the visual editor disabled in their WordPress profile will not see it.
API key validation on the settings page
Section titled “API key validation on the settings page”When you save or leave the API key field on the General tab, the page checks the key live against the provider and shows one of:
| Result | Meaning |
|---|---|
| API key is valid and working | The key works. |
| Invalid API key | GIPHY returned 403, or Klipy returned 401 / 403 / 404. The key is wrong, or a GIPHY app was set to SDK instead of API. |
| API rate limit exceeded | The provider returned 429. Wait and try again. |
| Error checking API key (with a status code) | Another response was returned. |
The key is saved even when it fails validation, so you can correct it without retyping.
Errors members see in the picker
Section titled “Errors members see in the picker”The GIF popup shows one of these when it cannot load GIFs:
| Situation | Message |
|---|---|
| No GIPHY key saved | “Giphy API key not configured. Please configure your API key in the plugin settings.” (with a link to settings) |
| No Klipy key saved | “Klipy API key not configured. Please configure your API key in the plugin settings.” (with a link to settings) |
| Cannot reach the provider | “Failed to connect to [Giphy/Klipy]. Please check your internet connection.” |
| Invalid key or bad request | “Invalid API key or request failed. Please check your settings.” |
| No GIFs returned | “No GIFs available. Please try again later.” |
| Search returned nothing | “No GIFs found. Try searching for something.” |
Resolving common cases
Section titled “Resolving common cases”Missing API key. Go to General, select the correct provider, enter your API key, and save.
Invalid API key. The key may have been regenerated or deleted in your provider account. Log in to the GIPHY or Klipy developer dashboard, copy the current key, paste it into General, and save.
Rate limit exceeded. Both GIPHY and Klipy enforce request limits on free-tier keys. On a busy community you may hit the limit. Wait a few minutes; free-tier limits typically reset within an hour. For high traffic, contact the provider about higher-tier access.
Cannot reach the provider (network error). Check that your server can make outbound HTTPS requests to api.giphy.com or api.klipy.com. Some hosts block outbound requests by default.
GIFs load but look too large or too small. Adjust the GIF rendition on General. Smaller renditions (GIPHY fixed_width/fixed_width_downsampled, Klipy sm/xs) load faster and suit mobile.
Klipy returns fewer GIFs than expected. Klipy caps each request at 50. If “Number of GIFs to load” is above 50, Klipy still returns at most 50.
Fallback behaviour
Section titled “Fallback behaviour”When GIFs cannot load, nothing else in your community breaks. Members can still post text-only activity, comments, messages, and forum posts. Only the GIF grid is replaced by an error message.