Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No rendering when adding H1-tag #137

Closed
PhenX opened this issue Dec 6, 2012 · 8 comments
Closed

No rendering when adding H1-tag #137

PhenX opened this issue Dec 6, 2012 · 8 comments

Comments

@PhenX
Copy link
Member

PhenX commented Dec 6, 2012

Original author: luttk...@gmail.com (March 08, 2010 19:12:07)

What steps will reproduce the problem?

  1. Run the attached file with dompdf 0.6.0. The rendering should not work.
  2. Remove the line indicated in file lagenhet.htm
  3. Now the rendering works

What is the expected output? What do you see instead?
A rendered PDF that looks like the lagenhet.htm, now nothing happens.

What version of the product are you using? On what operating system?
dompdf 0.6.0, MAMP

Original issue: http://code.google.com/p/dompdf/issues/detail?id=131

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From fabien.menager on March 08, 2010 19:50:56
Did you try to remove only the H1 tag and let the comment where it is ? ;)
The problem is that you use a bad syntax for the comment : this should be

<!-- My comment -->

and not

<!-- My comment --!>

So the rest of the file is being commented and nothing is rendered. A good syntax
coloring editor would have helped you see that everything was commented.

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From luttk...@gmail.com on March 08, 2010 19:59:32
Ah...You're right. But that's not the issue, I had the same problem before I added
the comment.

Does it work for you when removing the comment and leaving the H1-tag?

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From luttk...@gmail.com on March 08, 2010 20:02:12
PS: I'm using TextWrangler to color my code, but it didn't detect it :(

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From fabien.menager on March 08, 2010 20:10:09
Yes it works perfectly, I'm joining the resulting PDF.

PS: I suggest you to change your editor :)

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From luttk...@gmail.com on March 08, 2010 20:24:47
That is strange. Is there any way to receive an error msg so I know where something
goes wrong?

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From fabien.menager on March 08, 2010 20:35:11
You can set the global variable $_dompdf_show_warnings to true and you'll see all
the warnings generated by DomPDF. Its declaration is in dompdf_config.inc.php with
other debug variables.

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From luttk...@gmail.com on March 08, 2010 21:05:35
That didn't show anything. I tried to turn on the debug-mode, and it says that "the
entire tree is dumped to stdout in dompdf.cls.php." I'm not sure how to access this
tree of information. I've attached my php-file.

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From eclecticgeek on March 09, 2010 18:59:49
I don't see anything so far that would indicate a bug.

If turning on debug-mode doesn't show anything then DOMPDF probably isn't loading
your document at all. Since you're also not seeing errors PHP may not be set up to
show errors to the browser. Check your PHP error.log or add the following code to the
top of your PHP file:

ini_set('display_errors', 1);

@PhenX PhenX closed this as completed Dec 6, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant