Consider instead of tagMode:

- 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'.

> Please everyone test this module and comment on the functionality

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]]

Module ListPages seems to report wrong %%date%% values.

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

You could consider supporting a "categories" attribute instead or in addition to the "category" attribute. That would also be more consistent with the existing "tags" attribute.

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.

1. When inserting %%content{1}%%, %%description%%, or %%short%%, Wikidot should remove all formatting (e.g. <h1>) and also line terminators. It is impossible to show this, for example:

%%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.

Thanks for all the valuable comments!

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.

When below code lists its own page (i. e. the page that contains this code) you get several “The ListPages module does not work recursively” errors. Not sure though if this is “working as designed” or a bug.

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]]

Maybe perPage and limit need better explanation. I'm not sure I fully understand, when to set which of them to what value.

Since the module is not yet widely used (and not yet in the official list of modules) there might be a few changes we would like to consider. One of them is default values for

• 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 code (see http://sandbox.wikidot.com/listpages)

[[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