Hi all,
I'm new to the SmallWiki world. I've installed it in a squeak image
and after playing arround for a while I can't see the commands 'view
edit ...' even when I log as admin.
any clue?
best regards,
Sebastián Sastre
ssastre(a)seaswork.com.ar
www.seaswork.com.ar <http://www.seaswork.com.ar/>
Glenn Swanlund wrote:
> I’m using SmallWiki with Squeak 3.6 and adding some customization. When
> an error occurs while running new code, there is no error message in the
> browser or Squeak. Is there a way to get the error message visible somehow?
You have to set the Debug Level of the Comanche Server.
Regards
Chris Burkert
--
http://www.chrisburkert.de/
Hello,
I downloaded the latest SmallWiki from the Cincom store, but after
loading it two of the tests fail, and I cannot start a server. This
happens on OS-X and Windows. I tried with different versions of Swazoo,
but to no avail. What am I doing wrong?
--
Roel Wuyts
DeComp
roel.wuyts(a)ulb.ac.be Université Libre de
Bruxelles
http://homepages.ulb.ac.be/~rowuyts/
Belgique
Board Member of the European Smalltalk User Group: www.esug.org
Hi,
> That is a strange error. I couldn't recover it. I use VW7.2, same
> as you. Anyway, please try more primitive way. Here is a changeset
> version.
loading SmallWikiI18N from the changeset worked nicely. The
web-interface seem to run fine, but unfortunately there are 12 tests
suddenly failing. What is more, there are no tests that cover the added
functionality.
Maybe you (or somebody else) could have a look at those problems?
Currently I'm too flooded with other things, therefor I'm unable to
spend much time on SmallWiki.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
hi lukas
I tried to add http://kilana.unibe.ch:9090/?action=RSSChangesFeed to a
rss feed reader and it did not work.
I guess that this is because the action RSSchangesFeed is not enable at
the top level.
Is it right? should we add it on each local wiki?
Stef
Hi!
What is the meaning of the following:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
!Contents of this Site
[ "If you are not logged-in as administrator, please remove everything between the square-brackets before saving the page!"
structure renderListOfChildrenOn: html ]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
I understand they are intended to render all the children of a folder.
However it make people to wonder about it. Its meaning is not obvious. For instance Michele called me because of this 3 lines.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
hi,
there are two management interfaces for smallwiki available at cincom
store:
1) SmallWiki Admin Default: interface to the original security model of
smallwiki. easy to use and understand
2) SmallWiki Admin: interface to the extended security model of
smallwiki. more complex.
1) functionality of default interface:
======================
- create/delete users
- assign roles to users
- create/delete roles
- assign permissions to roles
restrictions that apply via the interface:
- an admin can only assign those roles to users that he has created
himself or that he owns himself.
- an admin can only delete the roles that he has created himself.
- an admin can only delete users that he has created himself.
- an admin can only assign those permissions to a role that he owns himself.
- BUT: an admin can redefine any role he wants to. therefore he is able
to remove permissions from some other admin roles!
modification to original model:
- when a user visits the root of the wiki tree, the permissions of his
role(s) are removed (cleanup).
(this is necessary when a role is not defined at the root of the wiki
tree, but at some 'lower' level in the tree.)
2) functionality of extended interface:
========================
- create/delete users
- assign roles to users
- create/delete roles
- assign permissions to roles
- create a barrier role in order to stop the acquisition mechanism for
the other roles at the same level.
restrictions that apply via the interface:
- an admin can only manage roles and users that he has created himself.
- an admin can only manage permissions that he owns himself. i.e., he
can only add/remove those permissions that he owns.
modification to the original model:
- the computation of roles is done in a different way (using some sort
of acquisition that is similar to the zope model)
FAQ:
====
1) when should I use the interface 1?
=> when just one administrator is managing the wiki site.
2) when should I use the interface 2?
=> when you have several administrators, that are responsible for
'their' part (structures, roles, users) of the wiki site.
documentation:
==========
- the documentation (the difference of the two models are explained and
discussed) of these two models is available at:
http://www.iam.unibe.ch/~scg/smallwiki/smallwiki_models_description.pdf
- the management interface to the default securtity model described in
this docmentation (smallwiki_models_description.pdf) is already enhanced:
- an admin can only assign those roles to users that he has created
himself or that he owns himself.
- an admin can only delete the roles that he has created himself.
- an admin can only delete users that he has created himself.
- an admin can only assign those permissions to a role that he owns
himself.
cheers,
david.
