• Hi,

    special characters (like “/”) in page titles could lead to failures while writing cache-files and result in empty pages.

    A possible workaround is to replace all “get_the_title()” calls with “sanitize_title(get_the_title())” in “wp-pdf-templates.php”.

    Would be great if you could fix it in the next versions.

    Thanks & best regards,
    Marcus

    https://www.ads-software.com/plugins/wp-pdf-templates/

Viewing 1 replies (of 1 total)
  • Colin

    (@colinsafranek)

    +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.

Viewing 1 replies (of 1 total)
  • The topic ‘missing filename sanitization could lead to blank pages’ is closed to new replies.