Re: num_entries should not apply to category views

> Anyone else have any thoughts or use-cases where changing this behavior 
> is a bad idea?
> 
> /will

Although I agree with the original argument that it is somewhat absurd not to be
able to read rest of the entries due to the num_entries, I find myself liking the
current behavior. Thanks goes to two plugins and their authors: wbgpager-plugin 
breaks num_entries nicely into pieces and readmore-plugin cuts longer entries. The 
result is visually appealing and easy to navigate. (I abstain from saying anything 
about what goes under the hood.)

So a counterargument: if you have categories with huge number of entries in them, 
and especially if you tend to write a little longer entries, the old problem (cf. 
the change of num_entries from fifty to ten) appears; loading a page under these 
settings is neither efficient nor ergonomic.

- Jukka.

> chombee wrote:
> > I'd like to propose that the num_entries config variable should only
> > apply to the front page of a blog, i.e. /pyblosxom.cgi and not also to
> > category paths like pyblosxom.cgi/computers/operating_systems/ as it
> > currently does. I just don't see the usefulness of being able to read
> > the first num_entries posts of a given category but not the rest, and I
> > think viewers will naturally take the posts shown to be the full content
> > of the category. I think that blogs would be much quicker and easier to
> > navigate if category paths showed all entries of the specified category,
> > just like time-based paths show all entries matching the specified time,
> > and this behaviour also seems to fit better with the blosxom philosophy
> > (of behaving like the file system).


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace