Contents

Blocks - Plugixa Exam

Five blocks ship free and Pro adds a sixth. Find them in the block inserter by searching for exam.

Every block is a thin wrapper over the same server-rendered output as the equivalent shortcode, so the two never drift apart.

The blocks

Block Renders Settings Edition
Exam catalogue Every published exam limit Free
Exam search A search box over the catalogue per_page Free
My exams What the learner has been assigned none Free
My results What they have scored limit Free
My certificates What they have earned none Free
Exam leaderboard Opt-in public rankings exam, top, title PRO

Exam catalogue

The list of published exams. limit caps how many appear; leave it at 0 to show all of them.

A signed-in visitor sees their own standing on each row, so the same block reads differently to a learner part-way through a course than to a first-time visitor.

A search field over the catalogue. per_page sets how many results a page holds.

My exams, My results, My certificates

The three learner-portal lists, each usable on its own so you can build a dashboard page that matches your site rather than using the plugin’s.

They render on the server and are never cached, because they carry one person’s own data.

Exam leaderboard PRO

Rankings for one exam. exam picks it, top sets how many places to show, and title puts a heading above the table. Participation is opt-in per learner.

Server-rendered, and why that matters

Each block saves only its settings. The markup is produced by PHP when the page is requested, which has three consequences:

  • The block never goes stale. Improving the catalogue markup improves every page that already embeds the block, with no “this block contains unexpected content” warnings and nothing to re-save.
  • It works without JavaScript on the front end, like the rest of the plugin.
  • The editor shows a preview, not the real thing. What you see while editing is a representation; the page itself is authoritative.

Not compiled, on purpose

The blocks are plain JavaScript written against the wp.* globals rather than a bundled build. There is no npm run build step for them, and no compiled asset to keep in sync with its source.

That matters if you are reading the plugin’s source or submitting it anywhere that asks for human-readable code: what ships is what was written.

Blocks or shortcodes?

Use blocks if you are in the block editor and want the settings in a sidebar. Use shortcodes for widgets, page builders, or anywhere you want the same output expressed as text you can copy.

There is no functional difference in the output.

Troubleshooting

Symptom Usual cause
The blocks are missing from the inserter The relevant capability is off in the App Manager, or the plugin is not active on this site in a multisite.
The editor preview is empty Several blocks show one person’s own data and there is none for you in the editor. Check the front end.
The leaderboard block is missing It is a Pro block. Check the premium build is the one installed.
A block renders but is unstyled The page is served from a cache built before the plugin was active. Clear the page cache.

What to do next

Quick Links