Troubleshooting & FAQ

This article collects the most common issues operators run into after installing the plugin, and the fastest path to a fix.

The sign-in overlay never appears

Check, in order:

Is the Auth module enabled under Unidy → Overview? Disabled modules silently drop their shortcodes and click interception.

Does the link you're clicking match a Trigger URL pattern (default /login)? Add the correct pattern under Unidy → Auth → Trigger URL patterns.

Is the Container selector scoping the interception too narrowly? Try clearing it to catch clicks site-wide.

Is the SDK bundle loading? Open your browser's DevTools and confirm no net::ERR_FAILED errors are shown for the Unidy CDN.

"Instance URL not reachable" on the Overview screen

Verify the instance URL includes the protocol (https://...).

Check that your WordPress server can make outbound HTTPS requests. Some managed hosts block outbound traffic by default.

On the Unidy instance side, confirm your WordPress domain is on the allowed origins list.

Modules stopped working after a plugin update

Open the WordPress admin as the site administrator and go to Unidy → Overview. If any module is disabled that shouldn't be, re-enable it.

If you use WP Rocket or a similar page cache, purge the entire cache. Some plugin updates change the localized JS config that gets embedded on every page.

In rare cases the plugin's composer autoloader needs regeneration. Deactivate and reactivate the plugin (Plugins → Unidy SDK → Deactivate → Activate) to run the migration routine again.

Cards on a dark host page look weird

By default our cards render on a white surface — this reads well as "editorial white on dark". If you want the cards to match the host's dark background instead, contact your Unidy CSM. This is an advanced integration option not exposed in the admin UI yet.

The sign-in modal shows an outdated title

The modal title is configured under Unidy → Auth → Texts → Header title. If it still shows an old value after editing, clear your page cache.

Users see raw error codes like `invalid_verification_code`

This means the plugin's Custom Error Messages system can't map the SDK's error to a configured message. Either:

Change the active preset under Unidy → Auth → Fehlermeldungen & Bestätigungen to Casual DE or Formal DE — both cover the standard SDK codes.

Or override that specific code with your own text in the same admin screen.

If a code you're seeing isn't listed in the admin editor, contact your Unidy CSM — new SDK versions occasionally introduce codes we haven't cataloged yet.

Sign-in works, but modules still show "signed out"

After sign-in the plugin re-hydrates its inline modules automatically (newsletter, tickets, transactions, subscriptions, profile). If a module still shows the signed-out state:

Reload the page manually — this always fixes it. If it doesn't, the SDK auth cookie isn't being set (check DevTools → Application → Cookies).

Confirm you're on the Frontend only session mode. In Create WP user or Match mode, the plugin reloads the page automatically after sign-in, which side-steps this class of issue.

Where to get help

Product questions: your Unidy Customer Success contact.

Bug reports: github.com/UnidyID/unidy-wordpress-plugin/issues — include your WordPress version, PHP version, active plugins list, and a clear reproduction path.