Reza RAZAVI | 1 Apr 12:08 2010
Picon

Login issue on deployed Pier

Hi,

I pointed Pier to a student. He installed and deployed it, thanks to 
piercms.com. However, he is unsuccessful in logging into the deployed 
image, whilst the same work on his local computer.

Any comment and suggestion would be greatly appreciated,
Regards,
Reza  

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Lukas Renggli | 1 Apr 13:12 2010
Picon

Re: Login issue on deployed Pier

> I pointed Pier to a student. He installed and deployed it, thanks to
> piercms.com. However, he is unsuccessful in logging into the deployed image,
> whilst the same work on his local computer.

What happens when he logs in?

What happens if he gives wrong username and password?

Anything else that is broken?

Lukas

--

-- 
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Reza RAZAVI | 1 Apr 14:26 2010
Picon

Re: Login issue on deployed Pier

Hi Lukas,

At 13:12 01/04/2010, you wrote:
What happens when he logs in?

The same page is just rendered again.

What happens if he gives wrong username and password?

Just nothing.

Anything else that is broken?

Well, I wanted once to show him how Pier works. So, on his local machine, I logged and added a post to the blog. But, then wasn't able to find it, neither in the blog page, nor in in the archive list. I'm not sure; maybe I've made a wrong manipulation.

Just in case you would like to have a look, his experimental site is here:
http://www.bamlux.net/

username and password are the default ones.

The image is the one available at:
http://piercms.com/

It's running on a Debian / Apache2 server, configured following your instructions here:
http://www.piercms.com/doc/deploy

Thanks for having considered my request,
Regards,
Reza
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Lukas Renggli | 1 Apr 14:46 2010
Picon

Re: Login issue on deployed Pier

> Just in case you would like to have a look, his experimental site is here:
> http://www.bamlux.net/
>
> username and password are the default ones.
>
> The image is the one available at:
> http://piercms.com/

The URL that Seaside generates is wrong:

     http://www.bamlux.net/seaside/pier

You need to go to the configuration of the application and change the
'Server Base Path' to '/'. Then it should work. You can find some more
information on the base path at
<http://book.seaside.st/book/advanced/deployment/deployment-preparing>.

Lukas

--

-- 
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Reza RAZAVI | 1 Apr 15:20 2010
Picon

Re: Login issue on deployed Pier

At 14:46 01/04/2010, you wrote:
>You need to go to the configuration of the application and change the
>'Server Base Path' to '/'.

Many thanks Lukas; it works now.
(the site may be down, since he is "playing" with Apache).

Cheers,
Reza 

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Lukas Renggli | 2 Apr 10:08 2010
Picon

Re: MADescription beHidden don't update model

I do not understand your question, but maybe the FAQ sheds some light on it?

    http://www.lukas-renggli.ch/smalltalk/magritte/faq

Lukas

On 25 March 2010 16:56, dtrussardi <at> tiscali.it <dtrussardi <at> tiscali.it> wrote:
> Hi,
>
> i have a model with some descriptions.
>
> One of it, descriptionMap, is set with beHidden property because i think to use it only for update the
relative cache description into descriptionContainer.
>
> The relative code is :
>
> ^( super descriptionContainer )
>        addCondition:[ : memento|
>
>                 memento cache at: self descriptionOK
>
>                         ifTrue: [      memento cache   at: self descriptionMap put:  'xyz'.    
 true ]
>
>                        ifFalse:[ false ].
>
>                                ]
>        labelled:  'Error is not ok;
>        yourself
>
>
>
> The cache is right update.
>
> The problem is to update the model relative to the descriptionMap cache.
>
> When confirm the form other instances model is right update but descriptionMap not.
>
> Any idea?
>
> Thanks,
>
>        Dario
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

--

-- 
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Francois Stephany | 2 Apr 22:10 2010
Picon

Magritte validations may weaken domain model

Hi all,

I'm reading the chapter on magritte in the seaside book and found this 
in section 24.5 :

"There are advantages to having your rules outside your domain objects, 
[...snip...] Still you have to pay attention since it may weaken your 
domain model."

Any pointer to a discussion about the pro/cons of this approach ?
Nothing important, I'm just curious to know...

Cheers,
Francois

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Lukas Renggli | 3 Apr 09:33 2010
Picon

Re: Magritte validations may weaken domain model

On 2 April 2010 22:10, Francois Stephany <tulipe.moutarde <at> gmail.com> wrote:
> Hi all,
>
> I'm reading the chapter on magritte in the seaside book and found this in
> section 24.5 :
>
> "There are advantages to having your rules outside your domain objects,
> [...snip...] Still you have to pay attention since it may weaken your domain
> model."

What this means is that it might be better to put the validation
directly into your model.

    MyModel>>isValid
        ^ some complicated condition

Generally there is a trade-off between putting the domain validation
into the model or into the meta-model (as with about anything that can
be part of the meta-model). If you put it into the model it is closer
to the data and behavior and might be easier for people not accustomed
to meta-models; if you put it into the meta-model it is more generic
and can potentially be reused and extended for different models.

Sort of as a workaround you can call the meta-model to do the
validation from the model. Something like:

    MyModel>>isValid
         ^ self description isSatisfiedBy: self

Lukas

>
> Any pointer to a discussion about the pro/cons of this approach ?
> Nothing important, I'm just curious to know...
>
> Cheers,
> Francois
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

--

-- 
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Norbert Hartl | 5 Apr 17:40 2010

http view parameter not working in gemstone

I installed a complete new pier on a fresh gemstone image and noticed that the RSS views are not working. This
is due another "aString is not equal to aSymbol" issue.

In PRPierFrame class>>classFromRequest: aRequest name: aString base: aBaseClass

there is 

^ aBaseClass withAllConcreteClasses
		detect: [ :each | 
			each isAbstract not
				and: [ each name = value 
				or: [ each label = value ] ] ]
		ifNone: [ nil ]

but class names are symbols and http parameters are strings. So I changed this to

^ aBaseClass withAllConcreteClasses
		detect: [ :each | 
			each isAbstract not
				and: [ each name = value asSymbol
				or: [ each label = value ] ] ]
		ifNone: [ nil ]

Norbert
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Lukas Renggli | 5 Apr 17:56 2010
Picon

Re: http view parameter not working in gemstone

Thank you for the bug report. I've committed a fix.

On 5 April 2010 17:40, Norbert Hartl <norbert <at> hartl.name> wrote:
> I installed a complete new pier on a fresh gemstone image and noticed that the RSS views are not working.
This is due another "aString is not equal to aSymbol" issue.
>
> In PRPierFrame class>>classFromRequest: aRequest name: aString base: aBaseClass
>
> there is
>
> ^ aBaseClass withAllConcreteClasses
>                detect: [ :each |
>                        each isAbstract not
>                                and: [ each name = value
>                                or: [ each label = value ] ] ]
>                ifNone: [ nil ]
>
> but class names are symbols and http parameters are strings. So I changed this to
>
> ^ aBaseClass withAllConcreteClasses
>                detect: [ :each |
>                        each isAbstract not
>                                and: [ each name = value asSymbol
>                                or: [ each label = value ] ] ]
>                ifNone: [ nil ]
>
> Norbert
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

--

-- 
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki


Gmane