IsaacSaito's profile - activity

I did click "Trial" from Basic Plan (here) and got the message Internal Server Error.

Snapshot can be seen

here

.

Since its recent upgrade, answers.ros.org's comment area seems to be following this decision. I still really liked minimum formatting eg. auto-link URL.

I seem not to find same thread so I'm posting this.

I'm using answers.ros.org v0.7.48. I have at least one unread message for sure that was received older than those received recently. On http://%DOM%/users/%USERID%/%USERNAME%/?sort=inbox&section=forum, I can only see recent ones and I see no way to go back to the older messages. Any workaround?

I see. Then I'll ask the site admin about this.

I'm using answers.ros.org that seem to have upgraded to v0.7.48 recently. Probably since then, e-mail notifications from the web site starts going into spam folder on my GMail. I can't tell why GMail does that, but this might be something I wanted to report, and ask if there's already any workaround.

---

Update) I found that GMail complains that the smtp server domain that my e-mail address uses is found spammy by them, which seems to mean the cause might not be on askbot-powered server's side? But then why does this issue suddenly start coincidentally with server software update...

I see. So..., is the person listed in the link I cited working on a translation on different stuff?

I can join Japanese translation team.

(Since I found someone might have already started working on it here, think I should contact the person listed first).

Yep this works for me. Just want to share that "user ID" is not the account name but the unique number system uses, which is visible in URL in each user's page.

@Evgeny thx. Once I manage to have time I'll try your suggestion and report.

I have installed askbot experimentally on Amazon EC2, both of which I'm new to. On EC2 there's a feature called "Elastic IP" that assigns static IP to its virtual machine instance. When I start running askbot by following command WITHOUT using Elastic IP (meaning I used the IP dynamically assigned by EC2 at that moment), I can access to my askbot via browser by using WAN IP.

sudo python manage.py runserver `hostname -i`:8008

However, when I turn on Elastic IP, I can't access via browser ("not found" on browser, and no record in the web server's log).

It looks like hostname command returns LAN IP on EC2. So I tried:

sudo python manage.py runserver %WAN_IP%:8008

where %WAN_IP% is the one assigned by Elastic IP. This fails to run askbot complaining "Error: That IP address can't be assigned-to."

I want to keep using Elastic IP (since it's too cumbersome every time to change IP accordingly). Any idea would be appreciated.

The last 4 lines of my setting.py looks like this:

DOMAIN_NAME = '%WAN_IP%'

CSRF_COOKIE_NAME = '%WAN_IP%_csrf'
CSRF_COOKIE_DOMAIN = DOMAIN_NAME