search

Zunenonooo / dompdf

Automatically exported from code.google.com/p/dompdf
0 stars 0 forks source link

PHP error #519

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
dunno exactly 

What is the expected output? What do you see instead?
expected output would be no error, but instead getting:
Warning: explode() expects parameter 2 to be string, array given in 
C:\www\EE_3-2\wp-content\plugins\invoice-sidney\tpc\dompdf\include\style.cls.php
 on line 956

What version of dompdf are you using? What version of PHP? On what operating 
system?
latest DOMPDF, PHP 5.3, Windows 7

Please provide the HTML source code you want to convert, or any additional 
information.

Here's part of the call stack when the error occurs:

10  0.3632  32279512    DOMPDF->render( )   ..\Invoice.class.php:134
11  0.4366  35330248    Stylesheet->apply_styles( ) ..\dompdf.cls.php:593
12  0.5092  37004600    Style->inherit( )   ..\stylesheet.cls.php:794
13  0.5093  37019184    Style->__get( ) ..\stylesheet.cls.php:585
14  0.5093  37019272    Style->get_background_position( )   ..\style.cls.php:732
15  0.5093  37019400    explode ( ) ..\style.cls.php:956

and this is the content of the array (which should be a string) that is not 
getting processed properlly:

Array
(
    [0] => 0%
    [x] => 0%
    [1] => 0%
    [y] => 0%
)

Original issue reported on code.google.com by br...@eventespresso.com on 19 Jul 2012 at 10:22

GoogleCodeExporter commented 8 years ago 
This is just a warning so the document should still render, but you'll have to 
disable error display (which is recommended for a production environment). 
However, we would like to address the issue. Can you post the HTML+CSS that 
you're trying to render?

Original comment by eclecticgeek on 20 Jul 2012 at 2:48

GoogleCodeExporter commented 8 years ago 
yes the document still rendered fine.
discovered a way to stop the error. It was being thrown anytime the shortform 
"background" property was used for "background-color". 
ie: background:#fff; would cause the error whereas background-color:#fff; would 
not.
will try to get the full doc for you later today.

Original comment by br...@eventespresso.com on 20 Jul 2012 at 3:14

GoogleCodeExporter commented 8 years ago 
This may be related to issue 101, but we'll know better once you post a sample 
document. I have so far been unable to reproduce the warning.

Original comment by eclecticgeek on 20 Jul 2012 at 6:24

GoogleCodeExporter commented 8 years ago

Original comment by eclecticgeek on 24 May 2013 at 3:00