Client-side PDF flipbook content element for TYPO3 v14.
The extension is built for broad server compatibility:
- no server-side PDF conversion
- no
ImagickorGhostscriptdependency - no runtime shell commands
- local vendor assets only
- custom content element
Aistea FlippingBook - PDF source via FAL
- optional cover image
- desktop flipbook powered by
pdf.js+StPageFlip - mobile fallback with incremental scroll loading
- optional toolbar actions for fullscreen and download
- configurable viewer width, height, start page, theme and cover mode
- Require or update the package:
composer update aistea/aistea-flippingbook- Apply TYPO3 database schema changes:
vendor/bin/typo3 database:updateschema "*.add,*.change"- Clear TYPO3 caches:
vendor/bin/typo3 cache:flush- Ensure the site includes the extension set
FlippingBook.
The extension expects local browser builds at these paths:
Resources/Public/Vendor/pdfjs/pdf.min.mjsResources/Public/Vendor/pdfjs/pdf.worker.min.mjsResources/Public/Vendor/stpageflip/stpageflip.min.jsResources/Public/Vendor/stpageflip/stpageflip.css
The current package already references these files directly. If one of them is missing, the frontend falls back to a notice plus direct PDF link.
- Create a new content element:
Aistea FlippingBook - Select the PDF in
PDF document - Optionally add a cover image
- Adjust viewer settings only if the default output is not sufficient
PDF documentThe source file rendered by the viewer.Viewer widthBase desktop width in pixels. Larger values improve sharpness but cost more performance.Viewer heightBase desktop height in pixels.Start pageFirst page opened in the viewer.Use cover modeTreats first and last page as hard covers for more realistic page turning.Mobile modeControls small-screen behavior.ThemeShell styling around the viewer.Shadow strengthVisual intensity of the viewer frame and stage.
Viewer width:1200Viewer height:760Use cover mode: enabledMobile mode:scrollTheme:autoordark
- the PDF is rendered to page images with
pdf.js StPageFliphandles the page turning interaction- only nearby pages are rendered initially to keep startup lighter
- default mode is
scroll - pages are appended incrementally in small batches
- this avoids reserving space for the whole PDF at once
flipmode is still available if a book-like interaction is preferred
- very large PDFs still cost client-side memory and CPU
- higher width and height values increase render time
scrollis the safest mobile mode for long documents- desktop flip mode is best suited for brochures, presentations and shorter publications
Check:
- PDF file exists and is publicly reachable
pdf.min.mjsandpdf.worker.min.mjsare presentstpageflip.min.jsandstpageflip.cssare present- TYPO3 caches were flushed after deployment
One or more frontend vendor assets are missing or failed to load.
This usually means stale JS/CSS is still cached. Flush TYPO3 caches and hard reload the browser. The current implementation appends mobile pages incrementally instead of creating the full placeholder stack up front.
Enable Use cover mode. The extension marks the first and last page as hard cover pages for StPageFlip.
- Namespace:
Aistea\AisteaFlippingbook - Extension key:
aistea_flippingbook - CType:
aisteaflippingbook_book
- client-side rendering is not ideal for extremely large PDFs
- there is no text search or full PDF.js default viewer UI
- the toolbar is intentionally compact and custom
- custom backend preview renderer
- editor presets instead of raw width/height values
- page thumbnails
- deep-linking to a specific page
- analytics events for page turns