Conversation
supportThank you!! Notice: Undefined index: ACI_Routine_Log_JS_Errors in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 152 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: ACI_Routine_Log_Plugin_Change in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 152 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: ACI_Routine_Log_Site_Change in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 152 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 98 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 185 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 98 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 185 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: ACI_Routine_Check_Site_Visibility in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 152 Notice: Undefined index: aci_check_wp_upload_permissions in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 152 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 98 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 185 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: ACI_Log_User_Capability_Change in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 152 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: inspection_method in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 50 Notice: Undefined index: ACI_Routine_Check_Write_Permissions in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 152 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 98 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 185 Notice: Undefined index: site_specific_settings in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/routine_handler.php on line 98 Notice: Undefined index: page in /home/viktor/public_keszul/server/wp-content/plugins/angry-creative-logger/classes/settings.php on line 51 https://wordpress.org/plugins/angry-creative-logger/
Hi! Thank you for notifying us. We do develop with debugging on, it’s just not a guarantee for detecting all issues. In this case, it’s probably a matter of variables that is loaded from the database that was set in our development environment but not when doing a fresh install. We should of course have tested for this as well, but as an open source project without paying customers to finance the development, we apply the release early release often philosophy. So again, thank you for letting us know and expect it to be fixed in our next update. 🙂
Nice to hear this honest voice.
You could open a GitHub repo, and set up travisCI to do it for you. See for example wp-cli how they set up WP in travis.
We do have the tools and processes for developing with CI, although Travis really doesn’t do the trick for us since it only supports Github and we strongly prefer Bitbucket. We use Jenkins in combination with Sauce on Demand by Sauce Labs. It’s really neat stuff if you’re interested in that kind of thing. However, errors like the above are still prone to go undetected when you haven’t foreseen all possible scenarios and/or just haven’t got the resources to anticipate them. As with so many other projects like these, it’s matter of time and money resources rather than tools or know how.
As an update and final comment on this issue; the latest release (v0.5.1) fixes some php warnings/notices, although I suspect some may still show the first time you install and not all variables are defined yet. However, it should be noted that this plugin has yet to be released as version 1.0, ie it’s not yet a full stable release. Consider it more like a public beta and that issues like this is to be expected. This because the code base is still being refactored from release to release, making it futile to write error checks for every variable that is almost certain to be rendered obselete in the next rewrite anyways. Once we’re closing up on a real stable release though, of course it should not be ignored nor left uncared for. With that in mind, I thank you once again for your feedback and mark this topic as resolved.
Hi! Thank you for notifying us. We do develop with debugging on, it’s just not a guarantee for detecting all issues. In this case, it’s probably a matter of variables that is loaded from the database that was set in our development environment but not when doing a fresh install. We should of course have tested for this as well, but as an open source project without paying customers to finance the development, we apply the release early release often philosophy. So again, thank you for letting us know and expect it to be fixed in our next update. 🙂
Nice to hear this honest voice.
You could open a GitHub repo, and set up travisCI to do it for you. See for example wp-cli how they set up WP in travis.
We do have the tools and processes for developing with CI, although Travis really doesn’t do the trick for us since it only supports Github and we strongly prefer Bitbucket. We use Jenkins in combination with Sauce on Demand by Sauce Labs. It’s really neat stuff if you’re interested in that kind of thing. However, errors like the above are still prone to go undetected when you haven’t foreseen all possible scenarios and/or just haven’t got the resources to anticipate them. As with so many other projects like these, it’s matter of time and money resources rather than tools or know how.
As an update and final comment on this issue; the latest release (v0.5.1) fixes some php warnings/notices, although I suspect some may still show the first time you install and not all variables are defined yet. However, it should be noted that this plugin has yet to be released as version 1.0, ie it’s not yet a full stable release. Consider it more like a public beta and that issues like this is to be expected. This because the code base is still being refactored from release to release, making it futile to write error checks for every variable that is almost certain to be rendered obselete in the next rewrite anyways. Once we’re closing up on a real stable release though, of course it should not be ignored nor left uncared for. With that in mind, I thank you once again for your feedback and mark this topic as resolved.