![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I should just go home
May. 22nd, 2002 12:20 pmAnd after yesterday's post things went rapidly downhill. Having sorted outthe major problem without the client or customers noticing I promptly broke the site in about the biggest way I could. It was allowing customers to place orders as far as taking credit card details. It then told them there was an error and marked the order as awaiting payment. Payment couldn't be given even if they wanted to because they had already paid. Oh, and the order didn't get sent to our backend so there was never going to be any way to fix it.
The reason this happened? I forgot to copy a stored procedure up tot he live database so the page trying to access it errored. The irony of it was that the new code was designed to send an alert if orders got placed on the website but didn't get through to the backend system. Fixed after 30 minutes and another hour to fix the fallout (getting these orders properly placed and so on).
Then this morning, to try to fix some of the above problems that are caused by an unnecessary (and undesired) transaction we made some changes on the staging server to try to de-transaction it. It didn't work. After ten minutes of poking I was told that the live site was breaking in the same way as yesterday again. Odd I think and glance at the code. It was the work of just a few minutes to work out that i had been making changes to a live server and not the staging one which is why it all went horribly wrong.
People at work were quite supportive but I feel a complete idiot at the moment. I want to go curl up in a corner somewhere and ignore work for the rest of the day, not least of all because I am now afraid that every time I touch something I might fuck up the live site. :(
Oh well, gotta keep going really unless I claim illness and go home (I have had a headache for more than 24 hours now, ache quite a lot and am not thinking straight) but that isn't really an option since there is loads of work to do and unless I actually think I am going to hit negative productivity I should keep going. :)
The reason this happened? I forgot to copy a stored procedure up tot he live database so the page trying to access it errored. The irony of it was that the new code was designed to send an alert if orders got placed on the website but didn't get through to the backend system. Fixed after 30 minutes and another hour to fix the fallout (getting these orders properly placed and so on).
Then this morning, to try to fix some of the above problems that are caused by an unnecessary (and undesired) transaction we made some changes on the staging server to try to de-transaction it. It didn't work. After ten minutes of poking I was told that the live site was breaking in the same way as yesterday again. Odd I think and glance at the code. It was the work of just a few minutes to work out that i had been making changes to a live server and not the staging one which is why it all went horribly wrong.
People at work were quite supportive but I feel a complete idiot at the moment. I want to go curl up in a corner somewhere and ignore work for the rest of the day, not least of all because I am now afraid that every time I touch something I might fuck up the live site. :(
Oh well, gotta keep going really unless I claim illness and go home (I have had a headache for more than 24 hours now, ache quite a lot and am not thinking straight) but that isn't really an option since there is loads of work to do and unless I actually think I am going to hit negative productivity I should keep going. :)