Blog

  • Customizing your Fluency plugin satisfies your WordPress Admin Vanity

    Customizing your Fluency plugin satisfies your WordPress Admin Vanity

    Because I’m so vain with my WordPress admin, I decided to customize my Fluency plugin. Thanks again to Dean for making this customization easy as ABC and for updating Fluency to be compatible to WordPress 3.2. This post will not teach you how to customize your own Fluency admin, because it’s so easy to do so. Even a 3rd grader can customize it in minutes. What I want to do now is showcase my awesome WP-admin, powered by Fluency. Check out the image below:

    (more…)

  • The Library of Congress on the web

    The Library of Congress on the web

    If you’re looking for something that you cannot find in any search engines, specially Google, you can find it at the Library of Congress, of loc.gov. It’s a government owned website and it’s frequently updated about the latest additions in the library.

    You can access digital collection at loc.gov. You can freely browse about the American History archives, Historic Newspapers, International Collections, Legislative Information, Prints and Photographs, Veterans History, Early Sounds Recordings, and a lot more!
    (more…)

  • PageRank Rollback: Twitter is back to PR9 & Google is now PR10

    PageRank Rollback: Twitter is back to PR9 & Google is now PR10


    Yep, another PR update occurred a few days ago. Majority of the domains that gained PR, rolled back to their original PR. Some maintained their PageRank, and some gained a +1 PageRank after the last PR update. A few sites gained PageRank twice, but those are new sites from PR0 who gained PR2 last June 27, and promoted to PR3 last July 18.
    (more…)

  • Fluency Admin is now compatible with WordPress 3.2

    Fluency Admin is now compatible with WordPress 3.2


    I shared about Fluency before and its incompatibility with WordPress 3.2. Now, Dean, the geek behind 47 robots updated its awesome WP-admin plugin, and it’s now upgraded to Fluency Admin 3.2. So for those who are using Fluency Admin, and deactivated it because it’s not compatible with the latest WP version, now is the time to rejoice, because our precious Fluency admin plugin is now compatible with WP 3.2!
    (more…)

  • The Basic Na’vi Words and Phrases

    The Basic Na’vi Words and Phrases


    Because I’m a big fan of Avatar and I’ve been dreaming to live in planet Pandora, I’m gonna share to you the basic Na’vi words and phrases. I recently updated my about page and I included the Na’vi language in the stuff that I’m interested to write about. I also added a new category in my blog entitled Pandora.
    (more…)

  • Another Major Google PageRank Update: July 18, 2011


    I just noticed that another major Google PR update has occurred yesterday, July 18, 2011. I noticed a lot of sites returned to their original PageRanks after the June 27, 2011 major PR update. Some sites that gained +1 PR, rolled back to their original PageRank, such as PlurkThemes.com (PR7 to PR6), Ajalapus.com (PR6 to PR5), SachaChua.com (PR6 to PR5), Jehzlau-Concepts.com (PR6 to PR5), and other notable Filipino blogs.
    (more…)

  • Twitter’s PageRank (PR) is down from 9 to 0

    Twitter’s PageRank (PR) is down from 9 to 0

    If you haven’t noticed yet, Twitter’s PageRank is now zero. There’s a minor PR update last July 16, 2011, and only few website owners noticed this. The last major PR update was last June 27, 2011. I also noticed PR6 and PR7 sites that are now PR0, such as Circolo Sormani, and other well-known websites and blogs.
    (more…)

  • WordPress Fatal Error in wp-db.php on line 774

    WordPress Fatal Error in wp-db.php on line 774

    Wow, I just noticed that my blog is now full of WordPress fatal errors and how to fix it. I admit, I’m a certified WordPress junkie. Haha! This is my 78th blog post and my 12th WordPress error post. So… I’ll tag this one as WordPress and… I think just WordPress.

    This error is clasified as 500 Internal Server Error. This simply means that the server is the main cause that’s why this error occurred. If you’re familiar with the Fatal error Allowed memory size of [RANDOM NUMBERS HERE] bytes exhausted (tried to allocate [ANOTHER RANDOM NUMBERS HERE] bytes) in /home/user/public_html/wp-includes/wp-db.php on line 774, then you’ll have an idea that the main cause of this error is your server’s memory allocation to the specific user.
    (more…)