Aaahhhhhhh… die lah!.. die lah!..
blog, wordpress April 11th, 2008So many talks about upgrading to WordPress 2.5 experienced flying around the net. I had a ‘tense’ experience when I upgraded my snapshots yesterday.
I started around 6.00pm by trying to rename the folder containing the website contents. But it gave me error! I tried a few more times but it still gave me the same result.
I was planning like this… once I renamed the website folder, I will upload the new version to the right folder. But that was hampered by the error encountered every time I tried to rename the folder.
I called Ben, to ask him if he had upgraded his website. He had but did encounter a problem. But it’s not the same as mine!!!
At the end, I took the drastic step… I dropped a BOMB by DELETING the folder’s contents! If you are not sure what I mean, I was actually deleting the website’s contents! During the deleting process then only I found out there are two folders giving error. I believe these are the causes I can’t rename the master folder.
I keep trying to delete the two folders but it just don’t allow me to do it… the error message said I have no rights to the folders!
Then I said ‘what the heck!’… I just uploaded the new version and paste whatever necessary files into the folder. After uploading, I tried accessing the updated website. Damm… it asking me for password to access the site!!! I keep cancelling the password message… and the upgraded site appears. Shoottt… this is the results of the upgrade!!!
Aaahhhhhhh… die lah!.. die lah!.. At the end, I send a 24×7 ticket to my host asking them to delete the two folders. After one hour around 10pm, when I tried accessing the website again, woohoooooo… it’s working… it’s OK!!!
I check my email… got reply from the host. They said it seems the two folders are just floating there… so they just restarted all the services to my website and the two folders gone after that.
OK lah… that was my scary experience yesterday.
April 11th, 2008 at 11:47 pm
SO the lesson here seems to be: if something’s not right and you can’t solve it yourself, lodge a report with the webhost and stamp it ultra-urgent. My worst experience was last month when my server was topsy-turvy for about 2 days, after running fine for almost 3 years.
Lucky mine did not drag that long 😀
April 28th, 2016 at 9:05 am
Fidnnig this post solves a problem for me. Thanks!