Michal, shouldn't %%summary%% behave roughly like [[module Pages … preview="true"]] does?

%%summary%% displays so much more (formatted) text that it's very difficult to see when the summary for one page ends, and the next page starts — for an example see http://sandbox.wikidot.com/listpages-summary

It uses the following code to display page summaries. If I'm correct, there's even a Listpages bug, as you can see that the first page listed there doesn't even have a %%linked_title%%.

 [[module ListPages]] %%linked_title%% %%summary%% [[/module]] 

• ListPages -> Select
• category, categories -> from
• tags -> where
• prependLine -> header
• appendLine -> footer

Giving something like this:

 [[module Select from="blog,news" where="public" header="||~ Page||~ Date||"]] || %%linked_title%% || %%date%% || [[/module]] 

The actual implementation seems to behave differently:

If you have 100 pages and use perPage="10" or "20" (and you don't set limit) you get 10 or 20 pages without pagination.

Only if you use perPage="10" and specify limit="100" you get 10 by 10 pages with pagination.

For an example see http://sandbox.wikidot.com/listpages-pagination

It's not a link to a page, but plain text.

It took two include templates and six pages to implement this! A big advantage (and a feature that would help reduce the need for six pages down to one page) would be, if ListPages supported URL's such …wikidot.com/page-name/order/titleAsc (similar to what it supports for pagination) to overrule ListPages' sort order.

Support for …wikidot.com/page-name/category/category-name would be nice, too.

There seems to be a bug in the parser though, if you add style="…" attributes to the cell tag in prependLine — please see http://sandbox.wikidot.com/listpages

Thx

If the default for limit is “none”, then I would expect a default configuration to display all pages, but it actually just displays 20.

Is the documentation wrong? What does “none” mean? Zero? Unlimited?

 [[module ListPages prependLine="||~ Page||~ Date||"]] || %%linked_title%% || %%date%% || [[/module]] 

shows the following error(s):

An error occured when processing your request.
Warning: pg_query() [function.pg-query]: Query failed: ERROR: invalid input syntax for integer: "" in /var/www/www.wikidot.com/ozone/ozone/php/core/database/PgConnection.php on line 100

• rssEmbed (embeds link to a corresponding RSS feed in the HTML header so that browsers and other clients can discover it) and
• rssShow (shows an RSS icon below the generated list).

What do you thing would be the most commonly used settings for those two? Setting them manually to false too often could be annoying, but on the other hand it would be nice to promote the use of feeds.

RSS feeds exist independently of the module, the module just points to the proper URL that allows one to access the feed.

the reason the module "does not work recursively" is because it can enter an endless loop, exactly as in one of your early tests when displaying such a page brings "connection dropped" from the server. Thanks for finding this bug anyway! The quickest way to be 100% sure that no ListPages calls was to disable the nested ListPages.

Perhaps a better solution could be found. We were trying some other methods too but this one was the quickest to fix the problem. Any suggestions?

PerPage and limit work in the following way:

Suppose you have 100 pages in your category blog:. You want to show them all, but paginated, 10 per page. You use: perPage="10".
Now, to display just 10 pages, but nothing else, no pagination, you use: limit="10".
A combination of these: you want a visitor to browse only 50 first pages of 100, but still 10 per page: perPage="10", limit="50".

limit="n" limits the total number of results that fulfill the select conditions — if you have many pages, 10000, this can limit your set to e.g. 40. This limitation is applied first.
perPage="n" tells how to display the results — how many per one page. If you limit your result set from 10000 to 40, your can display them all at once (perPage="40") or e.g. by 10 (perPage="10") — it would create 4 pages of results with previous/next buttons.

I hope it helps!

Thanks for your comments!!!

m.

See http://sandbox.wikidot.com/listpages:recursive

 [[module ListPages category="listpages" rssEmbed="false" rssShow="false"]] %%linked_title%% ++++ Description %%description%% ++++ Content %%content%% ++++ Content{1} %%content{1}%% [[/module]] 

-Pieter

I'm not sure %%first_paragraph%% is a good name, it's kind of ugly. I'd prefer:

- %%content{n}%% to be explicit
- %%short%% to be the first paragraph (obviously, in the first section if any)
- %%description%% to be the same as short (and in fact, multiple names for the same thing is ugly too, and we should choose the nicest, shortest name, and deprecate the rest)

I can't see any case where the designer would want the current %%index%%/%%description%% behaviour… like I said, it's unstable because adding a second section makes it go bizarre. First you get the first paragraph, then suddenly you get the whole first section. Unstable is not good.

Lastly allowing both 'category' and 'categories' is another hack, and not the right solution. If you can't choose between two terms, they're both wrong. Try something different, like "from" (SQL semantics), and "where" for the tags property.

[[code]]
[[module ListPages from="blog,news,index" where="+public,-deleted"]]
etc.
[[/module]

I will try to answer most of them below here:

%%date%% issue

@Erich: thanks, dates are working fine now.

categories parameter and not recognized parameters.

OK, now categories is an alias to category. I think we can make warnings about wrong parameters later - the module took a bit more time than expected anyway. But certainly this is a good thing.

More on custom formatting

@Erich - unfortunately it is not possible to do custom formatting (i.e. table headers) the way you propose it because modules are processed at a different moment than the rest of the page. However I have a solution that does work: look at the prependLine and appendLine parameters. This works fine for me:

 [[module ListPages separate="false" rssShow="false" prependLine="||~ Page||~ Date||"]] || %%linked_title%% || %%date%% || [[/module]] 

@Pieter

1. Headers are now stripped from the summary and newlines are being removed.

2. There is now a %%first_paragraph%% that does what it says. %%content{1}%% will fetch the first section while the %%short%% and aliases will use either the first section (if exists) or would fall back to the first paragraph. I believe this brings some consistency.

3. Sure, one module to rule them all.

4. Yes, %%comments%% will be here, but first we would like to detach page comments from the forums structures and possibly make them a bit more blog-like.

5. Fixed. Just to be clear: this happened when you had %%content{n}%% in a ListModule inside a _template page.

Thanks for all the comments, I hope the module works much better now.

m.

A warning on unknown attributes would be generally useful. Also, later, help in the editor for entering module arguments.

%%content{1}%% (%%date|%O ago%%)

2. There is no way to ask for the first paragraph if one uses content separators. That is, adding a content separator anywhere into the page changes the behaviour of %%short%% and %%description%%, which is not good. I'd suggest that if people want to show the first content section they can use this explicitly:

%%content{1}%%

and if they use %%description%% or %%index%% then that should always take the first paragraph of text.

3. We eventually need selection on page rankings and parent page, so we can deprecate all these modules:

• ChildPages
• PagesByTag
• Backlinks
• RatedPages

4. We need the %%comments%% field in order to properly show blog entries and news stories.

5. When showing %%content{n}%% in a ListPages module on a page with content sections, it shows the data from the current page rather than the listed page. It should show the content section from the listed page.

Else you might consider to issue a warning if a non-existing attribute is specified. [[module ListPages categories="_default howto" ...]] works now, but doesn't list those two categories, but the current page's category.

See [http://community.wikidot.com/bugs:module-listpages].

Could you perhaps support ListPages configurations like the following? Thanks!

 [[table]] [[row]][[cell]]Page[[/cell]][[cell]]Date[[/cell]][[/row]] [[module ListPages separate="false" rssShow="false"]] [[row]][[cell]]%%linked_title%%[[/cell]][[cell]]%%date%%[[/cell]][[/row]] [[/module]] [[/table]] 

 ||~ Page||~ Date|| [[module ListPages separate="false" rssShow="false"]] || %%linked_title%% || %%date%% || [[/module]] 

Please everyone test this module and comment on the functionality, either here or on our dev list.

m.

- by default, tags are OR
- use +tag to make a tag mandatory in the selection
- use -tag to make a mandatory negative selection

For category, the default should be the current category, so that if I use ListPages in the blog: category the default category is "blog:"

To select all categories I should be able to use "*".

For the Rss options, use consistent naming:

• rssTitle
• rssShow
• rssEmbed

Instead of 'separate' with default 'true', use 'breaks' with default 'false'. It's not nice to have defaults that are 'true', in general a default should be 'off' until requested to be 'on'.