Troubleshooting - Plugixa FAQ

Grouped by what you are looking at rather than by which feature is at fault, because the feature at fault is usually the thing you cannot see.

Nothing renders

The shortcode prints as literal text. It is inside a code block, or the editor has escaped it. Retype it in a plain paragraph block.

The block is empty. Every answer is a draft. Publish at least one, or check the Status filter on the FAQ list.

It renders on one page and not another. The second page filters to a category with no published answers. Check the category attribute against the slug in the Categories screen.

It disappeared after a theme change. The new theme is not calling the_content on that template. This affects every shortcode on the site, not just ours.

The wrong design

It is not the view I chose. Check whether you passed a view id as id. The three selectors read alike and only one of them is a shortcode id:

id="3"          a saved shortcode
view="ocean-night"   a view slug
view_id="6"          a view id

Passing a view id as id finds nothing, falls back to the default view, and renders something plausible. This is the single most common cause.

Every page changed at once. They point at the same view, and that is what a view is for. Duplicate it and repoint one page at the copy.

It looks unstyled. Either Disable plugin CSS is on under Advanced, or the placement is somewhere the plugin could not detect in advance. Try Load assets globally.

Styling fights with the theme

The plugin styles through scoped CSS variables, so the fix is almost always to override the variable rather than the class:

.pxf-custom-faq-root { --pxf-question-bg: #f6f7fb; }

Targeting the classes directly works until the next release. Overriding --pxf-* is stable and is scoped to that one placement.

If your theme sets something with high specificity and wins anyway, scope your rule to a wrapper you control rather than adding !important.

Answers open strangely

All of them are open. The view sets Open first, or a theme stylesheet is forcing a height on the answer container.

Clicking does nothing. Another script on the page threw an error and stopped the listeners attaching. Open the browser console; the error is almost always from a different plugin or the theme.

Rows jump as they open. An image inside an answer has no width and height, so the browser does not know how tall the row will be until it loads.

Search and filters

Search finds nothing. It searches published answers only, in the current language.

A category is missing from the filter bar. It has no published answers. Empty categories are hidden rather than shown as dead ends.

Find-on-page misses an answer. Pagination is on, and the browser can only search what is rendered. Set pagination="none".

Permalinks

Answer pages 404. WordPress caches its rewrite rules. Open Settings, then Permalinks in WordPress, and press Save. Nothing needs changing; saving is what flushes them. This catches everyone once.

The URL did not change after renaming. Slugs are generated once and then kept, so existing links keep working. Clear the slug field and save to regenerate it.

Schema

No markup is detected. Schema is off in Settings, off on the shortcode, or the page is not publicly reachable.

Two FAQPage blocks. Two placements on one page. Set schema="false" on one.

Rich results never appear. Valid markup makes a page eligible, not guaranteed. There is nothing to fix at this end.

Multilingual

French answers sit in an English category. The answer’s category was never switched to its French counterpart. The translation groups being correct is not enough; the category on the record has to point at the French one.

A French page shows English answers. The fallback is set to show the default language. Set it to hide, or translate the answer.

Premium features

The Feedback or Submission tab configures nothing. Both tabs are visible in the free build, and both features are premium. This is confusing and it is not your setup.

A premium REST route 404s. The free build does not contain the premium code at all, so those routes are absent rather than refusing politely.

Collecting information for support

Before writing to us, it helps to have: your WordPress and PHP versions, whether this is the free or the Pro build, the exact shortcode from the page, and whatever the browser console says. Settings, then the health information on the Advanced tab, has the first three.

Still stuck

Email support with the information above and a link to the page. A URL we can open answers more questions than a description, and if the page is not public, a screenshot of the whole browser window including the console is the next best thing.