pagekit-devel — For PageKit Developers only.

Re: [Pagekit-devel] Character conversions

[Boris Z. <bo...@2b...>]

Hi Gabriel,

this is hopfully already fixed. With this patch, that works only for perl 5.8. 
Perl 5.6.1 should be fine already. I hope the patch applied clean. please let 
me know.

The reason for your double conversion is that perl now converts some strings 
to utf8 but Text::Iconv did not notice that and convert it again. So we 
remove T::I for perl 5.8.

Maybe we should have a patchpage where all this fixes have a little 
description and a tarball?

Am Dienstag, 10. Dezember 2002 21:23 schrieb Gabriel Burca:
> PageKit v1.10 (checked out of CVS on Nov 29th).
> Perl 5.8
> HTML::Template 2.6 (see below)
> HTML::FillInForm 1.0 (see below)
>
>
> In the model code I have:
> 	$model->fillinform(key => $utf8_string);
> 	$model->output(key => $utf8_string);
>
> In the template I have:
> 	<input type="text" name="key">
> 	<MODEL_VAR NAME="key">
> 	<CONTENT_VAR NAME="some_utf-8">
>
> Config.xml
> 	default_input_charset = "UTF-8"
> 	default_output_charset = "UTF-8"
>
> The form field and <CONTENT_VAR ...> contains the correct unicode
> characters. If I try to display the same characters using <MODEL_VAR
> ...> on the same page, it looks like the characters get converted to
> unicode twice (a single 2-byte unicode character shows up as two
> characters).
>
> I've patched both HTML::FillInForm and HTML::Template and replaced .=
> with sprintf "%s%s". That was before I realized the problem only occurs
> when using <MODEL_VAR ...>. The View.pm _preparse_model_tags sub has the
> "use bytes;" fix.
>
> This might be the same problem reported by Leo Cambilargiu in the "Odd
> Characters" thread. Did anyone figure out that problem? Any ideas of
> where the double-conversion might be happening?

-- 
Boris

[Pagekit-devel] Character conversions

[Gabriel B. <gbu...@eb...>]

PageKit v1.10 (checked out of CVS on Nov 29th).
Perl 5.8
HTML::Template 2.6 (see below)
HTML::FillInForm 1.0 (see below)


In the model code I have:
	$model->fillinform(key => $utf8_string);
	$model->output(key => $utf8_string);

In the template I have:
	<input type="text" name="key">
	<MODEL_VAR NAME="key">
	<CONTENT_VAR NAME="some_utf-8">

Config.xml
	default_input_charset = "UTF-8"
	default_output_charset = "UTF-8"

The form field and <CONTENT_VAR ...> contains the correct unicode
characters. If I try to display the same characters using <MODEL_VAR
...> on the same page, it looks like the characters get converted to
unicode twice (a single 2-byte unicode character shows up as two
characters).

I've patched both HTML::FillInForm and HTML::Template and replaced .=
with sprintf "%s%s". That was before I realized the problem only occurs
when using <MODEL_VAR ...>. The View.pm _preparse_model_tags sub has the
"use bytes;" fix.

This might be the same problem reported by Leo Cambilargiu in the "Odd
Characters" thread. Did anyone figure out that problem? Any ideas of
where the double-conversion might be happening?

--
gburca dash pkit at ebixio dot com

Re: [Pagekit-devel] PageKit 1.11

[Boris Z. <bo...@am...>]

Hi TJ,

that is fine for me. I put something on CPAN this week.

Am Montag, 9. Dezember 2002 01:19 schrieb TJ Mather:
> Hi Boris,
>
> What would you think of releasing PageKit 1.11 soon?  I've run into the
> pkit_validate_input error with D::FV 1.11 a couple of times, and it would
> be nice to have a version on CPAN so that it can be distributed more
> easily than checking out from CVS.
>
> The fix I'm taking is "Fix pkit_validate_input to work with
> Data::FormValidator >= 1.11" (Model.pm revision 1.83) and it fixes the
> following error:
> [error] Invalid input profile: messages is not a valid profile key
>
> Thanks,
> TJ Mather
> Lookup location by IP Address - http://maxmind.com/
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Pagekit-devel mailing list
> Pag...@li...
> https://lists.sourceforge.net/lists/listinfo/pagekit-devel

-- 
Boris

[Pagekit-devel] PageKit 1.11

[TJ M. <tjm...@ma...>]

Hi Boris,

What would you think of releasing PageKit 1.11 soon?  I've run into the
pkit_validate_input error with D::FV 1.11 a couple of times, and it would 
be nice to have a version on CPAN so that it can be distributed more 
easily than checking out from CVS.

The fix I'm taking is "Fix pkit_validate_input to work with 
Data::FormValidator >= 1.11" (Model.pm revision 1.83) and it fixes the 
following error:
[error] Invalid input profile: messages is not a valid profile key

Thanks,
TJ Mather
Lookup location by IP Address - http://maxmind.com/

[Pagekit-devel] Re: [Pagekit-users] Problem with static files in Apache::PageKit

[Boris Z. <bo...@2b...>]

Hi Paul,

thanks for your fix, it is in cvs now.

I wonder how you found this.

thanks

Am Freitag, 22. November 2002 16:22 schrieb Paul Weiss:
> You have the following code to decide whether to send a
> static file:
>
>         return $pk->_send_static_file($filename) unless ( $apr->param );
>
> Unfortunately, the unless clause always evaluates to false because
> it evaluates $apr->param in scalar context, which results in a
> blessed Apache::Table object.
>
> You need to correct it to this:
>
>         my @param = $apr->param;
>         return $pk->_send_static_file($filename) unless ( @param );
>
> -Paul Weiss

-- 
Boris

Re: [Pagekit-devel] RFC: PageKit with perl5.8

[Boris Z. <bo...@2b...>]

Hi,

Am Samstag, 16. November 2002 18:00 schrieb TJ Mather:
> Hi,
>
> There is a misspelling of $$ouptut_ref in the patch.  I have attached a
> corrected version of the patch.

ups, i could swear that i tested the patch. Hmm.

>
> I personally don't have a problem with making Perl 5.8 required for
> PageKit.  If somebody doesn't like it, they can submit a patch to
> make it run on both depending on if $] >= 5.008.

I started this way, but the differences are annoying. So my idea is to support 
both versions a while with a patch. first working for 5.6.1 and a patch to 
support 5.8. in PageKit 1.12 then make 5.8 the default and have a patch for 
at least 5.6.1. Then maybe only 5.8.

Attached another try to support perl 5.8 propper. But now really untested ;-)
>
> Thanks,
> TJ
>
> Ps. I got a "Can't locate PerlIO/ISO.pm in @INC" error when attempting
> to run the patched PageKit on Perl 5.8.0/Linux 2.4.18.
>
> On Wed, 13 Nov 2002, Boris Zentner wrote:
> > Hi all,
> > i installed perl5.8 and discovered, that Text::Iconv converts charsets to
> > something other but missed to inform perl about that change. Also p5.8 do
> > the conversion sometime by magic, but Text::Iconv did not know and
> > convert it again.
> >
> > So i think with perl 5.8 we must get rid of Text::Iconv. This patch does
> > that as a first draft.
> >
> > What do you want for future versions of PageKit?
> >
> > WHAT ABOUT MAKING PERL 5.8 REQUIRED for PAGEKIT IN SOME MONTH?

-- 
Boris

Re: [Pagekit-devel] RFC: PageKit with perl5.8

[TJ M. <tjm...@ma...>]

Hi,

There is a misspelling of $$ouptut_ref in the patch.  I have attached a
corrected version of the patch.

I personally don't have a problem with making Perl 5.8 required for
PageKit.  If somebody doesn't like it, they can submit a patch to
make it run on both depending on if $] >= 5.008.

Thanks,
TJ

Ps. I got a "Can't locate PerlIO/ISO.pm in @INC" error when attempting
to run the patched PageKit on Perl 5.8.0/Linux 2.4.18.

On Wed, 13 Nov 2002, Boris Zentner wrote:

> Hi all,
> i installed perl5.8 and discovered, that Text::Iconv converts charsets to 
> something other but missed to inform perl about that change. Also p5.8 do the 
> conversion sometime by magic, but Text::Iconv did not know and convert it 
> again.
> 
> So i think with perl 5.8 we must get rid of Text::Iconv. This patch does that 
> as a first draft.
> 
> What do you want for future versions of PageKit?
> 
> WHAT ABOUT MAKING PERL 5.8 REQUIRED for PAGEKIT IN SOME MONTH?
> 
> 

Re: [Pagekit-devel] RFC: PageKit with perl5.8

[TJ M. <tjm...@ma...>]

Hi,

There is a mispelling of $$ouptut_ref in the patch.  I have attached a 
corrected version of the patch.

I personally don't have a problem with making Perl 5.8 required for 
PageKit.  If somebody doesn't like it, they can submit a patch to
make it run on both depending on if $] >= 5.008.

Thanks,
TJ

On Wed, 13 Nov 2002, Boris Zentner wrote:

> Hi all,
> i installed perl5.8 and discovered, that Text::Iconv converts charsets to 
> something other but missed to inform perl about that change. Also p5.8 do the 
> conversion sometime by magic, but Text::Iconv did not know and convert it 
> again.
> 
> So i think with perl 5.8 we must get rid of Text::Iconv. This patch does that 
> as a first draft.
> 
> What do you want for future versions of PageKit?
> 
> WHAT ABOUT MAKING PERL 5.8 REQUIRED for PAGEKIT IN SOME MONTH?
> 
> 

[Pagekit-devel] RFC: PageKit with perl5.8

[Boris Z. <bo...@2b...>]

Hi all,
i installed perl5.8 and discovered, that Text::Iconv converts charsets to 
something other but missed to inform perl about that change. Also p5.8 do the 
conversion sometime by magic, but Text::Iconv did not know and convert it 
again.

So i think with perl 5.8 we must get rid of Text::Iconv. This patch does that 
as a first draft.

What do you want for future versions of PageKit?

WHAT ABOUT MAKING PERL 5.8 REQUIRED for PAGEKIT IN SOME MONTH?

-- 
Boris

[Pagekit-devel] fix for the search of page attrs

[Boris Z. <bo...@2b...>]

Hi,

Glenn Morgan find and fix a problem with the search of page attrs. If a page 
has a attr, and a section attr then wrongly the section attr is overlooked.

Thanks for the fix!
-- 
Boris

[Pagekit-devel] minor fix for the eg site.

[Boris Z. <bo...@2b...>]

Hi All,
here is a little correction to the example site.

-- 
Boris

[Pagekit-devel] Config.xml - Section attribs as defaults for Page attribs bug

[Glenn M. <Gl...@Mo...>]

Hi all

There appears to be a bug in config.pm or documentation, take your pick.
Can't find any mention of a fix so here are my findings.

Docs says....

Tags with the longest matching part of the id attribute provide the
defaults for pages without the attribute in question. <PAGE> attributes
written in the <PAGE> tag have the highest priority. If nothing is found
the <SECTION> Tags are scanned for a default.

I assume this means if we have the following 

<SECION id="/" require_login="recent">

<PAGE id="/somepage" browser_cache="no">

"/somepage" should still require a recent login because it does not have
a "require_login" attribute.


The code says.... (config.pm)

124	sub get_page_attr {
125	  my ($config, $page_id, $key) = @_;
126	  my $config_dir = $config->{config_dir};
127
128	  if ( exists $page_attr->{$config_dir}->{$page_id} ) {
129	    return $page_attr->{$config_dir}->{$page_id}->{$key};
130	  }
131
132	  # here page_id IS the section_id
133	  while ( $page_id =~ s!^(.*)/+[^/]*$!$1! ) {
134	    if ( exists $section_attr->{$config_dir}->{$page_id} ) {
135	      return $section_attr->{$config_dir}->{$page_id}->{$key};
136	    }
137	  }
138
139	  # test for a global default in the section '/' or ''
140	  return $section_attr->{$config_dir}->{''}->{$key};
141	}

shouldn't line 128 be checking the specific page attribute (ie.
$page_attr->{$config_dir}->{$page_id}->{$key}) and not just checking
whether the page has any, possibly unrelated, attributes.  And the same
goes for 134.  That way default attributes will be read from the lower
priority tag if they don't exist in higher priority tags.  Or, mod the
docs to correctly describe the current behaviour.  I prefer a code
patch.


Cheers

Glenn

Re: [Pagekit-devel] Re: no_sessions?

[Boris Z. <bo...@2b...>]

Hi Russell,

Am Mittwoch, 2. Oktober 2002 16:32 schrieb Russell D. Weiss:
> Hi Boris,
>
> Somehow I didn't see the patch on the last e-mail you sent.  Thanks!  T=
his
> patch "almost" works -- it didn't work, but I realized it's because of
> order of operations / combining of conditions...
>
> The line:
> if ($model->pkit_get_config_attr( 'PAGE', $pk->{page_id}, 'use_sessions=
' )
>
> || 'yes' eq 'yes' ) {
>
> should be changed to... (the 'yes' was OR'd in the wrong order)... perl=
 was
> saying "Of course 'yes' equals 'yes'!

okok you are right, i want to be sure you prove read it  ;-)

> if ( ($model->pkit_get_config_attr( 'PAGE', $pk->{page_id}, 'use_sessio=
ns'
> )
>
> || 'yes') eq 'yes' ) {
>
> Also, I notice it's only a PAGE attribute.  Can this be extended to SEC=
TION

No, it works also if you put some lines in the section part of the config.
 Try it.

> and possibly even GLOBAL.  I can see the potential usefulness of having=
 it
> be a SECTION attribute, and believe it or not, some people might put up
> sites that don't need use sessions at all.

these people should use <SECTION id=3D"/" use_sessions=3D'no'/>.

> Thanks for the great work and the quick response!

Thank you rusell. For testing and the explaning text of this option. I ta=
ke
part of it for the docs.

> Russell Weiss
> Founder & Technical Manager
> InfoRelay Online Systems, Inc.
> http://www.inforelay.com/
>
>
>
> ----- Original Message -----
> From: "Boris Zentner" <bo...@id...>
> To: "Russell D. Weiss" <rw...@in...>
> Sent: Wednesday, October 02, 2002 9:18 AM
> Subject: Re: no_sessions?
>
> > Hi Russell,
> >
> > Am Mittwoch, 2. Oktober 2002 14:55 hast Du geschrieben:
> > > Hey Boris, any word on my no_sessions question / idea?  I'm assumin=
g
> > > the feature isn't there? I'm hoping you can at least see the useful=
ness
> > > of
>
> it?
>
> > > Since you definitely seem to be the resident expert on PageKit, I'm
> > > wondering if you can suggest the best way to hack the session
>
> authorization
>
> > > methods to achieve this sort of functionality.
> >
> > Im not a native english speaker as you might know already. So maybe i
>
> missed
>
> > what you asked for. But on my answer to your first request for a
>
> no_session
>
> > attribute, i attached a patch that do what you want for the PAGE and
>
> SESSION
>
> > config options. also i have not tested the patch. If it works the way=
 you
> > need/like it i put it in the next version of pageKit.
> >
> > to be sure you get the patch now, i attch it again. And i renamed he
> > no_session attribute to use_sessions it defaults to 'yes'
> >
> > please try it and report your results.
> >
> > > Unless there are plans to add this sort of thing in as a PageKit
> > > feature
> > >
> > > :-).
> > >
> > > Thanks,
> > > Russell
> >
> > --
> > cu boris
> >
> > Kommt ein Mann in ein Herrenbekleidungsgesch=E4ft:
> > "Ich h=E4tte gern einen neuen schwarzen Blazer!""
> > Der Verk=E4ufer mit leicht n=E4selnder Stimme:
> > "Oh ja, ich auch..."
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Pagekit-devel mailing list
> Pag...@li...
> https://lists.sourceforge.net/lists/listinfo/pagekit-devel

--
Boris

[Pagekit-devel] Re: no_sessions?

[Russell D. W. <rw...@in...>]

Hi Boris,

Somehow I didn't see the patch on the last e-mail you sent.  Thanks!  This
patch "almost" works -- it didn't work, but I realized it's because of order
of operations / combining of conditions...

The line:
if ($model->pkit_get_config_attr( 'PAGE', $pk->{page_id}, 'use_sessions' )
|| 'yes' eq 'yes' ) {

should be changed to... (the 'yes' was OR'd in the wrong order)... perl was
saying "Of course 'yes' equals 'yes'!

if ( ($model->pkit_get_config_attr( 'PAGE', $pk->{page_id}, 'use_sessions' )
|| 'yes') eq 'yes' ) {

Also, I notice it's only a PAGE attribute.  Can this be extended to SECTION
and possibly even GLOBAL.  I can see the potential usefulness of having it
be a SECTION attribute, and believe it or not, some people might put up
sites that don't need use sessions at all.

Thanks for the great work and the quick response!

Russell Weiss
Founder & Technical Manager
InfoRelay Online Systems, Inc.
http://www.inforelay.com/



----- Original Message -----
From: "Boris Zentner" <bo...@id...>
To: "Russell D. Weiss" <rw...@in...>
Sent: Wednesday, October 02, 2002 9:18 AM
Subject: Re: no_sessions?


>
> Hi Russell,
>
> Am Mittwoch, 2. Oktober 2002 14:55 hast Du geschrieben:
> > Hey Boris, any word on my no_sessions question / idea?  I'm assuming the
> > feature isn't there? I'm hoping you can at least see the usefulness of
it?
> > Since you definitely seem to be the resident expert on PageKit, I'm
> > wondering if you can suggest the best way to hack the session
authorization
> > methods to achieve this sort of functionality.
>
> Im not a native english speaker as you might know already. So maybe i
missed
> what you asked for. But on my answer to your first request for a
no_session
> attribute, i attached a patch that do what you want for the PAGE and
SESSION
> config options. also i have not tested the patch. If it works the way you
> need/like it i put it in the next version of pageKit.
>
> to be sure you get the patch now, i attch it again. And i renamed he
> no_session attribute to use_sessions it defaults to 'yes'
>
> please try it and report your results.
>
> >
> > Unless there are plans to add this sort of thing in as a PageKit feature
> > :-).
> >
> > Thanks,
> > Russell
>
> --
> cu boris
>
> Kommt ein Mann in ein Herrenbekleidungsgeschäft:
> "Ich hätte gern einen neuen schwarzen Blazer!""
> Der Verkäufer mit leicht näselnder Stimme:
> "Oh ja, ich auch..."
>

[Pagekit-devel] minor cleanup

[Boris Z. <bo...@2b...>]

HI,
-- 
Boris

[Pagekit-devel] fix for empty parameters

[Boris Z. <bo...@2b...>]

Hi,
this patch is for empty parameters from Bill Karwin.
-- 
Boris

[Pagekit-devel] PKIT_MACROexpansion

[Boris Z. <bo...@2b...>]

Hi,

this patch fix the PKIT_MACRO expansion for components WITHOUT any parameters.

-- 
Boris

[Pagekit-devel] Conversion bug with Content

[Erik <eri...@bo...>]

Hi, again

Now it seams that I have found an other conversion bug. Previous I mail
about a problem when using XML::LibXML when fetching a search result.
The solution to that problem was to use Text::Iconv on the result with
works fine.

Now I have found an other place where same type of bug emerge. It is
when I use Content (and file.xml) with default input and output set to
ISO-8859-1. All text not in the content file don't get converted back
from UTF-8. This happens both with UTF-8 and ISO-8859-1 encoding on the
content file.=20

If I set the default input to UTF-8 all woks fine except that I get an
error on other pages saying that it can't convert to ISO-8859-1 from
UTF-8 (on line ~505 in .../PageKit/View.pm) and dies.
  =20
If I remove the component that use Content all works as expected. (no
error in converting chars on any page). So I guess that
PageKit/Content.pm has to be aware of that the default output and input
and convert the text if needed.

This happens in perl 5.6.1.


--=20

   /erikg=20
  =20
Erik G=FCnther                                     eri...@bo...
System Developer                                               Bokus AB
+46 (0)40 - 35 21 19                                           =20
 =20
Fortune:
Presidency:  The greased pig in the field game of American politics.
-- Ambrose Bierce

Re: [Pagekit-devel] virtual pages

[Boris Z. <bo...@am...>]

Hello Ben,

Am Montag, 30. September 2002 15:39 schrieb Ben Ausden:
> Hi,
>
> can anyone think of a way of handling 'virtual' URLs, e.g.
>
> /index   ->  maps to /index.tmpl (as normal)
> /something   ->  maps to /another/place/something.tmpl
> /else   ->  maps to /go/here.tmpl
>
>
> I originally wrote a pkit_default sub to handle this, then realized PageKit
> won't even run it, because something.tmpl doesn't exist. The reason I need
> is it because I need to be able to create simple URLs which map to complex
> URLs (stored in the database), so they can be displayed in advertisements,
> hoardings, bus shelters etc etc. I'd rather not have to create dummy
> templates to handle each URL.
>
> any ideas that don't involve hacking PageKit.pm ??!!
>
> ;-)

maybe pkit_fixup_uri is enough for this.

in Common.pm
sub pkit_fixup_uri {
  my $model = shift;
  my $uri = shift;
  my %map = ( '/something'=>'/another/place/something','/else'=>'/go/here');
  $map{$uri} || $uri;
}

-- 
Boris

[Pagekit-devel] virtual pages

[Ben A. <Ben...@na...>]

Hi,

can anyone think of a way of handling 'virtual' URLs, e.g.

/index   ->  maps to /index.tmpl (as normal)
/something   ->  maps to /another/place/something.tmpl
/else   ->  maps to /go/here.tmpl


I originally wrote a pkit_default sub to handle this, then realized =
PageKit won't even run it, because something.tmpl doesn't exist. The =
reason I need is it because I need to be able to create simple URLs =
which map to complex URLs (stored in the database), so they can be =
displayed in advertisements, hoardings, bus shelters etc etc. I'd rather =
not have to create dummy templates to handle each URL.

any ideas that don't involve hacking PageKit.pm ??!!

;-)


regards,
ben

[Pagekit-devel] Re: [Pagekit-users] SECTION no_session attribute?

[Russell D. W. <rw...@in...>]

Sometimes you just don't want to create a session or attempt to look for
one... mostly for efficiency purposes...

For example, if PayPal IPN (instant payment notification), or another
credit-card validation system is calling my server (in most cases just one
POST to a CGI will be made, and their client [server, actually] won't store
the cookie I'm sure anyway), there is no reason to bother creating a session
or seeing if one exists.

In other cases, such as running a URL redirection service (which my company
is doing, though currently not using pagekit), there is absolutely no reason
to trigger session creation or look for a session.  Users typically hit the
server once, and they are instantly redirected to another site.  Thousands
of hits come in per hour, and creating a session is simply not efficient of
CPU, disk, etc..  Especially because Apache::SessionX doesn't ever seem to
clean up old sessions from the database (am I missing something here), and
manual cleanups must be done, it makes sense to not create sessions at all
when you won't need them.

Well, it least it makes sense to me, but what do I know :-).

Ideally I'd like to see a no_session attribute which can be put in the
SECTION section (and possibly other sections) of the config file.

Thanks,
Russell

----- Original Message -----
From: "Boris Zentner" <bo...@am...>
To: "Russell D. Weiss" <rw...@in...>;
<pag...@li...>
Cc: "pkit devel" <pag...@li...>
Sent: Monday, September 30, 2002 4:53 AM
Subject: Re: [Pagekit-users] SECTION no_session attribute?


>
> Hi,
>
> Am Samstag, 28. September 2002 17:40 schrieb Russell D. Weiss:
> > I'd like to effectively make certain pages or sections not trigger the
> > creation of a new session, or attempt to look for a current session.
>
> could you please elaborate, why this is usefull at all?
>
> >
> > I did session any sort of attribute like this in the config.
documentation.
> >  I could probably manually edit pkit_session_setup and/or
> > pkit_auth_credential to get this working, but I'm wondering if there's a
> > config attribute.
>
> We do not have a option for this right now. But find a untested patch that
may
> work. A new page attribute use_sessions. It defaults to 'yes'.
>
> So a use_sessions='no' in the section or page config part may (should)
work.
>
> --
> Boris
>

[Pagekit-devel] Re: [Pagekit-users] SECTION no_session attribute?

[Boris Z. <bo...@am...>]

Hi,

Am Samstag, 28. September 2002 17:40 schrieb Russell D. Weiss:
> I'd like to effectively make certain pages or sections not trigger the
> creation of a new session, or attempt to look for a current session.

could you please elaborate, why this is usefull at all?

>
> I did session any sort of attribute like this in the config. documentation.
>  I could probably manually edit pkit_session_setup and/or
> pkit_auth_credential to get this working, but I'm wondering if there's a
> config attribute.

We do not have a option for this right now. But find a untested patch that may 
work. A new page attribute use_sessions. It defaults to 'yes'.

So a use_sessions='no' in the section or page config part may (should) work.

-- 
Boris

Re: [Pagekit-devel] PKIT_MACRO expansion in nested templates.

[Boris Z. <bo...@2b...>]

Sorry, i attached the wrong patch. Here is the right one.

Am Freitag, 20. September 2002 16:34 schrieb Boris Zentner:
> Hi,
>
> this patch fix PKIT_MACRO expansion in nested templates. Reported from
> Russell Weiss. Thanks!

-- 
Boris

[Pagekit-devel] PKIT_MACRO expansion in nested templates.

[Boris Z. <bo...@2b...>]

Hi,

this patch fix PKIT_MACRO expansion in nested templates. Reported from Russell 
Weiss. Thanks!

-- 
Boris

[Pagekit-devel] PATCH: setup.pl

[Boris Z. <bo...@2b...>]

Hi,

this patch makes setup.pl (more) os independend.
-- 
Boris