Contents

Troubleshooting — Plugixa Team

Common issues and how to fix them. If your problem isn’t here, collect the debug info at the bottom and contact support.

Recover admin access

If a plugin-related fatal error locks you out of the dashboard, log back in through the standard WP login page and reactivate the plugin in Safe Mode — WP-CLI or wp-config.php → define( 'WP_DEBUG', true ); is the quickest path.

WordPress login

Plugin & license

Plugin menu doesn’t appear in admin

Symptom: You installed and activated the plugin but no Plugixa Team menu appears.

Causes & fixes:

  • User role — the menu requires plugixa_team_settings (or the WP admin to have it). This cap is granted to administrators on activation. Non-admins don’t see the menu unless you grant them the cap.
  • Another plugin is suppressing it — switch to a default theme and deactivate all other plugins to isolate.
  • Autoloader failed — check the error log for Class "PlugixaTeam\Plugin" not found. Delete vendor/ and re-download the plugin ZIP.

License won’t activate

Symptom: Clicking Activate in Plugixa Team → Account returns an error.

Fixes:

  • Confirm the license key is copied without whitespace.
  • Confirm the site URL matches what’s on file in your Plugixa account. If you moved sites, deactivate the old one first.
  • Check outbound HTTPS from your server to api.freemius.com — some shared hosts block it by default.
  • If the error mentions “Already activated” — deactivate from the old site, or contact support to free up an activation slot.

Pro features show “Upgrade” card after licensing

  • Hard-refresh the admin page (Ctrl+Shift+R).
  • Confirm pro/ directory exists inside the plugin folder. If your install was from WordPress.org (free build), the Pro files aren’t shipped — re-download from your Plugixa account.
  • Run composer dump-autoload -o if you moved files manually (not a typical scenario).

Shortcodes & frontend

Shortcode prints as raw text

Symptom: The page shows [plugixa_team] literally instead of members.

Fixes:

  • Confirm the plugin is active: Plugins → Installed Plugins.
  • Check that quotes are straight (") not curly (""). The WP visual editor sometimes converts them — paste from a plain-text editor.
  • If you’re using a page builder, use the builder’s Shortcode widget, not a raw HTML block.

No members displayed

Symptom: Empty space where the team should be.

Run through this checklist:

  1. Members exist and are published — Plugixa Team → Members. Status must be published.
  2. Correct group slug — typos are the #1 cause. Compare the slug in Groups to the one in your shortcode.
  3. Language filter — if Multilingual is active, members in other languages are hidden. Try language="en" explicitly.
  4. Fallback setting — with multilingual_fallback="hide", missing translations show nothing. Switch to default_language.
  5. Featured filter — featured_only="1" with no featured members returns nothing.

Styling doesn’t match the view preview

Symptom: The view looks right in the editor preview but different on the frontend.

Causes & fixes:

  • Theme CSS conflicts — use browser DevTools to find the overriding rule. Plugixa Team classes all start with .pxt-custom-*. Scope your theme overrides to .pxt-custom-team-root {theme-rule}.
  • Shortcode overrides — show_*, dark_mode, pagination attributes override the view. Check the shortcode markup.
  • Caching — page cache, object cache, or CDN may serve a stale CSS file. Purge and retry.
  • Assets didn’t build — for a fresh install from git, make sure assets/frontend/build/css/frontend.css exists. Shipped ZIPs include the built file; source checkouts require npm run build.
  • Confirm the layout is carousel in the view.
  • Open DevTools Network panel — plugixateam-swiper-bundle.min.js must load. If blocked, a caching / minification plugin is likely deferring or combining it incorrectly. Exclude that file from optimization.
  • If Elementor is active and also registers Swiper, the plugin uses the plugixateam-swiper handle prefix to avoid collisions — but some custom themes call Swiper globally, which can race. Check the console for errors.

Dark mode doesn’t apply

  • Confirm the shortcode’s dark_mode is not disabled.
  • Confirm the view has dark-mode colors configured (not all white-on-white).
  • For auto mode: confirm your browser / OS has a dark-mode preference active — there’s nothing for Plugixa Team to match otherwise.

Members & forms

Save member fails silently

  • Check the browser console for validation errors — most failures surface here first.
  • Look at the admin error bar at the top of the React SPA — REST errors appear there.
  • Check PHP error log for database-level errors (e.g., unique slug collisions).

Submission form submissions aren’t arriving

See Submission Form → Troubleshooting for a comprehensive list. Most common:

  • reCAPTCHA score below threshold — temporarily lower recaptcha_threshold to 0.3 while testing.
  • Rate limit hit — you exceeded 5 submissions / 15 min from your IP while testing.
  • Required field missing — check the server response body for per-field errors.

Photo uploads fail

  • PHP upload_max_filesize / post_max_size too small.
  • Plugin photo_upload_max_size setting too small (default 2 MB).
  • Image type not in allowed list (jpeg, png, gif, webp).
  • Some managed hosts restrict media_handle_upload() for unauthenticated users — contact your host.

Multilingual (Polylang)

Multilingual migration did not run

  • Deactivate and reactivate the plugin — the migration is idempotent and only adds rows that are missing language_code.
  • Check wp_options for plugixateam_multilingual_migrated — if present but not 1, delete it and reactivate.

All languages show the same content

  • Check that each member has the correct language_code — empty = “belongs to all languages”.
  • Check each translation has status = published. Each has its own status.

Translation tabs are missing on the form

  • Confirm Polylang is active and has at least 2 languages configured.
  • Confirm Settings → Multilingual → Enabled is auto (or unset, which defaults to auto).
  • Hard-refresh the admin page.

Group filter doesn’t match a translated group

The plugin matches by translation_group UUID, not slug alone. Confirm both groups share the same UUID in the database.

AI Generator PRO

Test Connection fails

  • API key is wrong or revoked. Regenerate at the provider.
  • Outbound HTTPS is blocked — check with wp-cli eval 'var_dump(wp_remote_get("https://api.openai.com"));'.
  • Proxy / firewall interception strips required headers.

Generated members look generic

See AI Generator → Troubleshooting. Short version: raise topic specificity, lower temperature, provide a context paragraph.

URL scraping returns empty

Sites with bot detection or JS-rendered content can’t be scraped. Workaround: save as PDF and upload, or paste text into the topic field directly.

Import / Export PRO

CSV imports all in one column

Your file is tab-delimited or uses a non-comma separator. Re-save explicitly as “CSV (comma-delimited)”.

“Memory limit exceeded” during large imports

Raise memory_limit in PHP, or split the file. See Import / Export → Limits.

Exported photos don’t attach on the target site

Photo URLs are exported but not automatically downloaded. Either pre-upload photos to the target media library, or implement a photo-sideload filter — see Hooks.

Schema / SEO

Duplicate schema blocks in page source

Usually a page cache stale-serving before the suppression filter fires. Purge cache. If it persists, check whether Yoast / RankMath schema is being output from a different filter than expected in your version.

Person entities missing from Yoast graph

  • Confirm members are rendered on the page (the plugin only adds entities for members actually in the DOM).
  • Try schema="1" explicitly on the shortcode to force schema output.

Assets & build

404 on /build/css/main.css in admin

A fresh git checkout without running npm run build in assets/backend/app/. Run the build, or install from the shipped ZIP instead of git.

HMR not working during development

The includes/admin/class-hmr.php file gates dev-server asset loading. For HMR:

  • Run npm run dev in assets/backend/app/ (Vite on port 5174).
  • Confirm class-hmr.php exists (delete it for production).
  • Confirm the admin page can reach http://localhost:5174/ — browser security doesn’t block it on most setups.

Debug info to include with support requests

When contacting support, paste the output of these commands:

# Plugin version
wp plugin get plugixateam

# Active plugins
wp plugin list --status=active --fields=name,version

# PHP / WP versions
wp --info

# DB consistency (checks all Plugixa Team tables)
wp db query "SELECT table_name, table_rows FROM information_schema.tables WHERE table_schema = DATABASE() AND table_name LIKE '%plugixateam%'"

Also attach:

  • The last 100 lines of your PHP error log.
  • The failing shortcode’s exact text.
  • Browser console errors (if applicable).

Quick Links

Plugin page Changelog