Stealing code from live preview

I’m a new user here, so allow me a simple question.

How can we be sure people won’t copy our code from the live preview? It’s ok to present screenshots, but with the live preview people can just see our code and copy it… Is there a way to prevent code stealing? Am I being too concerned about it (people are educated enough not to do it)? As far as you know, did it happened already?

Thank you

Cuca

can make it pretty much challenging for the ripper to steal with HTML protector

You can make it harder, but you cannot prevent code stealing. Don’t lose your sleep over it.

It is sad that I received an email from a user here. He ask me to giveaway some site templates here for free, because he want to try out. I reject. then he said “never mind, I can copy the code and make one”....

I don’t think we can 100% prevent this, am I right?

Unfortunately not. If people want it bad enough, they can get it. I wouldn’t worry about it too much. It’s a very small percentage.

Unfortunately there is no way to stop this. There are ways to make it harder but then you are spending much more time trying to prevent theft when the people who really want to steal it are still going to.

In addition, some people like to see how your work has been coded. I don’t like buying things unless I see the code first. But if someone uses theft prevention methods that essentially scrambles the code, I won’t buy it unless I really really want it.

Some authors don’t like providing a live preview as to keep people from stealing their work but in the end, the live preview generates more sales than you lose by theft.

If you would still like to try some form of prevention, try these for starters.

http://www.google.com.au/search?q=html%20obfuscator http://www.google.com.au/search?q=css%20obfuscator

I personally have custom 404 and 403 error pages setup on my hosting server because people that use programs to rip sites will generate tons of errors. As soon as I see a flood coming in from a user agent that isn’t a search engine, I block the IP for at least 24 hours. You should also keep your directories protected, etc.

Hope this helps!

Unfortunately there is no way to stop this. There are ways to make it harder but then you are spending much more time trying to prevent theft when the people who really want to steal it are still going to.

In addition, some people like to see how your work has been coded. I don’t like buying things unless I see the code first. But if someone uses theft prevention methods that essentially scrambles the code, I won’t buy it unless I really really want it.

Some authors don’t like providing a live preview as to keep people from stealing their work but in the end, the live preview generates more sales than you lose by theft.

If you would still like to try some form of prevention, try these for starters.

http://www.google.com.au/search?q=html%20obfuscator http://www.google.com.au/search?q=css%20obfuscator

I personally have custom 404 and 403 error pages setup on my hosting server because people that use programs to rip sites will generate tons of errors. As soon as I see a flood coming in from a user agent that isn’t a search engine, I block the IP for at least 24 hours. You should also keep your directories protected, etc.

Hope this helps!

Care to write a tutorial for that ? seems like it would be an incredibly helpful article for the TF blog.

Unfortunately there is no way to stop this. There are ways to make it harder but then you are spending much more time trying to prevent theft when the people who really want to steal it are still going to.

In addition, some people like to see how your work has been coded. I don’t like buying things unless I see the code first. But if someone uses theft prevention methods that essentially scrambles the code, I won’t buy it unless I really really want it.

Some authors don’t like providing a live preview as to keep people from stealing their work but in the end, the live preview generates more sales than you lose by theft.

If you would still like to try some form of prevention, try these for starters.

http://www.google.com.au/search?q=html%20obfuscator http://www.google.com.au/search?q=css%20obfuscator

I personally have custom 404 and 403 error pages setup on my hosting server because people that use programs to rip sites will generate tons of errors. As soon as I see a flood coming in from a user agent that isn’t a search engine, I block the IP for at least 24 hours. You should also keep your directories protected, etc.

Hope this helps!

Care to write a tutorial for that ? seems like it would be an incredibly helpful article for the TF blog.

I Would Love If you do that! In fact I too was wondering about that!

Sure, I’d love to do that. I probably won’t get to it until Monday though.

It’s simple. If you make great templates people will buy it. Yes, somebody can steal code, but the most will buy it. Just do a good work.