[pmwiki-users] Recipe's for Facebook Like buttons and OpenID userauth
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 http://www.pmwiki.org/wiki/Cookbook/AuthUserOpenId still actively maintained? Yours Ville Takanen ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] Recipe's for Facebook Like buttons and OpenID userauth
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 sites talking about openID) and found a couple of sites that seemed to have been using OpenID for PmWiki at some point in the past, but seemed to be now broken (and emails to the folk running the sites generally went unanswered). I look forward to giving yours a shot! Cheers Steve 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 http://www.pmwiki.org/wiki/Cookbook/AuthUserOpenId still actively maintained? Yours Ville Takanen ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users -- Steve Glover: SDSS, EDINA, Causewayside House, 160 Causewayside EH9 1PR e:steve.glo...@ed.ac.uk t:0131 650 2908 f:0131 650 3308 m:07961 446 902 The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] Recipe's for Facebook Like buttons and OpenID userauth
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 expired. A quick search through the mail archive didn't turn up anything that appeared to be from the author. These *suggest* that the recipe is no longer actively maintained. ~ ~ Dave ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
[pmwiki-users] How to detect if a page has @nopass for the read password
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 see
(protected) even if they have the right to read the page.
Is there another way to write a conditional to detect whether a page's read
password is @nopass?
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] How to detect if a page has @nopass for the read password
On 12 July 2010 18:15, Randy Brown alongk...@aprivatespot.com 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 for users without attr authorization: they now just see
(protected) even if they have the right to read the page.
Is there another way to write a conditional to detect whether a page's read
password is @nopass?
Slightly hacky, but should work provided that the @nopass is set
directly for the page, and not inherited from the GroupAttributes
page:
Add to a config file:
$FmtPV['$NoReadPasswd'] = (trim(@\$page['passwdread']) === '@nopass')
? 'true' : 'false';
and then try the conditional:
(:if {*$NoReadPasswd}:)1(:else:)0(:ifend:)
eemeli
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] How to detect if a page has @nopass for the read password
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? Randy P.S. This is a pretty important conditional if you want to put visibility-dependent things like RSS links or Facebook Like buttons (http://www.pmwiki.org/wiki/Cookbook/FacebookLikeButton) on a page. I'm thinking if I display links and buttons on a page that won't service them due to password protection, it will just confuse users. On Jul 12, 2010, at 11:45 AM, Eemeli Aro wrote: Slightly hacky, but should work provided that the @nopass is set directly for the page, and not inherited from the GroupAttributes page: ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] Attach: Image - Cant attach after 2 page layers.
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 the relevant points. Many Thanks Kind Regards Terry M. Fake 7 Stanley Ave West Pennant Hills NSW 2125 Ph: +61 2 9873 4844 Fx: +61 2 9873 4855 Mo: 0412022572 Em: syst...@omniwaresystems.com.au * VOIP Phone Systems* Firewalls * UPS Power Protection * MINDER Business * Competitive Information* AVG Antivirus Software SoftwareSystems -Original Message- From: Petko Yotov [mailto:5...@5ko.fr] Sent: Monday, 12 July 2010 09:26 To: Omniware Systems Cc: pmwiki-users@pmichaud.com Subject: Re: [pmwiki-users] Attach: Image - Cant attach after 2 page layers. On Sunday 11 July 2010 10:29:39, Omniware Systems wrote : Problem: Using the Attach: command to display an image in the PMWiki page after two page layers ... I can get the Attach: cmd to work in the Main, FAQ's page using Attach:error47.jpg On the System Settings and Administration page I can only get it to work using Attach:main.FAQS/error47.jpg This is no good as it presupposses the image has been displayed previously at a higher level; which can not happen in all situations. It is possible these pages could go to 5 - 6 layers Read read the Basic Editing and Documentation Index section and Googled but didn't find my answer ( that I could see). Hello. Please see the notes about $UploadPrefixFmt at the pages: http://www.pmwiki.org/wiki/PmWiki/UploadsAdmin http://www.pmwiki.org/wiki/PmWiki/UploadVariables#UploadPrefixFmt In the default pmwiki installation, when you attach a file, it is attached to the WikiGroup so for example all pages in Main.* can display it with Attach:file.jpg . You seem to want this to work from all pages and all groups, in that case, you can set Single upload directory for site-wide uploads. This is configured with such a line in config.php: $UploadPrefixFmt = ''; Note that after this, all your current files will not be visible, until you mive them like this: from : pmwiki/uploads/Main/error47.jpg to:pmwiki/uploads/error47.jpg and so on for all your files. (After the change, the line Attach:main.FAQS/error47.jpg will still work, but the part main.FAQS/ will not be required. Thanks, Petko ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] Attach: Image - Cant attach after 2 page layers.
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 even searching the documentation sometimes you miss the relevant points. You're very welcome -- if you have other questions, just ask again. We should try to improve the documentation, so if you don't find what you need, or if it isn't clear enough, or if you find something that can be improved, you can either edit the page and improve it, or leave a message or a question on the related talk page, or e-mail to the mailing list (or to me). Thanks, Petko ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
[pmwiki-users] Pasting text from existing sources
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 PmWiki edit window it adds all the lines together and the output is not real readable. I don't want to just tell it preformated text because I would like to be able to put links and so forth in some places. I can, of course, add double slashes to the end of each line, but that is going to get tedious after a couple of minutes. Is there a markup or something that tells PmWiki to use carriage returns as carriage returns? -- Ivan Mann Any man who afflicts the human race with ideas must be prepared to see them misunderstood. H. L. Mencken ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] Pasting text from existing sources
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 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 PmWiki edit window it adds all the lines together and the output is not real readable. I don't want to just tell it preformated text because I would like to be able to put links and so forth in some places. I can, of course, add double slashes to the end of each line, but that is going to get tedious after a couple of minutes. Is there a markup or something that tells PmWiki to use carriage returns as carriage returns? -- Ivan Mann Any man who afflicts the human race with ideas must be prepared to see them misunderstood. H. L. Mencken ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] How to detect if a page has @nopass for the read password
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;
Then in markup put this:
(:if ( equal {*$Pagereadpswd} @nopass ) or
( ( equal {*$Pagereadpswd} ) and ( equal
{{*$Group}.GroupAttributes$Pagereadpswd} @nopass ) ):)
Randy
P.S. Does anyone have a better solution? Do you think the core should somehow
make this unnecessary? What would be a good change to the core?
On Jul 12, 2010, at 10:15 AM, 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 for users without attr authorization: they now just see
(protected) even if they have the right to read the page.
Is there another way to write a conditional to detect whether a page's read
password is @nopass?
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] How to detect if a page has @nopass for the read password
On 12 July 2010 21:07, Randy Brown alongk...@aprivatespot.com 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-inherited attributes. Is that possible? If so, any hints? Here's a still hacky but possibly more robust inheriting approach -- assuming that it works, as I haven't tested it: $FmtPV['$NoReadPasswd'] = ($GLOBALS['NoHTMLCache'] 2) ? 'false' : 'true'; That depends on not having a custom $AuthFunction, and no recipe fiddling with $NoHTMLCache in an odd way, and on RetrieveAuthPage() getting called at least once before PVs are resolved, all which I'm almost certain to be true in almost all cases. UserAuth might make that not work, but then you wouldn't be asking about @nopass since it handles access differently AFAIK. eemeli Randy P.S. This is a pretty important conditional if you want to put visibility-dependent things like RSS links or Facebook Like buttons (http://www.pmwiki.org/wiki/Cookbook/FacebookLikeButton) on a page. I'm thinking if I display links and buttons on a page that won't service them due to password protection, it will just confuse users. On Jul 12, 2010, at 11:45 AM, Eemeli Aro wrote: Slightly hacky, but should work provided that the @nopass is set directly for the page, and not inherited from the GroupAttributes page: ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] How to detect if a page has @nopass for the read password
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 config file put:
$PageReadPswd = (trim(@\$page['passwdread']));
$FmtPV['$PageReadPswd'] = $PageReadPswd;
$FmtPV['$SiteReadPswd'] = $DefaultPasswords['read'];
In markup on a page put:
(:if ( equal {*$PageReadPswd} @nopass ) or ( ( equal {*$PageReadPswd}
) and ( equal {{*$Group}.GroupAttributes$PageReadPswd} @nopass ) ) or ( (
equal {*$PageReadPswd} ) and ( equal
{{*$Group}.GroupAttributes$PageReadPswd} ) and ( equal {$SiteReadPswd}
nopass ) ) :)
Randy
On Jul 12, 2010, at 6:45 PM, Eemeli Aro wrote:
Here's a still hacky but possibly more robust inheriting approach --
assuming that it works, as I haven't tested it:
$FmtPV['$NoReadPasswd'] = ($GLOBALS['NoHTMLCache'] 2) ? 'false' : 'true';
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
