Tag: problems

  • Lots’u-pdates~a

    OK. So, I’m craving for pizza.[1] Well, it’s actually Yellow Cab I’m looking for if you’re really interested in sending me some. LOL

    Anyhow, I’ve managed to update my WordPress installation from 2.2.2 to 2.5 yesterday evening, fixed a little about the tag cloud in my templates that will now use the system native to WordPress, fixed some tags whose display contained spaces and/or hyphens, and updated some plugins I am using.

    I was actually watching the CSS Naked Day website around that time along with the UST Online Grades page. Unfortunately, they both weren’t updated even if I try to reload them pages once in about every 5 to 10 minutes. 😛 So, I just slept.

    I really thought there would be no CSS Naked Day this year. Made me sad, really. Dustin’s blog was updated March 9 when I last checked it before today. However, a good morning dawned upon me when I woke up. Someone commented on my plugin page asking me to update it, telling me Dustin moved the CSS Naked Day to the 9th. So, there, I updated it already!

    I have just one problem though. My site coughs up HTTP header errors whenever I try to respond to comments on my blog entries. The comments get posted still, but the errors are still annoying. Is there anyone else out there producing similar errors after updating to WordPress 2.5? Tell me please, and maybe how to eliminate it as well. Thank you!

    Update: Apparently it was the Extended Live Archives plugin I was using that causes the error. I have just tested it using my own comment below. It seems that the problem was already existent even months ago with the 2.3 release because of the database changes, but I already admitted I haven’t been fully aware of blogging news lately. The plugin remains disabled, so you might notice a little barer homepage than before. There seems to be a fix, though I guess I have to do it a little later as I am already tired after a full half day of tweaking with my installation.

    Footnote:

    1. ^ I’m always craving actually. OMG! I have to go on a diet. LOL
  • Redesign At Long Last

    I have announced a redesign more than a month ago, but since WP 2.2 has been delayed, I decided to delay it as well. It’s finished now … well, almost. The upgrading process and the redesign exhausted me. So this post will just be a placeholder. Place your comments here, but I will surely edit this entry later.

    I was just worried about some things the upgrade did to my database, it seems that some non-Latin characters was converted to something else. I will investigate on this matter after I wake up later this morning.

    *after waking up this afternoon*

    After years of having single color accents, I’ve decided to take on dual-color accents to be used on this new design. I just love having complementary orange and blue on almost anything, now they’re on my Web site as well.

    Some pages still wouldn’t work, and some are still being rewritten. The new Projects page will be used to organize all my work including Web development and WordPress plugin development pages.

    This design has been tested on Firefox 2.0.0.x, Opera 9.x and Internet Explorer 7. I may include some bug fixes for Internet Explorer 6 as I discover it, but don’t count on it.

    Credits go to Feed Icons for the standard feed icon, and to FamFamFam for the cute little Silk icons I’ve used throughout the whole site.

    Thanks to Arvin for pointing out that my comment form didn’t work. I’ve only used id attributes on the form elements that browsers handling HTML-compatible XHTML wouldn’t process as query string variable names like what they do on name attributes.

    Criticisms are welcome. 🙂

  • Internet Connection Problem Resolved?

    I would have blogged the buggy Internet connection I was experiencing since December 26 after I heard from my father news about the Taiwan earthquake that damaged undersea communication lines, but it was all over the Philippine Blogosphere with news from Jhay, Yuga, et al. that I decided to stay quiet instead—its no use blogging the same entry all over again.

    The early times during the lowered bandwidth period, I ,as well as my friend Jayson, noticed that we could still connect to our ISP, but it cannot resolve host names. I immediately turned my PC on and searched my browsing history for IP addresses. Alas! I found a Google cache URI of my site where Google used its IP address instead of its domain name. Great Google! Since it is a search engine in itself, I immediately searched for a Google cache of OpenDNS—I could not open its homepage in itself as my ISP currently could not resolve its domain name to the IP address—thus a cache is more than sufficient. My [and Jayson’s] DNS issues are resolved.

    Though I sometimes experience the reduced bandwidth and intermittent disconnections, I guess it’s still enough to say that it could have gotten worse than that, and I still feel somehow satisfied. But after reading Euri’s recent rant about crappy Internet connections from a café, I decided to test my own connection.

    Results from testmy.net

    I was shocked with the results considering I was downloading bittorrent files at 30-40 kBps, I’m on PLDT‘s slowest myDSL, plan 999, and test results from testmy.net prior to this one never reached 400 kbps! I even tried the Speakeasy Speed Test but got these lower but similar results from its Seattle, WA server:

    Last Result:
    Download Speed: 502 kbps (62.8 KB/sec transfer rate)
    Upload Speed: 114 kbps (14.3 KB/sec transfer rate)

    I really can’t tell whether or not I am the only one experiencing this, but I know the intermittent connections would likely last for several weeks. Was it really resolved so fast this time?

  • Fighting the inevitable

    People encounter problems no matter how much we try to prevent them — they are inevitable. But we shouldn’t avoid them; we should face them. It is with fear and anxiety that many people try to run away from their problems.

    Just remember, there is something we all have but we usually ignore …

    A quotation I received through email said:

    Stop telling God you’ve got big problems.
    Tell your problems you’ve got a big God!

    … Yes, a big God!

  • It’s time for some change

    We all have our own problems and we, sooner or later and in one way or another, would know how to take care of them. I just don’t know why I keep myself from solving them. Then, I remember I keep asking God about things I want to be able to do, but one little line from a favorite movie made me think again. It was when God said:

    People want me to do everything for them. What they don’t realize is that they have the power. You want to see a miracle? Be the miracle.

    I’ve watched the film, Bruce Almighty, for over five times now. I hope now it strikes me for good. I really won’t tell what changes I need to undergo. But I hope writing this article would make me remember everytime that there are people expecting me to change. Yes, I really want to…