pdf export not working

Just released IPM 1.4.0. It’s already updated in your WP.

Lots of problems are fixed + I added some logic in content parsing process to avoid incompatibilities with other content generator plugins and shortcodes. I can say that 50% of problems were very specific, those reasons were “Image Lezy Load”, “Child Pages Shortcode” and “BulletProof Security” plugins.

1) Fixed:

FPDF error: Missing or incorrect image file: https://12bytes|dot|org/wp-content/uploads/bs-tunnel-150×150.gif

2) Fixed:
BPS incompatibility. I’ve added a new image parsing logic, PHP ‘allow_url_fopen’ setting doesn’t affect it.

3) There is not such an issue:

and lastly the print function creates a file that seems to include none of the page content, but rather all of the main menu and sidebar items

4) Fixed:

from the page below the pdf export did work, but the featured image was duplicated in the file: https://12bytes|dot|org/products/xotic-pc

5) Fixed:

text export and docx both result in a 404 on each page i tested

6) Fixed:

for pdf export of page https://12bytes|dot|org/products`, that image (bs-tunnel-150×150.gif) is on a totally different page and is not found at all in the source of the ‘products’ page

BPS incompatibility. I’ve added a new image parsing logic, PHP ‘allow_url_fopen’ setting doesn’t affect it.

hmm no wonder it would not work on any of my Development or Production sites. All of my sites use php.ini files with allow_url_fopen = Off since this is very common attack vector that hackers like to exploit and is a basic/general security measure that is implemented on all my websites as a standard. I assume most other folks who are savvy would also have the allow_url_fopen directive set to off.

I didn’t mean that UPM turning that on or off. I mean that UPM finds way to do his job if allow_url_fopen = Off without setting it On.

hmm no wonder it would not work on any of my Development or Production sites. All of my sites use php.ini files with allow_url_fopen = Off since this is very common attack vector that hackers like to exploit and is a basic/general security measure that is implemented on all my websites as a standard. I assume most other folks who are savvy would also have the allow_url_fopen directive set to off

I hope you see that UPM doesn’t affect any secure things and it doesn’t change any PHP Settings.

Here is the complete description:
If allow_url_fopen = Off UPM can’t open images with absolute source URL like this:

https://example.com/images/pic.png

so it returns error.

Now if UPM finds absolute source URLs, it changes those to relative like this:

../images/pic.png

That’s it.
This kind of image source URLs are secured by allow_url_fopen = Off setting and are usable by UPM.

hi AIT – thanks for chiming in – i’ve been trying to figure out how to disable that on my shared site, but i may not be able to in my case

Tom – thanks – i’m guessing it’s been a very busy jam session for you ??

minor issue i noticed…

for pdf export, the following is not placed at the end of the last page…

This page was exported from - 12Bytes.org
Export date: Sat Nov 29 23:01:53 2014 / +0000 GMT

in the case of this page it is placed before the last paragraph:
https://12bytes.org/products

which brings me to my next question for which i didn’t find an answer in the available documentation i saw … how does one disable the plugin on a per-page basis? is there a shortcode i can use, or must i do it through post/page categories?

Regarding to the header information, it only placed on top of all pages, the last page has such an info on the top as well. If I add it at the end it’ll be duplication.

how does one disable the plugin on a per-page basis? is there a shortcode i can use, or must i do it through post/page categories?

It only allows to disable save buttons on all posts or on all pages. However I’m going to add a new option on Edit Posts/Page screen to turn it on/off per page. I’ll update it today or maximum tomorrow.

I hope you see that UPM doesn’t affect any secure things and it doesn’t change any PHP Settings.

Yes, I understand that. I was only stating that I use allow_url_fopen = Off as a general security standard setting on any/all websites/servers in a php.ini file. I assume that most other folks who understand website security would also do the same thing.