Thanks for the suggestion, Eemeli. Unfortunately, that just gave me a blank
page.
BTW, for those of you trying this at home, the solution I came up with earlier
doesn't handle the default being set by the site. To allow for a Site default
password requires an even more clumsy solution.
In a
On 12 July 2010 21:07, Randy Brown wrote:
> Thanks, Eemeli.
> That works as you described for passwords set on the page. Unfortunately,
> some of my pages inherit the attributes. I've tried numerous variations of
> your code, but haven't figured out how to do the test for Group and
> Site-inherite
I've found a clumsy solution, I think:
## Config file code to allow test of whether a page's password is world
readable;
## $Pagereadpswd refers to the page's read attribute, ignoring its inherited
value
$Pagereadpswd = "(trim(@\$page['passwdread']))";
$FmtPV['$Pagereadpswd'] = $Pagereadpswd;
Try
(:linebreaks:) (:comment -- make line breaks in markup significant ---:)
This is my
two lines of text
(:nolinebreaks:)
Randy
On Jul 12, 2010, at 5:54 PM, Ivan Mann wrote:
> I am converting a lot of web pages to PmWiki. Some of them have over a
> hundred lines of lists that I would like t
I am converting a lot of web pages to PmWiki. Some of them have over a
hundred lines of lists that I would like to appear in the PmWiki pages
pretty much the same way - a line followed by a blank line followed by the
next line, followed by a blank line, and so forth. Cutting and pasting into
the
On Monday 12 July 2010 21:09:51, Omniware Systems wrote :
> Thank you very much for your prompt and descriptive answer; both
> helped in resolving the problem
> and pointing me to the actual documentation section.
>
> What I didn't put in the original email was I'm very new at PmWiki and
> e
Hello Petko,
Thank you very much for your prompt and descriptive answer; both
helped in resolving the problem
and pointing me to the actual documentation section.
What I didn't put in the original email was I'm very new at PmWiki and
even searching the
documentation sometimes you miss t
Thanks, Eemeli.
That works as you described for passwords set on the page. Unfortunately, some
of my pages inherit the attributes. I've tried numerous variations of your
code, but haven't figured out how to do the test for Group and Site-inherited
attributes. Is that possible? If so, any hints?
On 12 July 2010 18:15, Randy Brown wrote:
> I'm using AuthUser. Version pmwiki-2.2.0-beta65 (and possibly later versions)
> allowed me to test whether a page was world readable by checking the value of
> {*$PasswdRead}. In the current version (pmwiki-2.2.17) that ability now seems
> to be gone
I'm using AuthUser. Version pmwiki-2.2.0-beta65 (and possibly later versions)
allowed me to test whether a page was world readable by checking the value of
{*$PasswdRead}. In the current version (pmwiki-2.2.17) that ability now seems
to be gone for users without attr authorization: they now just
On 7/12/2010 6:00 AM, Ville Takanen wrote:
Is the recipe at
http://www.pmwiki.org/wiki/Cookbook/AuthUserOpenId still actively
maintained?
The last page update by the author *seems* to be back in 2006/7 (page
history has been truncated due to inactivity). The authors domain name
is also expire
Hi Ville,
I've tried using that one, and couldn't get it to work universally (I
think it worked with one OpenID provider for a while, but it never
worked with, for example LiveJournal).
I did a bit of looking around (it's quite tricky googling for OpenID and
PmWiki: mostly you get pmwiki sit
Hi
I just uploaded initial release for Facebook like-button recipe to
http://www.pmwiki.org/wiki/Cookbook/FacebookLikeButton
I also have an updated/rewritten recipe for OpenID authentication with
differnet library components and better google support than the one in the
Cookbook. Is the recipe at
13 matches
Mail list logo
