hey i got the latest version of pier, when i added a system users component
to a page, when i click on any thing on the component which invokes a
callback. i get the following error
"WAComponentsNotFoundError: Components not found while processing callbacks:
an Array(a PUUsersWidget)" .
any ideas how to resolve this
--
View this message in context: http://www.nabble.com/Error-in-PUUsersWidget-tf4286525.html#a12202036
Sent from the SmallWiki mailing list archive at Nabble.com.
Hello,
I want to give pier users additional attributes (first name, last
name, email, etc). So far I was creating a subclass of PUUser. Would
it be better to just extend PUUser by a few Magritte descriptions on
the class side?
When I load new versions of Pier-Unix-Security from Monticello, I
guess my additional description methods would be deleted again? And if
I put them into my own category *my-customizations (with a star in the
name), monticello would leave them alone?
And, on a related note, what if I want to change a method in Pier's
core (like PULogin class>>isValidIn:), how do I avoid that the next
load from monticello gives me that old version again?
Cheers
Matthias
A small framework to enable external validation plugins to be added and
configured for Pier Login.
I am using this with a plugin (not included yet) which validates the
user/pass against a MYSQL query, then it logs in this user using an
internally defined pier-user (or as I call it a "role") as a template.
Finally I perform a second query to obtain a UserData record, and a
potential invalidation is performed on "any other criteria", such as an
account expiry date.
You add your plugin by subclassing PUExternalValidationPlugin, and
select the plugin to use in the application configuration.
Finally your plugin gets the opportunity to customize the Login Dialog's
descriptions. This enables you to customize the presentation of the
dialog if you add Magritte-ComponentDecoration 's. You should also be
able to add extra fields, though I leave this as an exercise for the reader.
enjoy
Keith
Hello,
I'd like to collect some snippets of documentation about Pier. Would
http://smallwiki.unibe.ch/smallwiki/pier/
be the right place to do so? I was not able to figure out a login to
that wiki :-(
Matthias
If you copy a component, it seems that the settings for both components
are the same instance. There is no longer a ui to change the settings on
the original (or is it the copy I am not sure which)
Keith
PRCommandLink allows the following syntax *command:PULogin* to generate
a link which performs that command. If the user is not authorized the
link does not show.
Alias's are supported in the normal manner: *Register
Here>command:PRRegisterUserCommand*
As an advanced example you can include command links in the dialogs of
other commands by adding a PRComponentDecoration's to the description.
e,g.
PUMyLogin-description
(super description)
componentDecorations: (Array with: PRComponentDecoration);
preAnnotation: 'If you do not have an account *Register
Here>command:PRRegisterUserCommand*';
yourself.
best regards
Keith
Enable PierWidgets to make use of ShoreComponents.
All you have to do is configure the application to use PRPierShoreFrame
as the root component and all those great shore components are yours!
best regards
Keith
p.s In this initial version there might be a very slight css effect from
the shore css, but I tracked it down yet.
Hello,
I have made a custom subclass of PULogin which will direct users to
their homepage after they login. The Commands widget in Pier then
shows both PULogin and my CustomLogin command. I'd like to hide
PULogin, so I thought I make PULogin invalid (isValidIn: aContext
returns false). Problem is that now I get CustomLogin listed twice in
the widget.
Here is the method, with some comments about what I think is going on
PRommandsWidget>>items
| commands command |
commands := self context commands. "These are all allowed commands"
^ Array
streamContents: [:stream | self commandClasses
"These are all possible commands"
do: [:class |
command := commands
detect: [:each | each = class
or: [each inheritsFrom: class]]
ifNone: [].
"command is an allowed command that is a subclass of any of
the command classes."
command isNil
ifFalse: [stream nextPut: command]]].
So it iterates over all possible commands (subclasses of PRCommand)
and adds allowed commands if they inherit from one of them.
My questions are:
- What's the point of the inheritance check?
- Shouldn't the list of commands in the widget be a subset of the
commands allowed in the context?
- Why shouldnt the widget just show the commands that the context allows?
I'd like to understand this before I patch it :-)
Cheers
Matthias
I put this in the pieraddons repository, it adds some configuratble
debugging hooks.
Name: Pier-Debugging-kph.1
Author: kph
Time: 16 August 2007, 4:26:56 pm
UUID: 207cf14d-4c0d-11dc-8162-000a95edb42a
Ancestors:
- some debugging hooks with switching in preferences
best regards
Keith
I've started using the really excellent ICal package (thanks
Phillipe!), and just loaded the ICal Magritte package.
On ICCalendarEntry class>>descriptionUrl, the definition is:
descriptionUrl
^(NAUrlDescription selector: #url label: 'Link' priority: 1000)
beEditable;
yourself
NAUrlDescription is not defined anywhere - I would expect it to be
named MAUrlDescription, but that isn't defined in my image either ;)
Any ideas where I can get this class, or what else should be in here?
Thanks!
Brian
