Report As File¶

Path structure

The directory structure mirrors exactly the typo3 page structure.

Each QFQ tt-content record corresponds to exactly one file located in the directory which is named after the page in which the tt-content record lies.

Problem: The page name might not be unique thus multiple directories with the same name must exist.

Problem: QFQ applications depend on more than the tt-content records:

• position of tt-content record on page (center/column)
• order of tt-content records on page
• page alias of page on which tt-content record is
• page alias of all other pages

Problem: If someone used the page id or the uid of a tt-content record inside a QFQ report as a link, then this will break.

File and tt-content table synchronization:

Assume we can recognize wheter the file or the report was changed since the last synchronization between the two.

Chalenges:

• recognize changes since last synchronization efficiently
  • Obvious solution: create table "Sync" and use it to track the last synchronization
    • columns:
      • id
      • recordId
      • recordFingerprint
      • pathFileName
      • fileFingerprint
      • modified
      • created
• overwrite tt-content without braking the typo3 tt-content history mechanism. 
  • look at how tt-content is edited by the QFQ admin interface in the frontend and copy aproach.
• scenarios not covered yet:
  • file exists, but not tt-content
  • tt-content exists, but not file
  • both exists but where never synchronized
• Typo3 does not enforce page pathes to be unique
  • Possible solution: QFQ enforces uniqueness by throwing exception if not satisfied