Feature #14518
closedPDF & Print by BestWebSoft
0%
Updated by Boone Gorges almost 3 years ago
- Status changed from New to Staged for Production Release
- Target version set to 1.18.12
Yes, we can give it a try. The item in the FAQ about file_put_contents() suggests to me that the plugin may not in fact be compatible with our hosting environment, but I can't be totally sure of this without putting it into production. It'll be part of the next release, and you can let me know at that point if there are problems.
https://github.com/cuny-academic-commons/cac/commit/15efedaf7b27890dfcc364d59aa726fe2d0b8edc
Updated by Boone Gorges almost 3 years ago
- Status changed from Staged for Production Release to Resolved
Updated by Raffi Khatchadourian almost 3 years ago
Seeing this message after activation:
Warning: Not enough permissions for the folder /var/www/html/commons/www/wp-content/plugins/pdf-print/mpdf/ttfontdata.
Please check and change permissions for your plugins folder (for folders - 755, for files - 644). For more info, please see Changing File Permissions and FAQ.
Updated by Boone Gorges almost 3 years ago
- Status changed from Resolved to Assigned
- Target version changed from 1.18.12 to 1.18.13
Thanks. This is exactly the sort of message I expected to see. This is a sign that the plugin does not adhere to best practices surrounding file-system access for WP plugins. As a matter of security policy, we don't modify directory permissions to allow this kind of write access. As such, I'm afraid we'll be unable to use this plugin. I'll remove it in the next release.
Updated by Raffi Khatchadourian almost 3 years ago
Also receiving this error on https://khatchad.commons.gc.cuny.edu/teaching/csci-40500-77100-software-engineering-sp-21/?print=pdf:
There has been a critical error on this website.
Learn more about debugging in WordPress.
Updated by Raffi Khatchadourian almost 3 years ago
Boone Gorges wrote:
Thanks. This is exactly the sort of message I expected to see. This is a sign that the plugin does not adhere to best practices surrounding file-system access for WP plugins. As a matter of security policy, we don't modify directory permissions to allow this kind of write access. As such, I'm afraid we'll be unable to use this plugin. I'll remove it in the next release.
Sounds good, Boone. Thanks for trying!
Updated by Boone Gorges almost 3 years ago
- Status changed from Assigned to Staged for Production Release
Updated by Boone Gorges almost 3 years ago
- Status changed from Staged for Production Release to Resolved