ciao!

Or maybe some templating of how tags are listed, a la ListPages. For example,

 [[module TagCloud stuff]] %%tagname%%,,[[size smaller]] %%tagcount%%[[/size]],, [[/module]] 

Nice!! this is going to help me alot!!

I've forgotten what the whole point of this module was. Can anyone give me a use-case, to help me think of ways to use this myself?

e.g. if I wanted a single page to have a theme applied to it, I'd just put it into it's own category. How is this different, apart from preventing us from having to create separate categories? :)

edit: Actually, I think the main use-case had something to do with CSIs. Might make the chatroom easier to install. Any other suggestions…?

note: this is an example where when you click on the comment, it goes to the page the comment was made for, but since theres no comment module, you have to scroll down and manually click on the disscuse button

The question is for me now - what is the limit for a batch ( the sum of all file-sizes in one go).

or is there no limit anymore?

I get the impression that there never was supposed to be a limit, and that by having it limited to 50 MB, that was a bug which was fixed on 26th November. In other words, it is now set up how it was always intended to be — no limit on a batch, only on each individual file.

_{http://www.wikidot.com/plans <— For anyone interested, there is a list of plans (including the free account) and the maximum file size that each plan type is allowed to upload. The 50 MB limit applies to Pro+ plans, all other plans have a lower limit.}

This was for free account available since 1-2 month

The question is for me now - what is the limit for a batch ( the sum of all file-sizes in one go).

or is there no limit anymore?

also, is this for free accounts or pro?

bienv wrote: BTW, how do you add a signature to your comments?

Now that is something I can answer very quickly for you :)

I noticed that you tried using a CSI. CSIs are disabled for forum comments, which is what you just tried using it in… they only work in pages. It's a limitation that I don't like, but there is no way around that.

To add a signature to all of your forum posts (note that it will apply to every site you post on, and there is no way of disabling it on a per-post basis), follow these steps:

1. Click on My account at the top of this page or, alternatively, click here instead: http://www.wikidot.com/account:you
2. Click on My profile (in the sidebar)
3. Click on Forum signature (in the main content area)
4. Type in your signature using Wikidot syntax, update to see if it looks how you want it to, then click on Save ;-)

[[include :bienv:nav:sig]]

I assumed that there would be some way (even with use of an external tool) to get this working without having to wait for Wikidot to implement something like this, but as no-one else has replied to this I assume I was wrong about that.

Why not here? http://community.wikidot.com/bugs

Good question, but though it looks obvious, there are several problems for me, to depend on that.

Rather than discuss that here, let me make a blog posting.

I'm aiming to make a new issue tracker (bugs.wikidot.com)

[Head, meet keyboard…] rebygv67um

Why not here? http://community.wikidot.com/bugs

There is still a bug somewhere. I admit it's a complex page but if you have a look at this page and you click on "meer tekst" @ the end of that page there is an include that does not get rendered… so the fix is probably only for one level, but that page opens his _template wich calls for another template wich has a Listpages inside and the include function is one of the contents {4}. And it does not get rendered…

It worked before because I added another step using an include… but I changed it just now, because it was said that this was fixed… but…

This will not work IMO if there is a ListPages inside the CSI-page

Do you have an example where it is broken?

In the last six months or so we've closed about 250 issues (and there are 150 open in our tracker). We're now getting pretty good at fixing problems within a week or two of a new report.

So this particular issue popped onto my radar on 13 November and I logged it, and we pushed the fix live the same day.

• In the _template, the %%parent_category%% variable was displaying %%category%% instead - fixed.
• %%parent…%% variables were not updating until pages were explicitly recompiled - fixed.
• In ListPages, when parent="=" was used on a page with no parent, it would select other orphans. Now, selects nothing.

Just thought I'd re-post these, as people that are reading this through email will not know that those were added to your post — they'll only see your original post (the first three bullet points only)

ListPages was misformatting dates in _templates.

Thanks. I had completely forgotten about that problem, because as soon as I saw it messing up my dates I deleted that section and opted for using %%title_linked%% only and not showing any content. Now that this is fixed, I might be able to change that.

Edit: I'm talking about something completely different. Ignore this! ;-)

(It's nice to know these things get addressed eventually. But what am I, chopped liver?)

Besides "csv", what other formats can be used for the format attribute?

The documentation is comprehensive. The only choice is 'csv'

EDIT

Also would like to decrease space between the cover and and the first book, how to do that?

EDIT (again)

The answer to your question is: the perfect result would be to have at least 4 spines next to the cover and any more to appear below the first 4. SO it would look like a bookshelf, maybe even add a bookshelf picture behind it later.

Did you want each book spine to touch the other book spines?

To get a better idea of how it should look please see here. It's the closest I've gotten to getting it right. As you can see, each 'Part' should stack a new book next to the previous one.

Current Code

 [[module ListPages category="book-cover" tags="cover" order="created_at"]] [[div style="float:left; font-size:200%; color:gold; font-weight:bold; height: 527px; margin-left:5px; padding-top: 115px; padding-left:17px; text-align:left; width: 30%; background-image: url(http://hobbycode.wikidot.com/local--files/wiki-book/book%20spine.png); background-repeat: repeat-y;"]] %%linked_title%% [[/div]] [[/module]] 

Too much padding perhaps?

Try adding this around the ListPages block:

 [[div style="float:left; width:45%;"]] [[module ListPages ...]] ... [[/module]] [[/div]] 

That should make the book spine's 30% width come from the amount of space left, instead of from the total page width.

As you can see from the above link, I want the books to appeare besides the previous one. I have tried tables and bested div's with no luck.

Any suggestions?

 [[module ListPages limit="3" range="after" category="book-cover" tags="cover" order="created_at"]] [[div style="float:left; font-size:200%; color:gold; font-weight:bold; height: 527px; margin-left:5px; padding-top: 115px; padding-left:17px; text-align:left; width: 30%; background-image: url(http://hobbycode.wikidot.com/local--files/wiki-book/book%20spine.png); background-repeat: repeat-y;"]] %%linked_title%% [[/div]] [[/module]] 

• User's timeline
• User's followers
• User's friends
• Search (not available in RSS)

• Site owners, admins and mods: all traffic on the whole site.
• Site members: new pages only (not edits).
• Page creator or editor: all traffic on that page.
• Page commentor: all traffic on that page.

I'm not sure about the site members getting new pages. That could be dropped.

Agreed.

I think that the best way to have it would be to only have people watch the things that they create. So that means that they don't auto-watch sites they join, but they do watch sites that they create, and pages that they create, edit or comment on.

Yes, and I think this should be automatic and not configured. That was the goal of design:2, partly.

OK… so… maybe a next step is to just remove this option and change to a more sensible default from design:2:

• Site owners, admins and mods: all traffic on the whole site.
• Site members: new pages only (not edits).
• Page creator or editor: all traffic on that page.
• Page commentor: all traffic on that page.

I'm not sure about the site members getting new pages. That could be dropped.

This is all one option: [_] Auto-watch sites I create or join, pages I create, edit or comment.

I think that the best way to have it would be to only have people watch the things that they create. So that means that they don't auto-watch sites they join, but they do watch sites that they create, and pages that they create, edit or comment on.

The problem being, that to set it up that way it's a bit more complicated than changing a simple setting's default value.

I have a feeling that there was an extensive discussion about the best way to do exactly that… but the only page I can find that remotely mentions this would be this page on the design blog (read the comments, not the design itself). I think there's a better reference somewhere…

Something like:

Watch sites:
[_] That I create [_] That I join
Watch pages
[_] That I create [_] That I edit [_] That I post a comment to

Wikidot is amazing… yet there are so many things that I and others want :) If only I had the money to pledge more at the roadmap site, I could show how much I appreciate the work you're doing.

OK, allow me to be explicit: I gave you a stripe, more than earned.

Oh =0 I didn't realise that… thanks! :)