But of course, they don't call me a Wikidot Super-Guru for nothing! Read on to see how it's done properly.

There are two useful tools that appear when we create new pages: the top and sidebar navigators. Whatever code you place in these two pages, it will appear on every page that utilises those particular navigators. Generally speaking, these navigators are usually global for the site on most wikis (however they can be customised on a per-category basis).

For our exercise today, we are going to focus on the sidebar navigator (usually located on the /nav:side page).

Step 1: Create your per-category CSS pages

Let's assume the category "survey". We are going to create a hidden page called /survey:_css for us to store our CSS module on. Place your CSS module on this page like so:

 [[module CSS]] a {color: #FFF !important;} [[/module]] 

This line of CSS code will ensure all links appear in the colour "white".

Step 2: Inject James' Brilliant Code

Navigate to your sidebar navigator page and place the following code at the bottom:

 [[div style="display: none;"]] [[module ListPages limit="1" pagetype="*" separate="false" prependLine="[!--" appendLine="--]]"]] [!----] [[include %%category%%:_css [[/module]] [[/div]] 

This Wikidot code will extract the source from the :_css page on a per-category basis. If no such page exists, nothing happens!

If you happen to have no sidebar navigator on your Wikidot site, I suggest that you:

1. Re-enable the sidebar from your /admin:manage page;
2. Go to the sidebar page (usually it's the /nav:side page);
3. Paste the following code at the top of the sidebar's source code to "remove" the sidebar:

 [[module CSS show="true"]] #side-bar {display: none;} [[/module]] 

Step 3: You're done! Check it out!

That's right, there is no Step 3! You can now create new pages with per-category customised CSS now!!!

No more messing around with the site's global CSS!

λ James Kanjo

Source

As taken from my blog post Wikidot: CSS Per Category

by James Kanjo

Under the "Viewer" of the (current) image are inserted some (neccessary) documentation like source, author, date,. description a.s.o)
Above is the hammer scrollbar ( module:2) usd for previous and next navigation of the images..
And under the "Viewer"-image is the collection ( by Listpages) of the thumbnails of the urls of all pages in the category.:

Question: is the Listpages too long to load ?

Notice the used "image-ext:_template of the images!

I am not sure if someone else had the same idea before - could be i am too late for such solution and I have overseen it.

Please - try to add another (external) image with the add button to test this …

by Helmuti_pdorf

• users are presented with a UI to set search filters for category, author and title
• admins can set default values for each of these values
  • in addition, admins are also able to enforce these default values (thereby restricting search results to the designated default filters)
  • plus, admins may hide these filter fields from users to remove confusion
• admins are able to set the label of the search button

"Now, that's all good", you may say. "So, how do you do it?"

Installing the new Advanced Search module is not advanced at all! I'll provide you with a couple of snippet examples for you to copy and edit to suit your needs. For each of these, simply copy the code displayed here and replace the Search Module in your wiki's search:site and vola! Let's begin:

"Simple" Advanced Search

"Simple" Advanced Search simply replaces the current search module with one with three extra filter fields for title, author and category.

Change the label

This is similar to the "Simple" Advanced Search - except you are able to define the search button text. This example changes the default "Search!" text with "Find me!".

Hiding filters

This is similar to the "Simple" Advanced Search - except you are able hide certain filter fields. This example hides the title filter field.

Setting default values

This is similar to the "Simple" Advanced Search - except the filter fields can have a default value. This example shows the default title value as being "community".

Enforcing default values

This is the most powerful option of all. It is able to define a default filter criteria and enforce it. In this example, you may set the default search filter to be only searching pages from the _default and doc categories. You are then able to enforce this be not allowing the user to change this option. Even if changed, the final search result will end up displaying the results with the default filter applied. Finally, the category filter is hidden to prevent users from wanting to change it.

Wasn't that easy!? Copy and paste :)
If you have any questions on how to set up this include, leave a comment here or at the CSI site.

~ Kenneth Tsang

by tsangk

First time the Wiki Syntax is translated in Russian:

Now starting: Russian Handbook

1 .I have created the langage dependent structure (ru)
2. I inserted the language dependent forum category on the side bar.

Regards
Helmut

by Helmuti_pdorf

and in "Beta": Edmund the Wikidot Explorer (with Mass-Edit)

If you beleive there is your app missing - please inform us with a comment!
The Link to the "Overview page" is inserted (like the featured sites) in the top menu "News" and in the left menu under APP's for Wikidot.

by Helmuti_pdorf

This site brings you a place to:

• Instantly test CSS code
• Store CSS code for future use
• Tweak your CSS themes before pushing them live on your website

Check it out for yourself!!!

by James Kanjo

An example of this in action:

To add a list like this in your own site, saving pages to the 'todo' category, use this code:

by Helmuti_pdorf

=> Look at the "tags" displayed after the tweet button!

Done with

 [[module CSS]] .site-actions div { float: left; margin-right: 10px; } .site-actions div a { color: #fff; background: #f7f; border: 1px solid #999; padding: 2px 10px 3px; text-decoration: none; -moz-border-radius: 5px; -webkit-border-radius: 5px; border-radius: 5px; text-shadow: 1px 1px 1px #bbb; opacity: 0.8; } .site-actions div a:hover { opacity: 1; } .site-actions div.redcolor a { background: #7ff; } .site-actions div.greencolor a { background: #f7f; } [[/module]] A syntax implementation makes it possible: We can use a new standalone @@[[@@**button set-tags +_tag1 -_tag2 text="Change tags"**@@]]@@ to update tags of a page with predefined settings.. - Documentation is here: [*http://www.wikidot.com/doc:wiki-syntax#toc61 Button for tag update] and some examples of usage now following : [[div class="site-actions"]] [[iftags -good -notgood]] [[div class="greencolor"]] ||~ Good ? || [[button set-tags +good -notgood text="mark as good or:"]] || ||~ Notgood ? || [[button set-tags +notgood -good text="mark as notgood"]] || [[/div]] [[/iftags]] [[iftags -open -closed]] [[div class="greencolor"]] ||~ Open ?|| [[button set-tags +open -closed text="mark as open or:"]] || ||~ Closed ?|| [[button set-tags +closed -open text="mark as closed "]] || [[/div]] [[/iftags]] [[iftags +good]] [[div class="redcolor"]] ||~ Notgood ?|| [[button set-tags +notgood -good text="mark as notgood (+ clear good)"]] || [[/div]] [[/iftags]] [[iftags +open]] [[div class="redcolor"]] ||~ Closed ?|| [[button set-tags +closed -open text="mark as closed (+ clear open)"]] || [[/div]] [[/iftags]] [[iftags +closed]] [[div class="greencolor"]] ||~ Open ? || [[button set-tags +open -closed text="mark as open (+ clear closed)"]] || [[/div]] [[/iftags]] [[iftags +notgood]] [[div class="greencolor"]] ||~ Good ?|| [[button set-tags +good -notgood text="mark as good (+ clear notgood)"]] || [[/div]] [[/iftags]] [[/div]] ~~~~ 

by Helmuti_pdorf

I made this copy after a request of a wikidot user.

by Helmuti_pdorf

• Threads,
• Tasks,
• Sticky Threads,
• Sub-task ,
  • subtaks to subtaks
    • subtaks to subtaks

a.s.o.
Any comments are welcome here or on this admin-forum :)

Here is a short copy of the playground admin forum description:
After the question in a german wiki how to make a non-commented forum for admins only I copied some pages and categories for an own "admin" forum:
this is a "page"-based solution for people who wants to have an "admin-forum" inside their Wiki - only viewable & editable by admins - without any comments of the per page discussions (which would be viewable).
Thanks to the Forum-Template from pieterh and the team - build out of the Projects site.
And thanks to the nocomment forum of leiger where I have learned that comments are not really neccessary…
This solution here is not (yet) a perfect one - I would like to chage the threads more to the nocomment forum layout…

To be honest - this solution is working with the "view and all other" -permissions checked out for specific "admin-.." categories, but this is not really 100% "secure and private"!. Some tricky members with a really very good wikidot knowledge can find a way to see and read the content of the amin-forum pages. But it is not easy and the trick is not written here.

Why an admin forum?

Often we got the question - "how can I make an admin forum for admins-only" - not viewable for all other visitors/memenrs. There are some discussions like design& layout setup , specific permission decisions which are not to be discussed in the standard open forum - viewable to all others.
On the community site we had taken the decision to use a parallel "private" site only for such an admin-forum. But with all problems of administration of membership ( the admins of the other , original site). Tthis is easy to insttall, maintain and use and needs only a link to it. But it costs a "private site" with limited membership for free accounts.

Why not on hidden foruum categories?

The standard forum has hidden categories ( like the deleted threads) - but you cannot stop visitors going back to the forum - hidden group and scroll throu the hidden Threads .

Why on pages?

The standard Forum is NOT included in any backup.zip file created out of the site manager ( for personal downloads) .
Means - if someone ( admin) deletes all the forum pages and categories - all is gone….

Why no comments on such admin-pages?

All "Per Page Discussions" ( = Comments) are stored om the standard forum - and therefore viewable again.

=> On this admin-forum solution all the per page discussions are switched off means"disabled" for the used "admin…" categories.

BUT: if you wish to use this forum for your own standard forum - than you can open the comments ( and allow it) in the "admin-thread:_template" where at the moment the module comments are out-commented ( :) )

How is it done with the "private" part?

All used "admin.." categories are in the permissions set to no one checked box - all is disallowed for them… only admins can use the pages
And for better service for unauthorized visitors - landing on such "admin.." category & page - there is the explaination on the specific "_public" pages - which says only - sorry, this admin pages are only allowed for admins.". or so..

Can i use a different nav:side menu ?

The "admin-nav:side" page ( with the joined "_public" page - see above) can be used to show a complete different nav-side menu for such "admin..: ." pages .
=> The setup is done in the Site Manager - Appearance - Navigation elelments

How can I make use of it now?

Transfer (= Copy the source, tags and parenting ) all the listed pages in the 4 categories:
"admin-forum" - the overview pages
"admin-section" - the sections of the forum ( like categories in the standard forum)
"admin-nav:side" - one page exta if used with a different layout for admins only..
"admin-threads" - the Thread - Pages - autonumbered in the site manager!
( from this threads you need not to copy all numbered threads - only the starting number - if you want 1-3 )

if you want you can make the (standard) "admin:" categorie private too - and create the neccessary "admin:_public" page for it.
( and can than include this page in all other "admin-…:_public" pages)

What setup is to be done in Site manager?

After the copy of the existing pages in these 4 categories you have to setup in the site manager following:

1. Check off all "Permission"-boxes of these 4 categories in the site manager - this makies the categories non "_publilc"
2. Set in the Forum - "Per Page discussions" - all 4 categories on "disabled" - this prevents from using the discuss button or comments module
3. if using it - set in the Appearance - Navigations the "admin-nav:side" as the nav:side menu for all these used "admin.." categories.

Is it worth all this work?

I think - there is a section like "Design" - where the admins have to discuss & store the outcome of important discussions like

• Forum groups and categories
• Forum - Permissions for whom ( registered users, members, anonymous)
• wiki structure
• menues
• Multilingual setup
• Comments allowed - and how? - Discuss button using or module comments in Templates?

Big Benefits are

• the "open tasks" - (Thread - tagged with "_task" ) with the "Open tasks" -list in the "admin-nav:side"
• to "_close" Threads by tagging !
• Sub-Threads ( nesting) into an endless level by pareting (ok, could be senseless)

Are there Cross Sites Includes?

Yes, there are some includes from "modules" site used.:
:modules:include:3 (in the section: and thread:_templates)

Where can I see it working?

In our playground site are these categories OPEN to view! (OTHERWISE YOU CANNOT COPY IT!)

Have a look on the Playground-admin-forum - and if you want - you can start and test and write whatever you want in the "General-test" section:

• Threads,
• Tasks,
• Sticky Threads,
• Sub-task ,
  • subtaks to subtaks
    • subtaks to subtaks

a.s.o.

by Helmuti_pdorf

by Helmuti_pdorf

bcammo

At the end of this blog you will see such "tweet" button. If you have a twitter account you need only to press this button and a little edit window opening to tweet a short text ( whatever you want) about this blog entry will give you the chance to tweet it under your user-id.
The counter left side of the button counts how many pwoplw have pressed this button…

Done on the "live _template" of blog: category with

 [[include :snippets:tweet-button |url=%%link%% |text=%%title%% |via=wikidot |count=horizontal |align=left ]] 

by eichbehl

As long as Wikidot team will not change or allow us our "localization" of the screen text we have a problem in every language..

regards
Helmut

by Helmuti_pdorf

What I share with the Community website ? The birthdate.
The Community was 4 years old on 1 Aug , add 44 45 and you'll know more about me. (déjà vu)

by gerdami

• help:autonumbering-of-pages feature for unique "primary keys per row's of the 2 categories (" db3country:", " db4town:");
• db3country:_template]] for showing and creating records over prepared newpage modules in the country table - using data-forms
• db4town:_template]] for showing and creating records in the town table using data-forms
• " the pagepath concept" for both table-records to have "outer join" links in the pages/records one to each other.

Every visitor is invited to test , create new entries and evaluate the Database!

I am awaiting your Comments!
(here or on the "Community-playground" - with the discuss Buttons
regards
Helmut

by Helmuti_pdorf

That means that tomorrow, it will be Wikidot.com's fourth birthday!

by leiger

I've named it the Specific Users Only Include, or SUO for short. It's easy to use, and I encourage you to test it out!

An example of the SUO Include in action is right here:

Enjoy!

by James Kanjo

To find out how to use this new feature, you can read the recently-updated Use html scripting How-To page right here on the Wikidot Community site!

Feel free to use the forums if you have any questions!

Example:

 [[html]] <h2>Custom HTML</h2> <p>Something else</p> <img src="http://community.wikidot.com/local--files/files/dataform.png" alt="hello ;-)"/> [[/html]] 

test from private Site:

 [[html]] <h2>Custom HTML from private Site</h2> <p> A Picture from a private site - if you are not a member of this site you will see (hopefully) only the "alt" text </p> <img src="http://privat-archiv-support.wikidot.com/local--files/images/Card_snap0014.jpg" alt="Privat Site! ;-)"/> [[/html]] 

by leiger

February 16, 2010 - Ed Johnson

Have you found certain Wikidot page elements that are all but impossible to style with CSS because the styles are hard-coded into the page? This how-to shows you a technique to override those stubborn styles.

Override Inline Styles With CSS

by Ed Johnson

And the "landing" page for visitors without the View allowance is called "category:_public"
which can hold the relevant information like:

by Helmuti_pdorf