Tag: troubleshotting

Categories
General

Solved: Nokia N9 can't connect to Twitter

After I had my Nokia N9 early this month, I setup my Twitter account first — after some basic phone settings, of course. Everything worked. The application is probably not the best, but it works.
Is it problem-free app? I thought so, until I got a problem: I can’t connect to Twitter using this app. I was not sure when the problem occurred for the first time. I did played with my phone (installing apps, downloading musics, adjusting settings, and including working from the command line). When an update was available, I also upgraded.
Added later: I was not sure what caused this problem. When I signed-in for the first time, everything worked without any issues. I deleted my Twitter account from the app, and tried to add it again. I forgot when I did this for sure, before or after installing the firmware update. It  was optional, but I decided to upgrade.
2011-11-13 01-49-48At first, I was not sure about the problem. Is it my phone, or the internet connection I was using. I switched to some different connections, but it didn’t solve my problem. When I tapped the “Sign In” button, it said: “Can’t connect to Twitter”.
So, I searched for a solution. And, I got one. It’s probably something too technical, but the instruction is easy to understand. According to the forum thread, here are some steps to fix the problem — I’m using Software Version: PR1.1 (20.2011.40-2_PR_005):

  • Activate “Developer mode” by going to: Settings > Security > Developer mode. It’s OFF by default. Turn it ON.
  • After having it activated, you will find a “Terminal” app button under application menu.
  • Open it and you need to execute these commands (one command per line):
    • gconftool --recursive-unset /system/http_proxy
    • gconftool --recursive-unset /system/proxy
    • gconftool --recursive-unset /system/osso

You may close your Terminal.
Those commands will wipe your active connection settings (bluetooth and internet data). But, it’s not a problem as I can add/manage connection settings easily. Problem fixed. Great.

Categories
General

Troubleshooting: Can't Login After WordPress Upgrade

Today, I was helping my client upgrading her WordPress-powered blog. He was using WordPress 2.6.x series. I upgraded using the standard procedur, and I thought the whole process was painless. But, it was not. I could not access its “Dashboard”. The login screen was there, but when I entered the username and password — I was 1,000% sure that I typed a correct combination — nothing happened.

Few months ago, I had a problem with the “Redirect Loop”. I made a speculation: removing all plugins under wp-content/plugins/ directory. Of course, after I made sure that I had the list of all active plugins. After that, I tried to login again, and voila! I continued re-installing all plugins needed. Problem solved.

Categories
General

Troubleshooting: SoftException in Application.cpp:544

When I had problem with WordPress installation, it was about WordPress Admin Area (Dashboard) Redirect Loop, I got the solution. Today, I experienced different problem. Still related to WordPress.
Okey, I’m not going to tell you that the problem only happens for WordPress. It might happen for other platforms or applications. Read on the details, you’ll know what I mean.
When I enter WordPress dashboard (admin area), I got 404 error page. It seems that the wp-admin folder does not exist. But, it’s there. I told Lala about this, and she reminds me that I’m not the one who got this problem. (see WordPress Support Forum thread for details).
So, I checked the error log. If you’re using cPanel for your hosting account, you should find the error log there. And, I got this:

[Tue Dec 30 09:20:18 2008] [error] [client ip.address.here] SoftException in Application.cpp:544: Directory "/home/username/public_html/somefolder" is writeable by group

Okey, it’s about SoftException in Application.cpp:544. I searched for answer using Google, and I found a useful answer.

As the message says, the specified foldername has been made writable by group.
That suggests that your server’s apache configuration doesn’t allow you to make folders writable by group.
ie: you’ve got the wrong permissions set on one or more folders.
Check with your hosting company to find out what permissions you’re allowed to set.

The answer is not related to WordPress issue, but it’s a solution for the same problem. So, I checked the wp-admin folder permission again. It was 777. Okey, I changed it into 755… and voila! Problem solved.
Okey, everything is working great now. It’s a new lesson for me :)