A Day without Wordpress
(No Ratings Yet)
Loading ...
Sometimes the most unfortunate of the events fall upon at the most ill deserved of the times. Frustrated with the waiting, I set out on a maiden voyage to brush up my skills as an Electronics Engineer and pick up quite a few new things along the way. Except for the fact that I had to wait at Kerala Electronics, Trichur for almost a full hour to buy the components during which time, I heard enough of the old Trichur slang, the purchase was fruitful. I even got to spend some quality time over a juice of fresh pineapple with an old, close friend of mine.
When I returned, I immediately started work upon the project, which was a complete success. An unprecedented first time result for me. As I was ready to vent out the day in a blog post, disaster strikes. I decided on changing the blog’s current theme to Azeem Azeez’s Brilliant and clean White as Milk. As I was editing the header file from the new theme, I accidently erased a huge part of the file and clicked on update. I know it is too difficult to do one without the other being noticed, but then again euphoria brings about changes in a man’s attention to details.
And no WordPress.
The database was fine, all tables intact. Nothing had been touched. I was never into databases and MySQL until yesterday. But if I had to get back into business, I had to use phpmyadmin and correct the errors. I first used phpmyadmin’s default Export command to create a SQL dump of the tables. Next I dropped the tables and reinstalled WordPress. I imported the SQL dump and the SQL Query Windows began to show goobledygook. A missing punctuation, a misplaced quotes and non-existent table values. To top it all, the good old KSEB failed right on time. Impeccable timing.
It was many an hour before the power came back. This time, after a small tweak I applied to the SQL Dump file, I was able to reinstate the tables. And Voila ? Not quite. WordPress was not working again.
I decided to get my hands dirty. I fired up the phpmyadmin and began to view the table entries. I believe the whole problem was a wrong database entry denoting the current theme. I cleared the values for “current_theme” and “recently_edited”. And as if magic, WordPress was right back on track. No problems with theme or anything. I was a bit surprised at this behaviour.
WordPress, being a blogging application, should have some default theme to resort to incase of a theme failure. Or else, everyone would be wondering what happened to their perfectly customized blog.
Was this my fault ? Or is it WordPress’s ? Your comments are highly appreciated.
Its the fault of Mr. Murphy. Happens to me once in a while too – everything goes wrong all together.