Fatal error: Class 'Dompdf\Options'

[cheesegrits]

Oh, right, yes, don't worry about that. And I'll fix it in 3.7.1.

-- hugh

 

[luisoferrandiz]

Ok,
I get the PDF but when I try to read it, The document is damage.

Luiso

 

[luisoferrandiz]

I have the Fabrik Package 3.42 but the version installed is 3.7.
Is it normal?
I can not get PDF "not corrupted"
-Luiso

 

[troester]

Fabrik Package is always showing the version of your first Fabrik installation m This is normal.
Can you open your damaged PDF with an editor like notepad++ to see what it contains?

Gesendet von meinem GT-I9300 mit Tapatalk

 

[luisoferrandiz]

<br />
<b>Warning</b>: strstr(): Empty needle in <b>/..../components/com_fabrik/helpers/pdf.php</b> on line <b>109</b><br />
<br />
<b>Warning</b>: strstr(): Empty needle in <b>/..../components/com_fabrik/helpers/pdf.php</b> on line <b>109</b><br />
<br />
<b>Warning</b>: strstr(): Empty needle in <b>/..../components/com_fabrik/helpers/pdf.php</b> on line <b>109</b><br />
<br />
<b>Warning</b>: strstr(): Empty needle in <b>/..../components/com_fabrik/helpers/pdf.php</b> on line <b>109</b><br />
%PDF-1.3
1 0 obj
<< /Type /Catalog
/Outlines 2 0 R
/Pages 3 0 R >>
endobj
2 0 obj
<< /Type /Outlines /Count 0 >>
endobj
3 0 obj
<< /Type /Pages
/Kids [6 0 R
12 0 R
15 0 R
19 0 R
23 0 R
26 0 R
30 0 R
33 0 R
37 0 R
]
/Count 9
/Resources <<
/ProcSet 4 0 R
/Font <<
/F1 8 0 R
/F2 9 0 R
>>
>>
/MediaBox [0.000 0.000 841.890 595.280]
>>
endobj
4 0 obj
[/PDF /Text ]
endobj
5 0 obj
<<
/Producer (dompdf <0f418c6> + CPDF)
/CreationDate (D:20170720171940+00'00')
/ModDate (D:20170720171940+00'00')
/Title (Decisions)
/Subject (JuryWeb)
>>
endobj
6 0 obj
<< /Type /Page
/MediaBox [0.000 0.000 841.890 595.280]
/Parent 3 0 R
/Contents 7 0 R
>>
endobj
7 0 obj
<<
/Length 18154 >>
stream

1.000 1.000 1.000 rg
34.016 49.016 773.859 504.749 re f
0.200 0.200 0.200 rg
BT 34.016 530.004 Td /F2 28.9 Tf [(Decisions)] TJ ETq
34.016 513.564 m
34.016 330.647 l
34.016 330.450 34.035 330.254 34.073 330.061 c
34.112 329.869 34.169 329.680 34.244 329.499 c

...more

 

[cheesegrits]

That was fixed about a week ago in github:

https://github.com/Fabrik/fabrik/commit/f90ec54ac1a568abfd5729256074b28b63251a27

Note that if you have error reporting enabled on your site, you will quite often see strange behavior that you won't get if you disable error reporting. Error reporting should only be enabled on test sites, and typically only if you are trying to track a problem, or do a lot of development work.

The issue is that PHP error reporting injects the output into whatever is being rendered. For example, PDF outputs. Or responses to AJAX calls in Javascript. And quite often, a simple warning about something which isn't really causing a problem (like this, it's just a warning that PHP isn't seeing quite what it expected, but it wasn't actually hurting anything) will break your site.

-- hugh

 

[luisoferrandiz]

Great ??? It looks that it is solved.
Thanks for your help.

-- Luiso.

 

[rbuelund]

After update to Fabrik 3.8 - i get the above mentiod error: Error displaying the error page: Class 'Dompdf\Options' not found: Class 'Dompdf\Options' not found

What is going on here !! I had updated from github before and it worked and then stable version breaks it again - please fix this asap !

 

[cheesegrits]

Can you provide a little more information about what you are doing when you get that error.

-- hugh

 

[rbuelund]

I am just pressing the default pdf button in details view ! I updated from github 6 days ago, and everything worked with Joomla 3.8.1 - then updated with the Fabrik 3.8 update yesterday - and it stopped working. Updated from github again, and it worked again. Something must be broken in the 3.8 release ??

 

[cheesegrits]

Ah, I think I know what that might be.

Lemme go do some tests.

I'm pretty sure it's going to be to do with the autoloader for the Composer libs. We had to split out our Composer loaded libraries into a separate installer, lib_fabrik.zip, which is separately downloadable. If you load from github, you get the right setup for the autoloader. But I think installing the component (without installing the library) will remove the library autoloading.

I'll get back to you.

-- hugh

 

[cheesegrits]

OK, I've fixed the issue in the component installer, so it'll no longer blow away the Composer autoload setup.

You don't need to do anything if you've uploaded github code, as you'll have the right code already.

-- hugh