Does it work on multilingual sites?

Thanks for the encouragement @yakos !
Sorry to hear you’re having trouble though.
Please help me understand the problem better.
What site are you using? What plugins are you using?
Do you have the same problem when you don’t select a category?

• This reply was modified 5 years, 7 months ago by Michael Nelson. Reason: Fix typo

Thanks for your response Michael.
The site is https://mnimes.org
There are a number of plugins, which I have always been using for years. All plugins are up to date.
Same problem when I don’t use a category. However we’re talking about a large number of posts here (about 650) and pages (about 125).
If I could describe the problem a little better, when I hit the “Prepare Print-page” button it opens up a page and starts, but never comes back. I left it there for 24 hours and nothing happened.

Still a great idea if I can get it to work… and thank you

Hi @yakos, I took a look at your site and there is a javascript error on the print page, having something to do with Google Recaptcha. I see that’s being run by some contact form 7 plugin code, although I don’t see the contact form on your home page so I don’t know why it’s using Google Recaptcha there.
I coudln’t reproduce the error on my test website (using your theme and contact form 7 with recaptcha enabled), and I see https://deadeasyfamilyhistory.org/print-my-blog/ works fine for your site. So there’s something more going on (maybe some custom code, or another plugin intefering?)

Do you know how you’re loading Google recaptcha on the homepage? Is there a hidden contact form 7? Having the list of plugins active would greatly help in debugging the issue.

Thanks @mnelson4
There is an Integration option in the Contact form 7 forms which contains v3 Google Recaptcha keys
I can try disabling it to see if it makes a difference.
There are at least 30 contact forms all over the site and they are crucial to the sites functionality. In fact I am collecting research data from these forms.
I have 22 active plugins including ContactForm7, Catablog, CM Tooltip Glossary, GA Google Analytics, EG-Series, Google Doc Embed, Grand Flash gallery, Next Gen Gallery, Leaflet Maps, Posts in page etc. Any of these could interfere.
I tried deactivating Contact Form 7 and Google reCAPTCHA but it did not make a difference to Print my Blog.

Ah ok thanks @yakos.
If deactivating contact form 7 didn’t fix it, I suspect there’s another error, because I’m quite confident that particular error was definetely coming from Contact form 7’s code. (Not necessarily to say they’re at fault, I think I’m setting up the print page in a way they wouldn’t have expected.)

Anyway, while I’m trying activating all those plugins to see if I can reproduce the error, I have a change that MIGHT fix the issue for you. I spotted a flaw in my code that could be causing this, and the fix can be downloaded from GitHub: https://github.com/mnelson4/printmyblog/archive/BUG/no-footer.zip (Just download that to your computer, deactivate and delete Print My Blog from your site, then go to “Add New Plugin”, and upload this zip file, and activate it.) It may fix the problem because it allows Javascript to run in the footer of the print-page, an important omission I made (which, surprisingly, you’re the first one to report).

It’s possible that may resolve the current issue, but there may be more afterwards. So even if it doesn’t fix the problem, it would be helpful for me if you could leave that version active for a while.

Thanks for working with me to resolve this issue, I suspect others may have had similar errors.

• This reply was modified 5 years, 7 months ago by Michael Nelson. Reason: corrected link to bugfix version

Oh @mnelson4
Your change fixed the issue.
I can now print categories.

Thank you very much… this is awesome !

Thanks for giving it a go! Great to hear it!
I’ll add that change to the main version of the plugin in case others have similar problems.
Thanks for working through it with me.
You may want to update your review https://www.ads-software.com/support/topic/very-good-plugin-1436/

Spoke to soon @mnelson4 .
I don’t know why, but it printed a couple of categories (small) but finds it difficult to get the larger categories.
Sorry to drag you back into this issue.
The fact that it worked for a couple of prints means no other plugin is interrupting. It’s either a problem with the database its trying to access or the plugin.

Oh darn. There’s probably content on some posts that is causing trouble. Which category isn’t working?

There are several categories not working. I am trying different categories and it seems its gone back to its original problem.
Since that I have deactivated, removed and re-installed, but doesn’t seem to make much difference.
Also the categories that worked before are still working.
Sounds to me there are corrupted tables/content in the blog that it cannot go past.
;-(

Hi @yakos, I see now what the problem is. The error I saw earlier was actually a distraction- while it’s a significant error, it doesn’t actually interfere with this plugin.
The trouble is actually coming from CataBlog- it’s adding a bunch of junk to REST API JSON responses (if that’s a term you aren’t familiar with, no worries- suffice it just to say there’s a technical reason!)
I’ll see if I can fix from my end, or pinpoint the error to report to them…

Ok @yakos I’ve updated the version at https://github.com/mnelson4/printmyblog/archive/BUG/no-footer.zip. Please re-download it and try it again. It should work even with CataBlog active. Please let me know how it goes!

Thanks @mnelson4
Your prompt response in one word is unreal.
I have disabled Catablog and things improved for now. I will download your new version later on today and report back.
Again much appreciated !

Hi @yakos, I’d like to release a new version of the plugin that includes the fixes for your situation. If you can confirm that it works that would be great; but no worries if not. I’m quite satisfied that it’s an improvement and would like to avoid having others encounter the same problem, and so will probably be releasing it in the next few days.

FYI @yakos I’ve incorporated the fixes for the bug you encountered into release 1.6.6. From what I can tell the issue is fixed on your site, but please tell me if you have any further issues (if they’re different, probably on a new issue).