The WP Content Copy Protection plugin uses multiple techniques in copy-protecting your blog content.
No! This plugin will only affect the user's browser (attempting to copy your content) and will have NO negative impact on your SEO.
The plugin will disable the given features for everyone (including site administration) at this stage. However, we are looking to disable this in our update.
Simply move your mouse pointer into your browser's URL (address) bar and then execute CTRL + F5 for a hard refresh. This function will (like all other content protection measures through the plugin), remain UN-executable in the current window, however, trigger from the URL/address bar. This was tested on all major browsers (latest versions).
Absolutely not! Although this plugin locks your content and prevents it from being copied by anyone else, your advertising blocks will remain UN-touched and UN-affected. These blocks will function without any trouble, and will work with Adsense, Chitika, as well as most other advertising programs.
This function was removed mainly due to the fact that it could scare away your website visitors - cause a higher bounce rate - and essentially defame your website.
This plugin works on all major browsers. The full functionality (features) of this plugin was tested on the latest versions of IE (Internet Explorer), Mozilla FF, and Chrome without any problems.
When uploading an image to your blog post - simply select the 'none' option just below your link URL (in the image uploading window). This will disable the LEFT click function on the image. The plugin will take care of the rest!
Once again, navigate to Line: 35 in the fwpconsec.php file and change it there. The current color code is: #FFF000 (Yellow). You can also change your font and font size here.
The text selection function was re-enabled simply to give users more "freedom" (knowing that even with text selection - they are still unable to actually copy any selected text). This way, the users are also LESS aware of the actual protection running in the backend (in hope of decreasing bounce rate).
Requires: 2.0 or higher
Compatible up to: 3.4.2
Last Updated: 2013-4-11
3 of 5 support threads in the last two months have been resolved.
Got something to say? Need help?