StatusNet has a feature called Fancy URLs, which is basically a way for the application to create SEO friendly URLs. This post is just a log of my experiences with this URL rewriting feature.
With this post we conclude our evaluation and our work with StatusNet. Consider this our final report on this micro blogging platform.
This post is part of the Working with StatusNet: how to article series.
We’ve been working with StatusNet for a couple of weeks now and have developed the need to manage the site’s users. Not that we have a lot of traffic, it is because we are attempting to resolve the Password Recovery Error: Bad Request – No such recovery code issue.
In this series of articles we will be documenting our work with the StatusNet micro blogging platform. Because managing an Open Source app like StatusNet requires some knowledge we will not waste a lot of time with what is considered basic information. Simply put, if you need to be here, it is assumed you understand the conversation.
We try to run an open forum so anyone and everyone is invited and welcome to partake in the discussion if you think you have something to add. We will also try to help if that help falls within our capabilities.
In looking for a way to manage my StatusNet users I came across the instructions for how to enable the StatusNet Welcomebot. This information is covered in StatusNet wiki for the the sake of quick reference through our offline documentation we will quickly paraphrase the instructions.
This is something that has been happening on one of our clients StatusNet installations. We have been aware that the password recovery functionality has not worked since we first did the installation but have continued working the script for the sake of both the clients choice and our Script Evaluation article series. At this point final deployment of the site hinges on the resolution of this issue as password recovery is an important feature.
This is not good as changing direction now will cost us about two weeks worth of work. There is also this: the fact that previous evaluations of this piece of software have been hindered by what we now know have been environmental issues on the hosting end, some very much out of our control. All the above considerations pose the question: how much further time, if any, should we devote to this issue?
This article will be our repository of any and all information regarding this issue. What follows is a description of the problem and hopefully, sooner or later, a resolution.
This is part four of our series in editing / styling StatusNet themes. So far in the series we have covered some of the StausNet theme basics. We have changed the styling of our layout and some of our header. and have changed the colors of our buttons, side nav, etc.. throughout the theme.
Now is the time for finishing off the header area of the theme.