Parse error unexpected T-STRING wp.dompfd.config.php

Hey @snoadweb,

Based on the error, it seems like the file has been corrupted at some point. My first recommendation is to remove that file completely, then deactivate the plugin and reactivate it. This should force the file to be regenerated, which should resolve any would-be syntax errors. If that does not solve it, we will move on to other options.

Let me know if that resolves it,
Loushou

I reactivated the openticktes-plugin, downloaded the plugin and installed it. the former error no longer occurs, I can download the tickets. but, at this moment i can’t open the PDF-file after downloading it; file-format probem

maybe the link helps…..

Hey @snoadweb,

Thanks for the link, because it does indeed help me see the problem. It seems that DOMPDF (the pdf library we are using) is having a problem interpreting Windows paths. I am going to take a closer look today and see if I can narrow down the problem, and write a patch for it. I will keep you posted about this throughout the day.

Loushou

Hey @snoadweb,

It seems my first thought was wrong, it was not a Windows path problem; however, there was a problem with it parsing ‘local file’ paths. It seems you have an older version of PHP (less than 5.3.3), which does two things that newer versions do not. First, it throws a warning when a url was failed to be parsed (which is corrupting your pdf files). Secondly, it does not properly parse ‘file://’ protocols, and only allows for ‘file:///’ (notice the third slash).

I made a patch for this inside the DOMPDF library, which will be in the next release. The patch does tow things. First, it suppresses all errors and warning produced by this parse_url call, so even if there are any warnings to report, none will be reported, and thus will not corrupt your PDFs. Second, I wrote a pre-parser for the urls, which converts the file:// urls to file:/// urls, so that they will be properly parsed. These two changes will prevent the PDF corruption you are experiencing, and hopefully that of others who have had a similar issue.

Loushou

Hey @snoadweb,

There was also one final issue that could have been causing this issue, which I released last week. This should resolve all the PDF issues. If not feel free to reach back out to us and we will go through another iteration.

Loushou