Problem after update to 2.0
-
Hello,
I updated plugin to version 2.0.0.0
Now instead of showing content of page in PDF there is some different content shown?After going back to 1.9.10 everything looks good again:
https://comorga.ch/produktsortiment/handflaschenzug/?pdf=1083Is this a known bug?
PS URL is from rolled back plugin again, because it’s a production site.
Kind regards
RenéThe page I need help with: [log in to see the link]
-
Hi,
we have the same problem and it’s giving us issues with our running ticket shop.
We would be very glad, if this bug can be fixed soon 🙂
Kind regards,
MelinaHello @renescr @melinatusch,
Sorry to heard that, as a quick solution please rollback the plugin to the previous version as renescr did for now.
I’ll need a bit more info to investigate it:
In the new “PDF Templates” tab, did you switched from “Legacy” to “Default” in “PDF Template Sets”? if so, try to switch back to “Legacy”.
Are you overwriting PDF templates in your theme? or are you using the default ones from the plugin?
Are you using any other customization like the any of the plugin shortcodes?
Hello @dinamiko
Thank you very much for your reply!
I’ll need a bit more info to investigate it:
In the new “PDF Templates” tab, did you switched from “Legacy” to “Default” in “PDF Template Sets”? if so, try to switch back to “Legacy”.Yes, before rolling back to 1.9.x I tried changing this setting.
Are you overwriting PDF templates in your theme? or are you using the default ones from the plugin?
I’m overwriting the template. If it will help, I can provide code for this.
Are you using any other customization like the any of the plugin shortcodes?
No.
Kind regards
RenéHello @renescr @melinatusch,
I’ve just released 2.0.1 that fixes an issue with some shortcodes not working properly, if that does not fixes your issue then ensure that “Legacy” is selected in PDF Templates / PDF Template Sets in case you are overwriting PDF templates in your theme.
Select “Legacy” set is mandatory is you were using the plugin before 2.0 together with overwriting templates in the theme, otherwise your customization would be broken.
Non “Legacy” template sets are meant for new users or existing users without PDF template overwrites in theme.Hey,
I’ve got the same problem – the 10 most recent posts are being outputted to the PDF file instead of the post ID that’s being passed in. I’ve tried updating to 2.0.1 and selected the legacy template but the issue is still persisting 🙁 . I’ve rolled back to 1.9.10 which has fixed it.
Hello @alexculshaw,
I’ve created a new release 2.0.2 in the GitHub repository with a fix that hopefully would get rid of the templates problem.
I would really appreciate if you can download the package (dk-pdf.zip) and give it a try to see if the issue is gone before I release it here in the WordPress repository, thanks!
Hello @dinamiko
I have just tested new version (2.0.2) but unfortunately no change on my end ☹️. Also tried to change setting to Default and back to Legacy again. No luck…
Rolled back to 1.9.10 and everything is fine again.
PS it wasn’t necessary to recreate the PDF. Just reloaded the page which showed the wrong PDF and after downgrade PDF show correct again.
Kind regards
René-
This reply was modified 7 months ago by
renescr. Reason: Edit typos
Same issue here. Also with the 2.0.2 version from Github. Instead of converting the current page, it converts the first six pages in the menu order.
@rickonline_nl @renescr @alexculshaw it seems the issue was related to how post content was retrieved in 2.0.
I have just re-uploaded the dk-pdf.zip package into 2.0.2 Github release, I would really appreciate if you can give it a try so we can ensure it works correctly before releasing it, thanks!!
Good morning @dinamiko
I just tested version from Github and this works perfectly. Thank you very much for your great support!
Kind regards
RenéI have just re-uploaded the dk-pdf.zip package into 2.0.2 Github release, I would really appreciate if you can give it a try so we can ensure it works correctly before releasing it, thanks!!
@dinamiko I’ve just tested this and it’s fixed it for me, the correct post is being outputted in the PDF file – thank you 🙂
Yes, the problem seems to be solved now. Thanks!
That sounds great, thank you all for checking!
-
This reply was modified 7 months ago by
The topic ‘Problem after update to 2.0’ is closed to new replies.