Hi @ninjateam, hi Tommy,
thank you for your reply. Unfortunately this was an expression of opinion, not a support question. I am sorry, if this seems rude, but I thought if you are going to sell premium / pro plugins, you might want to be informed.
If I use your plugin for a client – and this will mean PRO is unavoidable – I need it to be trustable. I do not have time to check the whole thing for security wholes. Basic SQL-errors give me an headache (this is even just MySQL). This may be neurotic, sorry, but wordpress allows badly written plugins.
To answer your questions:
- No, this has not been not the currently latest version (2.3). I had installed it before the upgrade. However, this seems like an error, you should find and fix before publication, so I went for a different solution.
- PHP-error-messages seem to be quite sufficient to understand the cause of the error. I have not reviewed the code however. So I am not going to install the plugin you recommended, because I can read php-error-logs.
I appreciate, that you put the effort into providing the free part of your plugin. However, for providing professional services, I need a certain standard of coding. Debug.log should not be filled with hundreds of error messages for a every-day-task / the main functionality of a plugin.
Thank you for your time and effort. I hope your last update did solve the problems. By the way, sorry for my English – I am not a native.
Philip from @phylogram
-
This reply was modified 5 years, 4 months ago by phylogram.
-
This reply was modified 5 years, 4 months ago by phylogram.