Latest upgrade to 1.0.2 does not allow inputs to be filled out

Hi Rich,

Thank you for reporting the issue. This fix was initially applied to version 1.0.1

I have tested input (email address field in joining up for epic Colorado magazine) and everything seems to work fine my side. However, let me double on things and get back to you.

On the other hand, all functionality (which includes drag, drop, save-as, text select, right click, plus all specified CTRL key functions works well on my end).

In the meanwhile (while i peek into things), could you please tell me which browser/version you are using? Also, have you tested on another browser?

We will have this sorted in no time,

Cheers

R

Hey – I am using Chrome on Mac. I purged all caches and it is still a problem with chrome, but not with FF…so maybe it is isolated to that browser. Thanks for all the help

Hi Rich,

Okay, could you please tell me which version of Chrome it is that you are using as everything on my side (including Chrome Version 23.0.1271.64 m) seems to work.

Thank you

Same on the Mac Chrome Version 23.0.1271.64

And Safari Version 6.0.2 (8536.26.17)

And Iphone and iPad.

Hi from Switzerland,
Same problem here: all the input fields are frozen. I tried deactivate Contact From 7, delete all files for that plugin on the database, and re-install, but still does not work.

May be of interest to you: it’s not working with Safari Version 6.0.2 (7536.26.17), but with Firefox 17.0.1. you can input the fields, however Sweetcaptcha is frozen, i.e. making it impossible to send

Cheers from snowy Switzerland

Hey RS – I am using Chrome Version 23.0.1271.95

The field is created from Gravity Forms

I’m having this same problem – maybe a bit more observation will be helpful.

When I use the native WordPress login screen, it works fine in all browsers I tried (FF, IE, Chrome, and Safari). But if I add a login plugin/widget (for example “Theme My Login”), the text entry fields for ID and password do not function in Chrome and Safari, but work fine in Firefox and IE.

I’ve observed this same behavior using four different login widgets.

A bit more: FF, IE, and Chrome browsers are the current versions – the Safari version was running on an iPhone.

Hi jrstaatsiii, RadiomanPA, and swisssnowman

We have made a few fixes to the current version of the plugin (one of which prevented user input via search and contact forms as well as one which prevented js drop down menu items from working). Please re-download the plugin and have a go if you will.

If you still have any issues hereafter, feel free to drop me an email (which can be found in the readme file).

Cheers

R

i have installed live chat support clickdesk at devangsolanki.com, “WP Content Copy Protection” plugin don’t allow to input values for livechat.

look in matter.

Hi Devang,

Thank you for the heads up email and letting me know that the issue is solved your side.

jrstaatsiii, RadiomanPA, and swisssnowman : Could you guys please advise so I can mark this thread as resolved.

Thank you

R

Works great for me now – in all four browsers I tried earlier. Good fix!

One difference I noticed, however, is that it now permits me to mark text, implying that copy/paste is possible. Copy/paste doesn’t actually work – but the earlier version did not even allow marking. I think that is a more desirable behavior.

I haven’t yet tried it on content other than text.

Hi Radioman,

Glad to hear the fix is working for you. Yes, we have purposely re-enabled the text select function KNOWING that the user are unable to copy/paste (via mouse and keyboard). This will also give the user a feel of more “control” (essentially lowering a possible bounce rate). However, if you wish to re-disable the respective function, please email me at rcstoltz[at]gmail[dot]com. Furthermore, we have had feedback on image select/copy/paste (mouse/keyboard), and the functionality thereof, and it is working (should work your side). However, if you have any issues, please do report them and we will have it sorted in no time.

Not a major issue for me. Perhaps you could make it selectable as a setting.