Application-level compatibility

Frameworks under test

A recognized tag is not enough. Each framework gate includes local source provenance, a request-driven demo, exact rendered output, and the language features that application needs.

Passingdemo + MariaDB fixture

PageBlocks 5.5

Block composition and MySQL-backed models

The fixture uses the recovered PageBlocks API, legacy form values, relative includes, prepared database work, record iteration, and PageBlocks-style block assembly.

  • Exact-output request test
  • Seeded MariaDB schema
  • Lasso 8.6 worker profile
Open the PageBlocks demo →
Passingrouter fixture

LassoFusebox / LFB

Fuseaction routing and include composition

The LFB fixture resolves a fuseaction, dispatches through framework-relative includes, and renders an exact response using the recovered Lasso 6–8 core files.

  • GET action parameter dispatch
  • Nested relative includes
  • Exact rendered response
Open the LFB demo →
Passing2015 Knop 8 source

Knop 8

The demanding third framework

The latest surviving Knop 8 namespace is vendored as a whole and gates old-style LassoScript definitions, custom types, navigation, forms, grids, localization, authentication, and database helpers. Its deployment files have been updated for nginx, HTML5, UTF-8, InnoDB, and protected configuration.

  • Zero-diagnostic full namespace gate
  • Real Knop tag in a request-driven demo
  • Modern deployment overlay
Open the Knop demo →

Meaning of “tested”

No compatibility by association

These results apply to the checked-in versions and demo paths. They do not claim that every third-party extension, connector, undocumented bug, or arbitrary application configuration will behave identically. Application acceptance testing remains part of migration.