Latest Update (1.9.9) Broke Functionality

Hi,

Thank you for contacting us!

It seems like the necessary fonts are missing in MPDF library folder. You should download them manually:

1) Go to https://github.com/lynxbee/mpdf;
2) Click on “Clone or download” and “Download ZIP”;
3) When archive will be downloaded, you should extract “mpdf-master.zip” file, rename the folder with MPDF library to MPDF_6_0 and create archive with “MPDF_6_0.zip” name;
4) Using FTP client (https://codex.www.ads-software.com/FTP_Clients) upload “MPDF_6_0.zip” archive to [wp_root]/wp_content/uploads;
5) Go to the plugin settings page and click “Load Fonts”.

Please let us know if you have any additional questions.

Ok, will do but a couple of questions:

1. There is already a /pdf-print-fonts/ in the uploads directory, does this not contain the fonts needed?
2. Why doesn’t the plugin properly load the files and need the manual operation? Is the package needed not embedded in the setup?

Thanks.

Here’s an update. I did as you suggested and it said Additional fonts were loaded successfully. and the file then disappears from the upload folder, so it seems to have processed it, however the error persists:

Warning: A non-numeric value encountered in /content/plugins/pdf-print/mpdf/mpdf.php on line 30650
Warning: A non-numeric value encountered in /content/plugins/pdf-print/mpdf/mpdf.php on line 30650
Warning: A non-numeric value encountered in /content/plugins/pdf-print/mpdf/mpdf.php on line 30650
Warning: A non-numeric value encountered in /content/plugins/pdf-print/mpdf/mpdf.php on line 30650
Warning: A non-numeric value encountered in /content/plugins/pdf-print/mpdf/mpdf.php on line 30650
Warning: A non-numeric value encountered in /content/plugins/pdf-print/mpdf/mpdf.php on line 30650
Warning: A non-numeric value encountered in /content/plugins/pdf-print/mpdf/mpdf.php on line 30650
Warning: Cannot modify header information - headers already sent by (output started at /content/plugins/pdf-print/mpdf/mpdf.php:30650) in /content/plugins/pdf-print/mpdf/mpdf.php on line 9420
Fatal error: Uncaught MpdfException: Some data has already been output to browser, can't send PDF file in /content/plugins/pdf-print/mpdf/mpdf.php:9422 Stack trace: #0 /content/plugins/pdf-print/pdf-print.php(1030): mPDF->Output('', 'D') #1 /wp-includes/class-wp-hook.php(286): pdfprnt_print(Object(WP)) #2 /wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #3 /wp-includes/plugin.php(515): WP_Hook->do_action(Array) #4 /wp-includes/class-wp.php(726): do_action_ref_array('wp', Array) #5 /wp-includes/functions.php(960): WP->main('') #6 /wp-blog-header.php(16): wp() #7 /index.php(17): require('') #8 {main} thrown in /content/plugins/pdf-print/mpdf/mpdf.php on line 9422

So what do we do next? It seems to be having bad values and throwing an error in the library file. Please advise.

Hi,

Unfortunately, we cannot reproduce this problem on our local environment. Please provide the access credentials to your WordPress admin dashboard (with Administrator’s permissions) and the FTP credentials (host, username, and password), in order to detect the reason and find the solution.

During making tests we’ll probably deactivate some of your plugins or switch the theme. That’s why before giving the access, we recommend you to make a full backup of your site.

Since this data is confidential, maybe, it would be better if you create a private ticket on our support forum (https://support.bestwebsoft.com/hc/en-us/requests/new). Please include a link to this post, so that we could recall the case immediately.

I don’t feel comfortable providing all that access, private or otherwise. The errors are pretty explicit as to what is happening (or not happening) and should be more than sufficient to audit the code to see what might be causing it. Even if it works in your dev environment which doesn’t reflect all the real world installations of the plugins, it doesn’t preclude an issue that you didn’t consider on your end.

I now have to look for an alternative, there was too many restrictions and push for premium anyway, this might be the final straw we needed to find another solution. Thanks.

Hi,

If you cannot provide access to your live site, maybe you can setup a development environment (dev website) on the same server without using the commercially sensitive data, so we can reproduce the described issue.

I am sorry but the amount of effort to debug a plugin that should just work is not something I am willing to invest my time, energy and resources in.

This has always been more problem than it is worth and it is bloated for what it needs to do and the limitations to push for premium has always been a bit excessive and petty.

So I just need to find a more stable, streamlined and lightweight solution that doesn’t break so easily and require this much effort to be resolved. If you ever do figure it out, be sure to let me know; because I suspect this is something you guys are failing to catch because you are not looking for it or testing it right, so it will come up again I am sure.

A place to start might be what you did in the last few updates that didn’t break in your dev environment but maybe looks to narrowly which ignores other systems where it can break it, since it was working before the last two updates. Nothing changed on our end, just yours.

Thanks.

Hi,

Unfortunately, we are not able to reproduce this issue on our local machines. We need accesses to your website (or dev website) to detect the issue and find the solution.

I understand, I already went ahead and replaced with a very lightweight, fast and stable solution that is very efficiently designed and unrestricted.

I guess I needed the push, since switching solutions is not something fun and having used something for a while that works, you tend to let it go; but this was too much effort to spend the time and no upshot. Specially that you don’t see a problem on your end that on our end is tied directly to your last update. So either your installation is more forgiving or much more narrowly configured.

Either way thank you but I don’t have the time or energy to debug this or spend more time on it. But do me a favor and when you find out (which you will I am sure of it) what broke, please be kind enough to post it here so I get notified, so at least I know; assuming you acknowledge it publicly of course. Take care.

Hello,

I would like to say that the error is there on php >= 7.1.
Going back to php 7.0 resolved the issue for me.

@bestwebsoft could you confirm you can reproduce the issue or tell which php version you are testing with ?

Regards,

• This reply was modified 6 years, 7 months ago by Gil-.

@gil-2 to provide information to help you narrow down your findings, my PHP version is 7.2.3 – good luck.

Moved this post here.

• This reply was modified 6 years, 3 months ago by Muxelmann.
• This reply was modified 6 years, 3 months ago by Muxelmann.
• This reply was modified 6 years, 3 months ago by Muxelmann.