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

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

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.

{syntax type="tiki" editor="plain"}
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

{img fileId="452"}

When you define workspace areas, there is no mechanism to delete them. They can be edited, but not deleted.

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

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');

This line dont work with tiki wiki: * ((Les fichiers d'Exportation (ADX)|Créer un fichier d'exportation (ADX) de la société.)) It's work iust if I remove ()

In version 9.11, creating a Workspace using Perspectives and Category Jail would permit a user to view a tracker and all of its tracker items when that tracker was categorized appropriately. Upon upgrading to version 12.11, the tracker is still visible to users within the Perspective, but the "View Items" page does not list any items. The items are still accessible and editable by the user if they know the Item ID or have links to them, but they cannot be browsed. The item count will show correctly when viewing the list of trackers, but the tracker itself will report that it contains 0 items when viewing the items list.

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

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]

Use "~" for Namespace separator as advised/ suggested by tiki-doc.
Create Workspace Template, generate Workspace from it.
Produces "template~workspace" as workspace name for category, group, perspective.

Now such a workspace needs permissions changed from the default of the template.
Admin Category, hit "Permissions", edit entries for the dedicated group(s), save.

In the Permissions UI the save is not reflected, it's the same as before.
In the DB the table "users_objectpermissions" received new entries for "template" rather than "template~workspace".

Haven't verified yet whether it's related to "~" as Namespace separator or not.

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.

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

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

This tracker is made to help filtering and sorting the features vs categories vs options we need to tag a bug/regression/wish with.