Table of Content7 Sections
What Was Actually Checked?
Read each test record with its release, date and sample scope. The 3.4.0 record is the historical English baseline, including its separately identified 3.3.0 demonstrations. Later records describe only the checks actually completed for those releases. A new version number does not turn an earlier run into a new test. The examples use harmless documents with known text, images, tables or form values.
Current Release Checks
Evidence reviewed: 10 October 2026 · Theme release: 3.21.0
| Check | Observed result | Scope |
|---|---|---|
| Page and language coverage | 87 native pages and 66 tools in every edition. | English remains the master. New page bodies, controls, errors, FAQs and metadata match its content structure. |
| New conversion workflows | 255 browser conversions passed; 765 genuine tutorial screenshots recorded. | Seventeen added tools tested in every interface with harmless local samples, saved downloads and no document-upload requests. |
| Saved-file checks | Structured exports, image conversions and DXF outputs passed independent checks. | Known values, pixels or geometry were parsed or compared. Supported format, page, memory and fidelity limits still apply. |
| Archival PDF profiles | Representative PDF/A-1b, PDF/A-2b and PDF/A-3b outputs passed veraPDF. | These tools rebuild page images. Searchable text, interactive objects, attachments and original signatures are not retained. |
| Upgrade and metadata | Existing customizations and complete page metadata verified locally. | Fresh default and owner-edited upgrades; repeated synchronization; all 1,305 rendered pages checked. No live-host certification. |
These are local release checks, not a live hosting benchmark or a guarantee for every document. Content and translations received AI-assisted review; no independent native-speaker certification is claimed. Historical evidence retains its original release and date.
Historical Checks
Evidence reviewed: 8 October 2026 · Theme release: 3.4.0
| Check | Observed result | Scope |
|---|---|---|
| 49 tool demonstrations | All 49 sample uploads, settings, processing and saved downloads passed; zero browser script errors. | Version 3.3.0 baseline, 8 October 2026. The same day’s 3.4.0 checks below cover changed processing and new examples. |
| Five reproducible output examples | Rotate, Redact, Excel to PDF, OCR and Compress passed actual UI conversion and saved-output checks. Source and result downloads are provided. | Fresh 3.4.0 checks, Chromium. These are illustrative sample outcomes, not quality or compression guarantees. |
| Rotation and redaction | A one-page source changed from 90° to 0° with unchanged extracted text. The redaction example removed the fictional marked text and produced one image-only page. | Known sample documents; saved orientation, rendered coverage and extracted text checked. |
| Excel, OCR and compression | Excel preserved the sample total of 125.00 as selectable PDF text. OCR added 176 recognized characters. Lossless compression reduced the six-page fixture by 35.5% with unchanged rendered pages and text. | The supplied examples use supported cells, clear English text and a deliberately redundant PDF. |
| Summary and CSV regressions | 11 actual browser checks passed, including wrapped text, Dr. Rivera, decimal values, page ranges/order, the 12-passage cap, fallback behavior, rejected inputs and semicolon/tab CSV exports. | Fresh 3.4.0 checks of downloaded TXT/CSV files; zero browser script errors. |
| SEO-plugin metadata and FAQs | 126 assertions passed for metadata fallbacks, explicit plugin overrides, FAQ deduplication and hook-registration isolation. | PHP hook-contract fixtures for Yoast, Rank Math, AIOSEO and SEOPress; full live plugin installations were not exercised. |
| Updates and public support settings | Nine migration cases and 15 support/admin checks passed. Bundled content updates while custom page bodies, titles and metadata are preserved; configured public details render with escaped output. | PHP fixtures with simulated WordPress APIs. Contact delivery was mocked; no real email was sent. |
| Word and PowerPoint exports | A two-page Word document, a one-page Word document and a two-slide PowerPoint file produced readable image-based PDF pages. A blank-first-page issue in Word capture was fixed and the saved results were rechecked. | Fresh 3.4.0 Chromium uploads and downloads; five rendered pages visually inspected with known-text spot checks. No universal layout guarantee. |
These checks used the shipped theme in a local PHP template fixture and Chromium with harmless sample documents. They do not establish live hosting, every plugin edition, mail delivery, real-device performance or compatibility with every input file.
How Were Source and Output Compared?
| Operation | What the checks examined | What still needs document-specific review |
|---|---|---|
| Arrange and edit PDF pages | Saved page count, order, rotation, dimensions, overlays and form-field behavior. | Unusual annotations, complex forms, existing digital signatures and application-specific rendering. |
| Export page images | The downloaded image/archive opened with the expected pages and image dimensions. | Whether the chosen resolution is sufficient for a particular print or screen size. |
| Extract text and tables | Expected source text, selected-page behavior and the structure of generated text and spreadsheet files. | Reading order, inferred columns, merged cells, dates and numerical meaning. |
| Create searchable scans | OCR output contained recognized text for the known English sample. | Recognition of each word, handwriting, unusual fonts and low-quality photographs. |
| Convert Office files | Generated PDFs opened and representative text, images, tables and page/slide counts were inspected. | Exact desktop pagination, unsupported objects, fonts and complex workbook print layouts. |
| Protect, unlock and flatten | Password behavior and the saved document structure, including field appearances and remaining annotations. | Whether a recipient accepts the chosen security settings or document workflow. |
Can You Inspect a Source and Result Yourself?
The Rotate PDF, Redact PDF, Excel to PDF, OCR PDF and Compress PDF guides include worked examples beside their instructions. Use the provided source and output to check the exact change described: a saved orientation, a removed region, worksheet values rendered on a PDF page, recognized words or a measured file-size change. These examples show a bounded result for a known sample; they are not proof that every document will convert identically.
Tutorial screenshots across the tool guides show file selection, settings and a completed result in the shipped interface. They were captured in a local test environment using sample files. Numbered arrows explain which control to use; they do not change the downloaded document. Output examples add a separate check of what the tool produced.
Which Failure Cases Were Included?
The release evidence also records rejected inputs and resource limits, including unsupported Office content, invalid or oversized inputs and missing formula results. A no-text scan was treated differently from a PDF with selectable text. The expected behavior was a useful error or a clearly described output, rather than a success message attached to an unusable file.
Targeted regression checks addressed reported defects such as downloading a long PDF in Reader, applying selected page ranges and retaining flattened form appearances. The dated summary separates these specific checks from broader demonstrations. A passing example narrows the uncertainty for that case; it does not remove the limits stated on the tool page.
What Do Browser Office Checks Establish?
Browser Word and PowerPoint export produces image-based PDF pages. Their checks concern rendered appearance and page or slide structure. Excel export produces supported cell text and saved formula values; it does not recalculate formulas. The original workbook must contain the values needed for export. A visual PDF check cannot establish that a spreadsheet calculation is correct.
What Was Outside the Test Environment?
Local template and browser tests do not reproduce every live WordPress installation, plugin combination, cache, security policy or mobile device. They do not establish production email delivery, search indexing or performance on every connection. Optional Native Office export also depends on the host’s LibreOffice installation, fonts, permissions and temporary storage; browser demonstrations do not validate that server route.
The guides were prepared with AI assistance and checked against the available controls and cited official documentation. Researching an external application’s instructions is different from executing them on a device. The records identify actual browser or file checks where performed; they do not imply unrecorded mobile tests, a named human review or professional certification.
How Can a New Failure Be Investigated?
Report the tool, source format, settings, browser and exact result through Contact. If the output differs on one page, identify that page and the changed element. A small harmless sample with the same structure is more useful than a private full document. Do not send passwords or confidential content. The original file should remain available for your own comparison while the issue is investigated.