From tamouse.lists at gmail.com Wed Sep 2 21:33:21 2015 From: tamouse.lists at gmail.com (tamouse pontiki) Date: Wed, 2 Sep 2015 21:33:21 -0500 Subject: [pmwiki-users] my recipes In-Reply-To: <63c46ac283716d3cece4928dbed2fe63@5ko.fr> References: <63c46ac283716d3cece4928dbed2fe63@5ko.fr> Message-ID: I *think* I've updated all the cookbook and skin contributions I've made to PmWiki such that they include appropriate copyright and licensure and stuff like that. Cheers, all! On Fri, Aug 14, 2015 at 2:15 AM, Petko Yotov <5ko at 5ko.fr> wrote: > On 2015-08-14 00:46, tamouse pontiki wrote: > >> I'm not using PmWiki any more, and am not maintaining anything there. If >> the question comes up further for anything I've put there, a blanket >> answer >> would be to use the same license PmWiki uses itself, and if possible, I'd >> relinquish copyright to PmWiki Community. >> > > Hi Tamara, > > Thanks for your message. > > PmWiki is licensed under the GNU GPL, "either version 2 of the License, or > (at your option) any later version." > > If you license your recipes the same way, it may be easier for people if > some day PmWiki becomes licensed under a more recent version of the GNU GPL. > > The PmWiki community is not a legal entity so you cannot relinquish your > copyrights to it. But the fact that you select a free license allowing > modification and re-distribution is sufficient if there is a need to update > those recipes some day. > > My personal development has taken me in completely different directions >> > > Thanks and good luck to you! > > Petko > > > _______________________________________________ > pmwiki-users mailing list > pmwiki-users at pmichaud.com > http://www.pmichaud.com/mailman/listinfo/pmwiki-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xraysmalevich at gmail.com Fri Sep 4 09:31:04 2015 From: xraysmalevich at gmail.com (michael paulukonis) Date: Fri, 4 Sep 2015 10:31:04 -0400 Subject: [pmwiki-users] my recipes In-Reply-To: References: <63c46ac283716d3cece4928dbed2fe63@5ko.fr> Message-ID: Sad to see you go -- and thanks for all your contributions, and continuing wikizeniquette. To, uh, coin a word. -Michael Paulukonis http://www.xradiograph.com Interference Patterns (a blog) @XraysMonaLisa http://michaelpaulukonis.com Sent from somewhere in the Cloud (hearthrug, by the fender) On Wed, Sep 2, 2015 at 10:33 PM, tamouse pontiki wrote: > I *think* I've updated all the cookbook and skin contributions I've made > to PmWiki such that they include appropriate copyright and licensure and > stuff like that. > > Cheers, all! > > On Fri, Aug 14, 2015 at 2:15 AM, Petko Yotov <5ko at 5ko.fr> wrote: > >> On 2015-08-14 00:46, tamouse pontiki wrote: >> >>> I'm not using PmWiki any more, and am not maintaining anything there. If >>> the question comes up further for anything I've put there, a blanket >>> answer >>> would be to use the same license PmWiki uses itself, and if possible, I'd >>> relinquish copyright to PmWiki Community. >>> >> >> Hi Tamara, >> >> Thanks for your message. >> >> PmWiki is licensed under the GNU GPL, "either version 2 of the License, or >> (at your option) any later version." >> >> If you license your recipes the same way, it may be easier for people if >> some day PmWiki becomes licensed under a more recent version of the GNU GPL. >> >> The PmWiki community is not a legal entity so you cannot relinquish your >> copyrights to it. But the fact that you select a free license allowing >> modification and re-distribution is sufficient if there is a need to update >> those recipes some day. >> >> My personal development has taken me in completely different directions >>> >> >> Thanks and good luck to you! >> >> Petko >> >> >> _______________________________________________ >> pmwiki-users mailing list >> pmwiki-users at pmichaud.com >> http://www.pmichaud.com/mailman/listinfo/pmwiki-users >> > > > _______________________________________________ > pmwiki-users mailing list > pmwiki-users at pmichaud.com > http://www.pmichaud.com/mailman/listinfo/pmwiki-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 5ko at 5ko.fr Sun Sep 6 10:04:37 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Sun, 06 Sep 2015 17:04:37 +0200 Subject: [pmwiki-users] Strange issue with PageListSortCmp In-Reply-To: References: Message-ID: <82fd898d91a56a4a25d1b5c41d1541ff@5ko.fr> On 2015-08-31 10:07, ABClf wrote: > Fort the special sorting, in my config : > > # sorting pages by numerical integer pagetextvar data > function IntegerDataCompare($x, $y, $var) { > # get integer value of the page text variable > $xval = intval(PageTextVar($x, $var)); > $yval = intval(PageTextVar($y, $var)); > # compare integer values > if($xval > $yval) $c = 1; > elseif($xval < $yval) $c = -1; > else $c = 0; > return $c; > } > > $PageListSortCmp['registre_origine'] = 'IntegerDataCompare($x, $y, > "registre_origine")'; > > My pagelist : > > (:pagelist group=Bob link=Source.2048 $:registre_origine=- > fmt=#registre order=registre_origine:) > > Strangely, it's half working, half broken : data are ordered, but it > looks like the list is splitted : I get something like this, (where x > appears as if it were empty) : 10 10 10 9 9 8 8 7 7 6 6 5 5 4 4 3 x 10 > 10 9 9 (etc., list continues, broken several times by an empty value). Thanks for your message and for letting me test your wiki -- it uncovered an issue I haven't contemplated. This error in sorting is caused by the large number of calls to the core function PageTextVar(). When that happens, you quickly hit the $MaxPageTextVars limits which are set to prevent infinite loops like these: Var1: {$:Var2} Var2: {$:Var1} Obviously, in a pagelist sorting we don't risk an infinite loop, but a variable of a page will be compared hundreds of times to the same variable on hundreds of other pages. I have updated the custom pagelist sort functions documented in the Cookbook to directly use the "cached" variables instead of calling PageTextVar() every time: http://www.pmwiki.org/wiki/Cookbook/CustomPagelistSortOrderFunctions I'll think about maybe adding a switch in the core to temporarily ignore $MaxPageTextVars from a custom local function. But for now use the helper function I wrote at the above page. Petko -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades If this message helped you and saved you time, feel free to make a small contribution: ? http://5ko.fr/donate-ml (mailing list). From unfies at gmail.com Wed Sep 9 06:01:16 2015 From: unfies at gmail.com (Will Langford) Date: Wed, 9 Sep 2015 06:01:16 -0500 Subject: [pmwiki-users] Stand alone wiki on an Android device ? In-Reply-To: References: <55DF698A.8090309@gmail.com> Message-ID: Did a tiny bit of work on this.. not a whole lot. Not wanting to spend even $2 on a webserver, was looking at free stuff. ---- "Server for PHP" is free, but pmwiki don't work apparently. Has no ads though, which is nice and kinda makes it preferred heh. pmwiki.php - Call to undefined function crypt() in pmwiki.php line 480 I kinda don't understand how that error is even possible heh. Aint crypt() a built in?! ---- "Palapa Web Server" is free, and might work. It has ads on it's status screen though, which is irksome. Based on lighthttpd. Extracting the wiki to it and browsing to it yielded a permissions problem on wiki.d ... restarting the server seemed to fix it. During the restart, also added pmwiki.php to it's list of "index" files. Was able to edit Main/Homepage without drama. Copied over sample-config.php, renamed it, set the script/pub url's and wiki / site name. Seems okay. Haven't tried uploads yet. Haven't done any the rewrite rules stuff for clean url's etc. -unfy / Will On Thu, Aug 27, 2015 at 4:45 PM, Edwin Marte wrote: > Hello William, > > I haven't tried that but I think the idea is interesting and could be very > useful. I did a quick search and found a few options that may o may not > work. Pmwiki only needs a php server as far as I understand so we have Ultil > Server > , > Droidphp and here there is a good tutorial > . > > I haven't tested none of them but I surely sometimes during this week will > try Ultil Server. > > I hope this helps and looking forward to see your results > > On Thu, Aug 27, 2015 at 2:48 PM, William Langford > wrote: > >> 'lo, >> >> First, a LONG preface. Six months ago I bought an android based tablet. >> It's a nice Yoga 2 from Lenovo. Not bottle barrel atom processor, 1080p >> screen, 20+ hours of battery life, 2 weeks of stand by time (or >> something). The hardware seems to fit my base desires for a tablet just >> fine (save maybe the fact that it doesn't have a stylus holder). >> >> The thing is, I still can't find a practical use for the thing. I have >> no desire to use it as a media consumption device (see also: youtube, >> netflix, facebook, etc). I don't really "skype" or whatever a lot either. >> I do have an electronics workbench with a nice DSO and stuff... so I've >> naturally downloaded some electronics related apps (formulas, resistor >> codes, etc). Also grabbed the thread pitch tool cause... I dunno. Lastly, >> Xodo so that I can draw on (pdf) schematics while assembling boards or >> whatever. >> >> Buuuutttt... it's still of limited use. >> >> Found something called "UrForms" which seems to be a slapped together >> front end for working with sqlite databases. Now we're getting slightly >> more useful. I've created some basic "forms" (aka tables?) for listing >> some stuff I own, some stuff I want, etc. Sadly, the interface is a bit >> lacking. >> >> ---- >> >> Getting to the point. >> >> Why the )!(Q*%)(* just not run PmWiki on the thing ? I really do love / >> use pmwiki for a lot of things already. As a semi-personal database of >> sorts it makes sense! >> >> I want it self contained within the tablet without internet connectivity >> required. I've looked at the Standalone and WikiOnAStick cookbook, and >> neither really suit my needs. >> >> Has anyone done a PmWiki install running from an Android device ? >> >> Was there a particular web server / setup they liked working with ? >> >> Any warnings / pit falls ? >> >> I don't think I've got root on the tablet, btw. >> >> Any thoughts on accessing from outside the device (such as >> http://tablet:4242/wiki/ ... or somehow having a different webserver >> access the files on the tablet somehow) ? Being able to access the wiki >> from a computer would be handy (see also: bigger screen / better keyboard, >> etc) ? >> >> In the coming weeks, I'll prolly go about making this happen on my own - >> and will either report back here or make a 'cookbook' out of it (even if >> just documentation ?). >> >> -Will / unfy >> >> >> _______________________________________________ >> pmwiki-users mailing list >> pmwiki-users at pmichaud.com >> http://www.pmichaud.com/mailman/listinfo/pmwiki-users >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burggraaferik at gmail.com Thu Sep 10 11:29:47 2015 From: burggraaferik at gmail.com (erik burggraaf) Date: Thu, 10 Sep 2015 09:29:47 -0700 Subject: [pmwiki-users] Notes from the useradmin talk page. Message-ID: <9AA788D2-7DFC-45C3-B5DA-B85DD25EA830@gmail.com> Hi all, Now that my useradmin dbase is set up and working, I have a few questions. I went off to the talk page and it didn't answer my questions, but it at least let me know that others are thinking along the same lines. First, where are the instructions for adding groups in useradmin Dbase? I did not see them in the configuration section of the recipe page, but I see from the talk page that some one got it up and working. Second, another user from the talk page wanted to discuss extending member profiles and adding pieces of information, presumably name, contact info, and so on. I have instructions for how to do this and I will play with it a bit. Final thing from the talk page. We want to do an operation where we collect info from users, save that info, then direct users to a payment solution. For example, registering for a conference held by the organisation. We want users to fill out their registration online, then be taken directly through the process of paying the sign up fee. I would appreciate any thoughts you all may have. Of course, I will chip away at these things myself little by little, but at the moment I'm really daungted by the whole idea. If I could get a pointer to the instructions for DBase groups then I could at least practice extending the sign up form and see how users get added to groups. THanks, Erik From jimbo.molo at gmail.com Fri Sep 11 13:48:36 2015 From: jimbo.molo at gmail.com (Jimbo Molo) Date: Fri, 11 Sep 2015 11:48:36 -0700 Subject: [pmwiki-users] AD Auth Failing in IIS8 Message-ID: I'm unable to get AD auth working via IIS8. I've read the instructions on the following pages to configure the lines below in local/config.php but continue to receive the error "Name/password not recognized": http://sfwiki01/pmwiki.php?n=PmWiki.AuthUser http://www.pmwiki.org/wiki/Cookbook/AuthUserViaMicrosoftLDAP $AuthLDAPBindDN = "mydc.com\\username"; $AuthLDAPBindPassword = "password"; $DefaultPasswords['read'] = 'password'; #$HandleAuth['diff'] = 'edit'; #$DefaultPasswords['edit'] = 'id:*'; #$Author = $AuthId; $AuthUser['ldap'] = 'ldap://ldap.mydc.com/'; include_once("$FarmD /scripts/authuser.php"); I've also added "ldap_set_option($ds, LDAP_OPT_REFERRALS, 0);" after "ldap_set_option($ds, LDAP_OPT_PROTOCOL_VERSION, 3);" in scripts/authuser.php ( http://www.pmwiki.org/wiki/Cookbook/AuthUserViaMicrosoftLDAP-Talk ) to no avail. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From design at softflow.co.uk Mon Sep 14 07:21:52 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 14 Sep 2015 13:21:52 +0100 Subject: [pmwiki-users] formatting title markup directive Message-ID: <173953165.20150914132152@softflow.co.uk> How can I apply inline styling for the (:title ...:) directive? In particular I would like to be able to use inline markup '^text^' (HTML sup) and '_text_' (HTML sub) I can use it after ! header markup, but not within the title markup. Is it possible? Any hacks for it? thanks Hans From byronlunz at gmail.com Mon Sep 14 13:56:01 2015 From: byronlunz at gmail.com (Byron Lunz) Date: Mon, 14 Sep 2015 11:56:01 -0700 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please Message-ID: I've been happily using pmwiki & the notsosimple skin for several years. But I've run into a problem and I'm not skilled enough with CSS or pmwiki to find the solution. Is anyone here able to help? You can reply off-list to keep down the noise if you prefer. The issue is that the notsosimple skin has a fixed width of about 900px. The SideBar then consumes 160px of that width on every page. But I now have a page where I need more width and I'd like the SideBar to collapse/disappear on that page and only that page. I found a reference to (:noleft:) but it's not working on my installation. Is anyone able to assist me or point me in the right direction? -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.rankin at affinity.co.nz Mon Sep 14 14:26:47 2015 From: john.rankin at affinity.co.nz (John Rankin) Date: Tue, 15 Sep 2015 07:26:47 +1200 Subject: [pmwiki-users] formatting title markup directive In-Reply-To: <173953165.20150914132152@softflow.co.uk> References: <173953165.20150914132152@softflow.co.uk> Message-ID: <3444406e2723f08c732f8235251286df.squirrel@mail.affinity.co.nz> > How can I apply inline styling for the (:title ...:) directive? > > In particular I would like to be able to use inline markup > '^text^' (HTML sup) and '_text_' (HTML sub) > > I can use it after ! header markup, but not within the title markup. > Is it possible? Any hacks for it? > > thanks > Hans > You could try the following in local/config.php: $tmpwhen = IsEnabled($EnablePageTitlePriority, 0) ? 'inline'; $tmpkeep = IsEnabled($EnablePageTitlePriority, 0) ? '1' : 'NULL'; Markup_e('title', $tmpwhen, '/\\(:title\\s(.*?):\\)/i', "PZZ(PCache(\$pagename, \$zz=array('title' => SetProperty(\$pagename, 'title', PSS(\$m[1]), NULL, $tmpkeep))))"); unset($tmpwhen, $tmpkeep); This should evaluate the title directive after the inline markup rules. Good luck! JR -- John Rankin From design at softflow.co.uk Mon Sep 14 14:52:30 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 14 Sep 2015 20:52:30 +0100 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: References: Message-ID: <505027939.20150914205230@softflow.co.uk> > I've been happily using pmwiki & the notsosimple skin for several > years. But I've run into a problem and I'm not skilled enough with > CSS or pmwiki to find the solution. Is anyone here able to help? You > can reply off-list to keep down the noise if you prefer. > The issue is that the notsosimple skin has a fixed width of about > 900px. The SideBar then consumes 160px of that width on every page. > But I now have a page where I need more width and I'd like the > SideBar to collapse/disappear on that page and only that page. I > found a reference to (:noleft:) but it's not working on my installation. you would need to edit the notsosimple.tmpl file. You could try this: swap these lines in the tmpl file: The tmpl file is also missing markup for (:noleft:) to work, but since you want to change width for one specific page, you could change some css rules via a Group.PageName.css file (name of Group and page for which you want css changes) in the pub/css/ folder. Create such file and add to it something like this: #header, #main { width: 1200px; } /*set your page width*/ #content { width: 1150px; } /*adjust main div width*/ #wikitext { width: 1100px } /*adjust wikitext div width*/ #sidebar { display: none; } the reason you need to change the tmpl file is that such a page specific css file gets loaded after the skin's csss file, so the rules set by the skin will get overridden by your pub/css/Group.Page.css file Best regards, Hans From design at softflow.co.uk Mon Sep 14 15:00:02 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 14 Sep 2015 21:00:02 +0100 Subject: [pmwiki-users] formatting title markup directive In-Reply-To: <3444406e2723f08c732f8235251286df.squirrel@mail.affinity.co.nz> References: <173953165.20150914132152@softflow.co.uk> <3444406e2723f08c732f8235251286df.squirrel@mail.affinity.co.nz> Message-ID: <29382823.20150914210002@softflow.co.uk> > You could try the following in local/config.php: > $tmpwhen = IsEnabled($EnablePageTitlePriority, 0) ? 'inline'; > $tmpkeep = IsEnabled($EnablePageTitlePriority, 0) ? '1' : 'NULL'; > Markup_e('title', $tmpwhen, > '/\\(:title\\s(.*?):\\)/i', > "PZZ(PCache(\$pagename, > \$zz=array('title' => SetProperty(\$pagename, 'title', PSS(\$m[1]), > NULL, $tmpkeep))))"); > unset($tmpwhen, $tmpkeep); > This should evaluate the title directive after the inline markup rules. thanks! It did not work, but changing the markup timing from '>include' to '>{-'which is the last of the inline rules I think worked. The new problem was that now the HTML Titel got HTML markup visible, so I had to scrub it out via a preg_replace call, with: $HTMLTitle = preg_replace('/<.*?>/','',PageVar($pagename, '$Title')).' - '.$WikiTitle; (I got the page name included as part of the HTML title, together with the Wiki name) Best regards, Hans From byronlunz at gmail.com Mon Sep 14 15:00:47 2015 From: byronlunz at gmail.com (Byron Lunz) Date: Mon, 14 Sep 2015 13:00:47 -0700 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: <505027939.20150914205230@softflow.co.uk> References: <505027939.20150914205230@softflow.co.uk> Message-ID: Thank You Hans! That's close. But I see my description wasn't entirely accurate. It's not just ONE page where I need to disable the SideBar, it's any page named "EditMessages" regardless of Group. So, maybe I can create just a PageName.css file with those changes? I'll go experiment. On Mon, Sep 14, 2015 at 12:52 PM, Hans Bracker wrote: > > > I've been happily using pmwiki & the notsosimple skin for several > > years. But I've run into a problem and I'm not skilled enough with > > CSS or pmwiki to find the solution. Is anyone here able to help? You > > can reply off-list to keep down the noise if you prefer. > > > The issue is that the notsosimple skin has a fixed width of about > > 900px. The SideBar then consumes 160px of that width on every page. > > But I now have a page where I need more width and I'd like the > > SideBar to collapse/disappear on that page and only that page. I > > found a reference to (:noleft:) but it's not working on my installation. > > you would need to edit the notsosimple.tmpl file. > You could try this: > > swap these lines in the tmpl file: > > href='$SkinDirUrl/notsosimple.css' type='text/css' /> > > The tmpl file is also missing markup for (:noleft:) to work, but since > you want to change width for one specific page, you could change some > css rules via a Group.PageName.css file (name of Group and page for > which you want css changes) in the pub/css/ folder. > Create such file and add to it something like this: > > #header, #main { width: 1200px; } /*set your page width*/ > #content { width: 1150px; } /*adjust main div width*/ > #wikitext { width: 1100px } /*adjust wikitext div width*/ > #sidebar { display: none; } > > the reason you need to change the tmpl file is that such a page > specific css file gets loaded after the skin's csss file, so the rules > set by the skin will get overridden by your pub/css/Group.Page.css file > > Best regards, > Hans > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From design at softflow.co.uk Mon Sep 14 15:09:25 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 14 Sep 2015 21:09:25 +0100 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: References: <505027939.20150914205230@softflow.co.uk> Message-ID: <125944790.20150914210925@softflow.co.uk> > It's not just ONE page where I need to disable the SideBar, it's > any page named "EditMessages" regardless of Group. pub/css/Name.css will be used for all pages of wiki group called 'Name', so that would not help you. Instead try add in config.phpsomething like this: $pagename = ResolvePageName($pagename); $name = PageVar($pagename,'$Name'); $group = PageVar($pagename,'$Group'); if ($name=='EditMessages') $HTMLStylesFmt['skinwidth'] = " #header, #main { width: 1200px; } /*set your page width*/ #content { width: 1150px; } /*adjust main div width*/ #wikitext { width: 1100px } /*adjust wikitext div width*/ #sidebar { display: none; } "; so you do not need a css file. $HTMLStylesFmt gets put into the HTML head. You still need the hack to the tmpl file for this to work! cheers, Hans From byronlunz at gmail.com Mon Sep 14 15:11:32 2015 From: byronlunz at gmail.com (Byron Lunz) Date: Mon, 14 Sep 2015 13:11:32 -0700 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: <125944790.20150914210925@softflow.co.uk> References: <505027939.20150914205230@softflow.co.uk> <125944790.20150914210925@softflow.co.uk> Message-ID: Sorry to be so dense, but what do you mean by "hack to the tmpl file"? On Mon, Sep 14, 2015 at 1:09 PM, Hans Bracker wrote: > > > It's not just ONE page where I need to disable the SideBar, it's > > any page named "EditMessages" regardless of Group. > > pub/css/Name.css will be used for all pages of wiki group called > 'Name', so that would not help you. > Instead try add in config.phpsomething like this: > > $pagename = ResolvePageName($pagename); > $name = PageVar($pagename,'$Name'); > $group = PageVar($pagename,'$Group'); > if ($name=='EditMessages') > $HTMLStylesFmt['skinwidth'] = " > #header, #main { width: 1200px; } /*set your page width*/ > #content { width: 1150px; } /*adjust main div width*/ > #wikitext { width: 1100px } /*adjust wikitext div width*/ > #sidebar { display: none; } > "; > > so you do not need a css file. $HTMLStylesFmt gets put into the HTML > head. You still need the hack to the tmpl file for this to work! > > > cheers, > Hans > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 5ko at 5ko.fr Mon Sep 14 15:12:50 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Mon, 14 Sep 2015 22:12:50 +0200 Subject: [pmwiki-users] formatting title markup directive In-Reply-To: <173953165.20150914132152@softflow.co.uk> References: <173953165.20150914132152@softflow.co.uk> Message-ID: On 2015-09-14 14:21, Hans Bracker wrote: > How can I apply inline styling for the (:title ...:) directive? > > In particular I would like to be able to use inline markup > '^text^' (HTML sup) and '_text_' (HTML sub) > > I can use it after ! header markup, but not within the title markup. > Is it possible? Any hacks for it? The (:title ...:) markup sets the content in the ... tags in the HTML page, and usually appears in the browser top border and on the tabs; just note that this content cannot have other HTML tags, and any hack or solution you use should probably remove any added tags from the string. You should estimate if the resulting string in the browser border is acceptable for you. If not, I'd probably use two different markups, one for the <title> text, the other for the <h1> text. Petko -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From design at softflow.co.uk Mon Sep 14 15:17:06 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 14 Sep 2015 21:17:06 +0100 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: <CAM7XBvYjWbYRbWwEH=_imHzdA33uErsyB_zapKfrfbePc57a6A@mail.gmail.com> References: <CAM7XBvbLdpLn_Ng76ByN9_Zr=aTRd8TZWTuCGpcCp2SremUVEg@mail.gmail.com> <505027939.20150914205230@softflow.co.uk> <CAM7XBvYuy_5uCXWun06AbR+==fUjTW5CkwTDZYZya4gLt0UpDA@mail.gmail.com> <125944790.20150914210925@softflow.co.uk> <CAM7XBvYjWbYRbWwEH=_imHzdA33uErsyB_zapKfrfbePc57a6A@mail.gmail.com> Message-ID: <1484789476.20150914211706@softflow.co.uk> > Sorry to be so dense, but what do you mean by "hack to the tmpl file"? what I wrote in the first mail: swapping of two lines in the notsosimple.tmpl file so it should read: ..... <link rel='stylesheet' title="(NotSo) Simple" href='$SkinDirUrl/notsosimple.css' type='text/css' /> <!--HeaderText--> ..... Hans From languefrancaise at gmail.com Mon Sep 14 15:20:31 2015 From: languefrancaise at gmail.com (ABClf) Date: Mon, 14 Sep 2015 22:20:31 +0200 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: <125944790.20150914210925@softflow.co.uk> References: <CAM7XBvbLdpLn_Ng76ByN9_Zr=aTRd8TZWTuCGpcCp2SremUVEg@mail.gmail.com> <505027939.20150914205230@softflow.co.uk> <CAM7XBvYuy_5uCXWun06AbR+==fUjTW5CkwTDZYZya4gLt0UpDA@mail.gmail.com> <125944790.20150914210925@softflow.co.uk> Message-ID: <CACE3LEty4b27q9GgtOaeOY2hrLVCDO=eknapKBzuS_iby9VEGg@mail.gmail.com> Depending what you want to do, it might be relevant to say you can decide to do directives (:noleft:) or (:noright:) or (:nofooter:) etc. for enumerated actions, using this kind of command in config.php : # For listed actions, don't print out sidebar global $action; if ($action=='edit'|| $action == 'search' || $action == 'imgtpl' || $action == 'upload' ) {SetTmplDisplay('PageLeftFmt', 0); # SetTmplDisplay('PageFooterFmt', 0); # SetTmplDisplay('PageTitleFmt', 0); }; (cf. obsolete recipe : http://www.pmwiki.org/wiki/Cookbook/LayoutEditModified) You might have a look as well to Petko's recipe LocalCSS : http://www.pmwiki.org/wiki/Cookbook/LocalCSS Gilles. 2015-09-14 22:09 GMT+02:00 Hans Bracker <design at softflow.co.uk>: > >> It's not just ONE page where I need to disable the SideBar, it's >> any page named "EditMessages" regardless of Group. > > pub/css/Name.css will be used for all pages of wiki group called > 'Name', so that would not help you. > Instead try add in config.phpsomething like this: > > $pagename = ResolvePageName($pagename); > $name = PageVar($pagename,'$Name'); > $group = PageVar($pagename,'$Group'); > if ($name=='EditMessages') > $HTMLStylesFmt['skinwidth'] = " > #header, #main { width: 1200px; } /*set your page width*/ > #content { width: 1150px; } /*adjust main div width*/ > #wikitext { width: 1100px } /*adjust wikitext div width*/ > #sidebar { display: none; } > "; > > so you do not need a css file. $HTMLStylesFmt gets put into the HTML > head. You still need the hack to the tmpl file for this to work! > > > cheers, > Hans > > > _______________________________________________ > pmwiki-users mailing list > pmwiki-users at pmichaud.com > http://www.pmichaud.com/mailman/listinfo/pmwiki-users From byronlunz at gmail.com Mon Sep 14 15:24:22 2015 From: byronlunz at gmail.com (Byron Lunz) Date: Mon, 14 Sep 2015 13:24:22 -0700 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: <1484789476.20150914211706@softflow.co.uk> References: <CAM7XBvbLdpLn_Ng76ByN9_Zr=aTRd8TZWTuCGpcCp2SremUVEg@mail.gmail.com> <505027939.20150914205230@softflow.co.uk> <CAM7XBvYuy_5uCXWun06AbR+==fUjTW5CkwTDZYZya4gLt0UpDA@mail.gmail.com> <125944790.20150914210925@softflow.co.uk> <CAM7XBvYjWbYRbWwEH=_imHzdA33uErsyB_zapKfrfbePc57a6A@mail.gmail.com> <1484789476.20150914211706@softflow.co.uk> Message-ID: <CAM7XBvbLj1yssqdn=5+d30a4AWcsZQYQ_BKBHyS+3huE=XcDXQ@mail.gmail.com> Hans, THANK YOU! This looks like it will do exactly what I need! I appreciate your help very much! Byron On Mon, Sep 14, 2015 at 1:17 PM, Hans Bracker <design at softflow.co.uk> wrote: > > Sorry to be so dense, but what do you mean by "hack to the tmpl file"? > > what I wrote in the first mail: > swapping of two lines in the notsosimple.tmpl file > > so it should read: > ..... > <link rel='stylesheet' title="(NotSo) Simple" > href='$SkinDirUrl/notsosimple.css' type='text/css' /> > <!--HeaderText--> > ..... > > > Hans > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150914/cb94c7e3/attachment.html> From design at softflow.co.uk Mon Sep 14 15:40:01 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 14 Sep 2015 21:40:01 +0100 Subject: [pmwiki-users] Looking for a little help with notsosimple skin please In-Reply-To: <CAM7XBvbLj1yssqdn=5+d30a4AWcsZQYQ_BKBHyS+3huE=XcDXQ@mail.gmail.com> References: <CAM7XBvbLdpLn_Ng76ByN9_Zr=aTRd8TZWTuCGpcCp2SremUVEg@mail.gmail.com> <505027939.20150914205230@softflow.co.uk> <CAM7XBvYuy_5uCXWun06AbR+==fUjTW5CkwTDZYZya4gLt0UpDA@mail.gmail.com> <125944790.20150914210925@softflow.co.uk> <CAM7XBvYjWbYRbWwEH=_imHzdA33uErsyB_zapKfrfbePc57a6A@mail.gmail.com> <1484789476.20150914211706@softflow.co.uk> <CAM7XBvbLj1yssqdn=5+d30a4AWcsZQYQ_BKBHyS+3huE=XcDXQ@mail.gmail.com> Message-ID: <637512463.20150914214001@softflow.co.uk> > Hans, THANK YOU! This looks like it will do exactly what I need! I appreciate your help very much! your most welcome! Just for completenes sake, IF at some point you want to be able to use (:noleft:) in a wiki page to suppress the sidebar, then you need to change the notsosimple.tmpl file like this: add <!--PageLeftFmt--> directly before these lines: <div id="menubar" $SkinMenuBarVisible> <div id="wikicmds" align="right"> <!--wiki:$Group.PageActions $SiteGroup.PageActions--> </div> <div class="clearer"></div> </div> and add <!--/PageLeftFmt--> directly after those cheers From design at softflow.co.uk Mon Sep 14 15:58:19 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 14 Sep 2015 21:58:19 +0100 Subject: [pmwiki-users] formatting title markup directive In-Reply-To: <bf60bf5a4913991e69bfca375f840cb4@5ko.fr> References: <173953165.20150914132152@softflow.co.uk> <bf60bf5a4913991e69bfca375f840cb4@5ko.fr> Message-ID: <10511016.20150914215819@softflow.co.uk> > The (:title ...:) markup sets the content in the <title>... tags > in the HTML page, and usually appears in the browser top border and on > the tabs; just note that this content cannot have other HTML tags, and > any hack or solution you use should probably remove any added tags from > the string. You should estimate if the resulting string in the > browser border is acceptable for you. > If not, I'd probably use two different markups, one for the <title> > text, the other for the <h1> text. thanks for your explanations! Yes I removed the added inline tags when setting $HTMLTitle in config. Otherwise they appear as text in the HTML Title. Two different markups for HTML title and h1 "title" is a bit too complex, as it most likely means changes to the skin template. So a custom title markup which gets evaluated after inline rules, and a $HTMLTitle which has added HTML tags removed is proving to work well, and not messing up other pages. Best regards, Hans From pbowers at pobox.com Tue Sep 15 09:54:15 2015 From: pbowers at pobox.com (Peter Bowers) Date: Tue, 15 Sep 2015 22:54:15 +0800 Subject: [pmwiki-users] Notes from the useradmin talk page. In-Reply-To: <9AA788D2-7DFC-45C3-B5DA-B85DD25EA830@gmail.com> References: <9AA788D2-7DFC-45C3-B5DA-B85DD25EA830@gmail.com> Message-ID: <CAMS2R8EbMDh00mO6zbfHEqO9z37BWFH5ZQe5M7wAHPmVYBOdhg@mail.gmail.com> Apologies for the delay - I've been traveling. On Fri, Sep 11, 2015 at 12:29 AM, erik burggraaf <burggraaferik at gmail.com> wrote: > First, where are the instructions for adding groups in useradmin Dbase? I > did not see them in the configuration section of the recipe page, but I see > from the talk page that some one got it up and working. > You must be logged in with admin privileges (able to read a page with "admin" rights) and then access the URL with either ?action=user/menu and choose "edit user group" or go directly to ?action=user/group. It should be obvious from there, with the caveat that groups must begin with @ -- I just accidentally tested without the @ and it gives a misleading error message that I'll need to fix later. (Now looking more carefully I see that was reported in mid-August by Gerolkae on the talk page.) Second, another user from the talk page wanted to discuss extending member > profiles and adding pieces of information, presumably name, contact info, > and so on. I have instructions for how to do this and I will play with it > a bit. > I have done no testing with allowing custom fields in useradmin-dbase. Without doubt you will have to update the database manually (phpmyadmin or the like) and be careful to follow naming conventions. I'd be surprised if it worked, but stranger things have happened... :-) Let me know what problems you run into and I'll try to fix them as I'm able. > Final thing from the talk page. We want to do an operation where we > collect info from users, save that info, then direct users to a payment > solution. For example, registering for a conference held by the > organisation. We want users to fill out their registration online, then be > taken directly through the process of paying the sign up fee. > Does it suffice to have a configurable target redirect page after registration? Or does there need to be a greater degree of control? Are you thinking of having useradmin handle the payment side of things (unlikely that will be implemented) or does useradmin just need to provide the signup details in a URL (much more do-able - perhaps already available through a custom form)? -Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150915/0a9728bd/attachment-0001.html> From dzosborn at gmail.com Tue Sep 15 21:10:16 2015 From: dzosborn at gmail.com (Donald Z. Osborn) Date: Tue, 15 Sep 2015 22:10:16 -0400 Subject: [pmwiki-users] Fatal error in upgrading from 2.2.45 Message-ID: <CALSbqwXQ390B9XA5S8sSLL=3Bw4R+1=CiaX7f1+64cm4FdOhsw@mail.gmail.com> In the process of manually updating a 2.2.45 installation with the latest. Have encountered two issues: 1) when adding to config the code suggested for 2.2.35 and after on http://www.pmwiki.org/wiki/PmWiki/Upgrades#v220 , which was missing from my config file, I got an error message about the xlpage-utf-8.php page in scripts 2) I updated the scripts pages including that same xlpage-utf-8.php file, and got this error message: *Fatal error*: Call to undefined function PCCF() in */misc/32/000/115/128/8/user/web/donosborn.org/pmwiki/scripts/xlpage-utf-8.php <http://donosborn.org/pmwiki/scripts/xlpage-utf-8.php>* on line *50* ... it is easy enough to backtrack on #1 (though perhaps not deal), but for #2, other than reverting to the old xlpage-utf-8.php, where would the PCCF() function be found in the rest of the installation? Still working my way through. TIA for any ideas or info, Don Osborn -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150915/964b71aa/attachment.html> From 5ko at 5ko.fr Wed Sep 16 02:28:50 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Wed, 16 Sep 2015 09:28:50 +0200 Subject: [pmwiki-users] Fatal error in upgrading from 2.2.45 In-Reply-To: <CALSbqwXQ390B9XA5S8sSLL=3Bw4R+1=CiaX7f1+64cm4FdOhsw@mail.gmail.com> References: <CALSbqwXQ390B9XA5S8sSLL=3Bw4R+1=CiaX7f1+64cm4FdOhsw@mail.gmail.com> Message-ID: <0dde5df7395afd6dfe5f71bb42c0297e@5ko.fr> On 2015-09-16 04:10, Donald Z. Osborn wrote: > In the process of manually updating a 2.2.45 installation with the > latest. > > Have encountered two issues: > > 1) when adding to config the code suggested for 2.2.35 and after on > http://www.pmwiki.org/wiki/PmWiki/Upgrades#v220 , which was missing > from my > config file, I got an error message about the xlpage-utf-8.php page in > scripts > > 2) I updated the scripts pages including that same xlpage-utf-8.php > file, > and got this error message: > > *Fatal error*: Call to undefined function PCCF() in > */misc/32/000/115/128/8/user/web/donosborn.org/pmwiki/scripts/xlpage-utf-8.php > <http://donosborn.org/pmwiki/scripts/xlpage-utf-8.php>* on line *50* > > ... it is easy enough to backtrack on #1 (though perhaps not deal), but > for > #2, other than reverting to the old xlpage-utf-8.php, where would the > PCCF() function be found in the rest of the installation? > That function is declared in pmwiki.php, make sure you have updated this file to the latest version. -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From dzosborn at gmail.com Wed Sep 16 08:40:57 2015 From: dzosborn at gmail.com (Donald Z. Osborn) Date: Wed, 16 Sep 2015 09:40:57 -0400 Subject: [pmwiki-users] Fatal error in upgrading from 2.2.45 In-Reply-To: <0dde5df7395afd6dfe5f71bb42c0297e@5ko.fr> References: <CALSbqwXQ390B9XA5S8sSLL=3Bw4R+1=CiaX7f1+64cm4FdOhsw@mail.gmail.com> <0dde5df7395afd6dfe5f71bb42c0297e@5ko.fr> Message-ID: <CALSbqwX8fFDebX_8YFcVx1eEndtUBX+VvSQLkUVErgTmpkuHng@mail.gmail.com> Thank you Petko. I had gone about this backwards it seems. All working now. One question - the new version does not include rss.php in the scripts folder, but when I took it out of my installation, the wikipages had error messages at top indicating this file was not found. I simply re-added it, which seems to have solved that issue, but wondered if there is another way I should have addressed this or any longer term issues with rss.php. Next task is more complex - I have an old installation - 2.0 - on another site and need to either update it or simply remove it (the wiki contents are obsolete) and install new. The object will be to receive contents of another wiki of about the same generation that went offline when the host site went offline (complicated story, but it boils down to funding ending for the project that sponsored it). I'm tempted just to start fresh with a new installation and hope the wiki-d files work. Or would it make more sense to import wiki.d, config, and skin, and then do an update from 2.0? Any advice or experience of others would be appreciated. Don On Wed, Sep 16, 2015 at 3:28 AM, Petko Yotov <5ko at 5ko.fr> wrote: > On 2015-09-16 04:10, Donald Z. Osborn wrote: > >> In the process of manually updating a 2.2.45 installation with the latest. >> >> Have encountered two issues: >> >> 1) when adding to config the code suggested for 2.2.35 and after on >> http://www.pmwiki.org/wiki/PmWiki/Upgrades#v220 , which was missing from >> my >> config file, I got an error message about the xlpage-utf-8.php page in >> scripts >> >> 2) I updated the scripts pages including that same xlpage-utf-8.php file, >> and got this error message: >> >> *Fatal error*: Call to undefined function PCCF() in >> */misc/32/000/115/128/8/user/web/ >> donosborn.org/pmwiki/scripts/xlpage-utf-8.php >> <http://donosborn.org/pmwiki/scripts/xlpage-utf-8.php>* on line *50* >> >> ... it is easy enough to backtrack on #1 (though perhaps not deal), but >> for >> #2, other than reverting to the old xlpage-utf-8.php, where would the >> PCCF() function be found in the rest of the installation? >> >> > That function is declared in pmwiki.php, make sure you have updated this > file to the latest version. > > -- > Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog > Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes > If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades > > > > _______________________________________________ > pmwiki-users mailing list > pmwiki-users at pmichaud.com > http://www.pmichaud.com/mailman/listinfo/pmwiki-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150916/7462e17c/attachment.html> From 5ko at 5ko.fr Wed Sep 16 11:39:02 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Wed, 16 Sep 2015 18:39:02 +0200 Subject: [pmwiki-users] Fatal error in upgrading from 2.2.45 In-Reply-To: <CALSbqwX8fFDebX_8YFcVx1eEndtUBX+VvSQLkUVErgTmpkuHng@mail.gmail.com> References: <CALSbqwXQ390B9XA5S8sSLL=3Bw4R+1=CiaX7f1+64cm4FdOhsw@mail.gmail.com> <0dde5df7395afd6dfe5f71bb42c0297e@5ko.fr> <CALSbqwX8fFDebX_8YFcVx1eEndtUBX+VvSQLkUVErgTmpkuHng@mail.gmail.com> Message-ID: <78f7b1b25f767c7725788fee78c512b1@5ko.fr> On 2015-09-16 15:40, Donald Z. Osborn wrote: > Thank you Petko. I had gone about this backwards it seems. All working > now. > > One question - the new version does not include rss.php in the scripts > folder, but when I took it out of my installation, the wikipages had > error > messages at top indicating this file was not found. I simply re-added > it, > which seems to have solved that issue, but wondered if there is another > way > I should have addressed this or any longer term issues with rss.php. The new core file with RSS functions is scripts/feeds.php. See this page: http://www.pmwiki.org/wiki/PmWiki/WebFeeds My advice is to disable rss.php which is no longer supported and use feeds.php. > Next task is more complex - I have an old installation - 2.0 - on > another > site and need to either update it or simply remove it (the wiki > contents > are obsolete) and install new. The object will be to receive contents > of > another wiki of about the same generation that went offline when the > host > site went offline (complicated story, but it boils down to funding > ending > for the project that sponsored it). > > I'm tempted just to start fresh with a new installation and hope the > wiki-d > files work. Yes, this would be my way to do it. > Or would it make more sense to import wiki.d, config, and skin, > and then do an update from 2.0? Any advice or experience of others > would be appreciated. Have backups in case something breaks. I'd fresh install the latest version of PmWiki and the wiki.d pages. On the first run, PmWiki will likely prompt you to accept some updates (moving pages) -- accept them. See what works, what doesn't -- read Upgrades and ReleaseNotes. Get the latest versions of all recipes/skins you used and enable them one after another to see if there are warnings or errors. Your original skin might still work, or you may have to add some markers in it like <!--HTMLHeader-->; if you cannot make the old skin work, maybe try another skin. If you have any difficulty, tell us and we'll help you. Petko -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From jimbo.molo at gmail.com Wed Sep 16 11:51:44 2015 From: jimbo.molo at gmail.com (Jimbo Molo) Date: Wed, 16 Sep 2015 09:51:44 -0700 Subject: [pmwiki-users] AD Auth Failing in IIS8 Message-ID: <CAMRpjudi-Hz7sndSoiLji0CxfDW=wEutCzh0mHNhUmwR68RXFQ@mail.gmail.com> This is my 2nd time posting this message as I haven't received a response: I'm unable to get AD auth working via IIS8. I've read the instructions on the following pages to configure the lines below in local/config.php but continue to receive the error "Name/password not recognized": http://sfwiki01/pmwiki.php?n=PmWiki.AuthUser http://www.pmwiki.org/wiki/Cookbook/AuthUserViaMicrosoftLDAP $AuthLDAPBindDN = "mydc.com\\username"; $AuthLDAPBindPassword = "password"; $DefaultPasswords['read'] = 'password'; #$HandleAuth['diff'] = 'edit'; #$DefaultPasswords['edit'] = 'id:*'; #$Author = $AuthId; $AuthUser['ldap'] = 'ldap://ldap.mydc.com/'; include_once("$FarmD <http://www.pmwiki.org/wiki/PmWiki/PathVariables#FarmD> /scripts/authuser.php"); I've also added "ldap_set_option($ds, LDAP_OPT_REFERRALS, 0);" after "ldap_set_option($ds, LDAP_OPT_PROTOCOL_VERSION, 3);" in scripts/authuser.php ( http://www.pmwiki.org/wiki/Cookbook/AuthUserViaMicrosoftLDAP-Talk ) to no avail. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150916/94594e8e/attachment.html> From dzosborn at gmail.com Fri Sep 18 07:55:35 2015 From: dzosborn at gmail.com (Donald Z. Osborn) Date: Fri, 18 Sep 2015 08:55:35 -0400 Subject: [pmwiki-users] Fatal error in upgrading from 2.2.45 In-Reply-To: <78f7b1b25f767c7725788fee78c512b1@5ko.fr> References: <CALSbqwXQ390B9XA5S8sSLL=3Bw4R+1=CiaX7f1+64cm4FdOhsw@mail.gmail.com> <0dde5df7395afd6dfe5f71bb42c0297e@5ko.fr> <CALSbqwX8fFDebX_8YFcVx1eEndtUBX+VvSQLkUVErgTmpkuHng@mail.gmail.com> <78f7b1b25f767c7725788fee78c512b1@5ko.fr> Message-ID: <CALSbqwWXjzW0ozq6VsVERxzkKSbtP45azEfSFw0L6mCcjJ4wAw@mail.gmail.com> Thank you Petko, This has worked out well, though I did manually install so not sure what moving pages have or have not been updated. Will return to the rss / feed issue later, as it involves a number of pages. I changed the skin for all but one wikigroup to Triad, but there are two issues: 1) I have a "backlinks" link at the top of the sidebar, which used to act on the page viewed, not the sidebar, but in this skin it acts on the sidebar (giving me backlinks to the sidebar, not the page being viewed). I'm guessing this is because of how Triad handles sidebars. In any event, is there an easy way to modify this code to point to the page viewed rather than the sidebar in which the code is placed? [[{$Name}?action=search&q=link={$FullName}+list=all | $[Backlinks]]] That's on the sidebar at http://www.bisharat.net/wikidoc/pmwiki.php/PanAfrLoc/ 2) In the one wikigroup where I did not change the skin, the "edit" and other tabs point not to the page viewed but always to Site/PageActions. I think this is a problem with older skins using the latest PmWiki upgrade - I also noted it in the old skin for the rest of the wiki before switching to Triad. Am hoping there is a relatively easy fix to the skin to correct this. See tabs at http://www.bisharat.net/wikidoc/pmwiki.php/Marrakech/HomePage By way of background, this is an effort to resurrect a wiki that was part of two successive projects (2005-11), but which went offline when the second project's funding ended and site closed. All the best, Don Osborn On Wed, Sep 16, 2015 at 12:39 PM, Petko Yotov <5ko at 5ko.fr> wrote: > > > On 2015-09-16 15:40, Donald Z. Osborn wrote: > >> Thank you Petko. I had gone about this backwards it seems. All working >> now. >> >> One question - the new version does not include rss.php in the scripts >> folder, but when I took it out of my installation, the wikipages had error >> messages at top indicating this file was not found. I simply re-added it, >> which seems to have solved that issue, but wondered if there is another >> way >> I should have addressed this or any longer term issues with rss.php. >> > > The new core file with RSS functions is scripts/feeds.php. See this page: > > http://www.pmwiki.org/wiki/PmWiki/WebFeeds > > My advice is to disable rss.php which is no longer supported and use > feeds.php. > > Next task is more complex - I have an old installation - 2.0 - on another >> site and need to either update it or simply remove it (the wiki contents >> are obsolete) and install new. The object will be to receive contents of >> another wiki of about the same generation that went offline when the host >> site went offline (complicated story, but it boils down to funding ending >> for the project that sponsored it). >> >> I'm tempted just to start fresh with a new installation and hope the >> wiki-d >> files work. >> > > Yes, this would be my way to do it. > > Or would it make more sense to import wiki.d, config, and skin, >> and then do an update from 2.0? Any advice or experience of others >> would be appreciated. >> > > Have backups in case something breaks. > > I'd fresh install the latest version of PmWiki and the wiki.d pages. > > On the first run, PmWiki will likely prompt you to accept some updates > (moving pages) -- accept them. See what works, what doesn't -- read > Upgrades and ReleaseNotes. Get the latest versions of all recipes/skins you > used and enable them one after another to see if there are warnings or > errors. Your original skin might still work, or you may have to add some > markers in it like <!--HTMLHeader-->; if you cannot make the old skin work, > maybe try another skin. > > If you have any difficulty, tell us and we'll help you. > > Petko > > > -- > Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog > Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes > If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150918/69432459/attachment.html> From 5ko at 5ko.fr Fri Sep 18 10:19:16 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Fri, 18 Sep 2015 17:19:16 +0200 Subject: [pmwiki-users] Fatal error in upgrading from 2.2.45 In-Reply-To: <CALSbqwWXjzW0ozq6VsVERxzkKSbtP45azEfSFw0L6mCcjJ4wAw@mail.gmail.com> References: <CALSbqwXQ390B9XA5S8sSLL=3Bw4R+1=CiaX7f1+64cm4FdOhsw@mail.gmail.com> <0dde5df7395afd6dfe5f71bb42c0297e@5ko.fr> <CALSbqwX8fFDebX_8YFcVx1eEndtUBX+VvSQLkUVErgTmpkuHng@mail.gmail.com> <78f7b1b25f767c7725788fee78c512b1@5ko.fr> <CALSbqwWXjzW0ozq6VsVERxzkKSbtP45azEfSFw0L6mCcjJ4wAw@mail.gmail.com> Message-ID: <3fbb7c049cb10e244d8370b4d9229b9d@5ko.fr> Both issues you mention, Backlinks and PageActions, are related to the old use of {$Variable} instead of currently {*$Variable}, see the page "Upgrades": http://www.pmwiki.org/wiki/PmWiki/Upgrades (section starting with "Version 2.2.10") The page "Upgrades" contains the most important changes that may require some admins to do something on their wiki when upgrading. You should read that page when you upgrade (or when you import pages or whole groups from old wikis). There may be other changes that concern you on that page. These and other important changes, most of which should not require an action from you on upgrade, are in the Release notes, it is also a good idea to read the release notes between your previous version and the one you're installing: http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes Petko On 2015-09-18 14:55, Donald Z. Osborn wrote: > Thank you Petko, This has worked out well, though I did manually > install so > not sure what moving pages have or have not been updated. Will return > to > the rss / feed issue later, as it involves a number of pages. > > I changed the skin for all but one wikigroup to Triad, but there are > two > issues: > > 1) I have a "backlinks" link at the top of the sidebar, which used to > act > on the page viewed, not the sidebar, but in this skin it acts on the > sidebar (giving me backlinks to the sidebar, not the page being > viewed). > I'm guessing this is because of how Triad handles sidebars. In any > event, > is there an easy way to modify this code to point to the page viewed > rather > than the sidebar in which the code is placed? > > [[{$Name}?action=search&q=link={$FullName}+list=all | $[Backlinks]]] > > That's on the sidebar at > http://www.bisharat.net/wikidoc/pmwiki.php/PanAfrLoc/ > > 2) In the one wikigroup where I did not change the skin, the "edit" and > other tabs point not to the page viewed but always to Site/PageActions. > I > think this is a problem with older skins using the latest PmWiki > upgrade - > I also noted it in the old skin for the rest of the wiki before > switching > to Triad. Am hoping there is a relatively easy fix to the skin to > correct > this. > > See tabs at > http://www.bisharat.net/wikidoc/pmwiki.php/Marrakech/HomePage > > By way of background, this is an effort to resurrect a wiki that was > part > of two successive projects (2005-11), but which went offline when the > second project's funding ended and site closed. > > All the best, > > Don Osborn > > On Wed, Sep 16, 2015 at 12:39 PM, Petko Yotov <5ko at 5ko.fr> wrote: > >> >> >> On 2015-09-16 15:40, Donald Z. Osborn wrote: >> >>> Thank you Petko. I had gone about this backwards it seems. All >>> working >>> now. >>> >>> One question - the new version does not include rss.php in the >>> scripts >>> folder, but when I took it out of my installation, the wikipages had >>> error >>> messages at top indicating this file was not found. I simply re-added >>> it, >>> which seems to have solved that issue, but wondered if there is >>> another >>> way >>> I should have addressed this or any longer term issues with rss.php. >>> >> >> The new core file with RSS functions is scripts/feeds.php. See this >> page: >> >> http://www.pmwiki.org/wiki/PmWiki/WebFeeds >> >> My advice is to disable rss.php which is no longer supported and use >> feeds.php. >> >> Next task is more complex - I have an old installation - 2.0 - on >> another >>> site and need to either update it or simply remove it (the wiki >>> contents >>> are obsolete) and install new. The object will be to receive contents >>> of >>> another wiki of about the same generation that went offline when the >>> host >>> site went offline (complicated story, but it boils down to funding >>> ending >>> for the project that sponsored it). >>> >>> I'm tempted just to start fresh with a new installation and hope the >>> wiki-d >>> files work. >>> >> >> Yes, this would be my way to do it. >> >> Or would it make more sense to import wiki.d, config, and skin, >>> and then do an update from 2.0? Any advice or experience of others >>> would be appreciated. >>> >> >> Have backups in case something breaks. >> >> I'd fresh install the latest version of PmWiki and the wiki.d pages. >> >> On the first run, PmWiki will likely prompt you to accept some updates >> (moving pages) -- accept them. See what works, what doesn't -- read >> Upgrades and ReleaseNotes. Get the latest versions of all >> recipes/skins you >> used and enable them one after another to see if there are warnings or >> errors. Your original skin might still work, or you may have to add >> some >> markers in it like <!--HTMLHeader-->; if you cannot make the old skin >> work, >> maybe try another skin. >> >> If you have any difficulty, tell us and we'll help you. >> >> Petko -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From bobmueller at ravensbeak.com Fri Sep 18 23:57:43 2015 From: bobmueller at ravensbeak.com (Bob Mueller) Date: Fri, 18 Sep 2015 23:57:43 -0500 Subject: [pmwiki-users] PmWiki for a Writer? (Long) Message-ID: <55FCEB47.2070205@ravensbeak.com> Greetings all. I've got some feasibility and strategic questions about using PmWiki. I'm looking to use a wiki for a series bible. That's where you keep all of your information about characters and settings and locations across a series. I've been using Word docs and Excel spreadsheets, but that's a kludgy approach, and won't scale well, I think. Wikis are perfect for the idea, and I think PmWiki will be just what I want. I'll be the only user and admin for the foreseeable future. I have my own domain and a good web host. I have two book series that I want to use this for. Series1 has 2 books done, and a 3d in progress. Series2 has 6-7 books planned. I want the sections for the unwritten or in-progress books to stay private until the books are published. Then I'll open them up for public viewing (but almost certainly not editing) as each book is published. So am I talking about multiple groups here? I think I am, based on the documentation I've read. If I set up a Series1 group, can I also set up Book1, Book2, and Book3 subgroups? And for MainCharacter, I don't have to replicate his page across all three subgroups, right? But is this (all these subgroups) really the best way to handle it? Os is there something a little bit more elegant? Lastly (for now), if I want to make my character pages look almost exactly like https://en.wikipedia.org/w/index.php?title=Jack_Ryan_(character) for example, how difficult is it to set up what Wikipedia calls an infobox on the right side like that? I wasn't sure that Wikipedia and PmWiki use the same term for that construct, and I don't think I was finding what I needed in the docs or the Cookbook. Thanks much for any help here. -- Bob Mueller The Sad Girl - now available at Amazon Don't Stop Believin' - Fall 2015 http://bit.ly/IndefixaBooks From languefrancaise at gmail.com Sat Sep 19 08:28:07 2015 From: languefrancaise at gmail.com (ABClf) Date: Sat, 19 Sep 2015 15:28:07 +0200 Subject: [pmwiki-users] PmWiki for a Writer? (Long) In-Reply-To: <55FCEB47.2070205@ravensbeak.com> References: <55FCEB47.2070205@ravensbeak.com> Message-ID: <CACE3LEvcaAY09c=c7LXum7wHj-9yeuOeqEE21FZMHd04BGoDxQ@mail.gmail.com> It is important you decide first about what structure you will adopt for storing your data. PmWiki uses Group/Name structure ; you can easily extand with suffix Group/Name-Discussion (easy for targeting pages according to their names/functions). Other tools to know : PmWiki has very nice native pagelisting ability, making it able to collect data in your wiki, with many parameters and formatting options (tables, list, includes, up to you). PmWiki has also great support for PTV and includes. Have a look at other bible/database projects made using pmwiki to see how they are done if you like them (try ?action=source to see if source is accessible); it's going to take a day or more to browse the links (success story page will be of help, although not updated enough). These examples may be worth visiting, at least for watching their structure : http://www.trainsofturkey.com/w/pmwiki.php/Site/About http://classic-sf.com/ http://www.swcity.net/pmwiki/pmwiki.php http://becko.tabletop-minis.de/ Having multiple groups for multiple series makes sense (to my mind, what is important is to make things easy to target searches and pagelist and rss, and be short enough to write links fast) ; and use other category-like groups for collecting transversal data (Year, Location, Character, etc.), using GroupFooter and GroupHeader to automate the page listings. There is no one solution only. You have to brainstorm. A floating box, with structured data, should be easy to do. I guess its mainly a css work for the layout. You might use PTV there, thus you will be able to show panoramic pages with data collected among a set of pages, or set up a targeted search engine. My advice : check what others have done. Read doc about group, category, page variable, ptv, and pagelist. When its done, install and play with pmwiki. Create two groups, write a set of pages, with links, anchors, and ptv ; set up pagelists in transversal pages. It is a handy and nice tool, very powerfull and flexible, easy to upgrade, easy to backup. You have data ready so you can start playing soon, but you will have to do some rewriting work for using your data with PmWiki (write links, headers, anchors, ptv data, all things you will be able to use as selectors in pagelists). No matter what tool you will use for your project, you will have to learn how to use it first, and how to format your data for enjoying the tool you use at his best ;) Gilles. 2015-09-19 6:57 GMT+02:00 Bob Mueller <bobmueller at ravensbeak.com>: > Greetings all. I've got some feasibility and strategic questions about using > PmWiki. > > I'm looking to use a wiki for a series bible. That's where you keep all of > your information about characters and settings and locations across a > series. I've been using Word docs and Excel spreadsheets, but that's a > kludgy approach, and won't scale well, I think. Wikis are perfect for the > idea, and I think PmWiki will be just what I want. > > I'll be the only user and admin for the foreseeable future. I have my own > domain and a good web host. > > I have two book series that I want to use this for. Series1 has 2 books > done, and a 3d in progress. Series2 has 6-7 books planned. > > I want the sections for the unwritten or in-progress books to stay private > until the books are published. Then I'll open them up for public viewing > (but almost certainly not editing) as each book is published. > > So am I talking about multiple groups here? I think I am, based on the > documentation I've read. > > If I set up a Series1 group, can I also set up Book1, Book2, and Book3 > subgroups? And for MainCharacter, I don't have to replicate his page across > all three subgroups, right? > > But is this (all these subgroups) really the best way to handle it? Os is > there something a little bit more elegant? > > Lastly (for now), if I want to make my character pages look almost exactly > like https://en.wikipedia.org/w/index.php?title=Jack_Ryan_(character) for > example, how difficult is it to set up what Wikipedia calls an infobox on > the right side like that? I wasn't sure that Wikipedia and PmWiki use the > same term for that construct, and I don't think I was finding what I needed > in the docs or the Cookbook. > > Thanks much for any help here. > > -- > Bob Mueller > The Sad Girl - now available at Amazon > Don't Stop Believin' - Fall 2015 > http://bit.ly/IndefixaBooks > > _______________________________________________ > pmwiki-users mailing list > pmwiki-users at pmichaud.com > http://www.pmichaud.com/mailman/listinfo/pmwiki-users From 5ko at 5ko.fr Sat Sep 19 15:02:38 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Sat, 19 Sep 2015 22:02:38 +0200 Subject: [pmwiki-users] PmWiki for a Writer? (Long) In-Reply-To: <55FCEB47.2070205@ravensbeak.com> References: <55FCEB47.2070205@ravensbeak.com> Message-ID: <295f31d452dfa05b434b6f87b0b6cba7@5ko.fr> In addition to what Gilles wrote, you can look into WikiTrails, a feature allowing a table-of-contents-like pages and previous-next navigation links which can be automatically displayed in your page from a GroupHeader or GroupFooter. http://www.pmwiki.org/wiki/PmWiki/WikiTrails http://www.pmwiki.org/wiki/PmWiki/GroupHeaders You should definitely look into the Backlinks feature of PageLists, it can create automatic cross-page navigation. For example, in your chapter you mention characters and link to their pages like [[Characters/John]]. Then in the page Characters/John, after the description of the character, there is an automatic list to all chapters in all books linking to that page. (Only links to pages where the visitor has permissions to view will be listed, so a visitor will not see links to locked groups, but you as a logged in author will see them.) The core software does not support subgroups, but you can have individual groups for every book, and order those in sections of your navigation. (There are two modules about subgroups but their developers have left the community and the modules are not extensively tested or maintained). WikiGroups allow easier linking to pages in the same group, custom styling/appearance or locking of related group of pages, and repeated headers/footers for all pages in the group. About the "infobox" template feature, you can include other pages or sections formatted as templates containing {$$variables}, and these variables are defined from the page where the template is included: http://www.pmwiki.org/wiki/PmWiki/IncludeOtherPages#includevariable PmWiki allows private and public groups. You can lock a full group (book) and unlock it after if is published: http://www.pmwiki.org/wiki/PmWiki/Passwords I would keep the passwords simple: for a wiki with a single or a few trusted writers, probably the default "shared password" feature will be enough (and AuthUser will be too much). PmWiki has many features and modules, and the documentation can appear overwhelming. But you can start really simple, focus on your content, and think about infoboxes and backlinks later. But the WikiTrails feature will be very useful so read about it early. My advice is to keep the content simple, with few markups and features, even when you become an experienced editor. Also, if you need some feature, you can search the core documentation and Cookbook for a recipe/module, and look at the Talk and Users pages: a module used by more people and with more discussions tend to be good because more extensively tested. Or, you can ask the mailing list. Petko On 2015-09-19 06:57, Bob Mueller wrote: > Greetings all. I've got some feasibility and strategic questions about > using PmWiki. > > I'm looking to use a wiki for a series bible. That's where you keep > all of your information about characters and settings and locations > across a series. I've been using Word docs and Excel spreadsheets, but > that's a kludgy approach, and won't scale well, I think. Wikis are > perfect for the idea, and I think PmWiki will be just what I want. > > I'll be the only user and admin for the foreseeable future. I have my > own domain and a good web host. > > I have two book series that I want to use this for. Series1 has 2 > books done, and a 3d in progress. Series2 has 6-7 books planned. > > I want the sections for the unwritten or in-progress books to stay > private until the books are published. Then I'll open them up for > public viewing (but almost certainly not editing) as each book is > published. > > So am I talking about multiple groups here? I think I am, based on the > documentation I've read. > > If I set up a Series1 group, can I also set up Book1, Book2, and Book3 > subgroups? And for MainCharacter, I don't have to replicate his page > across all three subgroups, right? > > But is this (all these subgroups) really the best way to handle it? Os > is there something a little bit more elegant? > > Lastly (for now), if I want to make my character pages look almost > exactly like > https://en.wikipedia.org/w/index.php?title=Jack_Ryan_(character) for > example, how difficult is it to set up what Wikipedia calls an infobox > on the right side like that? I wasn't sure that Wikipedia and PmWiki > use the same term for that construct, and I don't think I was finding > what I needed in the docs or the Cookbook. > > Thanks much for any help here. -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From kirpi at kirpi.it Mon Sep 21 16:35:28 2015 From: kirpi at kirpi.it (kirpi at kirpi.it) Date: Mon, 21 Sep 2015 23:35:28 +0200 Subject: [pmwiki-users] Multiple checkboxes Message-ID: <CAMrCtLfpwdfUE1vzC1zacDf5+YubUQEjdkgvUx3A++q=1Nvq9g@mail.gmail.com> Setting a form with multiple checkboxes and storing a comma separated list of hobbies (just an example) in a ptv proved to be a little tricky, but many months ago I found that this approach works just fine: ''Hobby:'''\\ (:input hidden name=$:Hobby "":) (:input checkbox $:Hobby[] Travels (:if matchstring '/Travels/' "{{$FullName}$:Hobby}":)checked(:ifend:):) Travels\\ (:input checkbox $:Hobby[] Photography (:if matchstring '/Photography/' "{{$FullName}$:Hobby}":)checked(:ifend:):) Photography\\ (:input checkbox $:Hobby[] Music (:if matchstring '/Music/' "{{$FullName}$:Hobby}":)checked(:ifend:):) Music Actually, it did work until recently :-( Now, for some reason, it does not work any longer: if I edit the form (I use Fox) a second time, all the data are reset. Is it perhaps due to some changes in the latest version of Pmwiki? Thanks! Luigi From 5ko at 5ko.fr Mon Sep 21 18:12:23 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Tue, 22 Sep 2015 01:12:23 +0200 Subject: [pmwiki-users] Multiple checkboxes In-Reply-To: <CAMrCtLfpwdfUE1vzC1zacDf5+YubUQEjdkgvUx3A++q=1Nvq9g@mail.gmail.com> References: <CAMrCtLfpwdfUE1vzC1zacDf5+YubUQEjdkgvUx3A++q=1Nvq9g@mail.gmail.com> Message-ID: <fcd866b9fbb9293873ec006aacf78b9a@5ko.fr> There has been a change in May allowing setting and posting multiple checkboxes in some cases. See how to use it here: http://www.pmwiki.org/wiki/PITS/01032 I believe Fox was also updated to handle those. The current way to do this would be to set multiple default values, separated by spaces, like: your PageTextVariable (PTV): (:Hobby:Travels Music:) in the form: (:input default $:Hobby[] {$:Hobby}:) (:input checkbox $:Hobby[] Travels:) Travels (:input checkbox $:Hobby[] Photography:) Photography (:input checkbox $:Hobby[] Music:) Music No need to have (:if matchstring...:). Note that a PTV cannot set multiple-checkboxes directly with (:input default source={$FullName}:), as there is no PTV "$:Hobby[]" with brackets, the PTV is "$:Hobby". That's why I set a default value as an intermediate step: (:input default $:Hobby[] {$:Hobby}:) At the time I asked people to test and report any problems, and for ideas how to handle things, this is still possible. Petko On 2015-09-21 23:35, kirpi at kirpi.it wrote: > Setting a form with multiple checkboxes and storing a comma separated > list of hobbies (just an example) in a ptv proved to be a little > tricky, but many months ago I found that this approach works just > fine: > > ''Hobby:'''\\ > (:input hidden name=$:Hobby "":) > (:input checkbox $:Hobby[] Travels (:if matchstring '/Travels/' > "{{$FullName}$:Hobby}":)checked(:ifend:):) Travels\\ > (:input checkbox $:Hobby[] Photography (:if matchstring > '/Photography/' "{{$FullName}$:Hobby}":)checked(:ifend:):) > Photography\\ > (:input checkbox $:Hobby[] Music (:if matchstring '/Music/' > "{{$FullName}$:Hobby}":)checked(:ifend:):) Music > > Actually, it did work until recently :-( > > Now, for some reason, it does not work any longer: if I edit the form > (I use Fox) a second time, all the data are reset. > Is it perhaps due to some changes in the latest version of Pmwiki? -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From lernaway at gmail.com Tue Sep 22 10:21:38 2015 From: lernaway at gmail.com (Derek Lerner) Date: Tue, 22 Sep 2015 11:21:38 -0400 Subject: [pmwiki-users] EnableHTML for php5.6 Message-ID: <CANR9UnMQCUYGU1GwC7X2SDDi2jNu8QwBkkuqj8kCD6V+D-vqnQ@mail.gmail.com> Hello all, Is there a version of enablehtml.php that will work with php5.6? http://www.pmwiki.org/wiki/Cookbook/EnableHTML I attempted the below but got... Fatal error: Cannot redeclare MyHtml() (previously declared in /path-goes-here/enablehtml.php:10) in /path-goes-here/enablehtml.php on line 10 <?php if (!defined('PmWiki')) exit(); function EnableHtml($tag) { Markup( "html-$tag", '>{$var}', '/<(\/?('.$tag.')(?![a-z!])(([\'"]).*?\4|.*?)*?)>/i', "MyHtml" ); function MyHtml($matches) { return Keep('<'.$matches[1].'>'); } } ?> Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150922/ea185489/attachment.html> From design at softflow.co.uk Tue Sep 22 10:42:17 2015 From: design at softflow.co.uk (Hans Bracker) Date: Tue, 22 Sep 2015 16:42:17 +0100 Subject: [pmwiki-users] EnableHTML for php5.6 In-Reply-To: <CANR9UnMQCUYGU1GwC7X2SDDi2jNu8QwBkkuqj8kCD6V+D-vqnQ@mail.gmail.com> References: <CANR9UnMQCUYGU1GwC7X2SDDi2jNu8QwBkkuqj8kCD6V+D-vqnQ@mail.gmail.com> Message-ID: <15862371.20150922164217@softflow.co.uk> > Is there a version of enablehtml.php that will work with php5.6? try this for your enable.php file: <?php if (!defined('PmWiki')) exit(); function EnableHtml($tag) { Markup_e( "html-$tag", '>{$var}', '/<(\/?('.$tag.')(?![a-z!])(([\'"]).*?\4|.*?)*?)>/i', 'Keep(\'<\'.$m[1].\'>\')'); } Best regards, Hans From design at softflow.co.uk Tue Sep 22 11:51:53 2015 From: design at softflow.co.uk (Hans Bracker) Date: Tue, 22 Sep 2015 17:51:53 +0100 Subject: [pmwiki-users] Multiple checkboxes In-Reply-To: <fcd866b9fbb9293873ec006aacf78b9a@5ko.fr> References: <CAMrCtLfpwdfUE1vzC1zacDf5+YubUQEjdkgvUx3A++q=1Nvq9g@mail.gmail.com> <fcd866b9fbb9293873ec006aacf78b9a@5ko.fr> Message-ID: <1271338677.20150922175153@softflow.co.uk> > I believe Fox was also updated to handle those. > The current way to do this would be to set multiple default values, > separated by spaces, like: > your PageTextVariable (PTV): > (:Hobby:Travels Music:) The update to fox.php consisted in removing a now redundant custom InputDefault function. For adding and updating PTVs from a form with array elements as input Fox has always posted the array as a list of comma-sperated values. so in this example form (:foxmessages:) (:fox frm ptvtarget=Main.WikiSandbox ptvfmt=text:) (:input default $:Hobby[] {$:Hobby}:) (:input checkbox $:Hobby[] Travels:) Travels (:input checkbox $:Hobby[] Photography:) Photography (:input checkbox $:Hobby[] Music:) Music (:input submit post:) (:foxend frm:) multiple input box ticking results in a PTV looking something like this: Hobby: Travels,Photography,Music which then would not populate input defaults correctly, ie. it needs spaces between values not commas! How can we resolve this? I could add a Fox config variable "$FoxPTVArraySeparator", which could be set to a comma or a space or even a comma and a space or what ever. I am not sure what a change in the default from comma to space would break for sites updating fox.php. Could PmWiki have a similar configuration variable, so instead of a space a comma could be used in a PTV holding array elements? Best regards, Hans mailto:design at softflow.co.uk www.softflow.co.uk From 5ko at 5ko.fr Wed Sep 23 13:35:23 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Wed, 23 Sep 2015 20:35:23 +0200 Subject: [pmwiki-users] Multiple checkboxes In-Reply-To: <1271338677.20150922175153@softflow.co.uk> References: <CAMrCtLfpwdfUE1vzC1zacDf5+YubUQEjdkgvUx3A++q=1Nvq9g@mail.gmail.com> <fcd866b9fbb9293873ec006aacf78b9a@5ko.fr> <1271338677.20150922175153@softflow.co.uk> Message-ID: <314a1281008a73de930f81f7b4710f4b@5ko.fr> On 2015-09-22 18:51, Hans Bracker wrote: > multiple input box ticking results in a PTV looking something like > this: > > Hobby: Travels,Photography,Music > > which then would not populate input defaults correctly, ie. it needs > spaces between values not commas! > > How can we resolve this? I could add a Fox config variable > "$FoxPTVArraySeparator", which could be set to a comma or a space or > even a comma and a space or what ever. I am not sure what a change in > the default from comma to space would break for sites updating > fox.php. > Could PmWiki have a similar configuration variable, so instead of a > space > a comma could be used in a PTV holding array elements? Yes, it could. The new feature was added recently and is not yet in the core documentation so we can change it. Currently "space" is a separator but not so simple: one can quote strings containing spaces; this comes very handy from ParseArgs(). (:input default name[] val1 "val 2" val3 val4:) -> note, may change! Using a simple explode() with a separator is very easy but what happens if one of the values contains the separator? Also, the current markup for all input elements: (:input ELEMENT name 1,2,3,4,somevalue:) means that the "value" argument in the HTML input tag is "1,2,3,4,somevalue". It is not very consistent to have ONE way to define a value in (:input text name value:), (:input checkbox name value:) or any other element, and ANOTHER in (:input default name value:). I also also think that an existing PTV in the page should be able to check/uncheck the checkboxes, by simply setting (:input default source=1:). Let me think about it. Petko -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From design at softflow.co.uk Thu Sep 24 05:42:51 2015 From: design at softflow.co.uk (Hans Bracker) Date: Thu, 24 Sep 2015 11:42:51 +0100 Subject: [pmwiki-users] Multiple checkboxes In-Reply-To: <314a1281008a73de930f81f7b4710f4b@5ko.fr> References: <CAMrCtLfpwdfUE1vzC1zacDf5+YubUQEjdkgvUx3A++q=1Nvq9g@mail.gmail.com> <fcd866b9fbb9293873ec006aacf78b9a@5ko.fr> <1271338677.20150922175153@softflow.co.uk> <314a1281008a73de930f81f7b4710f4b@5ko.fr> Message-ID: <100685613.20150924114251@softflow.co.uk> > Using a simple explode() with a separator is very easy but what happens > if one of the values contains the separator? > Also, the current markup for all input elements: > (:input ELEMENT name 1,2,3,4,somevalue:) > means that the "value" argument in the HTML input tag is > "1,2,3,4,somevalue". It is not very consistent to have ONE way to define > a value in (:input text name value:), (:input checkbox name value:) or > any other element, and ANOTHER in (:input default name value:). I agree. I also think it may be too much to push the array concept too far when we want to save arrays in simple PTVs. Since the space separator works well enough with (:input default:), as illustrated with your example, it may be best to leave it at that. I will publish a fox.php version, which will use space as separatot when saving array values in a PTV, by default. And have an optional $FoxPTVArraySeparator variable, which can be set to "," or other separator character strings. I also found a way to have checkboxes reflect the values in such a PTV, by using a simple markup expression to clean up the PTV for use with spaces in (:input default .. :), like in this form example: (:foxmessages:) (:fox frm ptvtarget=Main.WikiSandbox ptvfmt=text :) (:input default $:Hobby[] {(foxcleanptv "{$:Hobby}")} :) (:input hidden $:Hobby " ":) (:input checkbox $:Hobby[] Travels:) Travels (:input checkbox $:Hobby[] Photo:) Photography (:input checkbox $:Hobby[] Music:) Music (:input submit post:) (:foxend frm:) The markup expression defined in config.php: $MarkupExpr['foxcleanptv'] = 'FoxCleanPTV($args[0])'; function FoxCleanPTV($arg) { global $FoxPTVArraySeparator; $pat = '/'.$FoxPTVArraySeparator.'/'; return preg_replace($pat," ",$arg); } This seems to work well with various separators, and the PTV can look for instance like these, in simple text PTVs: Hobby: Travels,Photo,Music Hobby: Travels, Photo, Music Hobby: Travels + Photo + Music Best regards, Hans mailto:design at softflow.co.uk www.softflow.co.uk From mirceapaul at rogers.com Thu Sep 24 12:03:42 2015 From: mirceapaul at rogers.com (mirceapaul at rogers.com) Date: Thu, 24 Sep 2015 17:03:42 +0000 (UTC) Subject: [pmwiki-users] unsubscribe In-Reply-To: <mailman.3.1443114002.30232.pmwiki-users@pmichaud.com> References: <mailman.3.1443114002.30232.pmwiki-users@pmichaud.com> Message-ID: <470387527.457950.1443114223005.JavaMail.yahoo@mail.yahoo.com> From: "pmwiki-users-request at pmichaud.com" <pmwiki-users-request at pmichaud.com> To: pmwiki-users at pmichaud.com Sent: Thursday, September 24, 2015 1:00 PM Subject: pmwiki-users Digest, Vol 123, Issue 15 Send pmwiki-users mailing list submissions to ??? pmwiki-users at pmichaud.com To subscribe or unsubscribe via the World Wide Web, visit ??? http://www.pmichaud.com/mailman/listinfo/pmwiki-users or, via email, send a message with subject or body 'help' to ??? pmwiki-users-request at pmichaud.com You can reach the person managing the list at ??? pmwiki-users-owner at pmichaud.com When replying, please edit your Subject line so it is more specific than "Re: Contents of pmwiki-users digest..." Today's Topics: ? 1. Re: Multiple checkboxes (Petko Yotov) ? 2. Re: Multiple checkboxes (Hans Bracker) ---------------------------------------------------------------------- Message: 1 Date: Wed, 23 Sep 2015 20:35:23 +0200 From: Petko Yotov <5ko at 5ko.fr> To: PmWiki Users <pmwiki-users at pmichaud.com> Subject: Re: [pmwiki-users] Multiple checkboxes Message-ID: <314a1281008a73de930f81f7b4710f4b at 5ko.fr> Content-Type: text/plain; charset=US-ASCII; format=flowed On 2015-09-22 18:51, Hans Bracker wrote: > multiple input box ticking results in a PTV looking something like > this: > > Hobby: Travels,Photography,Music > > which then would not populate input defaults correctly, ie. it needs > spaces between values not commas! > > How can we resolve this? I could add a Fox config variable > "$FoxPTVArraySeparator", which could be set to a comma or a space or > even a comma and a space or what ever. I am not sure what a change in > the default from comma to space would break for sites updating > fox.php. > Could PmWiki have a similar configuration variable, so instead of a? > space > a comma could be used in a PTV holding array elements? Yes, it could. The new feature was added recently and is not yet in the core documentation so we can change it. Currently "space" is a separator but not so simple: one can quote strings containing spaces; this comes very handy from ParseArgs(). ? (:input default name[] val1 "val 2" val3 val4:) ? -> note, may change! Using a simple explode() with a separator is very easy but what happens if one of the values contains the separator? Also, the current markup for all input elements: ? (:input ELEMENT name 1,2,3,4,somevalue:) means that the "value" argument in the HTML input tag is "1,2,3,4,somevalue". It is not very consistent to have ONE way to define a value in (:input text name value:), (:input checkbox name value:) or any other element, and ANOTHER in (:input default name value:). I also also think that an existing PTV in the page should be able to check/uncheck the checkboxes, by simply setting (:input default source=1:). Let me think about it. Petko -- Change log? ? :? http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes? :? http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade :? http://www.pmwiki.org/wiki/PmWiki/Upgrades ------------------------------ Message: 2 Date: Thu, 24 Sep 2015 11:42:51 +0100 From: Hans Bracker <design at softflow.co.uk> To: Petko Yotov <5ko at 5ko.fr> Cc: PmWiki Users <pmwiki-users at pmichaud.com> Subject: Re: [pmwiki-users] Multiple checkboxes Message-ID: <100685613.20150924114251 at softflow.co.uk> Content-Type: text/plain; charset=us-ascii > Using a simple explode() with a separator is very easy but what happens > if one of the values contains the separator? > Also, the current markup for all input elements: >? ? (:input ELEMENT name 1,2,3,4,somevalue:) > means that the "value" argument in the HTML input tag is > "1,2,3,4,somevalue". It is not very consistent to have ONE way to define > a value in (:input text name value:), (:input checkbox name value:) or > any other element, and ANOTHER in (:input default name value:). I agree. I also think it may be too much to push the array concept too far when we want to save arrays in simple PTVs. Since the space separator works well enough with (:input default:), as illustrated with your example, it may be best to leave it at that. I will publish a fox.php version, which will use space as separatot when saving array values in a PTV, by default. And have an optional $FoxPTVArraySeparator variable, which can be set to "," or other separator character strings. I also found a way to have checkboxes reflect the values in such a PTV, by using a simple markup expression to clean up the PTV for use with spaces in (:input default .. :), like in this form example: (:foxmessages:) (:fox frm ptvtarget=Main.WikiSandbox ptvfmt=text :) (:input default $:Hobby[] {(foxcleanptv "{$:Hobby}")} :) (:input hidden $:Hobby " ":) (:input checkbox $:Hobby[] Travels:) Travels (:input checkbox $:Hobby[] Photo:) Photography (:input checkbox $:Hobby[] Music:) Music (:input submit post:) (:foxend frm:) The markup expression defined in config.php: $MarkupExpr['foxcleanptv'] = 'FoxCleanPTV($args[0])'; function FoxCleanPTV($arg) { ? ? ? ? global $FoxPTVArraySeparator; ? ? ? ? $pat = '/'.$FoxPTVArraySeparator.'/'; ? ? ? ? return preg_replace($pat," ",$arg); } This seems to work well with various separators, and the PTV can look for instance like these, in simple text PTVs: Hobby: Travels,Photo,Music Hobby: Travels, Photo, Music Hobby: Travels + Photo + Music Best regards, Hans? ? ? ? ? ? ? ? ? ? ? ? mailto:design at softflow.co.uk www.softflow.co.uk ------------------------------ Subject: Digest Footer _______________________________________________ pmwiki-users mailing list pmwiki-users at pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users ------------------------------ End of pmwiki-users Digest, Vol 123, Issue 15 ********************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150924/ed11f7d7/attachment.html> From cobblestone at lindevej.dk Sat Sep 26 10:14:23 2015 From: cobblestone at lindevej.dk (Cobblestone) Date: Sat, 26 Sep 2015 17:14:23 +0200 Subject: [pmwiki-users] Moved wiki not loading Message-ID: <etPan.5606b650.1651d180.6728@Oles-iMac.local> I have moved web host and dutifully, I thought, copied everything. But when I load up my wiki page I do get a blank slate - without the wiki-contents from the old wiki showing. They are all there in the wiki.d folder.? Any ideas to the small (or big) things I have overlooked that prevents it from loading? http://lindevej.dk/oenskesedler/ ?? Ole / Cobblestone -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150926/db6645d0/attachment.html> From randy at brownragfilms.com Sat Sep 26 12:12:49 2015 From: randy at brownragfilms.com (Randy Brown) Date: Sat, 26 Sep 2015 12:12:49 -0500 Subject: [pmwiki-users] Moved wiki not loading (Cobblestone) In-Reply-To: <mailman.3.1443286802.3827.pmwiki-users@pmichaud.com> References: <mailman.3.1443286802.3827.pmwiki-users@pmichaud.com> Message-ID: <0821D1D3-026F-47A8-BAD1-5C0D586107FA@brownragfilms.com> If for some reason the wiki.d directory can?t be read (read permissions?) this might explain what happened. Also, does your configuration file specify the library directories explicitly? If PmWiki can?t find the specified wiki.d library, it may default to the wikilib.d directory, which will make your wiki seem brand new. Just some possibilities... I would try installing a fresh copy of PmWiki and then, if it looks correct, replacing the wiki.d directory. Randy > > I have moved web host and dutifully, I thought, copied everything. > > But when I load up my wiki page I do get a blank slate - without the wiki-contents from the old wiki showing. They are all there in the wiki.d folder.? > > Any ideas to the small (or big) things I have overlooked that prevents it from loading? > > http://lindevej.dk/oenskesedler/ > ************************************** From languefrancaise at gmail.com Sat Sep 26 16:34:02 2015 From: languefrancaise at gmail.com (ABClf) Date: Sat, 26 Sep 2015 23:34:02 +0200 Subject: [pmwiki-users] Moved wiki not loading In-Reply-To: <etPan.5606b650.1651d180.6728@Oles-iMac.local> References: <etPan.5606b650.1651d180.6728@Oles-iMac.local> Message-ID: <CACE3LEvaAjqWFJNz38Z_5vNNO8yk-TV1TOT6pARA4acf6d_L4Q@mail.gmail.com> You have wikilib.d working and one can write new page in new group in your wiki. At first, be sure to check file permissions on your server (chmod 777 wiki.d) and recheck pathes and everything related to accessing wiki pages (url, htaccess) in your config. Page of (little) help : http://www.pmwiki.org/wiki/PmWiki/BackupAndRestore Gilles. 2015-09-26 17:14 GMT+02:00 Cobblestone <cobblestone at lindevej.dk>: > I have moved web host and dutifully, I thought, copied everything. > > But when I load up my wiki page I do get a blank slate - without the > wiki-contents from the old wiki showing. They are all there in the wiki.d > folder. > > Any ideas to the small (or big) things I have overlooked that prevents it > from loading? > > http://lindevej.dk/oenskesedler/ > > ? > > Ole / Cobblestone > > _______________________________________________ > pmwiki-users mailing list > pmwiki-users at pmichaud.com > http://www.pmichaud.com/mailman/listinfo/pmwiki-users > From design at softflow.co.uk Mon Sep 28 05:59:12 2015 From: design at softflow.co.uk (Hans Bracker) Date: Mon, 28 Sep 2015 11:59:12 +0100 Subject: [pmwiki-users] Markup Expression parameters Message-ID: <401367666.20150928115912@softflow.co.uk> Trying to write a markup expression, I am having trouble getting the whole unaltered string from a PTV into my ME function. Only strings in double quotes do not get altered (but the double quotes get stripped, which I guess is okay). Otherwise PmWiki uses KeepTokens (if $params is used) and strips single quotes. I used both $params and $args to capture the string, with similar results. OTOH displaying a PTV does not change anything. Here is a test markup expression, and a test page content: //for testing $MarkupExpr['fixptv'] = 'FixPtv($params)'; function FixPtv($a) { print_r($a); echo "<br/>"; $r = (is_array($a)) ? implode(" ",$a) : $a; return $r; } //in wiki page Music1: Classical, "Rhythm & Blues", "Rock'n'Roll" as M.E.: {(fixptv {$:Music1})} as PTV: {$:Music1} Music2: Classical, Rhythm & Blues, Rock'n'Roll as M.E.: {(fixptv {$:Music2})} as PTV: {$:Music2} Music3: Classical,Rhythm & Blues,Rock'n'Roll as M.E.: {(fixptv {$:Music3})} as PTV: {$:Music3} Is there a way to get the PTV string unaltered into the function, for further manipulation there, including quotes? thanks Hans From 5ko at 5ko.fr Mon Sep 28 16:31:21 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Mon, 28 Sep 2015 23:31:21 +0200 Subject: [pmwiki-users] Markup Expression parameters In-Reply-To: <401367666.20150928115912@softflow.co.uk> References: <401367666.20150928115912@softflow.co.uk> Message-ID: <72a045e07d42d69aee1c5e8efd67b883@5ko.fr> On 2015-09-28 12:59, Hans Bracker wrote: > Trying to write a markup expression, I am having trouble getting the > whole unaltered string from a PTV into my ME function. > Only strings in double quotes do not get altered (but the double > quotes get stripped, which I guess is okay). > Otherwise PmWiki uses KeepTokens (if $params is used) > and strips single quotes. > I used both $params and $args to capture the string, > with similar results. > OTOH displaying a PTV does not change anything. In Markup expressions quoted strings are considered parameters; moreover there may be nested expressions which complicates things. > as M.E.: {(fixptv {$:Music1})} When markup expressions are processed, PmWiki actually sees here: {(fixptv Classical, "Rhythm & Blues", "Rock'n'Roll")} i.e. at that point the PTV is already expanded to its value; then the markup expression function parses and escapes the parameters to allow nested expressions and processes the string as many times as there are nested expressions. If your value contains parentheses like "(pop)rock" this will be considered another Markup expression and will be further escaped. To get the unaltered value of the variable, maybe you could write this like {(fixptv $:Music1)} without the internal set of braces. Then your function can call PageTextVar() to get the value. Petko -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From cgpmw13 at codingmaniac.com Tue Sep 29 03:23:37 2015 From: cgpmw13 at codingmaniac.com (Chuck G) Date: Tue, 29 Sep 2015 03:23:37 -0500 (CDT) Subject: [pmwiki-users] Markup Expression parameters References: <401367666.20150928115912@softflow.co.uk> Message-ID: <mudhqa$4mh$1@ger.gmane.org> Hans Bracker <design at softflow.co.uk> Wrote in message: > > Trying to write a markup expression, I am having trouble getting the > whole unaltered string from a PTV into my ME function. > Only strings in double quotes do not get altered (but the double > quotes get stripped, which I guess is okay). > Otherwise PmWiki uses KeepTokens (if $params is used) > and strips single quotes. > I used both $params and $args to capture the string, > with similar results. > OTOH displaying a PTV does not change anything. > > Here is a test markup expression, and a test page content: > > //for testing > $MarkupExpr['fixptv'] = 'FixPtv($params)'; > function FixPtv($a) { > print_r($a); echo "<br/>"; > $r = (is_array($a)) ? implode(" ",$a) : $a; > return $r; > } > > //in wiki page > Music1: Classical, "Rhythm & Blues", "Rock'n'Roll" > as M.E.: {(fixptv {$:Music1})} > as PTV: {$:Music1} > > Music2: Classical, Rhythm & Blues, Rock'n'Roll > as M.E.: {(fixptv {$:Music2})} > as PTV: {$:Music2} > > Music3: Classical,Rhythm & Blues,Rock'n'Roll > as M.E.: {(fixptv {$:Music3})} > as PTV: {$:Music3} > > Is there a way to get the PTV string unaltered into the function, for > further manipulation there, including quotes? > > thanks > Hans > See a possible solution at - http://www.codingmaniac.com/pmwikitest/apcu/index.php?n=ChuckG. MepTest01 Embedded PTV references within the PTV do get altered. Chuck G -- ----Android NewsGroup Reader---- http://usenet.sinaapp.com/ From design at softflow.co.uk Tue Sep 29 04:30:02 2015 From: design at softflow.co.uk (Hans Bracker) Date: Tue, 29 Sep 2015 10:30:02 +0100 Subject: [pmwiki-users] Markup Expression parameters In-Reply-To: <mudhqa$4mh$1@ger.gmane.org> References: <401367666.20150928115912@softflow.co.uk> <mudhqa$4mh$1@ger.gmane.org> Message-ID: <174586511.20150929103002@softflow.co.uk> Hello Chuck, Tuesday, September 29, 2015, 9:23:37 AM, you wrote: > - http://www.codingmaniac.com/pmwikitest/apcu/index.php?n=ChuckG. > MepTest01 > Embedded PTV references within the PTV do get altered. you need to use PageTextVar(), PageVar(), as Petko kindly advised. Something like this: $MarkupExpr['fixptv2'] = 'FixPtv2($pagename,$args[0])'; function FixPtv2($pn,$a) { $r = PageTextVar($pn, substr($a,2)); echo $pn; print_r($r); return $r; } embedded expressions and PTvs get rendered correctly in the return, but not before. thanks, Hans From design at softflow.co.uk Tue Sep 29 04:35:58 2015 From: design at softflow.co.uk (Hans Bracker) Date: Tue, 29 Sep 2015 10:35:58 +0100 Subject: [pmwiki-users] Markup Expression parameters In-Reply-To: <mudhqa$4mh$1@ger.gmane.org> References: <401367666.20150928115912@softflow.co.uk> <mudhqa$4mh$1@ger.gmane.org> Message-ID: <01976648.20150929103558@softflow.co.uk> I meant: you need to use PageTextVar(), not PageVar(), Hans From cgpmw13 at codingmaniac.com Tue Sep 29 20:03:03 2015 From: cgpmw13 at codingmaniac.com (Chuck G) Date: Tue, 29 Sep 2015 20:03:03 -0500 (CDT) Subject: [pmwiki-users] Markup Expression parameters References: <401367666.20150928115912@softflow.co.uk> <mudhqa$4mh$1@ger.gmane.org> <01976648.20150929103558@softflow.co.uk> Message-ID: <mufcc7$euo$1@ger.gmane.org> Hans Bracker <design at softflow.co.uk> Wrote in message: > > I meant: > > you need to use PageTextVar(), not PageVar(), > > > Hans > Using PageTextVar() is more efficient, but the result is the same. Chuck G -- ----Android NewsGroup Reader---- http://usenet.sinaapp.com/ From burggraaferik at gmail.com Wed Sep 30 10:44:14 2015 From: burggraaferik at gmail.com (erik burggraaf) Date: Wed, 30 Sep 2015 08:44:14 -0700 Subject: [pmwiki-users] ?about the print action Message-ID: <D1E02C35-4204-4819-B268-B0AF5CDDD8AD@gmail.com> Hi, I'm wondering . Is there markup for things like page breaks so that pmwiki can be made to print long articles intelligently? I'm not sure what to search for in the docs to get this answer. thanks for your help, Erik From randy at brownragfilms.com Wed Sep 30 16:24:36 2015 From: randy at brownragfilms.com (Randy Brown) Date: Wed, 30 Sep 2015 16:24:36 -0500 Subject: [pmwiki-users] ?about the print action Message-ID: <649A5A19-A9F0-46A0-BB3E-8ADC4A5CA1C5@brownragfilms.com> I don?t know of any way to do intelligent pagination in PmWiki. However, a recipe like one of these might help: http://www.pmwiki.org/wiki/Cookbook/PublishPDF <http://www.pmwiki.org/wiki/Cookbook/PublishPDF> http://www.pmwiki.org/wiki/Cookbook/BreakPage <http://www.pmwiki.org/wiki/Cookbook/BreakPage> Randy >> Hi, I'm wondering . Is there markup for things like page breaks so that pmwiki can be made to print long articles intelligently? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20150930/b0e1cf27/attachment.html> From 5ko at 5ko.fr Wed Sep 30 16:37:05 2015 From: 5ko at 5ko.fr (Petko Yotov) Date: Wed, 30 Sep 2015 23:37:05 +0200 Subject: [pmwiki-users] PmWiki 2.2.80 released Message-ID: <3b4d86fc37768de1bb8f1eb78f49a919@5ko.fr> Hello. PmWiki version 2.2.80 was published today, and is available at: http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.80.tgz http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.80.zip svn://www.pmwiki.org/pmwiki/tags/latest This version modifies the (:searchbox:) directive to use type="search" semantic input, and updates the documentation. I'd also like to read your opinions about any potential problems that may be expected, or not, if the search field of the default skin becomes of the recent semantic "search" type, instead of the current "text". I don't see any, as browsers consider and render input fields of unknown type as "text" inputs. Thanks, Petko -- Change log : http://www.pmwiki.org/wiki/PmWiki/ChangeLog Release notes : http://www.pmwiki.org/wiki/PmWiki/ReleaseNotes If you upgrade : http://www.pmwiki.org/wiki/PmWiki/Upgrades From kirpi at kirpi.it Wed Sep 30 17:06:09 2015 From: kirpi at kirpi.it (kirpi at kirpi.it) Date: Thu, 1 Oct 2015 00:06:09 +0200 Subject: [pmwiki-users] Multiple checkboxes In-Reply-To: <CAMrCtLdZuVQvCCXP+oiF2OwdsUefuUMjCeefnGnvMnh_NCNgqw@mail.gmail.com> References: <CAMrCtLfpwdfUE1vzC1zacDf5+YubUQEjdkgvUx3A++q=1Nvq9g@mail.gmail.com> <CAMrCtLdZuVQvCCXP+oiF2OwdsUefuUMjCeefnGnvMnh_NCNgqw@mail.gmail.com> Message-ID: <CAMrCtLdBYEH7doHAxRh4ewV7GMU99LbBHC74bxdYZ=pQSE=B-Q@mail.gmail.com> I want to thank Petko for his prompt and detailed help. As well as for his steady involvement in pmwiki development. Thank you Petko, really! Also, Hans' new enhancements of Fox made a big difference, as forms can be handled and processed in a very flexible way. So, as I adopt Fox, I ended up to have: (:input default $:Hobby[] {(foxfixptv $:Hobby)}:) (:input checkbox $:Hobby[] Travels:) Travels (:input checkbox $:Hobby[] Photography:) Photography (:input checkbox $:Hobby[] Music:) Music which works flawlessly and, depending on a simple Fox variable in config.php, is able to save as: Hobby: Travels Photography Music or Hobby: Travels,Photography,Music or Hobby: Travels, Photography, Music or Hobby: Travels + Photography + Music or any other suitable separator. Moreover, this setting is backward compatible, that is if a wiki already has PTV arrays written with a certain separator (be it space, comma or any other), it properly sets the relevant checkboxes on edit, and saves in any chosen format, without breaking the system. Thanks Petko, once more! And thanks Hans, again! :-) Luigi