Project

General

Profile

Actions
Copy link

Bug #9013

open

Error in Twig template not handled

Added by Nicola Chiapolini over 4 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
Carsten Rose
Target version:
next3
Start date:
04.09.2019
Due date:
% Done:

0%

Estimated time:
Discuss:
Prio Planung:
Vote:

Description

Bei einem Fehler im Twig-Template wird die "Oops, an errro occured..." Meldung angezeigt und der Debug-Output ist nirgends sichtbar. (analog zu #6216)

Actions
Copy link
 #1

Updated by Carsten Rose almost 4 years ago

  • Status changed from New to Some day maybe
Actions
Copy link
 #2

Updated by Marc Egger over 3 years ago

  • Status changed from Some day maybe to New
  • Assignee set to Marc Egger
Actions
Copy link
 #3

Updated by Marc Egger over 3 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #4

Updated by Marc Egger over 3 years ago

Created branch for issue and implemented it. Twig errors are shown.
Problem: QFQ removes new line characters early. The whole Twig template is on one line which makes the error messages useless.
Solution?: We have to find a way to keep the new line characters in the twig template when parsing a QFQ report.

Actions
Copy link
 #5

Updated by Marc Egger over 3 years ago

  • Status changed from In Progress to Priorize
Actions
Copy link
 #6

Updated by Marc Egger over 2 years ago

  • Status changed from Priorize to New
  • Assignee changed from Marc Egger to Carsten Rose

QFQ loescht alle new line characters raus, wenn es einen Report rendert. deshalb ist es nicht moeglich eine schoene Twig fehlermeldung auszugeben, da man das twig template nur als einzeiligen string und nicht mit originaler formatierung rendert.
Hast du irgend eine (quick and dirty) idee wie man das twig template samt newlines aus dem report ziehen koennte beim parsen?

Nicola wäre uns um dieses feature sehr dankbar

Actions
Copy link
 #7

Updated by Carsten Rose over 2 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #8

Updated by Carsten Rose over 2 years ago

  • Assignee changed from Carsten Rose to Marc Egger

Was waere mit '<br>'?

Actions
Copy link
 #9

Updated by Carsten Rose over 2 years ago

  • Target version set to next4
Actions
Copy link
 #10

Updated by Carsten Rose over 2 years ago

  • Target version changed from next4 to next3
Actions
Copy link
 #11

Updated by Carsten Rose over 2 years ago

  • Priority changed from High to Normal
Actions
Copy link
 #12

Updated by Carsten Rose over 2 years ago

  • Status changed from New to Priorize
Actions
Copy link
 #13

Updated by Marc Egger over 2 years ago

  • Status changed from Priorize to New
Actions
Copy link
 #14

Updated by Marc Egger over 2 years ago

Carsten weiss gerade nicht, weshalb alle \n geloescht werden.
Ansatz: das loeschen raus nehmen und probieren ob QFQ noch laeuft.
Falls nein: dann Twig keyword fuehzeitig erkennen und das loeschen der \n nur fuer non-twig machen
Falls ja: check ob wir das komplett rauslassen koennen

Actions
Copy link
 #15

Updated by Marc Egger over 2 years ago

  • Status changed from New to Priorize
Actions
Copy link
 #16

Updated by Marc Egger about 2 years ago

  • Assignee changed from Marc Egger to Carsten Rose
Actions
Copy link
 #17

Updated by Carsten Rose about 2 years ago

  • Status changed from Priorize to New
Actions
Copy link

Also available in: Atom PDF