Plugin Author
Baden
(@baden03)
can you share a link to your page?
It might be something simple, however if you are not interested in providing feedback to help solve your issue, you can always downgrade here.
Thanks a lot!! it’s works now!
Plugin Author
Baden
(@baden03)
Glad you got it working. Care to share what the issue was?
I don’t know. The only change I made before it stopped working was update the plugin to the newest version.
The only detail I noticed was, if I uncheck the “Close Print Window after Print” option, then cancel the popup print window (showing nothing to print), the blank window suddenly show the content with some espace character changed to <?> values.
I used Chrome.
Plugin Author
Baden
(@baden03)
alright, well, we can not recreate the issue on our end, so we’ll have to wait until someone else has the issue and we’ll get it resolved then.
In the mean time… I guess just don’t update.
This has just happened to me as well and I will be downgrading. I hate when this happens to plugins.
I am using the print-me target=”#frm_field_83_container, #frm_field_84_container, ” etc with these other plugins and WordPress version 4.5.3.
Active Directory Integration Version 1.1.8
CYAN Backup Version 2.3
Formidable Pro version 2.02.03
Simple Page Ordering Version 2.2.4
I placed print-me target=”#frm_field_83_container, #frm_field_84_container, ” etc within a Formidable Pro HTML element. which worked in the previous version.
Plugin Author
Baden
(@baden03)
right, so to be clear, you are targeting TWO elements. This might be the issue. Does it work if you only target a single element? We dislike this when it happens as well, but we had to make some changes so it would work with IE. We will do some testing with multiple targets and see if we can recreate the issue and get it resolved.
Thank you for the useful feedback. Issue re-opened.
Update: We just did a test using two targets without any issues.
Do you have the same issue with version 1.7.5a available on GitHub?
Baden,
I would like to help but it is during my business day and I have a deadline for this production app. Sorry. Also, I don’t know how to make the zip file from github as I am a novice at wordpress.
You can reproduce my environment by using the Formidable Pro (FP) version free trial(?) or light free version
create a form create some textboxes and dropdowns so you can print-me them.
then add the HTML and add the print-me code there.
fill out the for and print.
(note sure if it matters but the FP HTML segment was in a FP “Section” and my form has a few Section objects.
Hope this helps and thanks for the Plugin; it really works as advertised.
Baden,
I would like to help but it is during my business day and I have a deadline for this production app. Sorry. Also, I don’t know how to make the zip file from github as I am a novice at wordpress.
You can reproduce my environment by using the Formidable Pro (FP) version free trial(?) or light free version
create a form create some textboxes and dropdowns so you can print-me them.
then add the HTML and add the print-me code there.
fill out the for and print.
(note sure if it matters but the FP HTML segment was in a FP “Section” and my form has a few Section objects.
Hope this helps and thanks for the Plugin; it really works as advertised.
Baden,
I would like to help but it is during my business day and I have a deadline for this production app. Sorry. Also, I don’t know how to make the zip file from github as I am a novice at wordpress.
You can reproduce my environment by using the Formidable Pro (FP) version free trial(?) or light free version
create a form create some textboxes and dropdowns so you can print-me them.
then add the HTML and add the print-me code there.
fill out the for and print.
(note sure if it matters but the FP HTML segment was in a FP “Section” and my form has a few Section objects.
Hope this helps and thanks for the Plugin; it really works as advertised.
Plugin Author
Baden
(@baden03)
OK. (x3) Best to stick with the version that works for you for now.
We will do extensive testing and make sure this issue is resolved.
In the meantime we will leave the issue open for anyone else that has the same issue, and can work with us to help trouble shoot how to recreate the problem.
