Yeah, I would advise people who are making simpler plugins to refrain from using MySQL databases unless they know full well how to protect their plugins from SQL injections. You’d be much safer making use of simple text files which of course have no links to private details stored in password protected mySQL databases.
London – sort of like a Country within the U.K
Expensive city but still an amazing city, plus we’ve got the London 2012 Olympics in a few days, come and enjoy!
Sounds like a good idea. I usually just add a link to more complex stuff like that in my docs. The only other suggestion for sales is to get some help from a designer on improving the look of the app. But that is just my two cents.
Yeah, thanks for the suggestion. I sort of didn’t feel the admin panel would need a really eye catching design as when it comes to updaters I imagined people would rather it worked awesomely like they wanted and hopefully help entice users to buy their products.
Thanks for your reply. Maybe it’s because its my first time uploading anything to codecanyon, but I didn’t think to simplify my documentation for less tech-savvy users.
Okay, rather than just simplifying the documentation and things such as CHMOD in the install process, would I be better served if I created an install.php file that they would simply run, sort of like the wordpress install file and it would walk users through an installation process and attempt to do all the techy stuff for them?
Thanks for that, however I would still like more suggestions for improvement.
I was recently soft-rejected for my AutoUpdater script, and these were the quite valid reasons given for the rejection:
The documentation is sorely lacking.
Most importantly, remember that buyers may not be technically inclined. They may just be looking for an item to drop into their existing code base. Also keep in mind that a typical user won’t really know about all the features your system brings to the table. With them in mind, you should also look into providing a quick start guide of some sort. It need not be long: a short one will do.You can use a premade template or the Documenter tool for your documentation, both linked below: http://themeforest.net/forums/thread/the-documenter/40757?page=1 http://themeforest.s3.amazonaws.com/108_helpFile/Template.zip
I get the message, my documentation is lacking. However, it is unclear what I am expected to do to improve. I was sort of hoping that in the event of a rejection the recommendations would be spelled out – so to speak.
So I felt I should throw it out to you guys, what changes should I make to my documentation? Should I simplify it or should I expand it? I am not too sure what the reviewer expects.
You can read the unaltered documentation here: http://pintdreams.com/autoUPDATER/
One wouldn’t even need to be a hacker. If you’re using license codes to verify a purchase, it could be as simple as someone spreading around a legitimate license code.
Interesting point. Will take note, even though I think already have a solution to that in mind.
That will set development time back by a bit, but I guess its worth it.
Good point, but there is always an exception to every exception.
Nothing on the web is “impossible”
Unless you are a hacker, or we are dealing with a hacker, i.e. criminal offence where I am from… it would be extremely difficult, bordering on impossible, thanks to CHMOD
Would you mind telling me, besides hacking into my server, how you could access these files? I am curious.
P.S. it wouldn’t make any sense to hack into a developer’s server to get files that wont even make up 50% of the actual plugin as they are only files that needed to be updated.
It would make even less sense when the files are not actual updates but instructions to update specific variables.
Thanks for the reply.
Upon searching (by tags) I have seen similar examples of this type of script – which gives me confidence.
Also the script is not limited to envato plugins, it can be used for any plugins or themes you create, even ones that are sold outside of this marketplace.
So hopefully, if all goes well, you could be seeing this on the marketplace soon.
I recently finished developing an auto updater plugin that simplifies the process of updating any plugin or theme or item that is hosted on a server.
I am only now considering the possibility that envato might not allow such a plugin if they have one in the pipeline.
What do you guys think?
It might be helpful to note that the plugin is intended to update specific files and is downloaded automatically from a protected folder on the developer’s server, and those files are then overwritten. In other words, it would be impossible to gain access unless you owned a plugin that was auto updating.
I am also half way through completing a specific variable or code snippet updater for more lightweight precise updating.