When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I can't understand why things like troubleshooting or testing is done in a "production" environment.
Because sometimes it is necessary, such as the reason for the Edit being shown upon any edit, to make such a change. I said "troubleshoot" for the explanation because we were investigating an issue that is only possible on a live forum where the problem exists.
Originally Posted by c4cruiser
If there is a problem, then there should be a test environment that is used only for things like that. Once a fix or an improvement is ready, it can be moved to the production side.
There is a test environment and has been for a long time (years). But that doesn't mean everything will be perfect. Look at companies like Apple to see beta and production doesn't always guarantee no issues to the end user.
As a hoster and admin of a ton of vbulletin sites I have to defend them here for not having a "test" environment since you cant test a vbulletin site for anything more than "does the change completely crash the site and make it not load anymore" or "does it make it look bad instantly after a change".
Other than obvious scenarios like I listed above you will never find how a change effects a site without letting it "loose" in a production environment.
There is just no way to know how a change will show up with so many different browsers out there not to mention having enough people to try every possible way of using the site.
Last edited by crowz; Nov 7, 2015 at 04:53 PM.
Reason: spelling errors :)
But as I said above, we do have a "test" environment and have for years and there is a process used to test and pass or reject code changes. Of course there is way more variables out in production that may not be seen in a "test" environment.
But, again, this change to the Edit system was made to track down an issue that can only be done on a live forum. Such a change would have done nothing for us on a "test" environment.
Originally Posted by crowz
As a hoster and admin of a ton of vbulletin sites I have to defend them here for not having a "test" environment since you cant test a vbulletin site for anything more than "does the change completely crash the site and make it not load anymore" or "does it make it look bad instantly after a change".
Other than obvious scenarios like I listed above you will never find how a change effects a site without letting it "loose" in a production environment.
There is just no way to know how a change will show up with so many different browsers out there not to mention having enough people to try every possible way of using the site.