I would recommend 5.2+ for items on codecanyon.
If you have a smart phone it would be great if you can test my script that I’m working on. You can test it at: http://bit.ly/mobilepro . I just want to make sure it works OK on all sorts of mobile devices.
Let me know if it works OK on your device. If you have any problems or recommendation, let me know.
I will gladly answer your questions Chris .
Ask 1000 times the price of the item. That’s what I always do when I get this question .
Thanks for these great tips.
Friends tend to be more honest than a community of people commenting and “liking” items just for “reputation points”.
I think it’s exactly the opposite. I always use Forrst to get some feedback on my work. You get some very good tips and advice there for how to improve your work.
Go to My Settings > Item licences and there you can enable it .
@kailoon I think it is important that you turn on debug and fix these notices for 3 reasons:
1. Site performance You’re site will run slower when you have a bunch of notices in your code. Even if you don’t show or log them.Below you find a little benchmark result:
- 10k notices, with error_reporting and display_errors enabled : 5,162.76 ms
- same, but with display_errors disabled : 136.18 ms
- same, but with error_reporting disabled too : 117.79 ms
- and, finally, after patching the code so it doesn’t produce any notice anymore : 19.51 ms
2. Cleaner log files If you forget too disable logging for notices or your server logs by default all php errors then you will have massive logs files that take up way to much server space. Also the writing of all these notices to the log file will slow down your website.
3. Security If there is for example a plugin that has turned on dispaly errors for debuggging but the author of that plugin forgot to remove that line in his production code you’ll end up with a bunch of errors that will be shown to the visitor. And these kind of errors is what hackers love to see.