Fullscreen

Forum: [edu.tw.o] Development Help

Forums > [edu.tw.o] Development > ws doubts

ws doubts


posts: 25 3 stars
A problem for me in trying workspaces is the lack
of knowledge about what it was supposed to do.

I produced a patch to make aulawiki-1.6 work on tw-2.2 without ever knowing what aulawiki-1.5 was doing in tw 1.9

So I would like to point a few major doubts I've been carrying with
me for a while, probably common to anyone trying to evaluate workspaces for any project

1) How can 'teacher' create a GrupoC?
Can he be limited to create GrupoC only of predefined
types? Be/become automatically admin of 'GrupoC'?
2) tiki_p_admin_workspace
Should having object perms 'p_admin_workspace' on a
workspace allow you to to assign perms to all WS resources?
And also to all/certain child workspaces'?
3) is 'Owner' a special role that has not to be deleted and how
can one replicate its role setup? Has it to do with
'Portfolio'and 'Personal' WS types and how can be replicated?
4) workspace_resources module
Was the 'New Category' button in the admin bar intended to
create a child workspace?
Why are child workspaces listed as categories and can be
deleted as categories?
Sure new ones will come in mind.

Then, as a developer, I'd like to ask you links to any docu, mailing
lists periods, whatever to search about discussions held at the
design of workspaces and its features

pingus


rlopez posts: 32 3 stars
Pingus, everything you point is really interesting. Thanks! biggrin

We have to have something in mind all the time: workspaces are going to become part of tiki x.x as a feature. Because of this, it's important to start working in two parallel directions: one to improve/correct workspaces, other to integrate them in tiki. Both teams must travel in the same (like we are doing wink !).

I really believe that if we get a very stable aulawiki+workspaces mod, then the integration in tiki is going to be easier.

About the links ...
Well, one feature that it's going to play a vey important role in the new scenario is the profile. And not only in the integration of workspaces in tiki, but also in the management of them.
Data channels and profiles will let the teachers (for example), to create their own workspaces. In the last tikifest in Madrid, Javier Reyes (the author of aulawiki) mentioned that an abstraction layer to manage resources is a must. Profiles and data channels are supposed to do this. So we have to take them into account in the new workspaces, definitely.

I ask you to join the discussion of all these things here.

Other interesting links to read/watch:
-Workspaces
-The videos Xavi has uploaded in the wiki page for the tikifest in Madrid. By the way, Xavi, congratulations!


posts: 25 3 stars
> Well, one feature that it's going to play a vey important role in the new scenario is the profile.

Yes, I read about profiles, ant it's a logic tool, that can be fun to provide and very practical for an end user to use.

I am actually making my steps up from the code and the actual features/design, so the questions I posed are really important.

I am trying to see what and how can/should be done, then building a container/menu/replicable-profile is just a question of providing the correct links/variables to do it.

Being simplicistic, at the moment I can see a few choices:

a workspace type where, who has tiki_p_admin_workspace objectperms on it, can:
-admin the ws object's itself objectpermissions
-assign individual objectpermissions to all other objects of the WS
-create child workspaces only of a certain type (was that the case
of PERSONAL/PORTFOLIO private sub workspaces?)
-optionally do the same on all/ child workspaces, included
adding parent's WSGRPs with their objectpermissions to them

with 1.6.3x I realized that these things ('teacher' creates a new sub workspaces, 'teacher' admins all WS object perms, 'teacher' admins sub ws, 'teacher' adds parent's ws roles to child workspace) can be done/not done by twiddling with 'tiki_p_admin_workspace object permission of a workspace and this can be made heritable on child workspace type objects. Still messy, but I see it can be done.

> Data channels and profiles will let the teachers (for example), to create their own workspaces.
In the last tikifest in Madrid, Javier Reyes (the author of aulawiki) mentioned that an abstraction layer to manage resources is a must.

Where is he then? :-)
I think he knows a lot about this all.

Giancarlo Pinerolo 'pingus


xavi posts: 138 5 stars

> Being simplicistic, at the moment I can see a few choices:
>
> a workspace type where, who has tiki_p_admin_workspace objectperms on it, can:
> -admin the ws object's itself objectpermissions
ok
> -assign individual objectpermissions to all other objects of the WS
ok
> -create child workspaces only of a certain type (was that the case
> of PERSONAL/PORTFOLIO private sub workspaces?)
yes

> -optionally do the same on all/ child workspaces, included
> adding parent's WSGRPs with their objectpermissions to them

yes, pingus, your design is desirable!

> with 1.6.3x I realized that these things ('teacher' creates a new sub workspaces, 'teacher' admins all WS object perms, 'teacher' admins sub ws, 'teacher' adds parent's ws roles to child workspace) can be done/not done by twiddling with 'tiki_p_admin_workspace object permission of a workspace and this can be made heritable on child workspace type objects. Still messy, but I see it can be done.
>
> > Data channels and profiles will let the teachers (for example), to create their own workspaces.
> In the last tikifest in Madrid, Javier Reyes (the author of aulawiki) mentioned that an abstraction layer to manage resources is a must.
>
> Where is he then? :-)
> I think he knows a lot about this all.

Yes, pingus, you are right, he knows a lot. He did his best coming along to the recent TikiFestMadrid to explain as much as possible in person of what he had done up to date, and unluckily, he's not able to keep coding the workspaces anymore (according to what he told us), but told rlopez, mangapowerx and aldo on some hints on where and how to keep going.

> Giancarlo Pinerolo 'pingus

Thanks for all your work, Giancarlo.

We are all doing our best to make Tiki (code and community) grow better (and more bug free).


rlopez posts: 32 3 stars
>
> > Being simplicistic, at the moment I can see a few choices:
> >
> > a workspace type where, who has tiki_p_admin_workspace objectperms on it, can:
> > -admin the ws object's itself objectpermissions
> ok
> > -assign individual objectpermissions to all other objects of the WS
> ok
> > -create child workspaces only of a certain type (was that the case
> > of PERSONAL/PORTFOLIO private sub workspaces?)
> yes
>
> > -optionally do the same on all/ child workspaces, included
> > adding parent's WSGRPs with their objectpermissions to them
>
> yes, pingus, your design is desirable!

I agree with you on all these points biggrin , and thanks for all the work. I will test 1.6.3 this week, probably on friday (busy week).


Xavi, do you know if the people in Montreal are going to update mods.tikiwiki.org with 1.6.2.b? The code from pingus and I is up in the svn server.

Pingus I have seen you uploaded a tar file with the files you modified from 1.6.2.b to 1.6.3x in the tracker. Thanks! This friday I will commit the changes if they for me in tiki 3 wink

We stay in contact.


posts: 25 3 stars

> Pingus I have seen you uploaded a tar file with the files you modified from 1.6.2.b to 1.6.3x in the tracker. Thanks! This friday I will commit the changes if they for me in tiki 3 wink

I'd tell you to try 1.6.3x through, especially as 'teacher' or whatever sub-admin you prefer.
The major change is capability to admin perms of all ws objects, and of child ws and child ws objects (if he has'tiki_p_admin_workspace' for parent ws in RolePerms) through navigating child workspaces from the resources module (that keeps 'current workspace' set to the parent)

There's an errant bug that when he edits a wiki page with categories enabled site-wise, page looses its category and workspace.
You need to uncheck
"Permission to all (not just any) of an object's categories is required for access" in tiki-admin.php?page=category
Maybe that's solved in the cvs version or in 3.0.
Also I could't allow categorization of resources (eg show categories in editing a page) if not by acting on global perms, as I wrote in tiki-devel

good luck

giancarlo pingus


xavi posts: 138 5 stars
> -The videos Xavi has uploaded in the wiki page for the tikifest in Madrid. By the way, Xavi, congratulations!

Thanks, a pleasure (I'm slowly learning how to use my video camera and some basic edition skills with kdenlive ;-)



xavi posts: 138 5 stars
HI Pingus:

> A problem for me in trying workspaces is the lack
> of knowledge about what it was supposed to do.
> I produced a patch to make aulawiki-1.6 work on tw-2.2 without ever knowing what aulawiki-1.5 was doing in tw 1.9

Yes, what you are doing is really brave! A pity you couldn't attend to that meeting in Madrid.

> So I would like to point a few major doubts I've been carrying with
> me for a while, probably common to anyone trying to evaluate workspaces for any project
>
> 1) How can 'teacher' create a GrupoC?
> Can he be limited to create GrupoC only of predefined
> types? Be/become automatically admin of 'GrupoC'?

Pingus, that was not coded, as far as I know, but it would be vdery welcome if possible.
As far as I know, where AulaWiki has been used for production, it was the admin (or a single user with admin rights for all workspaces) the one creating them, etc.
But it would be much much more versatile if they could be managed as you say, pingus.

> 2) tiki_p_admin_workspace
> Should having object perms 'p_admin_workspace' on a
> workspace allow you to to assign perms to all WS resources?

I would say yes.

> And also to all/certain child workspaces'?

I would say yes, making it optional (like nowadays, with a checkbox on admin categories, where you can select to apply that to that categ. or also to their childs. So similarly, "allow local admin of this workspace to assign permissions to this workspaces and their children?" (or similar)


> 3) is 'Owner' a special role that has not to be deleted and how
> can one replicate its role setup? Has it to do with
> 'Portfolio'and 'Personal' WS types and how can be replicated?

As far as I know, yes, owner is for personal oprtfolio and learning folders, etc.
"How can it be replicated?" no idea

> 4) workspace_resources module
> Was the 'New Category' button in the admin bar intended to
> create a child workspace?

No idea. Workspaces were creating through the admin interface reported in the documentation (which has images for the workspaces documentation again in edu.tw.o)

> Why are child workspaces listed as categories and can be
> deleted as categories?

? Workspacs are not intented to be managed through categories, but through admin workspaces, afaik. I don't know the code behind, but would it be that if you delete a workspace through categories, you have some left voers in tiki from that workspace? Anyway, nowadays that in Tiki 2+, categories can have the tiki_p_view_categories, (and tiki_p_edit_categorized), those category names from workspaces could be hidden from the list to users or admins, if they shouldn't be able to delete workspaces through categories... (my 2 cents)

> Sure new ones will come in mind.
>
Yes, sure. Thanks for finding way to improve the code further, pingus! :-)

> Then, as a developer, I'd like to ask you links to any docu, mailing
> lists periods, whatever to search about discussions held at the
> design of workspaces and its features

They were initially discussed in Spanish, linked to http://gclub.ub.es/carpetiki/ project. But that project is not alive any more (funding finished, etc.)
So most things are the ones you can see in this site, and the documentation in this site also.

> pingus

Xavi



posts: 25 3 stars
> > > 2) tiki_p_admin_workspace
> > > Should having object perms 'p_admin_workspace' on a
> > > workspace allow you to to assign perms to all WS resources?
> >
> > I would say yes.
>
> Then you should try 1.6.3x
> Working as 'teacher', with most of the objectperms needed in the RolePerms template, most can be done from the resources module, where you can assign object perms to WS resources, create new ones, and also navigate to child ws still keeping parents' ws, if you've admin on it, so add parents' grup to child and be able to create new objects in child. (key and spanner icons next to the first resource, the workspace itself)
>
> To do this 'teacher' (admin role of parent's) needs to have tiki_p_admin_workspace' and 'tiki_p_create_workspace_resour'
> This needs a switch (new perm? new parent's hardcoded object type? are Personal an Portfolio of these types), or maybe state that having both these perms on parent's is enough?
>
> To allow creation of a new child ws needs modifying tiki_workspaces_admin.php.
>
> > > And also to all/certain child workspaces'?
> >
> > I would say yes, making it optional (like nowadays, with a checkbox on admin categories, where you can select to apply that to that categ. or also to their childs.
>
> Looks like this was thought in conjuction with categories, I'm missing the trait d'union...
>
> Giancarlo


Show posts:
Jump to forum:

For more information, please see Wiki Page Editor & Wiki Syntax

Wiki Syntax
Bold text     __text__
Italic text     2 single quotes (').     ''text''
Underlined text     ===text===
Colored text
~~#FFEE33:text~~ or ~~yellow:text~~. Will display using the indicated HTML color or color name. Color name can contain two colors separated by a comma. In this case, the first color would be the foreground and the second one the background.
Deleted text     2 dashes "-".     --text--
Headings
!heading1, !!heading2, !!!heading3
Show/Hide
!+, !!- show/hide heading section. + (shown) or - (hidden) by default.
Autonumbered Headings
!#, !!#, !+#, !-# ...
Table of contents
{toc}, {maketoc} prints out a table of contents for the current page based on structures (toc) or ! headings (maketoc)
Horizontal rule     ----
Text box     ^Box content^
Centered text     ::text::
Dynamic variables
%Name% Inserts an editable variable
External links
use square brackets for an external link: [URL], [URL|link_description],[URL|link_description|relation] or [URL|description|relation|nocache] (that last prevents the local Wiki from caching the linked page; relation can be used to insert rel attribute for the link - useful e.g. for shadowbox).
For an external Wiki, use ExternalWikiName:PageName or ((External Wiki Name: Page Name))
Square Brackets
Use [[foo] to show [foo].
Wiki References
JoinCapitalizedWords or use ((page)) or ((page|description)) for wiki references , ))SomeName(( prevents referencing
Lists
* for bullet lists, # for numbered lists, ;Word:definition for definiton lists
Indentation
+, ++ Creates an indentation for each plus (useful in list to continue at the same level)
Tables
||row1-col1|row1-col2|row1-col3
row2-col1|row2-col2|row2-col3||
Title bar     -=Title=-
Monospace font     -+Code sample+-
Line break
%%% (very useful especially in tables)
Drawings
{draw name=foo} creates the editable drawing foo
Multi-page pages
Use ...page... to separate pages
Non parsed sections
~np~ data ~/np~ Prevents wiki parsing of the enclosed data.
Preformated sections
~pp~ data ~/pp~ Displays preformated text/code; no Wiki processing is done inside these sections (as with np), and the spacing is fixed (no word wrapping is done). ~pre~ data ~/pre~ also displayes preformatted text with fixed spacing, but wiki processing still occurs on the text.
Comments
~tc~ Tiki Comment ~/tc~ makes a Tiki comment. It will be completely removed from the display, but saved in the file for future reference. ~hc~ HTML Comment ~/hc~ makes an HTML comment. It will be inserted as a comment in the output HTML; these are not normally displayed in browsers, but can be seen using "View Source" or similar.
Block Preformatting
Indent text with any number of spaces to turn it into a monospaced block that still follows other Wiki formatting instructions. It will be indended with the same number of spaces that you used. Note that this mode does not preserve exact spacing and line breaks; use ~pp~...~/pp~ for that.
Direction
{r2l}, {l2r}, {rm}, {lm}Insert resp. right-to-left and left-to-right text direction DIV (up to end of text) and markers for langages as arabic or hebrew.
Special characters
~hs~ hard space, ~c~ ©, ~amp~ &, ~lt~ <, ~gt~ >, ~ldq~ “, ~rdq~ ”, ~lsq~ ‘, ~rsq~ ’, ~--~ —, ~bs~ \, numeric between ~ for html numeric characters entity

Because the Wiki paragraph formatting feature is off, each line will be presented as you write it. This means that if you want paragraphs to be wrapped properly, a paragraph should be all together on one line.

Plugins Help

Note that plugin arguments can be enclosed with double quotes ("); this allows them to contain , or = or >.


Description
Attachment Help
Displays an attachment or a list of them
{ATTACH(
[ name="Gives the name of the attached file to link to" ]
[ file="Same as name" ]
[ page="Gives the name of another page the attached file is on. The file on that page is linked to instead. Only works with wiki pages" ]
[ showdesc="Shows the description as the link text instead of the file name" ]
[ bullets="Makes the list of attachments a bulleted list" ]
[ image="Says that this file is an image, and should be displayed inline using the img tag" ]
[ inline="Puts the stuff between {ATTACH} tags as the link text instead of the file name or description" ]
[ all="Shows all attachments from the whole wiki" ]
[ num="Gives the number, in the list of attachments, of the attachment to link to" ]
[ id="Gives the actual id of the attachment to link in. You probably should never use this" ]
[ dls="Puts the number of downloads in the alt comment" ]
[ icon="Shows a file icon" ]
)}
Comment
{ATTACH}
Box Help
Insert theme styled box on wiki page
{BOX(
[ title="Displayed above the content" ]
[ bg="As defined by CSS, name or Hex code." ]
[ width="In pixels or percentage. Default value is 100%." ]
[ align="left|right|center" ]
[ float="left|right, for box with width lesser than 100%, make text wrap around the box." ]
[ class="Apply custom CSS class to the box." ]
)}
text
{BOX}
Category Help
Insert list of items for the current/given category into wiki page
{category
[ id="List of category IDs separated by + signs. ex: 1+2+3. Default will use category of the current page." ]
[ types="List of object types to include in the list separated by plus signs. ex: article+blog+faq+fgal+forum+igal+newsletter+event+poll+quiz+survey+tracker+wiki+img" ]
[ sort="fieldName_asc|fieldName_desc, valid fields: type, created, name, hits, shuffle" ]
[ split="y|n" ]
[ and="y|n" ]
}
Category Orphans Help
Display Tiki objects that have not been categorized
{catorphans
[ objects="wiki|article|blog|faq|fgal|forum|igal|newsletter|poll|quizz|survey|tracker" ]
}
Category Path Help
Insert the full category path for each category that this wiki page belongs to
{catpath
[ divider="String used to separate the categories in the path. Default character is >." ]
[ top="yes|no, default to no" ]
}
Center Help
Centers the plugin content in the wiki page
{CENTER( )}
text
{CENTER}
Chart Help
Displays a chart from TikiSheet. This plugin can be generated by the TikiSheet chart tool.
{CHART(
id="Data sheet ID"
type="BarStackGraphic|MultibarGraphic|MultilineGraphic|PieChartGraphic"
width="Width in pixels."
height="Height in pixels."
[ value="Required for pie charts" ]
[ x="Required for types other than pie chart" ]
[ y0="Required for types other than pie chart" ]
[ y1="" ]
[ y2="" ]
[ y3="" ]
[ y4="" ]
[ color="List of colors to use." ]
[ style="List of styles to use." ]
[ label="Labels for the series or values in the legend." ]
)}
Chart caption.
{CHART}
Code Help
Displays a snippet of code
{CODE(
[ caption="Code snippet label." ]
[ wrap="0|1, Enable word wrapping on the code to avoid breaking the layout." ]
[ colors="Syntax highlighting to use. May not be used with line numbers. Available: php, html, sql, javascript, css, java, c, doxygen, delphi, ..." ]
[ ln="0|1, may not be used with colors." ]
[ wiki="0|1, parse wiki syntax within the code snippet." ]
[ rtl="0|1, switch the text display from left to right to right to left" ]
[ ishtml="0|1, display the content as is instead of escaping HTML special chars" ]
)}
code
{CODE}
Definition List Help
Creates a definition list
{DL( )}
One entry per line. Each line is in "Term: Definition" format.
{DL}
Draw Help
Displays drawings in the wiki page
{draw
name="Name of the drawing to display."
}
Events Help
Includes the list of events from a calendar in the page.
{events
calendarid="Numeric"
[ maxdays="Numeric" ]
[ max="Numeric" ]
[ datetime="0|1" ]
[ desc="0|1" ]
}
Fade Help
Displays a label. On click, the block of content will fade in and fade out.
{FADE(
label="Label to display on first display"
)}
Wiki syntax containing the text to display.
{FADE}
Fancy List Help
Creates a fancy looking list
{FANCYLIST(
[ div="Use div instead of ol" ]
[ class="CSS class of the fancylist" ]
)}
One item per line starting with anything followed by ")".
{FANCYLIST}
Fancy Table Help
Displays the data using the Tikiwiki odd/even table style
{FANCYTABLE(
[ head="Heading row of the table, same format as the body section." ]
[ headclass="CSS Class to apply on the heading row." ]
)}
One row per line, cells separated by ~|~.
{FANCYTABLE}
File Help
Displays a link to an attachment to a wiki page and can display an image attachment.
{file
name="Gives the name of the attached file to link to"
[ desc="Comment" ]
[ page="Gives the name of another page the attached file is on. The file on that page is linked to instead. Only works with wiki pages" ]
[ showdesc="Shows the description as the link text instead of the file name" ]
[ image="Says that this file is an image, and should be displayed inline using the img tag" ]
}
Files Help
Displays a list of files from the File Gallery
{FILES(
[ galleryId="Gallery ID" ]
[ categId="Category ID:Category ID" ]
[ sort="name_asc" ]
[ showaction="y|n" ]
[ showfind="y|n" ]
[ showid="y|n" ]
[ showicon="y|n" ]
[ showname="y|n" ]
[ showfilename="y|n" ]
[ showsize="y|n" ]
[ showdescription="y|n" ]
[ showcreated="y|n" ]
[ showhits="y|n" ]
[ showlockedby="y|n" ]
[ showlmodified="y|n" ]
[ showauthor="y|n" ]
[ showcreator="y|n" ]
[ showgallery="y|n" ]
[ showfiles="y|n" ]
[ slideshow="y|n" ]
)}
Title
{FILES}
Flash video Help
Displays a SWF on the wiki page
{flash
movie="Complete URL to the movie to include."
[ width="Default width: 425" ]
[ height="Default height: 350" ]
[ quality="Flash video quality. Default value: high" ]
}
Group Help
Display wiki text if user is in one of listed groups
{GROUP(
[ groups="Pipe separated list of groups allowed to view the block. ex: Admins|Developers" ]
[ notgroups="Pipe separated list of groups denied from viewing the block. ex: Anonymous|Managers" ]
)}
Wiki text to display if conditions are met. The body may contain {ELSE}. Text after the marker will be displayed to users not matching the condition.
{GROUP}
Img
Displays an image.
{img
[ src="Full URL to the image to display." ]
[ alt="Alternate text to display if impossible to load the image." ]
[ height="Height of the image to display." ]
[ width="Width of the image to display." ]
[ link="Alias: lnk. Location the image should point to." ]
[ rel=""rel" attribute to add to the link." ]
[ title="Description." ]
[ align="Image alignment in the page. (left, right, center) Uses HTML IMG tag." ]
[ imalign="Image alignment in the flow of the document. (left, right, none) Uses CSS float property." ]
[ desc="Image description to display on the page." ]
[ usemap="Name of the image map to use for the image." ]
[ class="Style to apply to the image." ]
}
Include Help
Include a page's content.
{include
page="Wiki page name to include."
[ start="When only a portion of the page should be included, specify the marker from which inclusion should start." ]
[ stop="When only a portion of the page should be included, specify the marker at which inclusion should end." ]
}
Language Help
Displays the text only if the language matchs
{LANG(
[ lang="List of languages for which the block is displayed. Languages use the two letter language codes (ex: en, fr, es, ...). Multiple languages can be specified by separating codes by + signs." ]
[ notlang="List of languages for which the block is not displayed. Languages use the two letter language codes (ex: en, fr, es, ...). Multiple languages can be specified by separating codes by + signs." ]
)}
text
{LANG}
Mediaplayer Help
Simple mp3 or flv Player
{mediaplayer
[ mp3="Complete URL to the mp3 to include." ]
[ flv="Complete URL to the flv to include." ]
[ style="One of:mini|normal|maxi|multi" ]
}
Mini Quiz Help
Displays a miniquiz
{MINIQUIZ(
trackerId="Tracker ID"
)}
Instructions::Feedback
{MINIQUIZ}
Insert Module Help
Displays a module inlined in page. More parameters can be added, not supported by UI.
{module
module="Module name as known in Tikiwiki."
[ float="left|right|none" ]
[ decoration="y|n" ]
[ flip="y|n" ]
[ max="y|n" ]
[ np="0|1" ]
[ notitle="y|n" ]
}
Mouse Over Help
Create a mouseover feature on some text
{MOUSEOVER(
label="Text displayed on the page. The body is the mouseover content"
[ url="Destination link when moused-over text is clicked. Use http:// for external links" ]
[ text="DEPRECATED Text displayed on the mouseover. The body contains the text of the page." ]
[ width="Mouse over box width. Default: 400px" ]
[ height="Mouse over box height. Default: 200px" ]
[ offsetx="Shifts the overlay to the right by the specified amount of pixels in relation to the cursor. Default: 5px" ]
[ offsety="Shifts the overlay to the bottom by the specified amount of pixels in relation to the cursor. Default: 0px" ]
[ parse="y|n, parse the body of the plugin as wiki content. (Default to y)" ]
[ bgcolor="Default: #F5F5F5" ]
[ textcolor="#FFFFFF" ]
[ sticky="y|n, when enabled, popup stays visible until an other one is displayed or it is clicked." ]
[ padding="Default: 5px" ]
)}
Mouseover text if param label exists. Page text if text param exists
{MOUSEOVER}
Quote Help
Quote text by surrounding the text with a box, like the [QUOTE] BBCode
{QUOTE(
[ replyto="Name of the quoted person." ]
)}
Quoted text
{QUOTE}
Remarks Box Help
Displays a comment, tip, note or warning box
{REMARKSBOX(
type="tip|comment|note|warning"
title="Label displayed above the remark."
[ highlight="y|n" ]
[ icon="Icon ID." ]
)}
remarks text
{REMARKSBOX}
RSS Feed Help
Inserts an RSS feed output.
{rss
id="List of feed IDs separated by colons. ex: feedId:feedId2"
[ max="Amount of results displayed." ]
[ date="0|1" ]
[ desc="0|1|max length" ]
[ author="0|1" ]
}
Sheet Help
Displays the content of a spreadsheet in the page.
{SHEET(
id="Internal ID of the TikiSheet."
)}
Sheet Heading
{SHEET}
Sort Help
Sorts the plugin content in the wiki page
{SORT(
[ sort="asc|desc|shuffle" ]
)}
Data to sort, one entry per line.
{SORT}
Split Help
Split a page into rows and columns
{split
[ joincols="y|n Generate the colspan attribute if columns are missing" ]
[ fixedsize="y|n Generate the width attribute on the columns" ]
[ colsize="?" ]
[ first="col|line" ]
[ edit="y|n Display edit icon for each section" ]
[ customclass="add a class to customize the design" ]
}
Subscript Help
Displays text in subscript.
{SUB( )}
text
{SUB}
Superscript Help
Displays text in superscript (exponent).
{SUP( )}
text
{SUP}
Thumbnail Help
Displays the thumbnail for an image
{THUMB(
[ file="File ID from the file gallery." ]
[ id="Image ID from the image gallery." ]
[ image="URL to the image." ]
[ max="Maximum width or height for the image." ]
[ float="left|right|none" ]
[ url="Link target of the image." ]
[ original="y|n" ]
[ sticky="y|n" ]
)}
description
{THUMB}
Top Friends Help
List top scoring users.
{topfriends
[ limit="Maximum result count." ]
[ public="y|n" ]
}
Tracker Help
Displays an input form for tracker submit
{TRACKER(
trackerId="Tracker ID"
fields="Colon-separated list of field IDs to be displayed. Example: 2:4:5"
[ action="Label on the submit button" ]
[ showtitle="y|n" ]
[ showdesc="y|n" ]
[ showmandatory="y|n" ]
[ embedded="y|n" ]
[ url="Url used for the field links" ]
[ values="Colon-separated list of values. Note that plugin arguments can be enclosed with double quotes "; this allows them to contain , or :" ]
[ sort="y|n" ]
[ preview="preview" ]
[ view="user|page" ]
[ itemId="itemId if you want to edit an item" ]
[ tpl="Name of the template used to display the tracker items." ]
[ wiki="Name of the wiki page containing the template to display the tracker items." ]
[ newstatus="o|p|c Default status applied to newly created items." ]
[ colwidth="## or ##% Specify the width in pixels or percentage of the first column in the tracker form." ]
)}
Confirmation message after posting form
{TRACKER}
Tracker Filter Help
Filters the items of a tracker, fields are indicated with numeric ids.
{TRACKERFILTER(
trackerId="Tracker ID"
[ fields="Colon-separated list of field IDs to be displayed. Example: 2:4:5" ]
[ sort="y|n" ]
[ popup="Colon-separated list of fields to display on click. Example: 6:7" ]
[ stickypopup="y|n" ]
[ showtitle="y|n" ]
[ showlinks="y|n" ]
[ showdesc="y|n" ]
[ shownbitems="y|n" ]
[ showinitials="y|n" ]
[ showstatus="y|n" ]
[ showcreated="y|n" ]
[ showlastmodif="y|n" ]
[ showfieldname="y|n" ]
[ status="o|p|c|op|oc|pc|opc Which item status to list. o = open, p = pending, c = closed." ]
[ sort_mode="?" ]
[ max="?" ]
[ filterfield="Colon separated list of fields to allow filtering on." ]
[ filtervalue="?" ]
[ exactvalue="?" ]
[ checkbox="?" ]
[ goIfOne="?" ]
[ more="y|n" ]
[ moreurl="?" ]
[ view="user|page Select automatically the item of the current user or the page" ]
[ tpl="?" ]
[ wiki="?" ]
[ view_user="?" ]
[ itemId="List of items Ids" ]
[ url="link url" ]
[ ldelim="?" ]
[ rdelim="?" ]
[ list_mode="y|n If y, value will be truncated" ]
[ export="y|n" ]
[ compute="Sum or average all the values of a field and displays it at the bottom of the table. fieldId/sum:fieldId/avg" ]
filters="Example:2/d:4/r:5"
[ action="Label on the submit button" ]
[ displayList="y|n" ]
[ line="y|n - displays all the filter on the same line" ]
)}
notice
{TRACKERFILTER}
Tracker Item Field Help
Displays the value of a tracker item field or the wiki text if the value of the field is set or has a value(if itemId not specified, use the itemId of the url or the user tracker).
{TRACKERITEMFIELD(
[ trackerId="Numeric value." ]
[ itemId="Numeric value." ]
[ fieldId="Numeric value." ]
[ fields="Colon separated list of field IDs." ]
[ status="o|p|c|op|oc|pc|opc" ]
[ test="0|1" ]
value="Value to compare against."
)}
Wiki text containing an {ELSE} marker.
{TRACKERITEMFIELD}
Tracker List Help
Displays the output of a tracker content, fields are indicated with numeric ids.
{TRACKERLIST(
trackerId="Tracker ID"
[ fields="Colon-separated list of field IDs to be displayed. Example: 2:4:5" ]
[ sort="y|n" ]
[ popup="Colon-separated list of fields to display on click. Example: 6:7" ]
[ stickypopup="y|n" ]
[ showtitle="y|n" ]
[ showlinks="y|n" ]
[ showdesc="y|n" ]
[ shownbitems="y|n" ]
[ showinitials="y|n" ]
[ showstatus="y|n" ]
[ showcreated="y|n" ]
[ showlastmodif="y|n" ]
[ showfieldname="y|n" ]
[ status="o|p|c|op|oc|pc|opc Which item status to list. o = open, p = pending, c = closed." ]
[ sort_mode="?" ]
[ max="?" ]
[ filterfield="Colon separated list of fields to allow filtering on." ]
[ filtervalue="?" ]
[ exactvalue="?" ]
[ checkbox="?" ]
[ goIfOne="?" ]
[ more="y|n" ]
[ moreurl="?" ]
[ view="user|page Select automatically the item of the current user or the page" ]
[ tpl="?" ]
[ wiki="?" ]
[ view_user="?" ]
[ itemId="List of items Ids" ]
[ url="link url" ]
[ ldelim="?" ]
[ rdelim="?" ]
[ list_mode="y|n If y, value will be truncated" ]
[ export="y|n" ]
[ compute="Sum or average all the values of a field and displays it at the bottom of the table. fieldId/sum:fieldId/avg" ]
)}
Notice
{TRACKERLIST}
Tracker Prefill Help
Displays a button to link to a page with a tracker plugin with prefilled tracker fields.
{trackerprefill
page="Tracker page name"
[ label="Button label." ]
field1="Field ID"
value1="Content of the field."
[ field2="Field ID" ]
[ value2="Content of the field." ]
[ field3="Field ID" ]
[ value3="Content of the field." ]
[ field4="Field ID" ]
[ value4="Content of the field." ]
[ field5="Field ID" ]
[ value5="Content of the field." ]
}
Tracker Stats Help
Displays some stat of a tracker content, fields are indicated with numeric ids.
{TRACKERSTAT(
trackerId="Tracker ID"
fields="Colon-separated list of field IDs to be displayed. Example: 2:4:5"
[ show_percent="y|n" ]
[ show_bar="y|n" ]
[ status="o|p|c|op|oc|pc|opc Which item status to list. o = open, p = pending, c = closed." ]
[ show_link="y|n" ]
)}
Title
{TRACKERSTAT}
Tracker Timeline Help
Timeline view of a tracker, can be used to display event schedules or gantt charts.
{trackertimeline
tracker="Numeric value"
title="Tracker Field ID containing the item title."
summary="Tracker Field ID containing the summary of the item. The summary will be displayed on the timeline when the item is focused."
start="Tracker Field ID containing the element start date. The field must be a datetime/jscalendar field."
end="Tracker Field ID containing the element end date. The field must be a datetime/jscalendar field."
group="Tracker Field ID containing the element's group. Elements of a same group are displayed on the same row."
lower="Date from which element should be displayed. Date must be provided in YYYY-MM-DD HH:mm:ss format."
upper="Date until which element should be displayed. Date must be provided in YYYY-MM-DD HH:mm:ss format."
[ scale1="hour, day, week, month or year (default to hour)" ]
[ scale2="hour, day, week, month, year or empty (default to empty)" ]
[ link_group="Convert the group name to a link. (y|n)" ]
[ link_page="Tracker Field ID containing the page name for item details." ]
}
Translated Help
Links to a translated content
{TRANSLATED(
lang="Two letter language code of the language, ex: fr"
[ flag="Country name, ex: France" ]
)}
[url] or ((wikiname)) or ((inter:interwiki)) (use wiki syntax)
{TRANSLATED}
Vote Help
Displays some stat of a tracker content, fields are indicated with numeric ids.
{VOTE(
trackerId="Tracker ID"
fields="Colon-separated list of field IDs to be displayed. Example: 2:4:5"
[ show_percent="y|n" ]
[ show_bar="y|n" ]
[ show_stat="y|n" ]
[ show_stat_only_after="y|n" ]
[ show_creator="y|n" ]
[ status="o|p|c|op|oc|pc|opc Which item status to list. o = open, p = pending, c = closed." ]
[ float="left|right" ]
)}
Title
{VOTE}
Youtube Help
Display youtube video in a wiki page
{youtube
movie="URL to the Youtube video"
[ width="Width in pixels" ]
[ height="Height in pixels" ]
[ quality="quality" ]
}

Menu

Search

in:

Search Wiki PageName

Exact match

Site Language: English

Kindly hosted at:

ourproject.org Logo

Copyleft

Creative Commons License
Content on this site is licensed under a Creative Commons Attribution-ShareAlike 2.5 Spain License.