I'd like to learn how you manage users in Pier. Since Pier is a
Wiki/CMS, allowing users to register, login/logout, and managing their
pages/assets is a big part of any Wiki or CMS.
My plan was to create a "register" component and a "managing users"
component for Pier, but I bet this has already been done - extending the
Unix Security component.
How do you manage users in Pier?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
I just updated to Lukas latest (you updated the tab for your stylesheet)
and now the "File Library" (I think that's what it was called) under
Pier in the configuration is gone. This is where the "file library" was
set. I had it set to my library.
Let me tell you what happens: If I use PRPierLibrary only under
"Libraries" (at the top), no problem with css. If I remove
PRPierLibrary and use my own MyLibrary (which is just a copy of
PRPierLibrary) no css file.
This worked before with MyLibrary.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Philippe Marschall wrote:
> 2007/2/17, Brad Fuller <brad(a)sonaural.com>:
>> Looking through the various Pier documentation, I see that code has
>> changed and thus there are several different explanations of how to
>> change stylesheets. I want to use a different css stylesheets but I
>> can't find out where to change it/them. Isn't there one place to
>> point Pier to one stylesheet?
>>
>> BTW: for some reason, I have no style sheet at all for Pier. I don't
>> know what I did, but I didn't edit any code... I must have loaded a
>> new version of some package. Anyway, unless it stomped on something
>> else, ifI can learn where to change the stylesheet pointer, It'd
>> give me a start.
>
> Thanks to Christoph Wysseier Pier now supports easy custom styles with
> FileLibraries. All you need to do is provide your own FileLibrary that
> implements #styleCss which returns a string that is the main CSS file.
> You can put all your CSS there, or in other selectors (as PierLibrary
> does) or in other locations by importing the CSS files you need.
>
> For example if #styleCss makes
> @import url(basic.css);
> this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary
> one of the classes that actually have a comment that describes what it
> does.
>
> In the configuration of your pier application under 'Pier' you can
> select it in 'File Library'.
Thanks, and in my Pier, it's set to PRPierLibrary.
I'm still a bit lost about File Library, though. Let's use css as an
example. My stylesheets were found only if I redirected, in apache,
where seaside retrieved the files:
RewriteCond /path/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L]
If I remove the RewriteCond, stylesheet files are not found, (even
though I also placed the same files in a sub dir of the image named
seaside/files/PRPierLibrary.)
(the access logs say apache is looking in /seaside/files/PRPierLibrary)
If I go to seaside/config and select configure for "files" I get the
listing of File Libraries, as expected. Selecting PRPierLibary lists
files that are all the css files that (I thought) are pointed to. Fine,
that seems to work. But, when I uploaded a file (just to see where the
file would go) and check the complete server, the file is no where to be
found. However, the file is retrievable from the configuration screen. I
can only assume that the image swallowed it up.
This is confusing. There is a class called PRPierLibrary. PRPierLibrary
is also a directory name - evident because apache is looking for that
directory. Also, if you go to PRPierLibrary in the configuration, the
"files" are not really files. The contents of the files are actually in
the methods of PRPierLibrary.
So, I'm still lost on exactly where seaside is retrieving files.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
how come when I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following classes:"
and there are many of them. Is there a better way to load Pier packages?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Will the seaside location/key of a file that has been uploaded as a
"file" in Pier be guaranteed to be static? For instance, can you always
be guaranteed that a photograph that was uploaded be guaranteed to be at
that address?
Example, this is a photo uploaded to pier:
http://www.<my_domain>/?_s=BGrhMyNQYJbYqctY"
Can this link be used to resize the photo and be guaranteed not to change?
<img src="http://www.<my_domain>/?_s=BGrhMyNQYJbYqctY" width="100"
height="300"
Or, what's the way to resize photos?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Lukas Renggli wrote:
>> But, when looking at the apache access log there is:
>>
>> GET /seaside/files/PRPierLibrary/style.css HTTP/1.1" 404 83
>>
>> In the configuration page, PRPierLibary is in the File Library under
>> Pier. But I don't know why there is css formating in the direct way
>> (http://www.my_domain.org:9999/seaside/pier), and apache is looking for
>> a css file in the second (http://www.my_domain.org/).
>
> That's the new way for Seaside to serve static files.
>
>> BTW: I did create a sub-directory called: files/PRPierLibrary with the
>> default style.css from Lukas under the directory where the image is
>> located, but that didn't do anything.
>> (I stopped and restarted WAKom just in case.)
>
> You either need to create a directory seaside/files/PRPierLibrary/
> with your files or add the following rewrite rule right after enabling
> the rewrite engine:
>
> RewriteRule ^/seaside/files/PRPierLibrary/(*.)$
> http://www.my_domain.org:9999//seaside/files/PRPierLibrary/$1 [P,L]
(I moved this to the Pier ML as I think it's Pier related, sorry if this
is confusing - don't want to bother others)
Thanks Lukas.
Along those same lines, I'm getting long lines after the domain name
when I select a link in Pier. Is this correct?
information/license?command=PRViewCommand&view=PRDefaultView&_k=swboZglt&29&_n&_s=MELVlGoXVospTlDw
?command=PRViewCommand&view=PRDefaultView&_k=zYTOouCP&21&_n&_s=MELVlGoXVospTlDw
information/license?command=PRViewCommand&view=PRDefaultView&_k=rKYbypAd&25&_n&_s=MELVlGoXVospTlDw
seems like it should be shorter.. they are shorter in my other seaside
app, although, it's not Pier.
Hi,
I use the Page Information Tutorial
(http://smallwiki.unibe.ch/smallwiki/pier/) of Damien Cassou to add my
widget on Pier.
But when I want to add my widget to the "Environment" (following chapter
4 and 5) the "Environment" page doesn't appear on the tree!
How does this actually work on Pier to add a widget to the
"Environment"? (the tutorial seems not up to date)
PS: my widget works great it's not the problem :)
Regards
Mat
Looking through the various Pier documentation, I see that code has
changed and thus there are several different explanations of how to
change stylesheets. I want to use a different css stylesheets but I
can't find out where to change it/them. Isn't there one place to point
Pier to one stylesheet?
BTW: for some reason, I have no style sheet at all for Pier. I don't
know what I did, but I didn't edit any code... I must have loaded a new
version of some package. Anyway, unless it stomped on something else, if
I can learn where to change the stylesheet pointer, It'd give me a start.
thanks,
brad
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
>>> Looks like there might be a problem with mc.lukas-renggli.ch (Sat
>>> 21:54).
>>
>> thanks for reporting. It seems to work for me. How did you got
>> into this problem?
>
> Initially by requesting to load the Pier-Blog Module in Squeak (no
> load), and then by visiting the website with safari, this over a
> period between 1900 and 2200 yesterday.
>
> So *now* I have the issue that loading Pier-All-lr.162 says:
>
> This package depends on the following classes:
> WAFileLibrary
>
> How can I do this?
Well after loading Pier from SqueakMap you have to update Seaside,
Magritte, and Pier to the latest version. Then you have to load the
package RSRSS from http://www.squeaksource.com/rsrss and then load
the blog plugin. Sorry, it is still a bit complicated and there are
still some strange bugs in the blog plugin ...
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
