"an Auto-Delete module for specified cat. pages to imit them" a new weneed : http://blog.wikidot.com/weneed:118 -

Please: rate it up!

The reason lies in the fact, that with the new Wikidot chatroom we got always new pages ( more and more..) and there is no automatic module or funtion available to delete "old" pages ( older than ### days) .
or all pages lower than a name like 1000 for a given catgeory.

Ticket on Pro Site: http://pro.wikidot.com/ticket:359

Links to forum Posts

by Helmuti_pdorf

This wish is for java applets to have a better way than this process:

The current process

(This was originally posted at tibasicdev.)

Hopefully new process

 [[Module JavaApplet src="http://tibasicdev.wikidot.com/local--files/files/TestAppletCode.jar" width="539" height="539"]] 

This would prevent all of the chaos above.

Links to forum Posts

http://tibasicdev.wikidot.com/forum/t-166105/tibasicdev#post-522236

by graphmastur

The current option is meta tag "Add to this page" or "Add to all pages".
I think that the option "Add to this category" would be also useful.

Links to forum Posts

I was reading the poll on language site tags and went to read this
W3.org article on Styling using the lang attribute.

Example: with the handbook, we could set language tags per en:, fr:, it:, de: category and then introduce some CSS codes depending on the lang tag.

Further reading: HTTP and meta for language information

by gerdami

Text-highlighter for the Wikidot syntax? Just a concept, but for example this:

 [[code type="wiki"]] [[div class="simple-box" style="text-align: justify; color: brown;"]] + Fruit Bowl! [[module ListPages category="fruit" perPage="10" separate="false"]] # %%title_linked%% [[/module]] Go [http://www.google.com to Google] or go [[[home |back home]]] [[/div]] [[/code]] 

could render this:

This would be nice for posting Wikidot code, as it makes it easier to read and comprehend where some parts start and other parts end.

It wouldn't necessarily be restricted to code blocks; you could also have the Wiki format render like this if you click on the "view-source" button of a page.

What do you think?

by James Kanjo

We have already interwiki links such as:
[wikipedia:Albert_Einstein Albert Einstein]
[google:free+wiki] Google search results
[dictionary:wiki] Dictionary.com lookup

It would be fine have the same syntax for Wikidot sites:
[handbook:fr:start] to short link to http://handbook.wikidot.com/fr:start

Notes

• Yes one [ because link is external to the current website.
• Mind the double : the second is for the category.
• How to link to http://google.wikidot.com ? good question !

• Old request: localized versions of wikipedia

Update doc syntax for [wikipedia:it:Albert_Einstein Albert] Albert

Links to forum Posts

http://community.wikidot.com/forum/t-34949/community
http://community.wikidot.com/forum/t-27/community#post-54002
http://community.wikidot.com/forum/t-111673/community#post-347387
http://community.wikidot.com/forum/t-16880/community

by gerdami

With live templates and Listpages et al, it's already possible to create simple webapps. Some of which require no more user entry than a page title. For example, see the Community Polls (operating but for a ListPages custom format LiveTemplates bug). The user enters a title of a page in Polls to create a poll question, and then enters titles of pages in polloptions to create options for that poll (which are autotagged to separate one poll's options from other polls' options).

If a NewPage module attribute Autosave were created, it would remove the unnecessary step of the user waiting for the editor to open and then pressing save. I gather that wikidot, from recent posts on the wikidot blog, has webapps on the brain. A lot of them will operate in similar ways, and if Wikidot forms are coming anyway, an autosave option should be in the works. Do it now, and you get people thinking in webapps terms ahead of schedule and you get a peak at some of what people will come up with as you create a platform for more.

If Forms are created, there should still be an autosave option, but "Yes" should be the default instead of no. No and full should still be options.

Links to forum Posts

http://community.wikidot.com/forum/t-169670/newpage-module-autosave#post-536020

by David Marseilles

I don't know necessarily about just RSS, but maybe a way to have a module like the ListPages thing do something like this:

 [[module ListPages rss="fedd://community.wikidot.com/feed/forum/posts.xml"]] There has been %%posts_since_last%% posts since you were gone. [[/module]] 

Links to forum Posts

by graphmastur

I'd like an API to be in place to allow external programs to post blog entries. Most major blogs have such an API in place, and it can be extremely helpful. For instance, many mobile smartphones might be able to run software that could make use of the API, but most have really crappy browsers. Also functionality like future post dates could be implemented in the client software instead of Wikidot having to add it themselves.

Examples of Blog APIs:
MetaWeblog API
WordPress API
Blogger API

Example of programs using Blog APIs:
Windows Live Writer for Windows
Tblogger for Windows Mobile

Wikidot TOS:
Obviously the TOS prohibit automated usage that is not "officially available". Were wikidot to incorporate a blog API, it would be officially available and it would not violate the TOS.

by David Marseilles

Having a ListPages attribute User would allow any the creation of user-specific blogs without the need for per-user permissions to only allow that user to add to the blog. It would also allow users to showcase all created pages on profile pages more easily.

Examples:

 [[module ListPages category="blog" author="David_Marseilles"]] [[module ListPages category="blog" author="James_Kanjo"]] 

In the above cases, both James and I could add pages to the blog category, but on the page we each created for our blog, only our own posts would show up. If the edit permissions are set to only editable by the page creator, then the blog output is personalized and secure from anyone else trying to add posts to it.

You could also create an editor attribute for other uses.

Links to forum Posts

http://community.wikidot.com/forum/t-161029/blogging

by David Marseilles

module OrphanedPages should have near the same selection possible as in List Page Module

http://pro.wikidot.com/ticket:42 has the same wish (Orphaned Page and List Page Module)

Links to forum Posts

http://community.wikidot.com/forum/t-154438/how-to-exclude-categories-from-orphanedpages#post-473970

by Helmuti_pdorf

I wish there was a password module! Basically, the syntax would be like this:

 [[module Password password="sssshhhh" button="Enter the password"]] My //amazing// super incredible secret! [[/module]] 

The page would render like normal, but everything inside the Password module would not be displayed. Instead, a text-box and button (much like the NewPage module) would be displayed. Typing in the correct password would make the hidden source code render.

This whole idea is basically just like the Collapsible block, except the user needs to type in the correct password for the content to be displayed.

This is not supposed to be a security feature, this is just supposed to be an interface feature. It matters not that the user may be able to view the page source code, because that's an option that can easily be blocked.

Why?

This would be useful for:

• Viewing privileges (i.e. give certain users access to "non-public" information)
• Trivia games;
• Fun!

Links to forum Posts

by James Kanjo

The ability to future date, or schedule posts for later is pretty useful for any blogging platform. The idea is that you're limited to particular times for writing, but your readers like to see new content spread across the day (or week or month, or whatever) instead of getting blurted out all at once and then having the blog go silent for an extended period of time. You make the post, save it, put a date and time on it, and then blogging software posts it when you request without any further action on your part.

I'd imagine it being implemented by the user initially creating the page in a scheduling category, then at the assigned time, the system automagically creates a new page in the specified blogging category and copies the contents to the new page, and then deletes the scheduling page. That, rather than renaming the page so that the page creation date doesn't throw readers off.

Links to forum Posts

To be added later. I'm pretty sure I've read some before.

by David Marseilles

Currently, when you subscribe to Wikidot pages via RSS, the user who created the page is displayed at the bottom of the feed:

However, when you subscribe to Wikidot forums/threads/posts, no such evidence as to who created the post/comment is given:

Links to forum Posts

JoostinOnline reported this here

by James Kanjo

I'd really like the ability to allow users to upload files without having to navigate to the bottom of the page. A simple module that moved this functionality up to anywhere in the page would be really useful and make the functionality much more straight forward.

Links to forum Posts

upload files module

by The Claw

It would be really useful to have a module that lists all files uploaded to a particular page. This would allow users to quickly see the files and be able to download/view them.

I'm creating a site where I'd like users to be able to upload content (pdfs, ppts, docs, xls etc.) and share it with other uesrs. This would add the back-end of the process required.

Links to forum Posts

File Upload Listfiles Module

by The Claw

The Comments Module enables you to display the forum discussion of the page the code is inserted on.

There are some lacking features in this module… I would like to see:

• The ability to display forum threads other than the one attached to the particular page (it exists!);
• The ability to paginate long discussions;
• In linear threads:
  • The ability to limit the number of displayed posts;
  • The ability to reverse the order that posts are displayed (newest at the top). — Done!
• The ability to allow public comments only for X days after original posting
• The ability to collapse comments except for first N or latest N

Links to forum Posts

Timothy Foster suggested the idea of limiting the number of posts displayed in this post

by James Kanjo

Currently, we have a nice little comments module that can go on individual pages. However, a question comes up. What happens when there become too many comments? First, the loading time becomes elongated, second, the page starts to look frighteningly long, and you begin to have to scroll a long ways to get to the recent comments.

I would like for the comments module to have more flexibility, such as limiting the number of comments shown (per page or not), and giving the option of displaying the newest ones on top or not. This would make the comments module longer lasting, more powerful, and more convenient.

Links to forum Posts

• http://jameskanjo.wikidot.com/forum/t-107208/james-kanjo#post-426746

by Timothy Foster

by gerdami

one thing that wikidot could use is customizable member ranks. the three ranks, (members, moderators, and admin) are not enough. there needs to be a way to add custom ones such as VIP or power users and then be able to customize there permissions.would go nicely with Page View/Edit Permissions request.

Links to forum Posts

by rhombus p

I would like some way to track the number of times that a file has been downloaded.

Links to forum Posts

by rhombus p