2 print popup windows

Same issue for me! Any suggestions?

• This reply was modified 3 years, 8 months ago by wpbot1.

Same issue for me. Can’t work for mobile?
Any Solution for this issue?

Thanks.

@ymow Did already fixed issue? When I check your website, I didn’t see above issue.
Can share solugin with us, please?

Thanks.

Since I didn’t receive an answer, I fixed it without the plugin.

@ymow yes. thanks.
I also updated without plugin.

@ymow and @nangttt
What’s the fix?

@meestorx if you can share a link to the page that exhibits this behaviour we would be happy to assist you. Do you have more than one print trigger on the same page? Which browser(s) does this happen in? Have you tried the 2.0 Release candidate?

Thank you for your reply!
It’s at the bottom of this (long) page:
https://wp.remotely-possible.ca/sla-page

Is there a way to change the button from an icon to a regular button with text?
Where would I find the .zip file for the 2.0 release candidate?

I found the documentation, never mind about the icon question. Still don’t know where to find the 2.0 version download though!

I’d also like to know how to use the shortcode in a Divi button if anyone has done that…

how is the example page related to the issue of: ‘2 print popup windows’?

a way to change the button from an icon to a regular button with text:
how to use the shortcode in a Divi button

https://spacedonkey.de/2400/print-o-matic-external-buttons/

Where would I find the .zip file for the 2.0 release candidate?

https://github.com/baden03/print-o-matic/archive/refs/heads/2.0-redo.zip

• This reply was modified 3 years, 7 months ago by twinpictures.

how is the example page related to the issue of: ‘2 print popup windows’?

Not sure what you mean.

I’ll try the 2.0 version and see if that fixes the 2 popups.

I’m not totally clear on where to put the shortcodes on a Divi button from the information you gave me. Thank you for trying, though!

I wish you the best of luck. Post back on a new thread if you get stuck on something specific.

This is issue is going to be closed for now, as it seems the problem can not be clearly identified, and solution may be try different plugin.

Thank you.

v2.0 fixed the problem!

huzzah!
Here’s hoping your next issue is so easily resolved.
Cheers.