is Habari is so limited?
mayoosuf
I am very new to Habari and I realized Habari is so limited all
because it does not have some functionalities such as;
1. Category (Major problem)
2. Child Page
3. Permanent link structure
Other than mentioned, I love some of the in build features such as
User ACL and Quick interface and so on.
Basically why I am pointing out the Category as a major problem, all
because if I want to make a website with portfolio, blog and news
section in a one single installation I will have to think a lot to do
that, (but WordPress provide that feature, because of that WordPress
became a no 1 blogging platform)
Than that Habari does not allow the chilled post option. If the Habari
project included that feature, simply we can use Habari as a CMS
platform (I mean more than a Blogging platform)
Hope the next release will come up with a category option for entries,
I guess if you guys stick with this requirement, I am sure more users
will switch to Habari
Hope my comments will be useful and I appreciate the Habari project.
Because it’s a one hundred present OOP and PHP5. My comments will
continue for development folks because I am using Habari and I will
experiment more and more.
Regards,
mayoosuf
http://www.blog.eyoosuf.com
Michael Bishop
On Nov 5, 1:45 am, mayoosuf <mayoo...@gmail.com> wrote:
> Hello Habarians,
>
> I am very new to Habari and I realized Habari is so limited all
> because it does not have some functionalities such as;
> 1. Category (Major problem)
system, allowing for sites to define their own categorization
structure. I'm not sure of the name of the branch off the top of my
head, but if you are using SVN, you can check out the progress on
this.
> 2. Child Page
I believe there is a plugin in -extras that has basic parent/child
page hierarchy, however, I think once the taxonomy is finished, this
will be easier to define.
> 3. Permanent link structure
I haven't tested this plugin, http://blog.tinyau.net/archives/2008/03/12/habari-rn-custom-permalink-plugin,
but I believe that might be what you are looking for.
And welcome to the community, all input is always greatly
appreciated. I'm sure others will give more detailed information on
your points, I just wanted to point out that your concerns are ones
that either are being addressed, or have some solution already in
place.
Thanks again for checking out Habari, and we look forward to hearing
more on your experiences.
~miklb
Su
> On Nov 5, 1:45 am, mayoosuf <mayoo...@gmail.com> wrote:
> There is work being done currently to allow for a full taxonomy
> I believe there is a plugin in -extras that has basic parent/child
> I haven't tested this plugin, http://blog.tinyau.net/archives/2008/03/12/habari-rn-custom-
That's all great for the specific points raised, but maybe there's a
more generalized, "philosophical" response to be made, to cover the
title question.
(I've been lurking and studying for a few months, but those who've
been around longer feel free to say all the following is completely
backwards *grin*)
Habari has a more-than-usually minimal concept of what's "core"
functionality, with the expectation that if you want something more,
you'll either install the necessary plugin, or add it yourself(eg.
content types are extensible, so no point in having a bunch of default
fields that may not be used.) So, Habari /itself/ does roughly the
least possible(title, entry body), but makes it easy to bolt on just
about anything else you want. As I see it, this puts it a bit closer
to Drupal than WordPress, at least from an architectural standpoint.
Most applications take the approach of trying to cover all or most of
the fairly-common situations(categories! tags! trackback? ecommerce?!)
right from the start, with plugins only becoming necessary for
less-common tasks. So, for example, a few versions back WordPress
added a gallery creation feature in the core, but podcasting still
probably calls for a plugin.
This has certain advantages sometimes, but it also means that if you
/don't/ want those features, you have to take the time to hide them,
if the application even allows for it.
I don't think either approach is inherently superior, but it /is/
necessary to understand which one applies to whatever application
you're looking at, in order to know what your options and expectations
are when a feature is "missing." I've seen people in the MT forums ask
about incredibly specific functionality seemingly without even
considering to look in the plugin directory.
Beyond any of that there is, of course, the basic fact that Habari's
still only around 0.6.
mayoosuf
applications, so in order to be on top, we (Habari) should have some
sort of spacial stuff else some intresting stuff same like available
application (wordpress), that will make user to think of it.
Currently i am playing around with Habari, http://eyoosuf.com/habari/
once i am satisfied with that truly i will use it for my applications
as well as my clients.
My point was just for a motivation factor.
Will (habari) make as no one Blogging and CMS platform!
On Nov 5, 3:10 pm, Su <s...@generis.name> wrote:
> On Thu, Nov 5, 2009 at 12:56 AM, Michael Bishop <mi...@bloggingmeta.com> wrote:
> > On Nov 5, 1:45 am, mayoosuf <mayoo...@gmail.com> wrote:
> > There is work being done currently to allow for a full taxonomy
> [...]
> > I believe there is a plugin in -extras that has basic parent/child
> [...]