Category: Workspace

Sometimes, we want people to participate to one wiki page, to access their user tracker to update personal information or access a ((workspace))

Right now, we need to

#create a user
#create a group
#assign user to the group
#give permissions to group ( in general or for a specific item)
#inform this person, typically by email, on how to access this page


Instead, I would want to
#add an email
#pick the permissions this person has
#any limitations (works x times, or for x days/weeks)
#an optional message

And the system should send a 1-click login email (an email with a link in it which is unique / very difficult to guess).

Whoever clicks that link
*Would be authenticated with the appropriate permissions and according to the limitations.


Related:
Expiry date for group membership
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1071

Somewhat related:
Send welcome email (by admin to new user or user that has not connected in a while)
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1016

Contributors

Contributors

Contributors

Guys, I have to set up a company wiki, which is completely structured from top to bottom. So I noticed a very annoying thing about tiki.

Currently if you want to create a page, that is destined to be part of a structure, you have to create it using the navigation bar and set the option "as child".

But what if a user creates a new page from within a structred wiki page? I.E. If he simply sets up a new link to an non existing site. The new page is created as an orphan which is definitely a "no go" for a completely structured wiki. Pages like this have to be manually assigned to a structure by the admin.

So I request an option, that __forces pages created from within a page in a structure to be automatically part of the same structure__.

I guess even in pages like doc.tw.org this would be very helpful.

It would be lovely to set some new user defaults at
* Admin (home) > Login > User defaults, and/or
* Admin > Groups > (Edit a single group)

The ability to Subscribe/watch/monitor new users in the site or to that specific group, to specific Tiki objects.

Which tiki objects?: I would say, in this order:
# specific forums
# specific blogs
# specific calendars
# specific newsletters (ML: we can already subscribe groups to newsletters)
# specific wiki pages
# specific structures
# specific trackers
# specific categories
# new articles

This is specially useful for new users of the site, where they don't know yet how to subscribe to specific areas, etc. Very needed for educational scenarios, but I can see many other places where new users are a bit lost for some time while they learn how to use the Tiki site.

Related:
*[wish988|Forum: Let forum admins/moderators add groups and/or users as watching the forum]
*[tiki-index.php?page=Business%20Plans|Let small business start ups access collaborative sharing where the document being shared is not visible by anyone else]


Anywhere there is a watch eye, it should be possible for an admin to have group members watch this category

When I was testing various CMS/Wikis for a project, I ran across a module for another (Joomla or Drupal, can't remember which) CMS which allowed a user role or group to automatically generate a personal page, an image gallery, a weblog and any type of content page. It would be extremely useful for my project, but one of the few things missing from Tikiwiki (which is why I am implementing Tikiwiki, it has all of the other features I need in one install).

These are more patches on aulawiki.1.6.2 posted by xavi

* Versions 1.6.2x are intended just to make aulawiki work on tikiwiki
2.2, the way it worked before.
* Versions 1.6.3x -1.6.4 were transition step.
* Versions 1.6.5x -1.7.x has put back capability to add groups to the
workspace (not only users), and see all child's groups, starting from
the topmost a user can admin, when adding perms to single workspace
resources.
This was be done by adding some new functions to workspaceslib.php:

- get_includable_child_workspaces_groups : will get all groups in WS and child workspaces, starting from the uppermost on which one has admin objectperm down, purged by veryfing a list of includable groups to avoid loop inclusion.
- user_can_admin_workspace_or_upper(), an alias of
get_topmost_workspace_Iadmin(): will get up in the workspace path and
return an upmost parent workspace one can admin, thus gives him admin
capability on the ws and children, or false.
And in lib/workspaces/userslib.php, function group_can_include_group() will check if the group we are trying to include can be included.

with these functions a RolePerm with tiki_p_admin_workspace has
view of all child workspaces and their groups down from the
topmost one he can admin, no matter in which of these he is actually
(current workspace), and be able to add groups and assign perms to
groups within all these ones (only) without need of of having
tiki_p_admin_workspaces also on any child ws.

To the intermediate objectperm tiki_p_create_workspace_resour has been given as a gift the possibility to add single users, not groups, to the workspace predefined groups. On the other hand he can grant objectperms to his resources choosing among any group that belongs to his 'workspace-level'(brothers workspaces) + his parent's (dad, see what I am doing!)

This behaviour is easily changeable in the code, as the ability to do things is stated at the top, where (object)permissions on the workspace are tested once and translated into variables used throughout the code.

In practice:
===========
*'tiki_p_admin_workspaces' as an objectperm on a WS (got
from the RolePerms template for that type of Workspace) is de-facto a
local Workspace administrator. He can do everything (create new sub workspaces, add groups, change perms) except define new
workspace types and roles, and he sees only groups starting from the
topmost workspace he can admin to the bottom.
*tiki_p_create_workspace_resour, as objectperm on a WS (got from the
RolePerms template for that type of Workspace), can manage objectperms
of his ws resources (excluded the ws object itself) choosing among
a tree of groups that starts at his parent's level (dad, see what I am doing), includes 'brother workspaces' (on the same level, child of the same parent), down to bottom. He is a ''resource manager''. For adding users/groups to the ws, he can only add single users by typing the name, no groups. But if his ws has an admin group, he could add himself there. So __tipically workspaces either have a ws_admin role OR a ws_resource manager role__. On the other hand, a top, empty (no resources) workspace, with only an ws_admin role, would grant administration to all childs.
* For global tiki_p_admin_workspace nothing changes, although he is now prevented from including groups that include the includer, something that would put the entire site down.

For a user that has the approriate objectperms from the roles template
to the workspace (tiki_p_admin_workspace or, with less possibilities,
tiki_p_create_ws_resour, for the workspace object), everything can be
done starting from the resources module that has extra links to create child ws, add users/groups, and assign perms to resources.

The resouces module will show/hide Buttons and icons next to each
resource accordingly to what can be done by the actual type of user.


Most of the modifications happened in :

- tiki-workspaces_objectpermissions.ptp + templates
- modules/mod-workspaces_users_groups.php + templates
- lib/workspaceslib.php (new functions only)
- lib/users.php (new functions only)

With respect to the connection workspaces-categories, nothing should be changed. All categories related code is still there and used as before.

---
New permission scheme 1.7.0:
{CODE()}
1.6.2
------------------------------------------------------------------------
perm allows as allows as
name group perm objectperm
------------------------------------------------------------------------
view_ws - -view the ws

create_resour - -create resour onws

admin_ws do all on any ws -add group/user to ws


1.7.x
-----------------------------------------------------------------------
perm allows as allows as
name group perm objectperm
------------------------------------------------------------------------
view_ws - -view the ws

create_resour - (1) -create resour on ws
(de facto admin resour)
-change perms on ws
resources (excluded
the ws itself)
choosing from the
father ws groups and
childs
(father+brothers-to-bottom)
(3)

-add single users(not groups)
to ws predefined groups

admin_ws -do all on any ws(2) -create child workspaces for
any ws from the topmost ws
he has admin rights

-change perms on ws object
itself & resources &
child-ws objects and
resources choosing from
the topmost ws groups
he has admin rights

-add any groups to any ws
choosing from the
topmost ws groups
he has admin rights

-create child workspaces to
any ws from the topmost ws
he has admin rights

notes:
(1) this slot is free! Can't we use it to allow the creation of an
'organic workspace' of some predefined type with himself as
tiki_p_create_resour objectperm on it?

(2) as he can add the 'admins' group, and add users to it, he is
defacto a tiki_p_admin.
maybe he should only be able to add 'workspaces groups'? This would
make him different from a tiki_p_admin_groups and tiki_p_admin.
see comments and examples of different possiblties in
mod-workspaces_users_groups.php

(3) see comments and examples of different possiblties in
tiki-workspaces_objectpermissions.php
---------------------------------------------------------------------
TODO:
there's quite a lot I think, especially in the interface, making it
nicer and more intuitive.
-Add confirmation steps for various deletion actions
-Deletion of workspace does not delete its objects (should it?)
-test it really hard
-understand first, and maybe integrate, the working of 'Private Zones'
and 'user Workspace types' (isuserWS and userws filed in table).
{CODE}
---
LATEST NOTE:
Version 1.7.x has been committed to svn trunk.
You can now download the up-to-date version (not in mods format though) from:
https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/mods/trunk/features/aulawiki/
The mod in the repository does not provide a working example of these new features, it has the usual Teacher/Student Roles. One has to define roles with 'tiki_p_admin_workspace' and 'tiki_p_create_workspace_resour' to see this in action

Installation of aulawiki fails with this error:

Context:
File tiki-mods.php
Url tiki-mods.php?
Query:
INSERT INTO tiki_menus VALUES (100,'Workspace menu','Sample workspace menu','d');
Values:
Message:
Column count doesn't match value count at row 1
Built query was probably:
INSERT INTO tiki_menus VALUES (100,'Workspace menu','Sample workspace menu','d');

It is too difficult now to watch categories (but the feature works well).

Please see: ((Category Watch DogFood))


on ((SUMO)): [https://bugzilla.mozilla.org/show_bug.cgi?id=498001|Improve UI and feedback for watching categories to say you'll be e-mailed and offer easy way to turn off]

I'm having a problem installing the workspace mod in v. 2.0. I get an error message that indicates that
only 4 fields are being inserted into the table, although the table structure indicates that there are 5
columns. (The missing column appears to be the ICON field.) Is there a known workaround for this problem? I've
thought of modifying the table structure, but I suspect that would be setting up for problems down the road.

Workspaces (from ((doc:Mod AulaWiki)) are half broken on 1.10 since months ago.
Any action which is related to workspce calendar module gives fatal error (blank screen). Adding resources to workspaces also fails:

^
Fatal error: Call to undefined method WorkspaceResourcesLib::get_url_admin_file() in /var/www/tiki110/lib/workspaces/resourceslib.php on line 117
^

On this url (on an updated site to 1.10svn from May 2nd):
[http://moviments.net/cursos/tiki-workspaces_view_module.php?module=workspaces_resources&workspaceId=110]


http://edu.tikiwiki.org is also having the same kind of problem, on a less updated 1.10 site.

Contributors

Added some files with header("location: ../../index.php"); that some are included with PreferencesLib->getDefaults() and redirect to base.

Files:

img/icons/mime/index.php
img/icons/large/index.php
img/icons/sprite/index.php
img/openlayers/dark/index.php
installer/script/index.php
lib/db/index.php
lib/geo/index.php
lib/ajax/index.php
lib/core/Feed/Html/index.php
lib/core/Feed/ForwardLink/index.php
lib/core/Feed/Remote/ForwardLink/index.php
lib/core/Feed/Remote/index.php
lib/core/Feed/index.php
lib/core/Math/index.php
lib/core/Math/Formula/Parser/index.php
lib/core/Math/Formula/Runner/index.php
lib/core/Math/Formula/index.php
lib/core/Math/Formula/Function/index.php
lib/core/Event/index.php
lib/core/Horde/Yaml/index.php
lib/core/Horde/index.php
lib/core/Perms/Check/index.php
lib/core/Perms/Reflection/index.php
lib/core/Perms/index.php
lib/core/Perms/ResolverFactory/index.php
lib/core/Perms/Resolver/index.php
lib/core/Category/index.php
lib/core/Report/index.php
lib/core/Report/Definition/index.php
lib/core/Search/Expr/index.php
lib/core/Search/Type/index.php
lib/core/Search/Type/Factory/index.php
lib/core/Search/Index/index.php
lib/core/Search/Query/index.php
lib/core/Search/Query/WeightCalculator/index.php
lib/core/Search/Formatter/Plugin/index.php
lib/core/Search/Formatter/DataSource/index.php
lib/core/Search/Formatter/ValueFormatter/index.php
lib/core/Search/Formatter/index.php
lib/core/Search/ResultSet/index.php
lib/core/Search/ContentFilter/index.php
lib/core/Search/GlobalSource/index.php
lib/core/Search/index.php
lib/core/Search/ContentSource/index.php
lib/core/TikiDb/index.php
lib/core/WikiParser/index.php
lib/core/FileGallery/index.php
lib/core/Multilingual/Aligner/index.php
lib/core/Multilingual/MachineTranslation/index.php
lib/core/Multilingual/index.php
lib/core/Connect/index.php
lib/core/TikiFilter/index.php
lib/core/Reports/Send/index.php
lib/core/Reports/index.php
lib/core/Services/AuthSource/index.php
lib/core/Services/Draw/index.php
lib/core/Services/File/index.php
lib/core/Services/User/index.php
lib/core/Services/Wiki/index.php
lib/core/Services/Favorite/index.php
lib/core/Services/Object/index.php
lib/core/Services/Category/index.php
lib/core/Services/Report/index.php
lib/core/Services/Comment/index.php
lib/core/Services/Connect/index.php
lib/core/Services/Language/index.php
lib/core/Services/index.php
lib/core/Services/ResultLoader/index.php
lib/core/Services/Exception/index.php
lib/core/Services/Tracker/index.php
lib/core/StandardAnalyzer/index.php
lib/core/StandardAnalyzer/Analyzer/Standard/index.php
lib/core/StandardAnalyzer/Analyzer/index.php
lib/core/StandardAnalyzer/TokenFilter/EnglishStemmer/index.php
lib/core/StandardAnalyzer/TokenFilter/index.php
lib/core/index.php
lib/core/JitFilter/index.php
lib/core/DeclFilter/index.php
lib/core/JisonParser/Wiki/index.php
lib/core/JisonParser/Phraser/index.php
lib/core/JisonParser/index.php
lib/core/Tracker/Field/index.php
lib/core/Tracker/index.php
lib/diff/index.php
lib/ical/iCal/Parser/index.php
lib/ical/iCal/index.php
lib/ical/index.php
lib/ldap/index.php
lib/mail/index.php
lib/logs/index.php
lib/pear/OS/index.php
lib/pear/Net/DNS/RR/index.php
lib/pear/Net/DNS/index.php
lib/pear/Net/LDAP2/index.php
lib/pear/Auth/Yadis/index.php
lib/pear/Auth/OpenID/index.php
lib/pear/Auth/Frontend/index.php
lib/pear/PEAR/REST/index.php
lib/pear/PEAR/Task/Replace/index.php
lib/pear/PEAR/Task/index.php
lib/pear/PEAR/Task/Windowseol/index.php
lib/pear/PEAR/Task/Postinstallscript/index.php
lib/pear/PEAR/Task/Unixeol/index.php
lib/pear/PEAR/Validator/index.php
lib/pear/PEAR/Downloader/index.php
lib/pear/PEAR/Command/index.php
lib/pear/PEAR/Frontend/index.php
lib/pear/PEAR/Installer/Role/index.php
lib/pear/PEAR/Installer/index.php
lib/pear/PEAR/index.php
lib/pear/PEAR/ChannelFile/index.php
lib/pear/PEAR/PackageFile/v2/index.php
lib/pear/PEAR/PackageFile/Generator/index.php
lib/pear/PEAR/PackageFile/Parser/index.php
lib/pear/PEAR/PackageFile/index.php
lib/pear/Minify/CSS/index.php
lib/pear/Minify/index.php
lib/pear/XML_Parser/tests/index.php
lib/pear/XML_Parser/Parser/index.php
lib/pear/XML_Parser/index.php
lib/pear/XML_Parser/examples/index.php
lib/soap/index.php
lib/soap/nusoap/index.php
lib/test/auth/fixtures/index.php
lib/test/auth/index.php
lib/test/core/Math/index.php
lib/test/core/Math/Formula/DummyFunction/index.php
lib/test/core/Math/Formula/index.php
lib/test/core/temp/cache/index.php
lib/test/core/temp/index.php
lib/test/core/Event/index.php
lib/test/core/Perms/Check/index.php
lib/test/core/Perms/Reflection/index.php
lib/test/core/Perms/index.php
lib/test/core/Perms/ResolverFactory/index.php
lib/test/core/Perms/Resolver/index.php
lib/test/core/Category/index.php
lib/test/core/Search/Expr/index.php
lib/test/core/Search/Index/index.php
lib/test/core/Search/Query/index.php
lib/test/core/Search/Formatter/index.php
lib/test/core/Search/GlobalSource/index.php
lib/test/core/Search/index.php
lib/test/core/TikiDb/index.php
lib/test/core/WikiParser/index.php
lib/test/core/Multilingual/Aligner/index.php
lib/test/core/Multilingual/MachineTranslation/index.php
lib/test/core/Multilingual/index.php
lib/test/core/Connect/index.php
lib/test/core/TikiFilter/index.php
lib/test/core/Reports/Send/index.php
lib/test/core/Reports/fixtures/index.php
lib/test/core/Reports/index.php
lib/test/core/Request/index.php
lib/test/core/Services/index.php
lib/test/core/index.php
lib/test/core/JitFilter/index.php
lib/test/core/DeclFilter/index.php
lib/test/core/Transition/index.php
lib/test/shipping/index.php
lib/test/Calendar/index.php
lib/test/editlib/index.php
lib/test/reporstlib/index.php
lib/test/reportslib/index.php
lib/test/attributes/index.php
lib/test/comments/index.php
lib/test/freetag/index.php
lib/test/smarty_tiki/index.php
lib/test/IntegrationTests/index.php
lib/test/wiki-plugins/index.php
lib/test/index.php
lib/test/rating/index.php
lib/test/AcceptanceTests/utils/index.php
lib/test/AcceptanceTests/index.php
lib/test/payment/index.php
lib/test/TikiLib/index.php
lib/test/importer/fixtures/index.php
lib/test/importer/index.php
lib/test/language/FileType/index.php
lib/test/language/fixtures/index.php
lib/test/language/index.php
lib/test/language/WriteFile/index.php
lib/accounting/index.php
lib/codemirror_tiki/mode/r/index.php
lib/codemirror_tiki/mode/tiki/index.php
lib/codemirror_tiki/mode/index.php
lib/codemirror_tiki/index.php
lib/equation/index.php
lib/shipping/custom/index.php
lib/shipping/ups-wsdl/index.php
lib/shipping/index.php
lib/metadata/index.php
lib/videogals/index.php
lib/credits/index.php
lib/graph-engine/index.php
lib/svg-edit_tiki/index.php
lib/profilelib/index.php
lib/prefs/index.php
lib/setup/index.php
lib/sheet/conf/index.php
lib/sheet/include/org/index.php
lib/sheet/include/org/apicnet/io/OOo/index.php
lib/sheet/include/org/apicnet/io/OOo/objOOo/index.php
lib/sheet/include/org/apicnet/io/index.php
lib/sheet/include/org/apicnet/io/archive/index.php
lib/sheet/include/org/apicnet/util/index.php
lib/sheet/include/org/apicnet/index.php
lib/sheet/include/core/index.php
lib/sheet/include/index.php
lib/dracula/index.php
lib/swfobject/src/index.php
lib/swfobject/index.php
lib/attributes/index.php
lib/swfupload/js/index.php
lib/swfupload/src/index.php
lib/swfupload/index.php
lib/htmlpurifier_tiki/index.php
lib/metrics/index.php
lib/encoding/index.php
lib/jquery_tiki/colorpicker/index.php
lib/jquery_tiki/brosho/index.php
lib/jquery_tiki/tablesorter/index.php
lib/jquery_tiki/tablesorter/themes/tiki/index.php
lib/jquery_tiki/tablesorter/themes/index.php
lib/simile_tiki/index.php
lib/validators/index.php
lib/comments/index.php
lib/images/icons/index.php
lib/images/index.php
lib/minify/index.php
lib/TikiWebdav/Auth/index.php
lib/TikiWebdav/Backend/index.php
lib/TikiWebdav/index.php
lib/TikiWebdav/PathFactories/index.php
lib/parser/index.php
lib/rangy_tiki/index.php
lib/rating/formula/index.php
lib/rating/index.php
lib/webodf/index.php
lib/wiki3d/index.php
lib/importer/index.php
lib/language/js/index.php
lib/language/FileType/index.php
lib/language/WriteFile/index.php
lib/phpseclib_tiki/index.php
lib/multilingual/index.php
lib/ckeditor_tiki/index.php
lib/ckeditor_tiki/ckeditor-icons/index.php
lib/ckeditor_tiki/plugins/autosave/images/index.php
lib/ckeditor_tiki/plugins/autosave/index.php
lib/ckeditor_tiki/plugins/_tikilink/dialogs/index.php
lib/ckeditor_tiki/plugins/_tikilink/index.php
lib/ckeditor_tiki/plugins/index.php
lib/ckeditor_tiki/plugins/tikiwiki/index.php
styles/lite/index.php
styles/snow/Flash/index.php
styles/darkroom/pics/icons/index.php
styles/darkroom/pics/index.php
styles/darkroom/options/small-type/index.php
styles/darkroom/options/index.php
styles/twist/pics/icons/index.php
styles/twist/pics/index.php
styles/coelesce/pics/icons/index.php
styles/coelesce/pics/index.php
styles/thenews/pics/icons/index.php
styles/thenews/pics/index.php
styles/thenews/options/narrow_left_column/index.php
styles/eatlon/options/teal/index.php
styles/eatlon/options/index.php
styles/arcturus/index.php
styles/strasa/img/icons/index.php
styles/strasa/img/index.php
styles/strasa/options/cool/index.php
styles/strasa/options/mono/index.php
styles/tikinewt/pics/icons/index.php
styles/tikinewt/pics/index.php
styles/tikinewt/index.php
temp/public/index.php
templates/draw/index.php
templates/comment/index.php
templates/admin/index.php
templates/tracker_search/index.php
templates/trackeroutput/index.php
templates/wiki-plugins/index.php
templates/tracker/index.php
templates/object/infobox/index.php
templates/report/index.php
templates/tracker_sync/index.php
templates/tracker_todo/index.php
templates/trackerinput/index.php
templates/styles/mobile/index.php
templates/translation/index.php
templates/plugins/index.php

Features Classification

Related:
[wish1887|Modules use should be restrictable with standard permissions]


Read from bottom up:

2008-05-27 00:46:33 Norrin_Rrr mmh
2008-05-27 00:45:57 prozaq you could probably modify that
2008-05-27 00:45:39 prozaq that displays all categories
2008-05-27 00:45:32 prozaq Norrin_Rrr: in 1.10 there is a module called "categories"
2008-05-27 00:41:25 Norrin_Rrr will try it
2008-05-27 00:41:16 Norrin_Rrr the example in the documentation says its for features not sections that s weird
2008-05-27 00:40:51 prozaq oh - yes I think so, but Ive never tried it
2008-05-27 00:40:34 prozaq beg your pardon?
2008-05-27 00:39:45 Norrin_Rrr the section parameter in the menu its to set wich section (wiki/cms/forums) will display the menu ?
2008-05-27 00:38:54 Norrin_Rrr that should be doable
2008-05-27 00:38:19 prozaq so you should be able to copy some of the code from the tiki-browse_categories pages
2008-05-27 00:34:38 Norrin_Rrr yes
2008-05-27 00:34:16 prozaq but isnät that when you are creating a module from scratch?
2008-05-27 00:34:07 Norrin_Rrr i am not sure but there seems a possibility for hacking ?
2008-05-27 00:33:44 Norrin_Rrr "So if you know about Smarty template editing you can use any Smarty tag in your user modules."
2008-05-27 00:33:05 Norrin_Rrr ah okay i am at the module documentation, and its seems there are some conditionals with TW1.10 for modules but unfortunatly none for specific category
2008-05-27 00:32:56 *** franck has left #tikiwikin
2008-05-27 00:29:43 *** kiilo_ has quit IRCn
2008-05-27 00:28:34 Suprano even more if you paste in in a formular :D
2008-05-27 00:28:15 Suprano hmmm copying 4mb text slows down the pc
2008-05-27 00:28:10 Norrin_Rrr and display a menu that gather the various item of this category
2008-05-27 00:27:59 prozaq marclaporte: earlier I posted a bug to the tracker item Bugs & Wish list on dev.tikiwiki.org but how do I post to the "All Bugs" section or the "Release 110 taged bugs" ? section
2008-05-27 00:27:38 Norrin_Rrr yes
2008-05-27 00:27:30 marclaporte the goal would be to show a certain module only if current item (page, etc) is in category X ?
2008-05-27 00:26:07 prozaq eek...
2008-05-27 00:25:45 Norrin_Rrr its seems it works for feature enabled on the site but not for category (?)
2008-05-27 00:25:16 Norrin_Rrr yep i have the doc about the menu under my nose but i don't understand the section parameter
2008-05-27 00:24:39 marclaporte hi prozaq
2008-05-27 00:24:24 prozaq marclaporte: hi
2008-05-27 00:24:19 prozaq but Iäm not sure a specific category would fall under that
2008-05-27 00:23:57 prozaq it seems that you can tell a module which "section" it should appear in
2008-05-27 00:22:37 Norrin_Rrr for now 1.9.9 but 1.10 soon i hope :)
2008-05-27 00:21:20 *** marclaporte has joined #tikiwikin
2008-05-27 00:20:45 prozaq which version are you using norrin?
2008-05-27 00:18:38 Norrin_Rrr i am not sure, a module with a menu would be nice
2008-05-27 00:18:08 prozaq a menu item or a module with menus?
2008-05-27 00:17:29 Norrin_Rrr and hello everybody ;)
2008-05-27 00:16:39 Norrin_Rrr Is it possible to show a menu only when a user reach an item belonging to a given category ?
2008-05-27 00:15:24 *** Norrin_Rrr has joined #tikiwikin







Sylvie has recently added some useful code in BRANCH-1-10 so we can use categories as conditions in templates (.tpl)

[http://dev.tikiwiki.org/Hello+World#To_do_something_specific_in_a_template_ex_tiki_tpl_conditional_to_the_current_item_being_in_a_category_Ex_different_header_picture_|related info in Hello World]

Tiki 1.9.8 ships with 94 modules. (excellent)


Need a "module manager"

Module should come with a screenshot or preview.

A page listing all modules with descriptions and parameters- grouped by feature.


currently, the "user modules" and "assigned modules" titles are very non-intuitive. Should say "custom modules" and "active modules"




However, all modules are listed at all times. Module listing should check for features which are activated. It would be easier on new Tiki admins. For example, if articles are deactivated, don't show me last_articles in tiki-admin_modules.php



Admin modules does not display titles of available modules or provide easy method for selecting unused modules, such as with a listbox. The missing information is not available unless a Tiki admin has system admin permissions.



Also, all possible parameters for the current module should be listed (or picked from a drop-down)
See:
[http://doc.tikiwiki.org/Module]



Related:
Plugins admin interface
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=502

To reproduce:

1- tiki-admin_menus.php

2- click the permission key

ex.:
tiki-objectpermissions.php?objectName=Go Green&objectType=menus&permType=menus&objectId=56

{CODE()}Permissions
No rows found

Warning
You must select at least one feature.{CODE}

I support 3 languages on my web site...
and have problems when a page title is the same in different languages...

Example..

"Projekter" in Danish
"Projects" in English
"Projekter" in Swedish

I cannot have two pages named "projekter" even though they are different languages..

Actually pretty annoying that you cannot have two wiki pages with the same title...
because you maybe have different contents...

patch for aulawiki.1.6 to run on tikiwiki.2.2

Perspective

after installation of the learning_center profile, on top of a bare-bones instalation, the perspective module is not shown nowadays, but it did while in ((tw:TikiFestBarcelona))

and looking at the edit module interface, it says: "perspective (param): Only display the module if in one of the listed perspectives. Semi-colon separated."
and that param is empty by default

I do that logged as admin, and just in case, included the registered group into the admin group.

And deleted tiki caches several times just in case
No change.

I can't continue with that profile

after installation of the learning_center profile, on top of a bare-bones instalation, the perspective module is not shown nowadays, but it did while in ((tw:TikiFestBarcelona))

and looking at the edit module interface, it says: "perspective (param): Only display the module if in one of the listed perspectives. Semi-colon separated."
and that param is empty by default

I do that logged as admin, and just in case, included the registered group into the admin group.

And deleted tiki caches several times just in case
No change.

I can't continue with that profile

Copied some suggestion I just throwed on irc..., after fighting each time on some of my production sites to manually send messages to many users which are kind of lost some times at the beggining of their participation in a tiki-site-powered community.

{QUOTE()}
(11:37:39) xavi: I was just wondering about a new and easy improvement of the registration process of new users to a community sit eusing tiki
(11:38:07) xavi: just through allowing an admin to add acustomized welcome message to new users successfully registered to the site...
(11:38:29) xavi: ... with the text and links he might need to tell to new users....
(11:38:52) xavi: ...in a similar way to what mailman does for the welcome message to new users...
(11:39:48) xavi: ...I imagine a simple text area, like site identity does, where the admin can write any simple text (with or without wiki markup? like the newsletter feature does/allows)...
(11:40:45) xavi: ...so that the admin can set that message easily (without manualy searching for the appropiate template to hack through ftp)...
(11:42:48) xavi: ..and the the new user, can review the infos and tips that he/she needs to know on that site: "now you can: # watch that forum where that important thing is discussed.... #join that newsletter/blog/articlefeature to be up to date about news from that community, #review and/or subscribe to that tracker..., ...
(11:45:22) xavi: oh well, I can't code php+mysql myself (yet, at least ;-) ), but I guess that this shouldn't be that difficult nor time consuming to an experienced coder, provided that that person agrees on that this feature is "low hanging fruit" to improve the experience of newcomers to a community, through improving the communication while the first steps of that person in the community site...
{QUOTE}

This could also be important for ((Workspaces)), and ((Organic Groups)). So that, not just to register (join the registered group), but as a customized message per group, so that, when joining a new group (at registration time, or later on through the subscribe groups plugin), you get the specific message with hints, links and remindings of things adapted for that group.

For some situations it would be extremely useful to be able to set a separate permission to allow a Group to create a new Forum.

This would then avoid having to give the Group the full tiki_p_admin_forum permission, which then also allows users in this Group to set Permissions.

Whilst the full Permission functionality is extraordinarily flexible and feature rich, it can also be quite confusing for a less experienced user and the use of Categories (ie using pre-packaged sets of permissions) is a much easier function which obviously should still be allowed from the Create New Forum screen.

This is still a valid feature request - so I've refreshed it (Aug 2013) - but its not a particularly high priority

Documentation of Tiki (doc.tw.o) needs some help, as well as any other tiki site aiming to produce structured documentatation to be exported as "printer-ready" (.pdf, .odt, ...)

!!- (1). Original idea, as posted in devel list (but improved, and made it easier, below, in (2) )
I include here a copy of the [http://sourceforge.net/mailarchive/forum.php?thread_name=467565F1.9080905%40ub.edu&forum_name=tikiwiki-devel|original post at tiki-devel list]:

{QUOTE()}
[Tikiwiki-devel] New documentation file: Tiki198alpha.pdf
From: Xavier de Pedro Puente <xavier.depedro@ub...> - 2007-06-17 16:44

(...)

There are some issues that, it solved from coders, they would make
easier to produce next documents like the pdf ones:

(1) Page Title is not automatically shown on wiki pages on the server,
and thus, manual header1 was added everywhere (Almost). But when
printing to html, page title is duplicated. => if Show Page Title option
is disabled under "Admin > Wiki", Page title should not be added
automatically at print-to-html time.

(2) to produce the same structure (same level structure of headings) as
in table of contents http://doc.tikiwiki.org/Documentation , some hack
(optional) would be very welcome so that heading 1 in doc.tw.o pages is
not printed as heading 1 in through the multiprint, but as header 2, at
least. (optional).
This is, for instance, what is produced when printing a full structure
from a Workspace - AulaWiki Mod - : a coder could grab the code from
AulaWiki Mod as a reference....
In there, the description of the page is set as the Page title (header
2, I think), and the page title is included below for completeness (in
lower font, and with version number next to it)...

edutwo_ws_print_structure4.png

(3) Numbering of headings: somehow, in Workspaces this is handled
internally, and the user/documenter doesn't need to bother with manual
numbering: it's produced also at print time.
[http://edu.tikiwiki.org/tiki-workspaces_view_structure.php?print=4]

Example of print structure differences between Tiki's multi-print and
Workspaces print structure:

Print to html "Aula-Wiki Tutorial" from here:
[http://edu.tikiwiki.org/tiki-print_pages.php]

or from here:
[http://edu.tikiwiki.org/tiki-workspaces_view_structure.php?print=4]

Well, as you could imagine, some changes to the code to make the work of
documenters a bit easier would be very wellcome also... :-)

(...)

{QUOTE}

!! (2) Update July 20th: Easier solution
Easier solution: Get levels for first heading in each wiki page of the structure not from the content of the page.

^__Example__: a page may start with a "! Title of page" (first level heading), and after that, "!! Subtitle of page" (2nd level heading), ...

Imagine that this page corresponded to "2.3.1 Module whatever" as the level in the table of contents of such structure.

The solution would be then that "!Title of page" (in that page "2.3.1 Module whatever"), when sent to (or fetched by) tiki-print_pages.php as a whole structure, was converted to "!!! Title of page"; and "!! Subtitle of page", should be converted to "!!!! Subtitle of page"..., and this way sequentially for all the title headings on each page from the structure...
^

The procedure below should become a 1-click from wiki (structures) to[http://doc.tikiwiki.org/Tiki19beta.pdf|PDF]. Please see:[http://doc.tikiwiki.org/Printing+the+Documentation|How to produce the .pdf out of the .odt]

-----

Dec 13 2008. Update:
Previous problem is fixed. However, I notice that automatic numbering with heading within a page (!!#, !!!#, ...), should be also considered in the global autonumbering.

Plus width of wide images and tables would be better if not that wide when exported to html (maybe an option), for the case when you plan to import it to OpenOFfice, and they are too wide to the document. Should this be another RFE or bug report?

---
REOPENING BUG
update on Jan. 7th, 2009:
See the other bug report: autonumbering didn't work for me with doc.tw.o/Documentation, even if it did a month ago on another site/structure

Related (and newer) bug report/RFE:
[http://dev.tikiwiki.org/bug2255]

Use case:
*Manage many sites/domains with one Tiki installation
*"Park" all the domains on top of each other and get Tiki to send people to the right page depending on the domain.
*Common user base & permissions
*Theme control to provide different theme per section/category/page
*Could be different domain per language

Ideas
*Maybe domains could be links to categories. Put a page in a category and it gets its theme from theme control center
*Modules per domain
*If on page for domain X, force/rewrite URL to that domain
For example
^www.musicband1.com/introband1
www.musicband2.com/introband2
www.musicband3.com/introband3

So if I go to:
www.musicband1.com/introband2
I am redirected to
www.musicband1.com/introband1^


Limitation:
*pagename collision. Ex: domain1.com/intro = domain2.com/intro
*Single shared search engine
*Meta-tags will be shared

Also need to think about the Use Case where different workgroups want different domains. (A bit like *tikiwiki.org sites)

With new Tiki4 Workspaces, we could associate the domain as a preference.

What happens if a wiki page is in many categories, and they have different domain names. How would the priority work? Random? An order? Same idea as default group?



Related:
((WikiFarm))
((TRIM))
((Workspace))

tiki-list_object_permissions.php is fantastic

It lets me review any permissions received from category, and individual perms.


Some enhancements:
* Link to the category perm interface so I may adjust the perms
** As of 4.0, I need to check each category to see why the perms are applied
* Type group is missing (permissions ''about'' groups)

This is for internal groups within a wiki, a bit like ((workspace))s.

Some pages have special perms. We'd need a way that new pages created from these inherit permissions.

It could be possible to do via category permissions but..

I have instaled TW 2.4 and Aulawiki 1.7.1.
I can define the workspace types but I can't assign default resources because the list it's empty.

with latest cvs updates in our site (1.9.7 -> 1.9.8cvs), and at least when logged in, the module workspace calendar (from ((doc:Mod AulaWiki))) is showing those lines between module "workspace members" and "workspace calendar":

{CODE(wrap=>1)}
Warning: Missing argument 2 for date_format() in /home/httpd/tiki19/lib/tikilib.php on line 6307

Warning: Missing argument 2 for date_format() in /home/httpd/tiki19/lib/tikilib.php on line 6307

Warning: Missing argument 2 for date_format() in /home/httpd/tiki19/lib/tikilib.php on line 6307
{CODE}

Example:
[http://www.moviments.net/cursos/ws100]

And the date in workspace calendar is from 1970, when it used to be the present date.

Please see ((workspace roadmap))

What You See Is What (You Want) To See Now