Colin

Is there a reason no one has answered this question?

Looks like support is active. Why no love?

Is anyone supporting this plugin anymore?

It’s getting buggier and buggier. Please help us!

I am having a similar problem. In chrome, when navigating to the /pdf or /?pdf endpoint, the browser’s PDF viewer loads but the following error displays: “Failed to load PDF document”.

Please help! This is a very important feature for my website.

It would be tremendously appreciated! Let me know if there is anything I can do to help make that happen.

Do you have roadmap page anywhere for the plugin so I can keep an eye out?

Cheers!

– Colin

Thank you.

Can you point me to a comprehensive list of similar helper classes? That would be extremely helpful.

Cheers!

Ah, that was the issue. I was testing on a development site (using WP Engine’s hosting platform), which was password protected.

Thank you!

+1 on this!

Please make this part of core!

Also, could you please update the defined path for the Font Directory and Font Cache?

Currently the following are defined in wp-pdf-templates.php:

/**
 * Redefine font directories
 */
if (!defined('DOMPDF_FONT_DIR'))
  define('DOMPDF_FONT_DIR', $upload_dir['basedir'] . '/dompdf-fonts/');

if (!defined('DOMPDF_FONT_CACHE'))
  define('DOMPDF_FONT_CACHE', $upload_dir['basedir'] . '/dompdf-fonts/');

Which results in the following path when DOMpdf runs the request for the dompdf_font_family_cache.php file:

/wp-content/uploads/dompdf-fonts//dompdf_font_family_cache.php

Notice the extra forward slash before the desired file. If updated to the following:

/**
 * Redefine font directories
 */
if (!defined('DOMPDF_FONT_DIR'))
  define('DOMPDF_FONT_DIR', $upload_dir['basedir'] . '/dompdf-fonts');

if (!defined('DOMPDF_FONT_CACHE'))
  define('DOMPDF_FONT_CACHE', $upload_dir['basedir'] . '/dompdf-fonts');

Taking out the trailing slash on the dompdf-fonts directory corrects the issue.

Please include this in the next version as well.

Thank you.

Same for me. Can the developers please clean this up? My concern is also that it will effect other functionality.

Thank you!

@spraveenitpro

Can you please give us an idea of when this fix will be available?

@bigger

This can be accomplished by using the User Switching plugin: https://www.ads-software.com/plugins/user-switching/

@spraveenitpro

Can you please give us an idea of when this fix will be available? It’s been 5 months since WooCommerce 2.6 was released. We are already at version 2.6.6. In internet software time, that’s ages! I don’t think it’s wise to continue using pre 2.6 WC anymore.

Please give us an update.

Thanks.

@spraveenitpro Hi Praveen,

I see that version 3.0.3 has already been released, but when I test this new version with the latest WooCommerce the saved card info disappears still.

If I use the workaround that @mrfrent37 mentioned above, I can restore a user’s saved card info (log in as a registered customer, and then initiate a checkout process, then go back to the saved cards section, and the info is there). But this is not a practical solution because I can’t feasibly do this for all my registered customers one-by-one. So unless there is a way to do this sort of reset for all my users at once… will you have a fix for this any time soon? Was the fix supposed to be shipped in 3.0.3?

Please help.

Thanks.

Hi again Antti,

would you be available for paid work? I have followed your instructions for optimizing the PDF template generation speeds, but some of my longer templates which include queries for up to 31 posts can take as long as 60 to 90 seconds to render. Many of my customers assume that the PDF export feature is just broken and leave before the file fully renders.

The issue I have, as stated above, is that the PDF content is protected by membership software, so I have to check that the user meets certain criteria before allowing the file to be rendered for each user. I have not been able to figure out how to do this for cached PDF files. If I could cache the files then the render/download speeds would be almost instantaneous.

Are you available for hire? I really need a solution for this. Would you be able to recommend someone that is also familiar with DOM PDF?

Please let me know. Thank you!

@esmi, I don’t follow. This is my issue. Same plugin conflict. What am I missing?

Hi, I am having the same issue. Cannot assign a ticket to any of my support staff because they do not show up in the search/select field. There is an error in the console: select2.min.js?ver=3.5.2:21 Uncaught Error: Option ‘ajax’ is not allowed for Select2 when attached to a <select> element.

This is related to ACFPro, but I absolutely cannot disable ACF because many of my templates rely on it heavily. My site would basically be non functional without it.

Has there been any fix/solution found for this?

Thank you!

@spraveenitpro Any updates on this issue?

ETA on the next version release?

Much appreciated.