Re: [pmwiki-users] PmWiki 20 years, version 2.3.1 released

[ABClf]

Thank you Petko for all your work and everyday support.
That is greatly appreciated.

Le sam. 15 janv. 2022 à 16:06, Petko Yotov <5...@5ko.fr> a écrit :
>
> Hello,
>
> PmWiki version 2.3.1 was published today, and is available at:
>
> https://www.pmwiki.org/pub/pmwiki/pmwiki-2.3.1.tgz
> https://www.pmwiki.org/pub/pmwiki/pmwiki-2.3.1.zip
> svn://www.pmwiki.org/pmwiki/tags/latest
>
>
> January 2022 is the 20th year anniversary of the release of PmWiki version 
> 0.1, and 13 years since I (Petko) became core developer. This merited 
> additional work and effort with hopefully interesting and useful new 
> production.
>
>
> PHP 5.3 - 8.1 compatibility
>
> PmWiki 2.3.1 includes updates for PHP 8.0 and 8.1.
> Consequently, it requires PHP version 5.3 (released 2009) or more recent.
>
>
> PmSyntax. A new function PmSyntax was added to the core, and enabled on 
> pmwiki.org.
>
> It highlights PmWiki syntax in the documentation, and possibly in the basic 
> edit form.
> It only highlights PmWiki markup, and is independent from Highlight.js. See 
> Cookbook:PmSyntax and $EnablePmSyntax.
> It should highlight most core language features and those of many recipes, 
> see this mashup of various markups.
> Developers can add custom rules in the $CustomSyntax array, see 
> Cookbook:CustomSyntax.
> The (:markup:) directive can now have class=norender to only show the source 
> code without processing it. This may be useful, together with PmSyntax, in 2 
> cases: writing/discussing markup code without actually running it, or working 
> on PageList Templates where you want to see and edit them highlighted.
>
>
> Improvements to the edit form
>
> PmSyntax (above) can be enabled to highlight the PmWiki markup the edit form, 
> and should work in recent standards-compliant browsers.
> The variable $EnableNotSavedWarning is now enabled by default. Add to 
> config.php $EnableNotSavedWarning = 0; to disable it.
> A new variable $EnableIncludedPages allows listing of other pages included 
> from the currently edited page, with links to see or edit them. When the 
> variable is enabled, the list of pages appears in the edit form, after the 
> text area, in a collapsed  element. The list includes pages from 
> which text, text variables, or templates are included from the edited page. 
> This is enabled on pmwiki.org if you wish to preview it.
> The $EnableEditAutoText function will now feel more like other text editors 
> by removing the automatically inserted bullet when Enter is pressed twice.
>
>
> Dates and times, monitoring, review
>
> The {(ftime)} Markup expression now accepts a new format '%o' for the ordinal 
> suffix of the date.
> The Notify feature now accepts a tz= timezone specifier for individual 
> subscribers. See Notify#tz.
> A function based on Cookbook:LocalTimes was added to the core. See the recipe 
> page for the differences. You can continue using the recipe, or disable it 
> and enable the core function.
> New core variables $EnableLocalTimes, $CurrentLocalTime.
> New markup @2022-01-09T08:35:00Z output as a  element, formatted via 
> $TimeFmt; localized if $EnableLocalTimes.
> Added a variable $EnableRecentUploads which makes it easy to enable the 
> Recent Uploads feature on AllRecentChanges. This is a basic format that may 
> be good enough for many wikis. For more options, see 
> Cookbook:RecentUploadsLog.
> The default $RecentChangesFmt now use the variable $CurrentLocalTime instead 
> of $CurrentTime. In the wiki source text it saves the timestamps in a 
> portable time format in GMT, which is then shown formatted per $TimeFmt (wiki 
> timezone). It looks just like $CurrentTime did previously, but can be 
> converted to the visitor's time zone if LocalTimes is enabled. If you have 
> custom $RecentChangesFmt entries that use $CurrentTime, nothing will change 
> for you, but you may want to update these with $CurrentLocalTime if you want 
> to benefit from localization.
> The "page history" page now has CSS classes for the delay between edits: 
> diffday, diffweek, diffmonth, diffyear. These allow styling of vertical 
> spacing between individual edits in page histories. See Cookbook:DiffDelay 
> for an example.
> The page history can now have a "hidden" edit type, in addition to "minor". 
> This is intended to be used by recipes in order to hide, rather than delete, 
> some edits from the page history. A couple of new recipes using this feature 
> will be added in the next few days.
>
>
> PageLists, categories, backlinks
>
> PageLists now accept a new argument category=Name which lists only pages 
> declared in the category with the markup [[!Name]], and does not include 
> pages simply linking to [[Category/Name]] (unless they also contain 
> [[!Name]]).
>
> The differentiation between links to !Name and Category.Name requires the 
> pages containing category links to be re-indexed; see 
> Cookbook:ReindexCategories which can automate this.
>
> Also in PageLists, the arguments link= and category= 

Re: [pmwiki-users] Should $EnableNotSavedWarning be enabled by default?

[ABClf]

No matter what choice will be done for sample-config, it's convenient
to have this line
written in starting config (commented or no), so that administrators
know that such option does exist.

As for me I have no preference here. I did not use that option ; testing now.
If the message written in the pop-up can be modified, I would prefer
"Quit this page" instead of "Quit website".

Thank you.
Gilles.

Le mar. 4 janv. 2022 à 21:40, Simon  a écrit :
>
> I couldn't agree more.
> As there is no easy undo if you close without saving, and the consequences 
> are severe - the loss of potentially a lot of work.
>
> Also I think modern expectation (cf online editing such as google docs) is 
> that you can't/shouldn't be able to accidentally lose input.
>
> great idea
>
> Simon
>
>
> On Wed, 5 Jan 2022 at 00:23, Petko Yotov <5...@5ko.fr> wrote:
>>
>> Currently by default PmWiki doesn't warn when people edit a page, and
>> try to move away from the edit form without saving.
>>
>> We have $EnableNotSavedWarning but it needs to be enabled in config.php
>> by the administrator.
>>
>> I added it to sample-config.php, but I wonder if instead we should
>> simply enable it by default.
>>
>> I believe the setting dramatically improves the user experience and
>> saves a lot of frustration, especially with inexperienced editors and
>> administrators (who have yet to read the documentation and enable the
>> setting).
>>
>> The setting, enabled, might possibly interfere with some custom edit
>> forms, although I am not aware of such a case, or with some of the
>> existing recipes that do exactly this.
>>
>> If we enable it by default, anyone who doesn't need this feature can
>> disable it with
>>
>>$EnableNotSavedWarning = 0;
>>
>> Even if there might be existing administrators who may be annoyed to add
>> this line when they upgrade, I feel the benefit from having the feature
>> enabled outweighs the downside.
>>
>> Thoughts?
>>
>> Petko
>>
>> ___
>> pmwiki-users mailing list
>> pmwiki-users@pmichaud.com
>> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Intermap with accented link

[ABClf]

That works now as expected ; thank you Petko.
I should have noted the different case.

for littré as interlink command word, set this in config :

$LinkFunctions['littré:'] = 'LinkIMap';
$IMap['littré:'] = 'https://www.littre.org/definition/$1';

Le ven. 31 déc. 2021 à 05:26, Petko Yotov <5...@5ko.fr> a écrit :
>
> Pardon, ce que j'ai fait crée un préfixe "Littré:" avec "L" majuscule et
> non "littré:" tout en minuscules.
>
> On peut faire
> $LinkFunctions['littré:'] = 'LinkIMap';
> $IMap['littré:'] = 'https://www.littre.org/definition/$1';
>
> Petko
>
> On 30/12/2021 21:04, ABClf wrote:
> > Thank you Petko,
> > No, it still doesn't work with accented letters (at least, me, my
> > setup, I was not successfull) ;
> > I use Cookbook/ISO8859MakePageNamePatterns which doesn't look faulty
> > (same behaviour when code is deleted)
> > and $DefaultPageCharset = array(''=>'ISO-8859-1'); is a commented line
> > in my config.
> >
> > I test soon with pristine pmwiki last version.
> >
> >
> > Le jeu. 30 déc. 2021 à 13:26, Petko Yotov <5...@5ko.fr> a écrit :
> >>
> >> Accented characters in Site.InterMap may or may not work. It may
> >> depend
> >> on your server locale and PHP version. Normally only "word"-characters
> >> can be used, but in different languages different characters can
> >> appear
> >> in words.
> >>
> >> The following, added to config.php, appears to work regardless of the
> >> server locale, from a UTF-8 enabled wiki, to a UTF-8 enabled target:
> >>
> >>$LinkFunctions['Littré:'] = 'LinkIMap';
> >>$IMap['Littré:'] = 'https://www.littre.org/definition/$1';
> >>
> >> In your case, both your wiki and the target website are UTF-8 enabled.
> >>
> >> Also, config.php must be saved in the UTF-8 encoding (it probably is;
> >> this is selected in the "File-Save As" dialogue box, or on some text
> >> editors from "File-Save With Encoding", or "Tools-Encoding", or
> >> "Tools-Charset").
> >>
> >> Petko
> >>
> >> --
> >> If you upgrade :  http://www.pmwiki.org/Upgrades
> >>
> >>
> >> On 30/12/2021 12:58, ABClf wrote:
> >> > Hello,
> >> >
> >> > I would like to know if intermap links do work if accented characters
> >> > is used for the command word. In my case, it doesn't, but my config
> >> > might be involved (can not test on pmwiki as my link has to be
> >> > approved first) :
> >> >
> >> > intermap tested :
> >> > littré:  https://www.littre.org/definition/
> >> >
> >> > command tested :
> >> > littré:péquin
> >> >
> >> > Thank you.
> >> > Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Intermap with accented link

[ABClf]

Thank you Petko,
No, it still doesn't work with accented letters (at least, me, my
setup, I was not successfull) ;
I use Cookbook/ISO8859MakePageNamePatterns which doesn't look faulty
(same behaviour when code is deleted)
and $DefaultPageCharset = array(''=>'ISO-8859-1'); is a commented line
in my config.

I test soon with pristine pmwiki last version.


Le jeu. 30 déc. 2021 à 13:26, Petko Yotov <5...@5ko.fr> a écrit :
>
> Accented characters in Site.InterMap may or may not work. It may depend
> on your server locale and PHP version. Normally only "word"-characters
> can be used, but in different languages different characters can appear
> in words.
>
> The following, added to config.php, appears to work regardless of the
> server locale, from a UTF-8 enabled wiki, to a UTF-8 enabled target:
>
>$LinkFunctions['Littré:'] = 'LinkIMap';
>$IMap['Littré:'] = 'https://www.littre.org/definition/$1';
>
> In your case, both your wiki and the target website are UTF-8 enabled.
>
> Also, config.php must be saved in the UTF-8 encoding (it probably is;
> this is selected in the "File-Save As" dialogue box, or on some text
> editors from "File-Save With Encoding", or "Tools-Encoding", or
> "Tools-Charset").
>
> Petko
>
> --
> If you upgrade :  http://www.pmwiki.org/Upgrades
>
>
> On 30/12/2021 12:58, ABClf wrote:
> > Hello,
> >
> > I would like to know if intermap links do work if accented characters
> > is used for the command word. In my case, it doesn't, but my config
> > might be involved (can not test on pmwiki as my link has to be
> > approved first) :
> >
> > intermap tested :
> > littré:  https://www.littre.org/definition/
> >
> > command tested :
> > littré:péquin
> >
> > Thank you.
> > Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Intermap with accented link

[ABClf]

Hello,

I would like to know if intermap links do work if accented characters
is used for the command word. In my case, it doesn't, but my config
might be involved (can not test on pmwiki as my link has to be
approved first) :

intermap tested :
littré:  https://www.littre.org/definition/

command tested :
littré:péquin

Thank you.
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] [pmwiki-devel] RFC: Community poll for PageList link/category arguments

[ABClf]

>>Indeed, in 2.3.0, when you have link=SinglePage, then the original
>>scanning method is used, so the times should be very close to the
>>current ones.
That's nice.
Thank you Petko for your answer (and for your great support, as always).

Le lun. 27 déc. 2021 à 09:04, Petko Yotov <5...@5ko.fr> a écrit :
>
> On 27/12/2021 07:57, Petko Yotov wrote:
> > When you're searching for links to multiple pages or to wildcards, the
> > new core algorithm is different from the one in the recipe, with fewer
> > loops, and I believe (hope) it will be faster than the current recipe.
>
> On PmWiki.org we only have about 10K pages, and here is our benchmark:
>
>https://www.pmwiki.org/wiki/Test/CorePLMT2
>
> Single page:
>link=PmWiki.BasicEditing
>
> 17: 00.22 00.21 PageListTermsTargets begin count=10109
> 20: 00.25 00.24 PageListTermsTargets end count=70
>
> That's 0.03 seconds.
>
>
> Wildcard, multiple pages:
>link=PmWiki.BasicEditin?,NoSuchGroup654.NoSuchPage987
>
> 52: 00.32 00.30 PageListTermsTargets begin count=10109
> 55: 00.39 00.37 PageListTermsTargets end count=72
>
> That's 0.07 seconds, only 0.04s or 1/25th of a second slower than the
> first one. I think it might be good enough for many people.
>
> Note that the second search is case-insensitive, it returns 2 additional
> pages which link to Pmwiki.BasicEditing (lowercase "w" in "Pmwiki")
> which doesn't exist.
>
> Not sure if I should do something about this case, or not.
>
> Petko
>
> On 27/12/2021 07:57, Petko Yotov wrote:
> > Thank you Gilles, these are great questions. My replies below.
> >
> > On 27/12/2021 01:28, ABClf wrote:
> >> I understand current installations won't be broken, yet I have a
> >> question about performance, concerning multiple link in pagelist :
> >> when benchmarking the same pagelist, targeting a one single link,
> >> native link=mylink against cookbooked links=mylink,
> >> it looks to me that native is faster ; am I right ?
> >>
> >> https://www.languefrancaise.net/Test/PageListMultiple (around 3)
> >> https://www.languefrancaise.net/Test/PageListNormal (around 1,70)
> >>
> >> If so, would it be possible to get the best of each : native for one
> >> target search, and complex for complex queries ?
> >
> > First, this is a fabulous installation with 64817 pages! It will be
> > great indeed to benchmark the new feature.
> >
> > Second, we need to look at the numbers between the start and end of
> > the functions, so the difference between the core and the recipe are
> > even greater:
> >
> > 422: 00,69 PageListTermsTargets begin count=64817
> > 425: 01,09 PageListTermsTargets end count=164
> >
> > 1.09-0.69=0.4 seconds for the core processing
> >
> > 422: 00,76 PageListMultiTargets begin count=64817
> > 425: 03,17 PageListMultiTargets end count=164
> >
> > 3.17-0.76=2.41 seconds for the recipe, that's about 6 times more
> > CPU-intensive.
> >
> >
> > Indeed, in 2.3.0, when you have link=SinglePage, then the original
> > scanning method is used, so the times should be very close to the
> > current ones.
> >
> > When you're searching for links to multiple pages or to wildcards, the
> > new core algorithm is different from the one in the recipe, with fewer
> > loops, and I believe (hope) it will be faster than the current recipe.
> >
> > Again, your installation will be a great place to verify this.
> >
> >
> >> Question 2, for this paragraph :
> >>
> >> link=PageA,PageB should list pages linking to "AT LEAST ONE" among
> >> PageA and PageB.
> >> link=+PageA,+PageB should list pages linking to "BOTH" PageA and
> >> PageB.
> >>
> >> I would like to know if case bellow is involved in the choice.
> >> In my case, I have a group made of pages named 1900, 1901, 1902, etc.,
> >> for aggregating words by years.
> >> Then, for the query
> >> links=Year.199*
> >> expected output would be to list pages having a link to any year page
> >> from 1990 to 1999 (and not list pages having a link to all pages
> >> included in the range).
> >
> > link=Year.199* or link=+Year.199* lists pages linking to any page with
> > the pattern, not to all pages, whether the target page exists or not.
> >
> > The wildcard characters are about characters, not about existing pages:
> >
> >   ? = exactly one character, any character
> >   * = between zero and any number of any character(s)
> >

Re: [pmwiki-users] RFC: Community poll for PageList link/category arguments

[ABClf]

Hello,

I understand current installations won't be broken, yet I have a
question about performance, concerning multiple link in pagelist :
when benchmarking the same pagelist, targeting a one single link,
native link=mylink against cookbooked links=mylink,
it looks to me that native is faster ; am I right ?

https://www.languefrancaise.net/Test/PageListMultiple (around 3)
https://www.languefrancaise.net/Test/PageListNormal (around 1,70)

If so, would it be possible to get the best of each : native for one
target search, and complex for complex queries ?

Gilles.

Le sam. 25 déc. 2021 à 09:13, Petko Yotov <5...@5ko.fr> a écrit :
>
> Hello,
>
> I hope you are all safe, and happy holidays if you're celebrating!
>
> I've been working on some new features for version 2.3.0 and I'd like
> your input.
>
> If you have a few minutes, please look at this page:
>
>https://www.pmwiki.org/wiki/PITS/01475
>
> ...and consider which ones of the proposed implementations may suit your
> wiki and your editors best, and add your name.
>
> I'd like to see some comments/votes and to release 2.3.0 by January 8.
> 2022, which will include implementing and documenting the new features.
>
> If you have questions or suggestions, you can add them to the page, or
> reply to the mailing list.
>
> Thank you in advance.
>
> Petko
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelist with RecentChanges trail : how to get rid of deleted pages which are listed ?

[ABClf]

Test done ;
indeed, improved code is quite faster.
For the test pagelist I have used, result is :
872: 02,98 now (to be compared with older 23420: 09,42).
I will have to do some thinking about what I want to do, and how fast.
Thank you Petko.


Le ven. 29 oct. 2021 à 17:23, Petko Yotov <5...@5ko.fr> a écrit :
>
> Next version should be released early next month, but you can already
> try the pre-release now -- get it from the PmWiki/ChangeLog page. Only
> pmwiki.php has changes related to this.
>
> It already has the "if exists" optimization, which on large pagelists
> may improve the stopwatch times by a factor of 10 or more. It is still
> case-insensitive, and this is unlikely to change in the core, but will
> allow a local configuration to override it or add a new one.
>
> Petko
>
> On 29/10/2021 16:05, ABClf wrote:
> > Thank you Petko ;
> > One, I believe I have used if="exists {=$FullName}" parameter with
> > defective syntax, and obviously failed in getting the expected result.
> >
> > Two, since I want to collect recently changed pages among several
> > groups in one shot, using fmt for grouping the output, I use
> > trail=Site.AllRecentChanges group=Group1,Group2,Group3. Might not be
> > cost effective, yet it looks like it's working decently.
> >
> > if="exists {=$FullName}" param can not be used in such a long pagelist
> > case ; with this parameter on, pagelist does too much for work, giving
> > :
> > 23420: 09,42 (using if exists)
> > 460: 00,52 (without if exists).
> >
> > I will try with the next version.
> > Gilles.
> >
> >
> > In my case I don't mind about case.
> >
> >
> >
> > Le dim. 24 oct. 2021 à 10:54, Petko Yotov <5...@5ko.fr> a écrit :
> >>
> >> The most efficient should be this:
> >>
> >>(:pagelist group=Main trail=Main.RecentChanges if="exists
> >> {=$FullName}":)
> >>
> >> group=Main is recommended if your pages are all from the same group.
> >>
> >> I just found out that the "exists" conditional can be optimized a lot,
> >> especially when called multiple times from a pagelist. This will be
> >> released in the next version in a few days.
> >>
> >> One other note, the "exists" conditional is case insensitive, like the
> >> "name" and "group" conditionals, but unlike "match". This means if we
> >> test for deleted pages "Wikisandbox" and "WikiSandBox", but there is
> >> the
> >> correct page "WikiSandbox", it will return true:
> >>
> >>https://www.pmwiki.org/wiki/Test/CondExists2
> >>
> >> I wouldn't want to change the current state and risk breaking existing
> >> wikis relying on the case insensitivity, but in your situation this
> >> can
> >> be clearly wrong.
> >>
> >> I'll have to think about what to do. Possibly adding a new conditional
> >> for "case-sensitive exists" or a way to configure the current one to
> >> be
> >> case sensitive. Let's think about it.
> >>
> >> Petko
> >>
> >> --
> >> If you upgrade :  http://www.pmwiki.org/Upgrades
> >>
> >>
> >> On 22/10/2021 16:04, ABClf wrote:
> >> > I have a pagelist using a RecentChanges as trail source ;
> >> > page which have been deleted does appear in the RecentChanges trail (I
> >> > believe it's the normal behaviour) ; thus they also get listed in
> >> > pagelist result.
> >> > I don't know how to get rid of the deleted pages ; I believe I have
> >> > use the (:if exists:) param or set up a special list= parameter.
> >> > How would you do ?
> >> > Thank you,
> >> > Gilles.
> >

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelist with RecentChanges trail : how to get rid of deleted pages which are listed ?

[ABClf]

Thank you Petko ;
One, I believe I have used if="exists {=$FullName}" parameter with
defective syntax, and obviously failed in getting the expected result.

Two, since I want to collect recently changed pages among several
groups in one shot, using fmt for grouping the output, I use
trail=Site.AllRecentChanges group=Group1,Group2,Group3. Might not be
cost effective, yet it looks like it's working decently.

if="exists {=$FullName}" param can not be used in such a long pagelist
case ; with this parameter on, pagelist does too much for work, giving
:
23420: 09,42 (using if exists)
460: 00,52 (without if exists).

I will try with the next version.
Gilles.


In my case I don't mind about case.



Le dim. 24 oct. 2021 à 10:54, Petko Yotov <5...@5ko.fr> a écrit :
>
> The most efficient should be this:
>
>(:pagelist group=Main trail=Main.RecentChanges if="exists
> {=$FullName}":)
>
> group=Main is recommended if your pages are all from the same group.
>
> I just found out that the "exists" conditional can be optimized a lot,
> especially when called multiple times from a pagelist. This will be
> released in the next version in a few days.
>
> One other note, the "exists" conditional is case insensitive, like the
> "name" and "group" conditionals, but unlike "match". This means if we
> test for deleted pages "Wikisandbox" and "WikiSandBox", but there is the
> correct page "WikiSandbox", it will return true:
>
>https://www.pmwiki.org/wiki/Test/CondExists2
>
> I wouldn't want to change the current state and risk breaking existing
> wikis relying on the case insensitivity, but in your situation this can
> be clearly wrong.
>
> I'll have to think about what to do. Possibly adding a new conditional
> for "case-sensitive exists" or a way to configure the current one to be
> case sensitive. Let's think about it.
>
> Petko
>
> --
> If you upgrade :  http://www.pmwiki.org/Upgrades
>
>
> On 22/10/2021 16:04, ABClf wrote:
> > I have a pagelist using a RecentChanges as trail source ;
> > page which have been deleted does appear in the RecentChanges trail (I
> > believe it's the normal behaviour) ; thus they also get listed in
> > pagelist result.
> > I don't know how to get rid of the deleted pages ; I believe I have
> > use the (:if exists:) param or set up a special list= parameter.
> > How would you do ?
> > Thank you,
> > Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] pagelist with RecentChanges trail : how to get rid of deleted pages which are listed ?

[ABClf]

Hello,

I have a pagelist using a RecentChanges as trail source ;
page which have been deleted does appear in the RecentChanges trail (I
believe it's the normal behaviour) ; thus they also get listed in
pagelist result.
I don't know how to get rid of the deleted pages ; I believe I have
use the (:if exists:) param or set up a special list= parameter.
How would you do ?
Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Custom block link : short html code rather than strict text link

[ABClf]

Adopted. Thank you. PmWiki can do so many things in so many ways.

Le sam. 16 oct. 2021 à 22:53, Petko Yotov <5...@5ko.fr> a écrit :
>
> Also this:
>{{=$FullName}$:vedette}
>
> can be replaced with:
>{=$:vedette}
>
> Petko
>
> On 16/10/2021 22:46, ABClf wrote:
> > Well, thank you, you are right,
> > [[my link| %h5% Title %% Some text]]
> > is the way to go for me.
> > It does allow pretty verbose command and is good for clickable list
> > item
> >
> > [[#listemots1]]
> > %apply=link class="class"%[[{=$FullName}|%h5%{{=$FullName}$:vedette}%%
> >  %rfloat badge%{=$:attestation}%%\\
> > ''{=$:sens}'']]%%
> > [[#listemots1end]]
> >
> > Tested and adopted.
> >
> > Le sam. 16 oct. 2021 à 10:14, Petko Yotov <5...@5ko.fr> a écrit :
> >>
> >> This is not a WikiLink markup so it doesn't convert pagenames to URLs.
> >>
> >> In the href="..." attribute you need to use the "page URL", not the
> >> "page name":
> >>
> >>(:blocklink href="{=$PageUrl}" :)
> >>
> >>
> >> Note that the current markup allows for the link href to include
> >> JavaScript code, e.g.:
> >>
> >>(:blocklink href="javascript:alert(document.cookie)":)
> >>
> >> which may allow editors to insert malicious code. So if untrusted
> >> people
> >> can edit the wiki, you shouldn't enable this markup in its current
> >> definition.
> >>
> >> Petko
> >>
> >> On 16/10/2021 04:18, ABClf wrote:
> >> > Playing with last solution ; almost working for my needs, excepted the
> >> > blocklink output which gives me unexpected result :
> >> > my pagelist is on GroupA, printing out a list of blocklinks linking to
> >> > :
> >> > https://www.mysite.fr/GroupA/GroupB.Page1
> >> > where expected result is :
> >> > http://www.mysite.fr/GroupB.Page1
> >> >
> >> > In my own case, I test the blocklink markup in localtemplates,
> >> > defining a new format, like that (code shortened) :
> >> > [[#listesynonyme]]
> >> > (:blocklink href={=$FullName} class="list-group-item":)
> >> > {{=$FullName}$:vedette}
> >> > (:blocklinkend:)
> >> > [[#listesynonymeend]]
> >> >
> >> > then, in group Synonyme, I have a pagelist using quoted format ; which
> >> > gives me a list of blocks, linking as expected, but pointing to
> >> > https://www.mysite.fr/Synonyme/Bob.15887 where
> >> > https://www.mysite.fr/Bob.15887 is expected.
> >> >
> >> > To get rid of this Group issue, one working solution is to write :
> >> > (:blocklink href="https://www.mysite.fr/Bob/{=$Name};
> >> > class="list-group-item":)
> >> >
> >> > Not sure if I'm doing mistake, if the code works as expected or if it
> >> > needs to be a little improved in how to handle the Group part.
> >> >
> >> > Thank you,
> >> > Gilles.
> >> >
> >> > Le ven. 15 oct. 2021 à 23:45, ABClf  a écrit
> >> > :
> >> >>
> >> >> Thank you Petko for your top notch answer ;
> >> >> I'm going to try the last one soon.
> >> >> Gilles.
> >> >>
> >> >> Le ven. 15 oct. 2021 à 18:13, Petko Yotov <5...@5ko.fr> a écrit :
> >> >> >
> >> >> > Indeed, this is not possible with core PmWiki markup.
> >> >> >
> >> >> > In the past, the HTML standards required links to be inline elements
> >> >> > which could not contain block-level elements like paragraphs or
> >> >> > headings.
> >> >> >
> >> >> > So in PmWiki markup, you can have 2 links, one in the heading, the 
> >> >> > other
> >> >> > in the text like this:
> >> >> >
> >> >> > ! [[my link|Title]]
> >> >> > [[my link|Some text]]
> >> >> >
> >> >> >
> >> >> > Or you can have a specially formatted and styled link text like this:
> >> >> >
> >> >> > [[my link| %h5% Title %% Some text]]
> >> >> >
> >> >> > then you style .h5 in your pub/css/local.css, for example:
> >> >> >
> >> >> > .h5 {
> >> >> >

Re: [pmwiki-users] Custom block link : short html code rather than strict text link

[ABClf]

Well, thank you, you are right,
[[my link| %h5% Title %% Some text]]
is the way to go for me.
It does allow pretty verbose command and is good for clickable list item

[[#listemots1]]
%apply=link class="class"%[[{=$FullName}|%h5%{{=$FullName}$:vedette}%%
 %rfloat badge%{=$:attestation}%%\\
''{=$:sens}'']]%%
[[#listemots1end]]

Tested and adopted.

Le sam. 16 oct. 2021 à 10:14, Petko Yotov <5...@5ko.fr> a écrit :
>
> This is not a WikiLink markup so it doesn't convert pagenames to URLs.
>
> In the href="..." attribute you need to use the "page URL", not the
> "page name":
>
>(:blocklink href="{=$PageUrl}" :)
>
>
> Note that the current markup allows for the link href to include
> JavaScript code, e.g.:
>
>(:blocklink href="javascript:alert(document.cookie)":)
>
> which may allow editors to insert malicious code. So if untrusted people
> can edit the wiki, you shouldn't enable this markup in its current
> definition.
>
> Petko
>
> On 16/10/2021 04:18, ABClf wrote:
> > Playing with last solution ; almost working for my needs, excepted the
> > blocklink output which gives me unexpected result :
> > my pagelist is on GroupA, printing out a list of blocklinks linking to
> > :
> > https://www.mysite.fr/GroupA/GroupB.Page1
> > where expected result is :
> > http://www.mysite.fr/GroupB.Page1
> >
> > In my own case, I test the blocklink markup in localtemplates,
> > defining a new format, like that (code shortened) :
> > [[#listesynonyme]]
> > (:blocklink href={=$FullName} class="list-group-item":)
> > {{=$FullName}$:vedette}
> > (:blocklinkend:)
> > [[#listesynonymeend]]
> >
> > then, in group Synonyme, I have a pagelist using quoted format ; which
> > gives me a list of blocks, linking as expected, but pointing to
> > https://www.mysite.fr/Synonyme/Bob.15887 where
> > https://www.mysite.fr/Bob.15887 is expected.
> >
> > To get rid of this Group issue, one working solution is to write :
> > (:blocklink href="https://www.mysite.fr/Bob/{=$Name};
> > class="list-group-item":)
> >
> > Not sure if I'm doing mistake, if the code works as expected or if it
> > needs to be a little improved in how to handle the Group part.
> >
> > Thank you,
> > Gilles.
> >
> > Le ven. 15 oct. 2021 à 23:45, ABClf  a écrit
> > :
> >>
> >> Thank you Petko for your top notch answer ;
> >> I'm going to try the last one soon.
> >> Gilles.
> >>
> >> Le ven. 15 oct. 2021 à 18:13, Petko Yotov <5...@5ko.fr> a écrit :
> >> >
> >> > Indeed, this is not possible with core PmWiki markup.
> >> >
> >> > In the past, the HTML standards required links to be inline elements
> >> > which could not contain block-level elements like paragraphs or
> >> > headings.
> >> >
> >> > So in PmWiki markup, you can have 2 links, one in the heading, the other
> >> > in the text like this:
> >> >
> >> > ! [[my link|Title]]
> >> > [[my link|Some text]]
> >> >
> >> >
> >> > Or you can have a specially formatted and styled link text like this:
> >> >
> >> > [[my link| %h5% Title %% Some text]]
> >> >
> >> > then you style .h5 in your pub/css/local.css, for example:
> >> >
> >> > .h5 {
> >> >display: block;
> >> >font-weight: bold;
> >> >font-size: 105%;
> >> > }
> >> >
> >> > This will work well in  lists for menus and navigation. I'd go with
> >> > this solution id I needed the feature.
> >> >
> >> >
> >> > Finally, and as usual, you can define your own markup rule to do this.
> >> > For example:
> >> >
> >> >Markup('blocklink', 'directives',
> >> >  '/^\\(:blocklink(end|)(?: (.*?))?:\\)/',
> >> >  'FmtBlockLink');
> >> >function FmtBlockLink($m) {
> >> >  if($m[1]) return "<:block>";
> >> >  return "<:block>".Keep("");
> >> >}
> >> >
> >> > Then in a wiki page, you type:
> >> >
> >> > (:blocklink href="https://www.pmwiki.org; class=myclass:)
> >> > ! Title
> >> > Some text
> >> > (:blocklinkend:)
> >> >
> >> >
> >> > Petko
> >> >
> >> >
> >> > On 15/10/2021 14:09, ABClf wrote:
> >> > > Something I don't know how to do with pmwiki markup, if doable,
> >> > > is having an html output like that :
> >> > >
> >> > > 
> >> > >   Title
> >> > >   Some text
> >> > >   
> >> > >
> >> > > (in order to have the full block working as a link, for easy click in
> >> > > bootstrap-like list, and benefit of link's style).
> >> > >
> >> > > In other words, have some html code embedded in  and  (not the
> >> > > sole text link).
> >> > > I believe I can not use regular [[linkadress|linktext]] markup for
> >> > > doing that.
> >> > >
> >> > > Thank you,
> >> > > Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Custom block link : short html code rather than strict text link

[ABClf]

Playing with last solution ; almost working for my needs, excepted the
blocklink output which gives me unexpected result :
my pagelist is on GroupA, printing out a list of blocklinks linking to :
https://www.mysite.fr/GroupA/GroupB.Page1
where expected result is :
http://www.mysite.fr/GroupB.Page1

In my own case, I test the blocklink markup in localtemplates,
defining a new format, like that (code shortened) :
[[#listesynonyme]]
(:blocklink href={=$FullName} class="list-group-item":)
{{=$FullName}$:vedette}
(:blocklinkend:)
[[#listesynonymeend]]

then, in group Synonyme, I have a pagelist using quoted format ; which
gives me a list of blocks, linking as expected, but pointing to
https://www.mysite.fr/Synonyme/Bob.15887 where
https://www.mysite.fr/Bob.15887 is expected.

To get rid of this Group issue, one working solution is to write :
(:blocklink href="https://www.mysite.fr/Bob/{=$Name}; class="list-group-item":)

Not sure if I'm doing mistake, if the code works as expected or if it
needs to be a little improved in how to handle the Group part.

Thank you,
Gilles.

Le ven. 15 oct. 2021 à 23:45, ABClf  a écrit :
>
> Thank you Petko for your top notch answer ;
> I'm going to try the last one soon.
> Gilles.
>
> Le ven. 15 oct. 2021 à 18:13, Petko Yotov <5...@5ko.fr> a écrit :
> >
> > Indeed, this is not possible with core PmWiki markup.
> >
> > In the past, the HTML standards required links to be inline elements
> > which could not contain block-level elements like paragraphs or
> > headings.
> >
> > So in PmWiki markup, you can have 2 links, one in the heading, the other
> > in the text like this:
> >
> > ! [[my link|Title]]
> > [[my link|Some text]]
> >
> >
> > Or you can have a specially formatted and styled link text like this:
> >
> > [[my link| %h5% Title %% Some text]]
> >
> > then you style .h5 in your pub/css/local.css, for example:
> >
> > .h5 {
> >display: block;
> >font-weight: bold;
> >font-size: 105%;
> > }
> >
> > This will work well in  lists for menus and navigation. I'd go with
> > this solution id I needed the feature.
> >
> >
> > Finally, and as usual, you can define your own markup rule to do this.
> > For example:
> >
> >Markup('blocklink', 'directives',
> >  '/^\\(:blocklink(end|)(?: (.*?))?:\\)/',
> >  'FmtBlockLink');
> >function FmtBlockLink($m) {
> >  if($m[1]) return "<:block>";
> >  return "<:block>".Keep("");
> >}
> >
> > Then in a wiki page, you type:
> >
> > (:blocklink href="https://www.pmwiki.org; class=myclass:)
> > ! Title
> > Some text
> > (:blocklinkend:)
> >
> >
> > Petko
> >
> >
> > On 15/10/2021 14:09, ABClf wrote:
> > > Something I don't know how to do with pmwiki markup, if doable,
> > > is having an html output like that :
> > >
> > > 
> > >   Title
> > >   Some text
> > >   
> > >
> > > (in order to have the full block working as a link, for easy click in
> > > bootstrap-like list, and benefit of link's style).
> > >
> > > In other words, have some html code embedded in  and  (not the
> > > sole text link).
> > > I believe I can not use regular [[linkadress|linktext]] markup for
> > > doing that.
> > >
> > > Thank you,
> > > Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Custom block link : short html code rather than strict text link

[ABClf]

Thank you Petko for your top notch answer ;
I'm going to try the last one soon.
Gilles.

Le ven. 15 oct. 2021 à 18:13, Petko Yotov <5...@5ko.fr> a écrit :
>
> Indeed, this is not possible with core PmWiki markup.
>
> In the past, the HTML standards required links to be inline elements
> which could not contain block-level elements like paragraphs or
> headings.
>
> So in PmWiki markup, you can have 2 links, one in the heading, the other
> in the text like this:
>
> ! [[my link|Title]]
> [[my link|Some text]]
>
>
> Or you can have a specially formatted and styled link text like this:
>
> [[my link| %h5% Title %% Some text]]
>
> then you style .h5 in your pub/css/local.css, for example:
>
> .h5 {
>display: block;
>font-weight: bold;
>font-size: 105%;
> }
>
> This will work well in  lists for menus and navigation. I'd go with
> this solution id I needed the feature.
>
>
> Finally, and as usual, you can define your own markup rule to do this.
> For example:
>
>Markup('blocklink', 'directives',
>  '/^\\(:blocklink(end|)(?: (.*?))?:\\)/',
>  'FmtBlockLink');
>function FmtBlockLink($m) {
>  if($m[1]) return "<:block>";
>  return "<:block>".Keep("");
>}
>
> Then in a wiki page, you type:
>
> (:blocklink href="https://www.pmwiki.org; class=myclass:)
> ! Title
> Some text
> (:blocklinkend:)
>
>
> Petko
>
>
> On 15/10/2021 14:09, ABClf wrote:
> > Something I don't know how to do with pmwiki markup, if doable,
> > is having an html output like that :
> >
> > 
> >   Title
> >   Some text
> >   
> >
> > (in order to have the full block working as a link, for easy click in
> > bootstrap-like list, and benefit of link's style).
> >
> > In other words, have some html code embedded in  and  (not the
> > sole text link).
> > I believe I can not use regular [[linkadress|linktext]] markup for
> > doing that.
> >
> > Thank you,
> > Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Custom block link : short html code rather than strict text link

[ABClf]

Hello,

Something I don't know how to do with pmwiki markup, if doable,
is having an html output like that :


  Title
  Some text
  

(in order to have the full block working as a link, for easy click in
bootstrap-like list, and benefit of link's style).

In other words, have some html code embedded in  and  (not the
sole text link).
I believe I can not use regular [[linkadress|linktext]] markup for doing that.

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Syntax use of %style=margin-left:50px%{=$:Version}

[ABClf]

Well, thank you Petko for your explanation. It helps.

Le ven. 10 sept. 2021 à 18:37, Petko Yotov <5...@5ko.fr> a écrit :
>
> About:
>
>%style="margin-left:50px%
>
> This is not a valid wikistyle, you probably need:
>
>%margin-left=50px% text %% or
>
>%bloc margin-left=50px%
>
>
> About:
>
>%style="margin-left:50px%"
>
> When you use quotes (not in this invalid case, but in others), the
> closing quote needs to be before the closing % for example:
>
>%p padding="2em 5em" border="4px dotted red"% text
>
> Indeed these are somewhat complex to set and to maintain. Myself I would
> make a CSS class in pmwiki/pub/css/local.css and use the classname in
> the wikistyle instead of the actual code.
>
> For example, in local.css:
>
>.myclassname { margin-left:50px; }
>
> On the wiki:
>
>%myclassname% text %% or
>%p myclassname% text or
>%bloc myclassname% text
>
> Petko
>
> On 10/09/2021 18:20, ABClf wrote:
> > Hello,
> >
> > I'm still playing with style and css and have a question about what
> > looks to me like unexpected behaviour related to the use and syntax
> > needed for inline styling :
> >
> > while formatting pagelist, writing,
> > %style="margin-left:50px%{=$:Version}
> > does clean left marging ;
> >
> > whereas writing,
> > %style="margin-left:50px%"{=$:Version}
> > or
> > %style=margin-left:50px%{=$:Version}
> > does print out an unexpected " (quote sign).
> >
> > To me it looks like the parsing might not be working as it should.
> > Am I wrong somewhere ?
> >
> > Test page done here :
> > https://www.pmwiki.org/wiki/Test/InlineStyle
> >
> > Thank you.
> > Gilles.
> >
> > ___
> > pmwiki-users mailing list
> > pmwiki-users@pmichaud.com
> > http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Syntax use of %style=margin-left:50px%{=$:Version}

[ABClf]

Hello,

I'm still playing with style and css and have a question about what
looks to me like unexpected behaviour related to the use and syntax
needed for inline styling :

while formatting pagelist, writing,
%style="margin-left:50px%{=$:Version}
does clean left marging ;

whereas writing,
%style="margin-left:50px%"{=$:Version}
or
%style=margin-left:50px%{=$:Version}
does print out an unexpected " (quote sign).

To me it looks like the parsing might not be working as it should.
Am I wrong somewhere ?

Test page done here :
https://www.pmwiki.org/wiki/Test/InlineStyle

Thank you.
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Markup for button ?

[ABClf]

Thank you Petko.
Will play and see.

Le jeu. 2 sept. 2021 à 15:56, Petko Yotov <5...@5ko.fr> a écrit :
>
> Recent PmWiki versions have "input button" similar to "input submit":
>
>(:input button value="Red button" id=button_id class="btn btn-red":)
>
> This is translated to  however, not to
>  and unlike it the label or value can only be plain text.
>
> If you must have a  element instead, you should make a custom
> markup.
>
> Petko
>
> --
> If you upgrade :  http://www.pmwiki.org/Upgrades
>
>
> On 01/09/2021 18:35, ABClf wrote:
> > I'm playing with css now and I'm just discover I don't know how to
> > create a button in pmwiki markup ;
> > my purpose is to be able to create something rendering in html as :
> > Red button

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Markup for button ?

[ABClf]

Hello,

I'm playing with css now and I'm just discover I don't know how to
create a button in pmwiki markup ;
my purpose is to be able to create something rendering in html as :
Red button

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Have pagelist condition : if result not null, then print pagelist

[ABClf]

Hello,

Well, well, one, sorry for the delay (I have a growing kid at home
leeching my free time...).
Two, sorry for the unclear question ; I was wrong : in case of
(:template first:) (:template each:) pagelist format (yes, for
inserting a heading before results are shown), pmwiki doesn't print
out template first when 0 result is found, which is the behaviour I
was expecting you to help me to get.
Three, thank you for your helping answers : no matter the question
asked was not silly, your indulgent answers lightened the right
direction (what you need is what pmwiki does by default).

Four, thank you for your help !


Le mer. 14 avr. 2021 à 11:33, Petko Yotov <5...@5ko.fr> a écrit :
>
> Pagelist usually shows nothing if there are no pages in the list.
>
> Unless you have a (:template none:) section -- it only appears when
> there are no pages.
>
> If you want to show something, like a heading, before the first result
> (when there is a first result), then use (:template first:). That
> section can be there in addition to (:template first {=$Group}:)
>
> I suspect I don't understand what is the exact problem, if so, please
> elaborate.
>
> Petko
>
> On 13/04/2021 05:21, ABClf wrote:
> > I don't know if it's possible to have a pagelist condition like : if
> > $MatchCount < 1 ;
> > in my case, I would like a pagelist to be printed only when there is
> > some positive result found.
> > If request gives nothing, then print nothing.
> >
> > Specifically, I use pagelist like this to collect linked citations :
> > (:pagelist group=Citation link=Bob.{*$Name} list=all fmt=#citation2:)
> > and I would like to have result printed out only when results are
> > found.
> > Is that doable ?

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Have pagelist condition : if result not null, then print pagelist

[ABClf]

Hello,

I don't know if it's possible to have a pagelist condition like : if
$MatchCount < 1 ;
in my case, I would like a pagelist to be printed only when there is
some positive result found.
If request gives nothing, then print nothing.

Specifically, I use pagelist like this to collect linked citations :
(:pagelist group=Citation link=Bob.{*$Name} list=all fmt=#citation2:)
and I would like to have result printed out only when results are found.
Is that doable ?

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] How to unprotect specific -Talk page in groupA and groupB

[ABClf]

Hello Simon,

well, in my project, no, regular doc password pages only say how to
protect full site, or group, or individual page, but I can not find
the conditional syntax for unprotecting a set of pages according to
its name.

Could be something like locking everything first, then unlocking
special pattern name ones ; maybe :

$DefaultPasswords['edit'] = pmcrypt('mypassword');
if (preg_match('/-Talk$/', $pagename)) $DefaultPasswords['edit'] = '';



Le lun. 16 nov. 2020 à 10:26, Simon  a écrit :
>
> From https://www.pmwiki.org/wiki/PmWiki/Security
> try https://www.pmwiki.org/wiki/PmWiki/Passwords
>
> hope this helps
>
> On Mon, 16 Nov 2020 at 10:20, ABClf  wrote:
> >
> > Hello,
> >
> > I would like to give visitors the right to read/edit *-Talk pages in a
> > bunch of Groups.
> > I didn't find how to get it in the doc.
> >
> > as of now, my config has a site wide basic edit protection :
> > $DefaultPasswords['edit'] = pmcrypt('mypassword');
> >
> > Thank you.
> >
> > ___
> > pmwiki-users mailing list
> > pmwiki-users@pmichaud.com
> > http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] How to unprotect specific -Talk page in groupA and groupB

[ABClf]

Hello,

I would like to give visitors the right to read/edit *-Talk pages in a
bunch of Groups.
I didn't find how to get it in the doc.

as of now, my config has a site wide basic edit protection :
$DefaultPasswords['edit'] = pmcrypt('mypassword');

Thank you.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Session (or authid?) and fastcache recipe issue

[ABClf]

I just have installed a new PmWiki test site somewhere on my website ;
then have installed and set up fastcache recipe + PmWiki very minimal
config (testing with and without "session" line).
As of now it looks like it's working as expected ; which means I have to
investigate my own mess.

I still have a question Petko :
what is the session line – session_name('XXXSESSID'); – in config ? This
line is not in sample-config and I don't know what is the benefit of it.
According to PmWiki/AuthUser#sessions it's mainly dedicated for users
running a PmWiki Farm. Does that mean it is useless for single (or
distinct) site installation ?

Thank you !!


Le sam. 17 oct. 2020 à 19:27, Petko Yotov <5...@5ko.fr> a écrit :
>
> I made a small correction to the $FastCacheValid variable: since PHP 5.3
> cookies are not in the $_REQUEST array by default.
>
> I don't have this installed and have no way to test it, please report --
> you'll need to edit a page and save it to clear existing cache.
>
> Someone who uses this recipe should take over the maintenance -- the
> original author Eemeli Aro no longer uses PmWiki, and has released all
> his addons as free/libre software allowing modification and
> redistribution.
>
> For example, PmWiki may issue a session cookie even to people who don't
> have any permissions and are logged out. In this case, apparently the
> cache will be invalidated, that is, not saved. Someone who needs this
> recipe and uses it should take a look at the logic.
>
> FYI, on your website there is no session cookie when the visitor is
> logged out, so you should be mostly safe.
>
> Petko
>
> On 17/10/2020 16:41, ABClf wrote:
> > Hello hello,
> >
> > It looks like I'm having a test page where condition
> > (:if auth admin:)test(:if:)
> >  is written (i'm logged as admin of course) ; then saved using
> > fastcache recipe on page1 (same code saved on page2 with fastcache
> > recipe disabled).
> >
> > With fastcache :
> > 1/ Logging out with action=logout
> > 2/ If browsing the page with ?action browse, "test" is not printed (as
> > expected)
> > 3/ If browsing with no action, "test" is printed (unexpected).
> > (I believe case 2 is because of the action query string ?, which
> > tells fastcache not to run).
> >
> > Without fastcache :
> > 1/ Logging out with action=logout
> > 2/ If browsing the page with ?action browse, "test" is not printed (as
> > expected)
> > 3/ If browsing with no action, test is not printed (expected).
> >
> > I have read doc, talk and pits and it looks like there might be an
> > issue with session, when using fastcache.
> > My config has only one line related to session, at the very top of my
> > config (just below  > session_name('ABCLFSESSID');
> >
> > Does anyone have any idea for getting things to work as expected ? I'm
> > a bit annoyed as I strongly rely on fastcache for speeding page
> > processing time and I would like to be able to use conditional (i.e.
> > ask fastcache to save the reader view page, rather than my admin view
> > page).
> >
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Session (or authid?) and fastcache recipe issue

[ABClf]

Hello hello,

It looks like I'm having a test page where condition
(:if auth admin:)test(:if:)
 is written (i'm logged as admin of course) ; then saved using
fastcache recipe on page1 (same code saved on page2 with fastcache
recipe disabled).

With fastcache :
1/ Logging out with action=logout
2/ If browsing the page with ?action browse, "test" is not printed (as expected)
3/ If browsing with no action, "test" is printed (unexpected).
(I believe case 2 is because of the action query string ?, which
tells fastcache not to run).

Without fastcache :
1/ Logging out with action=logout
2/ If browsing the page with ?action browse, "test" is not printed (as expected)
3/ If browsing with no action, test is not printed (expected).

I have read doc, talk and pits and it looks like there might be an
issue with session, when using fastcache.
My config has only one line related to session, at the very top of my
config (just below http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] get rid of special characters in page names creation (when Tagger recipe is used)

[ABClf]

Well, well, well, sorry Petko and PmWiki list readers, I believe I'm
wrong with my issue.
I just checked and rechecked and, hum hum..., frankly, it looks like
all is working as expected.
(One explanation for my mistake is I recently made changes to my
config, related to accentued characters, then I forgot to delete
already created pages).
Thank you for your answer (not useless as it helps me to find the
usual suspect : myself ;).


Le lun. 5 oct. 2020 à 16:38, Petko Yotov <5...@5ko.fr> a écrit :
>
> When you type in a page [[Index.Pépé123]] (not Index:pépé), does it
> create the page Index.Pepe123 or Index.Pépé123 ?
>
> If Index.Pepe123 is created and linked, the problem comes indeed from
> the Tagger recipe.
>
> If it creates Index.Pépé123, there is a problem either with PmWiki, or
> with your configuration.
>
> If you type a link [[A group not in tagger/Pépé123]], what page is
> linked, AGroupNotInTagger.Pepe123 or AGroupNotInTagger.Pépé123?
>
> In the first case all is good, in the second you have a problem with
> your configuration-- probably incorrect encoding of the config.php file.
> As the wiki has utf-8 enabled, then the config.php needs to be in the
> same encoding, see
>
>https://www.pmwiki.org/wiki/PmWiki/LocalCustomizations#encoding
>
> Petko
>
> On 03/10/2020 21:02, ABClf wrote:
> > I want internal links get rid of special characters, replacing for
> > example : é with e, ç with c, in such a way [[Pépé]] will link to page
> > named Pepe, and [[Garçon]] will link to page named Garcon.
> >
> > I have some lines (1) in my config devoted to that purpose and it
> > looks like it's working.
> >
> > But I have an issue with Tagger cookbook recipe (used together with
> > autocreate category).
> > Among other things, Tagger has these lines :
> >
> > $TaggerGroups['index'] = 'Index';
> > $AutoCreate['/^Index\\./'] = array('ctime' => $Now);
> >
> > Now, when writing something like
> > Index: myword
> > I automatically get a new page named "Myword" created.
> > If writing something like :
> > Index:pépé
> > then I get a page named Index.Pépé, where I am expecting a special
> > character free name (I want : Index.Pepe).
> >
> > Is there something I could do to ask Tagger to create links, using
> > special patterns for naming pages ?
> >
> > Thank you !
> > Gilles.
> >
> > (1) My config has these lines
> >
> > # UTF-8 & francisation
> > # The include_once line is recommended if you start a new wiki
> > # and it should be placed before the XLPage line (for languages with
> > alphabets other than the Latin, the include_once line is required).
> > # -- IMPORTANT -- These lines should be placed near the beginning of
> > config.php, but after any $WikiDir and $WikiLibDirs setting (if you
> > have such setting).
> > include_once("scripts/xlpage-utf-8.php");
> > #$DefaultPageCharset = array(''=>'ISO-8859-1'); # problématique
> > XLPage('fr','PmWikiFr.XLPage');
> > XLPage('fr','PmWikiFr.XLPageCookbook'); // S'il y a des modules
> >  
> >  
> >  
> > # standard patterns from pmwiki.php
> > SDV($PageNameChars, '-[:alnum:]');
> > SDV($MakePageNamePatterns, array(
> > "/'/" => '',# strip single-quotes
> > "/[^$PageNameChars]+/" => ' ', # convert everything else to
> > space
> > '/((^|[^-\\w])\\w)/' => 'cb_toupper',  # capitalize first letter of
> > word
> > '/ /' => '')); #function
> > # additonal character conversion patterns for ISO 8859-1 character set
> > SDV($ISO88591MakePageNamePatterns, array(
> > '/Á/' => 'A', '/Â/' => 'A', '/Ã/' => 'A', '/Ä/' => 'Ae', '/Å/' =>
> > 'Ao', '/Æ/' => 'Ae', '/Ç/' => 'C',
> > '/È/' => 'E', '/É/' => 'E', '/Ê/' => 'E', '/Ë/' => 'E', '/Ì/' => 'I',
> > '/Í/' => 'I', '/Î/' => 'I', '/Ï/' => 'I',
> > '/Ð/' => 'D', '/Ñ/' => 'N', '/Ú/' => 'U', '/Ó/' => 'O', '/Ô/' => 'O',
> > '/Õ/' => 'O', '/Ö/' => 'Oe', '/Ø/' => 'Oe',
> > '/Ù/' => 'U', '/Ú/' => 'U', '/Û/' => 'U', '/Ü/' => 'Ue', '/Ý/' => 'Y',
> > '/Þ/' => 'Th', '/ß/' => 'ss',
> > '/à/' => 'a', '/á/' => 'a', '/â/' => 'a', '/ã/' => 'a', '/ä/' => 'ae',
> > '/å/' => 'ao', '/æ/' => 'ae', '/ç/' => 'c',
> > '/è/' => 'e', '/é/' => 'e', '/ê/' => 'e', '/ë/' => 'e', '/ì/' => 'i',
> > '/í/' => 'i', '/î/' => 'i', '/ï/' => 'i',
> > '/ð/' => 'd', '/ñ/' => 'n', '/ò/' => 'o', '/ó/' => 'o', '/ô/' => 'o',
> > '/õ/' => 'o', '/ö/' => 'oe', '/ø/' => 'oe',
> > '/ù/' => 'u', '/ú/' => 'u', '/û/' => 'u', '/ü/' => 'ue', '/ý/' => 'y',
> > '/þ/' => 'th', '/ÿ/' => 'y'
> > ));
> > # join to standard patterns
> > $MakePageNamePatterns = array_merge($ISO88591MakePageNamePatterns,
> > $MakePageNamePatterns);

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] get rid of special characters in page names creation (when Tagger recipe is used)

[ABClf]

Hello,

I want internal links get rid of special characters, replacing for
example : é with e, ç with c, in such a way [[Pépé]] will link to page
named Pepe, and [[Garçon]] will link to page named Garcon.

I have some lines (1) in my config devoted to that purpose and it
looks like it's working.

But I have an issue with Tagger cookbook recipe (used together with
autocreate category).
Among other things, Tagger has these lines :

$TaggerGroups['index'] = 'Index';
$AutoCreate['/^Index\\./'] = array('ctime' => $Now);

Now, when writing something like
Index: myword
I automatically get a new page named "Myword" created.
If writing something like :
Index:pépé
then I get a page named Index.Pépé, where I am expecting a special
character free name (I want : Index.Pepe).

Is there something I could do to ask Tagger to create links, using
special patterns for naming pages ?

Thank you !
Gilles.

(1) My config has these lines

# UTF-8 & francisation
# The include_once line is recommended if you start a new wiki
# and it should be placed before the XLPage line (for languages with
alphabets other than the Latin, the include_once line is required).
# -- IMPORTANT -- These lines should be placed near the beginning of
config.php, but after any $WikiDir and $WikiLibDirs setting (if you
have such setting).
include_once("scripts/xlpage-utf-8.php");
#$DefaultPageCharset = array(''=>'ISO-8859-1'); # problématique
XLPage('fr','PmWikiFr.XLPage');
XLPage('fr','PmWikiFr.XLPageCookbook'); // S'il y a des modules
 
 
 
# standard patterns from pmwiki.php
SDV($PageNameChars, '-[:alnum:]');
SDV($MakePageNamePatterns, array(
"/'/" => '',# strip single-quotes
"/[^$PageNameChars]+/" => ' ', # convert everything else to space
'/((^|[^-\\w])\\w)/' => 'cb_toupper',  # capitalize first letter of word
'/ /' => '')); #function
# additonal character conversion patterns for ISO 8859-1 character set
SDV($ISO88591MakePageNamePatterns, array(
'/Á/' => 'A', '/Â/' => 'A', '/Ã/' => 'A', '/Ä/' => 'Ae', '/Å/' =>
'Ao', '/Æ/' => 'Ae', '/Ç/' => 'C',
'/È/' => 'E', '/É/' => 'E', '/Ê/' => 'E', '/Ë/' => 'E', '/Ì/' => 'I',
'/Í/' => 'I', '/Î/' => 'I', '/Ï/' => 'I',
'/Ð/' => 'D', '/Ñ/' => 'N', '/Ú/' => 'U', '/Ó/' => 'O', '/Ô/' => 'O',
'/Õ/' => 'O', '/Ö/' => 'Oe', '/Ø/' => 'Oe',
'/Ù/' => 'U', '/Ú/' => 'U', '/Û/' => 'U', '/Ü/' => 'Ue', '/Ý/' => 'Y',
'/Þ/' => 'Th', '/ß/' => 'ss',
'/à/' => 'a', '/á/' => 'a', '/â/' => 'a', '/ã/' => 'a', '/ä/' => 'ae',
'/å/' => 'ao', '/æ/' => 'ae', '/ç/' => 'c',
'/è/' => 'e', '/é/' => 'e', '/ê/' => 'e', '/ë/' => 'e', '/ì/' => 'i',
'/í/' => 'i', '/î/' => 'i', '/ï/' => 'i',
'/ð/' => 'd', '/ñ/' => 'n', '/ò/' => 'o', '/ó/' => 'o', '/ô/' => 'o',
'/õ/' => 'o', '/ö/' => 'oe', '/ø/' => 'oe',
'/ù/' => 'u', '/ú/' => 'u', '/û/' => 'u', '/ü/' => 'ue', '/ý/' => 'y',
'/þ/' => 'th', '/ÿ/' => 'y'
));
# join to standard patterns
$MakePageNamePatterns = array_merge($ISO88591MakePageNamePatterns,
$MakePageNamePatterns);

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Function not compatible anymore with php72

[ABClf]

Hello hello,

My config used to have this code (added for sorting search result in
alphabetical order, including french diacritic : a b c d eéè f ...) :

/*
# Sorting pages using locale (sort 'é', 'è', 'ê', etc. with 'e' for example)
$PageListSortCmp['namelocalesort'] = 'LocaleSort($x, $y)'; */
$PageListSortCmp['title'] = 'LocaleSort($PCache[$x][\'=title\'],
$PCache[$y][\'=title\'])';
function LocaleSort($a, $b) {
  $x = array($a, $b);
  setlocale(LC_ALL, 'fr_FR.utf8'); ## or 'fr_FR.utf8'
  sort($x, SORT_LOCALE_STRING);
  return ($x[0]==$a)? -1:1;
}

I believe this doesn't work anymore (with recent php) : when used in
config, I encounter this error :

Deprecated: Function create_function() is deprecated in
/home/www/dev6/scripts/pagelist.phpon line 520

Warning: Cannot modify header information - headers already sent by
(output started at /home/www/dev6/scripts/pagelist.php:520) in
/home/www/dev6/pmwiki.php on line 1337

I need help for updating that piece of code ; if possible I would like
to have the requested behaviour (alphabetical order including
diacritic) by default (no need to add param to search box).

Thank you.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Sorting function (natural order) not working anymore (php72)

[ABClf]

Hello hello,

Still working on updating my config for php72.
I used to have a code implemented in config to sort numerical PV
(named RevCount) in natural ordre. I use it to list most/less edited
pages (and want to have 9 revisions come before 10 revisions). It does
not work anymore if I'm not mistaken.

Here it is the original code (from Petko) :

# sorting with revcount param (natural order 12>2)
function IntegerNameCompare($x, $y) {
  # get integer value of the page name or title
  $xval = intval(PageVar($x, '$RevCount'));
  $yval = intval(PageVar($y, '$RevCount'));
  # compare integer values
  if($xval > $yval) $c = 1;
  elseif($xval < $yval) $c = -1;
  else $c = 0;
  return $c;
}
$PageListSortCmp['revcount'] = 'IntegerNameCompare($x, $y)';

I'm begging for help ;)
Thanks a lot.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Trouble with fastcache recipe

[ABClf]

Thank you Petko,

Indeed, for some reason I have not used the updated version of the recipe ;
As of now, it looks lite your revised version is working fine. Thank
you for your support.

Gilles.

Le sam. 25 janv. 2020 à 07:51, Petko Yotov <5...@5ko.fr> a écrit :
>
> The recipe was last updated 11 years and 3 days ago, in the mean time
> PHP changed a few things.
>
> I've uploaded a new version that should work with recent PHP versions --
> please review the cookbook page, test the new version and report any
> difficulties.
>
> Petko
>
>
> > I believe there is something wrong with fastcache recipe and php7.4 ;
> > if included, I get these error messages :
> >
> > --
> > Warning: Cannot modify header information - headers already sent by
> > (output started at /home/www/dev6/pmwiki.php:1866) in
> > /home/www/dev6/pmwiki.php on line 1337
> >
> > Warning: preg_replace(): The /e modifier is no longer supported, use
> > preg_replace_callback instead in /home/www/dev6/pmwiki.php on line
> > 1866
> >
> > Could this recipe be checked and upgraded ? That's a recipe I use
> > extensively

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] What is the best php version to use now ?

[ABClf]

Thank you for your replies,

in my case, it looks like I will go with php7.2 : I have still a few
issues to fix yet, of course ;
php7.4 breaks my forum due to magic quotes thing.

Warm thanks to those who update core and recipes.

Le dim. 26 janv. 2020 à 01:56, David Cooke  a écrit :
>
> Hi folks,
>
> We have had a number of people now mentioning problems they have due to PHP 
> 7.2. (Sorry I was one of them). It looks like a number of the hosts are 
> finally upgrading.
>
> I think, to help people like Petko see the size of the problem and exactly 
> where it is, we should try and produce an accurate list of recipes that we 
> are having problems with.
>
> Don't expect an immediate response, the problem isn't small and the guy has a 
> proper job to do as well. Although he is pretty good.
>
> Perhaps having a look ourselves at the recipes and looking to see where they 
> break might help if you have any experience with PHP. It could could 
> potentially reduce the pressure and give you more coding experience.
>
> Best of luck, all.
>
> Regards
>
> Dave Cooke
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Trouble with fastcache recipe

[ABClf]

Hello,

I believe there is something wrong with fastcache recipe and php7.4 ;
if included, I get these error messages :

--
Warning: Cannot modify header information - headers already sent by
(output started at /home/www/dev6/pmwiki.php:1866) in
/home/www/dev6/pmwiki.php on line 1337

Warning: preg_replace(): The /e modifier is no longer supported, use
preg_replace_callback instead in /home/www/dev6/pmwiki.php on line
1866
--

Could this recipe be checked and upgraded ? That's a recipe I use extensively ;)
Thank you for your help.
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] What is the best php version to use now ?

[ABClf]

Hello pmwiki users,

My host has upgraded everything and I'm now struggling to get my
website working as it did (I'm not happy).
First, please, what is the recommended php version to use with pmwiki
? I have a lot of work to do, and I would like to use the best option
while debugging all what I can ;)

Thank you !

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New features to be enabled in the PmWiki core

[ABClf]

To me, enhancements planned are a good and subtil choice (no bloating).
In my own case, the must have recipe I use (can't make pmwiki work
good without it) is : fastcache.
It makes reading fast for not logged in visitors and processor running
quietly (but you have to erase the cached files when needed).

Thank you.



Le mer. 4 sept. 2019 à 13:33, Petko Yotov <5...@5ko.fr> a écrit :
>
> I've added a basic "sortable tables" function, see:
>
>https://pmwiki.org/Tables#sortable
>
> By "basic" I mean numeric and alphabetic sorting only, but it is
> extensible for other comparisons like dates.
>
> You can get the latest development code from the ChangeLog or the
> Subversion pages, or you can test this anywhere on the wiki.
>
> Like discussed, this will be disabled by default until the administrator
> enables it with $EnableSortable = 1;
>
> Petko
>
> --
> If you upgrade :  http://www.pmwiki.org/Upgrades
>
>
> On 29/08/2019 21:59, Petko Yotov wrote:
> > Hello,
> >
> > This is to let you know that I've added to the PmWiki core in
> > Subversion a number of features from my own recipes/addons that are
> > somewhat popular and that I see myself installing on every new wiki I
> > create.
> >
> > Because many of you already use these or similar addons, the newly
> > added features will be disabled but it will be very easy to enable
> > them from config.php.
> >
> > Here is the list:
> >
> > Editing a wiki:
> > * PreviewChanges - this has been enabled on PmWiki.org for years,
> > shows a highlighted diff in Preview mode (already added in 2.2.118).
> > * NotSavedWarning - signal to editors when they are moving away from
> > the edit form and risk losing their changes (the Author/Summary
> > prompts from the recipe are not included in the core, because now it
> > is easy to add "required" attributes to the edit form fields).
> > * A sub-feature from NotSavedWarning scrolling to the same position
> > when pressing either Preview or Save (enabled by default).
> > * EditHelp - predictive insertion of markup like list bullets (I use
> > this a lot, especially on a mobile device).
> >
> > Reading a wiki:
> > * DeObMail - obfuscating e-mail links for spam bots.
> > * PmTOC - a really basic "table of contents +/- numbered headers",
> > currently a simpler subset of the AutoTOC recipe will be included in
> > the core, see:
> >   https://www.pmwiki.org/wiki/PmWiki/TableOfContents
> >
> > Again, these will be disabled in the default installation, but could
> > be enabled as easily as adding $EnableNotSavedWarning = 1; if you
> > decide to use any of them.
> >
> >
> > Other features planned for inclusion:
> > * PmEmbed, a subset of the Ape recipe (minus the OpenStreetMap part
> > which is too complex to include in the core at this point). The main
> > embedding function is light and simple and can be easily extended. As
> > more people need to include videos or other media from external
> > platforms, this recipe can do the job in a simple way.
> >
> >
> > Other recipes (actually their feature set) under consideration:
> >
> > * DragDropMultiUpload - upload files by dropping them into the edit
> > form.
> > * LocalTimes - RecentChanges enhancements.
> > * LocalCSS - CSS in a wiki page.
> > * A small subset of the features of Attachtable - I use a very old
> > fork with just rename/delete/restore.
> > * PageListMultiTargets - this allows a pagelist "link=" argument to
> > accept more than one link. We should decide if "link=Page1,Page2"
> > should include pages that link to *any* of the pages or to *both*
> > pages. Currently it includes any of the pages, and you need to use
> > "link=+Page1,+Page2" to require both pages.
> >
> > * Add a set of CSS rules for editors to be able to more easily create
> > nicer-looking tables -- to the default skins -- obviously other skins
> > can redefine the styles of the same classname(s), like they currently
> > do for the "frame" class.
> >
> > You can follow the progress of this project at:
> >
> >   https://www.pmwiki.org/wiki/PmWiki/ChangeLog
> >   https://www.pmwiki.org/wiki/Site/AllRecentChangesShort
> >
> > Tell me what you think. What recipes/addons do you install on your
> > wikis (especially if you have installed multiple wikis)?
> >
> > I am interested in features you and your editors actually use, not
> > "might be nice", and that do help editors create better content with
> > less effort.
> >
> > See how the above recipes once configured are mostly automatic, and
> > don't add new markups that people are required to learn. And they
> > considerably enhance the editing experience or the webmaster's work.
> >
> > Please comment.
> >
> > Petko
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki 2.2.118 released

[ABClf]

Thank you Petko.

Le mer. 28 août 2019 à 18:36, Petko Yotov <5...@5ko.fr> a écrit :
>
> Hello. PmWiki version 2.2.118 was published today, and is available at:
>
>http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.118.tgz
>http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.118.zip
> svn://www.pmwiki.org/pmwiki/tags/latest
>
> This version integrates the features of the recipe
> Cookbook:PreviewChanges into the core. If you currently use this
> recipe, please uninstall it and add to config.php:
>$EnablePreviewChanges = 1;
>
> The documentation was updated.
>
> Thanks,
> Petko
> --
> If you upgrade :  http://www.pmwiki.org/Upgrades
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Better way to want pagelist limited to numercial values than : ame=[0-9], [0-9][0-9], [0-9][0-9][0-9], [0-9][0-9][0-9][0-9]

[ABClf]

Well, that's something I couldn't imagine at all ; thank you Petko.

Le lun. 26 août 2019 à 07:37, Petko Yotov <5...@5ko.fr> a écrit :
>
> You can create a page variable $NumericName in config.php:
>
>$FmtPV['$NumericName'] = 'is_numeric($name)?"true":"false"';
>
> Then in the pagelist:
>(:pagelist $NumericName=true trail=Group.RecentChanges:)
>
> Petko
> --
> If you upgrade :  http://www.pmwiki.org/Upgrades
>
>
> On 26/08/2019 01:54, ABClf wrote:
> > I need a pagelist limited to pages named with serial/numerical name
> > (1, 123, 166358, etc.)
> > As of now, my pagelist is like that :
> >
> > (:pagelist trail=Group.RecentChanges
> > name=[0-9],[0-9][0-9],[0-9][0-9][0-9],[0-9][0-9][0-9][0-9] count=100:)
> >
> > Does someone know a better way to write the name argument ? Something
> > in the spirit of this perhaps (this one doesn't work) : [numeric] ?

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Better way to want pagelist limited to numercial values than : ame=[0-9], [0-9][0-9], [0-9][0-9][0-9], [0-9][0-9][0-9][0-9]

[ABClf]

Hello PmWiki users,

I need a pagelist limited to pages named with serial/numerical name
(1, 123, 166358, etc.)
As of now, my pagelist is like that :

(:pagelist trail=Group.RecentChanges
name=[0-9],[0-9][0-9],[0-9][0-9][0-9],[0-9][0-9][0-9][0-9] count=100:)

Does someone know a better way to write the name argument ? Something
in the spirit of this perhaps (this one doesn't work) : [numeric] ?

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] A decade

[ABClf]

Thank you Simon for posting this fair message ; all your words are
mine as well. Bis repetita placent.
Thank you Petko.

Le sam. 20 juil. 2019 à 09:01, Moni Kellermann  a écrit :
>
> Am 20.07.2019 um 04:26 schrieb Simon:
> > It's a bit belated, but is been a decade since Petko, in Jan 2009, took
> > over the day to day work of maintaining PmWiki
> >
> > Thanks Petko for keeping PmWiki alive, and more than that updating it for
> > newer versions of PHP, fixing security issues, and even updating recipes
> > written by others.
>
> Yes! Thank you, Petko! :)
>
> Maybe we should support his hard work by donating?
>
> https://www.pmwiki.org/wiki/PmWiki/PayForPmWiki
>
> Petko - please send me your IBAN/BIC, so you don't have to pay PayPal
> fees :)
>
> Herzliche Grüße
> moni k.
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problems with my PMWiki Site after Update to PHP7.2 (from PHP5.6) - link to my site

[ABClf]

Did you update PmWiki to the last version ? what version are you running ?

Le mar. 19 mars 2019 à 16:14, Michael Lang  a écrit :
>
> Here's the link to my site:
>
> https://www.miclangschach.de/index.php
>
> Regards, Michael
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Have found files named : core.XXX

[ABClf]

Thank you Petko for the explanation.
Indeed, failing processes do happen sometimes.
Le ven. 16 nov. 2018 à 20:39, Petko Yotov <5...@5ko.fr> a écrit :
>
> These are core dumps, when the PHP process has crashed.
>
>https://en.wikipedia.org/wiki/Core_dump
>
> It sometimes happens when a search returns far too many results and the
> process runs out of time or out of memory (on a shared hosting plan a
> lack of memory or CPU time may happen because of someone other than
> you).
>
> If you don't have hundreds of these per day you can delete them.
>
> Petko
>
> On 15/11/2018 19:16, ABClf wrote:
> > Hello,
> >
> > Checking my website on ftp, I discovered a few unexpected files named :
> > core.17422
> > core.19723
> > etc.
> > (5 files as of now).
> >
> > File size is quite big : around 18 mo each ; they look like binary
> > files (selecting a file, when I click on edit, then I get a liste of
> > numbers like that –   4000 3800 4401    – instead
> > of text).
> >
> > Does anyone have any idea where these files come from ?
> > Does pmwiki creates such kind of core.XXX files ?
> >
> > Thank you !
> > Gilles.
> >
> > ___
> > pmwiki-users mailing list
> > pmwiki-users@pmichaud.com
> > http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Have found files named : core.XXX

[ABClf]

Hello,

Checking my website on ftp, I discovered a few unexpected files named :
core.17422
core.19723
etc.
(5 files as of now).

File size is quite big : around 18 mo each ; they look like binary
files (selecting a file, when I click on edit, then I get a liste of
numbers like that –   4000 3800 4401    – instead
of text).

Does anyone have any idea where these files come from ?
Does pmwiki creates such kind of core.XXX files ?

Thank you !
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Have a canonical url declaration : how to ?

[ABClf]

Thank you Petko for code and comments ; that's what I was looking for I guess.
As for htmlcache location, I've added a Disallow line in robots.txt
for that directory.

Gilles.

2018-03-04 22:09 GMT+01:00 Petko Yotov <5...@5ko.fr>:
> Sorry, please use $HTMLHeaderFmt instead of $HTMLFooterFmt as below:
>
>if ($action == 'browse')
>  $HTMLHeaderFmt['canonical'] = ' />';
>
># optional
>else $HTMLHeaderFmt['canonical'] =
>  '';
>
> Petko
>
>
>
> On 04/03/2018 22:04, Petko Yotov wrote:
>>
>> Add this in config.php to insert a canonical link in the page header:
>>
>>   if ($action == 'browse')
>>$HTMLFooterFmt['canonical'] = '> />';
>>
>> If your wiki is accessible both through HTTP and HTTPS, you should
>> select one of those and set correctly the $ScriptUrl variable.
>>
>> I'm not sure what you mean by 'have such canonical thing if "action"
>> pages'.
>>
>> If you want to set as canonical the base "browse" URL on ?action=edit,
>> diff, upload, print and other action pages, remove the first line
>> above.
>>
>> If you want to set the action URL as a canonical URL, add after the above
>> lines:
>>
>>
>>   else $HTMLFooterFmt['canonical'] =
>> '';
>>
>> Note that search engines and bots are usually blocked when they try to
>> access ?action=edit and similar pages.
>>
>> All these canonical urls will not work well for pages where you have
>> (:pagelist ... request=1:) or if you use a recipe like HttpVariables
>> or MultiLanguage that take information from the URL to display
>> different content. (But neither will FastCache.)
>>
>> Petko
>>
>> On 04/03/2018 21:13, ABClf wrote:
>>>
>>> Hello hello,
>>>
>>> I'm playing with google search console ; there I see I am missing a
>>> canonical url.
>>>
>>> Most of my pages are visible at these different url :
>>> http://www.mysite.com/Group/Name
>>> http://www.mysite.com/Group.Name
>>> http://www.mysite/com/pub/htmlcache/Group.Name.html
>>>
>>> I believe I need a link rel=canonical somewhere to make different url
>>> point to a unique url (avoiding duplicate content) ;
>>> what would be the strategy to get it done ? (note : in my special
>>> case, most of the pages are saved in cache using fastcache recipe to
>>> be served quickly on request).
>>> Do I have to write something in template, using Name and Group ? or
>>> would a dedicated script in config do better job ?
>>>
>>> (by the way, perhaps might be good to have such canonical thing if
>>> "action" pages).
>>
>>
>> ___
>> pmwiki-users mailing list
>> pmwiki-users@pmichaud.com
>> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Have a canonical url declaration : how to ?

[ABClf]

Hello hello,

I'm playing with google search console ; there I see I am missing a
canonical url.

Most of my pages are visible at these different url :
http://www.mysite.com/Group/Name
http://www.mysite.com/Group.Name
http://www.mysite/com/pub/htmlcache/Group.Name.html

I believe I need a link rel=canonical somewhere to make different url
point to a unique url (avoiding duplicate content) ;
what would be the strategy to get it done ? (note : in my special
case, most of the pages are saved in cache using fastcache recipe to
be served quickly on request).
Do I have to write something in template, using Name and Group ? or
would a dedicated script in config do better job ?

(by the way, perhaps might be good to have such canonical thing if
"action" pages).

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Issue with accented letter in link (with alternate page name in config)

[ABClf]

Hello,

Just testing 2.2.103 on a new local installation (but probably not
related to that version) : I'm facing an issue for links with accented
french letter, when using dedicated alternate pagename in config.
I believe the snippet given in Cookbook/AlternateNamingScheme is doing
something I didn't expect.

In my config :

include_once("scripts/xlpage-utf-8.php");
[...]
$MakePageNamePatterns = array(
"/'/" => '',   # strip single-quotes
"/[^$PageNameChars]+/" => ' ', # convert everything else to space
'/((^|[^-\\w])\\w)/' => PCCF("return strtoupper(\$m[1]);"),
"/\\s+/" => '-');

Then,
[[mètre]] outputs links to : MèTre (same behavior with : é ; but works
as expected with : ç)

Can this be corrected or is that the normal behavior ?

Note :
in case I use next alternate page name scheme given in the recipe,
it's working as expected
"/(^\\w)/" => PCCF("return strtoupper(\$m[1]);"), # initial caps

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Selecting skins for testing?

[ABClf]

My mistake !
command is : ?skin= (temporary) or ?setskin= (setting up a cookie).

2017-09-18 22:59 GMT+02:00 ABClf <languefranca...@gmail.com>:
> Hello,
>
> Isn't the ?action=setskin the way to go ?
> http://www.pmwiki.org/wiki/Skins/SkinChange
>
> Gilles.
>
>
> 2017-09-18 17:51 GMT+02:00 Erik Burggraaf <burggraafe...@gmail.com>:
>> Hello, is there a way to choose a skin from the address bar? I would like to
>> test several different skins at once. I'm happy enough to edit the config
>> file if I have to, but I was wondering if there's a more elegant solution.
>>
>> Thanks and regards, Eric
>>
>>
>>
>> ___
>> pmwiki-users mailing list
>> pmwiki-users@pmichaud.com
>> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Selecting skins for testing?

[ABClf]

Hello,

Isn't the ?action=setskin the way to go ?
http://www.pmwiki.org/wiki/Skins/SkinChange

Gilles.


2017-09-18 17:51 GMT+02:00 Erik Burggraaf :
> Hello, is there a way to choose a skin from the address bar? I would like to
> test several different skins at once. I'm happy enough to edit the config
> file if I have to, but I was wondering if there's a more elegant solution.
>
> Thanks and regards, Eric
>
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] description of link in a trail

[ABClf]

To my modest knowledge I guess you can't collect more than pagename
value from your trail ;
in your case, you may want to write the informations you want to show
when outputting pagelists/search results inside each of your pages.

For example, give A, B, C, ... pages a directive title (or maybe
define other PageVariable, or use ptv).
Then write your trail this way
*[[A|+]]
*[[B|+]]
...
and format your recherche snippet with

[[#recherche]]
[[{=$FullName}|+]],
[[#recherche]]

Gilles.

2017-08-26 16:21 GMT+02:00 Benjamin Grassineau :
> Hello,
>
> I use a trail index with pagelist. For example :
>
> (:pagelist trail=Test#test#testend fmt=#recherche:)
>
> The list is, for example :
> [[#test]]
> *[[A|Allemagne]]
> *[[B|Belgique]]
> *[[C|Cameroun]]
> [[#testend]]
>
> [[#recherche]]
> {=$Name},
> [[#recherche]]
>
> Do you know if it is possible to get the link description in the result ? I
> mean, I would like to have the result : Allemagne, Belgique, Cameroun and
> not, A,B,C.
>
> Thanks for your help
>
> Benjamin
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] How to test IF name is 4 decimal ?

[ABClf]

Great. Thank you Petko.
By the way, can you confirm pattern like [d] won't work for one decimal ?

2017-08-08 10:39 GMT+02:00 Petko Yotov <5...@5ko.fr>:
> Something like this:
>
> (:if name [0-9][0-9][0-9][0-9]:)
> %green% Name is a 4-digit number.
> (:else:)
> %red% Name is NOT a 4-digit number.
> (:if:)
>
> You can have other characters like [a-z] for a range or [abc123] for
> specific characters. This defines a single character in the page name that
> is among those inside the brackets (case insentitive, but probably for a-z
> letters only, not for international letters).
>
> Petko
>
> --
> PmWeekly Blog  :  http://www.pmwiki.org/News
> If you upgrade :  http://www.pmwiki.org/Upgrades
>
>
> On 2017-08-08 10:25, ABClf wrote:
>>
>> Hello,
>>
>> I can't find what conditional markup is needed for testing if page
>> name is like 1970 (made of 4 decimals).
>> (:if name :) works, yet it's not restrictive enough for my need.
>> Does anyone know the trick ?
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] How to test IF name is 4 decimal ?

[ABClf]

Hello,

I can't find what conditional markup is needed for testing if page
name is like 1970 (made of 4 decimals).
(:if name :) works, yet it's not restrictive enough for my need.
Does anyone know the trick ?

Thank you !

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki 2.2.100 released

[ABClf]

Indeed, 2.2.101 cleans the warning ;
test done with php 5.4.
Thank you Petko.

2017-07-31 3:22 GMT+02:00 Petko Yotov <5...@5ko.fr>:
> I've released 2.2.101 that should fix this but likely becomes incompatible
> with PHP4.
>
> If anyone still does use PHP 4 and cannot upgrade it, but must upgrade
> PmWiki, please contact me and we'll figure out a workaround.
>
> This is not a problem, I just want to test my workaround on an actual PHP4
> installation before publishing it for all.
>
> Petko
>
> --
> PmWeekly Blog  :  http://www.pmwiki.org/wiki/News
> 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
>
>
> On 2017-07-31 00:47, ABClf wrote:
>>
>> Hello Petko,
>>
>> Unlike 2.2.98, 2.2.100 gives me these error warnings (on fresh install) :
>>
>> Strict Standards: Redefining already defined constructor for class
>> PageStore in /home/www/margi/pmwiki.php on line 1010
>>
>> Warning: Cannot modify header information - headers already sent by
>> (output started at /home/www/margi/pmwiki.php:1010) in
>> /home/www/margi/pmwiki.php on line 1257
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki 2.2.100 released

[ABClf]

Hello Petko,

Unlike 2.2.98, 2.2.100 gives me these error warnings (on fresh install) :

Strict Standards: Redefining already defined constructor for class
PageStore in /home/www/margi/pmwiki.php on line 1010

Warning: Cannot modify header information - headers already sent by
(output started at /home/www/margi/pmwiki.php:1010) in
/home/www/margi/pmwiki.php on line 1257

Thank you for all.

2017-07-30 12:25 GMT+02:00 Petko Yotov <5...@5ko.fr>:
> Hello. PmWiki version 2.2.100 was published today, and is available at:
>
>   http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.100.tgz
>   http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.100.zip
>svn://www.pmwiki.org/pmwiki/tags/latest
>
> This version provides a workaround for an incompatibility with our
> Subversion version control system, where the $Author wiki variable was
> considered a Subversion variable. A fix for the responsive skin adds
> some spacing above the WikiText block. The documentation was updated.
>
> Thanks,
> Petko
>
> --
> PmWeekly Blog  :  http://www.pmwiki.org/wiki/News
> 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@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki 2.2.98 released

[ABClf]

Thank you Petko ! Grateful.

One tiny question about responsive skin provided in latest pmwiki
version : how different is it as compared to Skins/2016 ?

Gilles.



2017-05-31 13:34 GMT+02:00 Petko Yotov <5...@5ko.fr>:
> Hello. PmWiki version 2.2.98 was published today, and is available at:
>
>   http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.98.tgz
>   http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.98.zip
>svn://www.pmwiki.org/pmwiki/tags/latest
>
> This version adds a new skin that is better adaptable to both large and
> small screens, desktop and mobile devices (touchscreens). The new skin
> "pmwiki-responsive" is not enabled by default but available as an
> option, and as a base for customized copies. It requires a relatively
> modern browser (post-2009). The old skin is still available and enabled
> by default.
>
> The Vardoc links now use MakeLink() to allow a custom LinkPage
> function. The function ReplaceOnSave() was refactored to allow easier
> calling from recipes. Markup processing functions now can access
> besides $pagename, a $markupid variable that contains the "name" of the
> processed markup rule, allowing a single function to process multiple
> markup rules. The "*.mkv" video extension was added to the list of
> allowed uploads.
>
> A bug was fixed with the (:markup:) output where a leading space was
> lost. Note that the "markup" frame is now wrapped in a  block with
> a "pre-wrap" style instead of .
>
> A number of other (minor) bugs were fixed: see ChangeLog, and the
> documentation was updated.
>
> 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
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with link to page built by includes

[ABClf]

I believe you may need to look at this recipe :
http://www.pmwiki.org/wiki/Cookbook/TitleMarkup

Gilles.

2017-01-26 15:57 GMT+01:00 Johan Bengtsson :
> Hi,
>
> I have problem with "Title-links" like this:
>
> [[RegularPage | +]]  # OK, the link will be the page $Title
>
> [[PageBuiltByIncludes | +]]  # The link will be PageBuiltByIncludes, not the
> $Title included from other pages.
>
> Is this a bug or a feature, is there any way to fix it?
>
> -Johan Bengtsson
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki 2.2.93 released

[ABClf]

Thank you Petko for your work ;
best wishes to all PmWiki users.

Gilles.

2016-12-31 18:54 GMT+01:00 Petko Yotov <5...@5ko.fr>:
> Hello. PmWiki version 2.2.93 was published today, and is available at:
>
>   http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.93.tgz
>   http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.93.zip
>svn://www.pmwiki.org/pmwiki/tags/latest
>
> This is a documentation update version.
>
> A happy new year to all helpers with the daily maintenance of our community
> website and documentation, to the translators, to the recipe developers, and
> to all wiki admins who install and use the software!
>
> 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
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] notify not working for me

[ABClf]

Shouldn't notify command be written in SiteAdmin.NotifyList page ?

Gilles.

2016-12-06 22:17 GMT+01:00 Ron :
> I have "$EnableNotify = 1" in local/config.php.  Also in local/config.php
> "$NotifyDelay = 600".  Spaces are as shown .
>
> I have "notify=rbelch...@charter.net delay=300" in SiteAdmin.UserAuth.
> Spaces are as shown .
>
> I am not getting any notifications.  Any idea what I might be doing wrong or
> not doing?
>
> Ron
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PS Embeded Web Address Characters -

[ABClf]

As for https, have you read the IncludeSite talk page ?
http://www.pmwiki.org/wiki/Cookbook/IncludeSite-Talk
It's suggested there to edit cookbook file and use updated code for
markup, allowing https and php5.5 compatible :

Markup_e('includeSite', 'directives',
"/\\(:includeSite\\s+(https?:[^$UrlExcludeChars]*?)\\s*:\\)/",
"includeSite(\$m[1])");

As for parenthesis, please have a look at
http://www.pmwiki.org/wiki/PmWiki/Links :

If the external link includes (parentheses), escape these using %28
for "(" and %29 for ")" :
[[http://en.wikipedia.org/wiki/Wiki_%28disambiguation%29 | link to
"Wiki (disambiguation)" ]]
link to "Wiki (disambiguation)"

and cookbook http://www.pmwiki.org/wiki/Cookbook/FixURL

Gilles.

2016-09-11 1:31 GMT+02:00 Kirk Siqveland :
> Addendum:
>
> The Code:
> This works fine
> (:includeSite http://en.wikipedia.org/wiki/Nikola_Tesla?printable=yes:)
>
> but this does not
> (:includeSite https://en.wikipedia.org/wiki/Nikola_Tesla?printable=yes:)
>
> Nor does this
> (:includeSite
> http://en.wikipedia.org/wiki/Stephen_Gray_(scientist)?printable=yes:)
>
> On 9/10/2016 4:07 PM, Kirk Siqveland wrote:
>
> Hi All,
>
> I have been building a site in which I am sometimes embedding other pages,
> particularly Wikipedia.
> Sometimes those URL's include parenthesis  e.g.:
> https://en.wikipedia.org/wiki/Stephen_Gray_(scientist)
> 
>
> The code to do this works nicely on other pages, but not in this case.  Is
> there some way to correct for links that include Parens...?
> And while we are at it, how about allowing https as well as http?
>
> Thanks,
>
> Kirk
>Siqveland
>
> Two Main sites manged with PMwiki:
> http://www.technites.wiki/pmwiki.php
> (I'm working on this one, but have not "launched" it yet so please do not
> link or discuss it publicly)
>
> and
>
> http://www.steam-age.net/
> - in my spare time, I have been tweaking the skin for this and will add it
> to the collection for everyone else to use pretty soon...
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Include from page with includes

[ABClf]

For the future,
you might be interested in testing that easy to install recipe (only
in config) :
http://www.pmwiki.org/wiki/Cookbook/AutomaticChangeSummary
« The change-summaries generated by this recipe consist of the first
ten lines or so of changes to the document. »

Then, if working as said, RecentChanges should print out a more
complete summary.

Gilles.


2016-08-11 19:25 GMT+02:00 Tami Hawes (PERA) :
> Yes, I can do that, but that report only lists the page that had a change, 
> not the change/update itself. I suppose I have to go into each page and look 
> at the history to find out what has been updated?
>
>
> TAMI HAWES | BENEFIT INFORMATION SPECIALIST | COMMUNICATION & EDUCATION 
> DIVISION
> PUBLIC EMPLOYEES RETIREMENT ASSOCIATION OF MINNESOTA
> 60 EMPIRE DR. STE 200 | ST PAUL MN 55103-2088
> 651.296.7460 | 1.800.652.9026 | www.mnpera.org
>
>
>
> -Original Message-
> From: pmwiki-users [mailto:pmwiki-users-boun...@pmichaud.com] On Behalf Of 
> Johan Bengtsson
> Sent: Thursday, August 11, 2016 8:55 AM
> To: pmwiki-users@pmichaud.com
> Subject: Re: [pmwiki-users] Include from page with includes
>
> On 08/11/2016 02:48 PM, Tami Hawes (PERA) wrote:
>> Does anyone know of a way to run a report that will detail all of the 
>> changes made within a wiki site without going to each individual page?
>> I have more than one person updating in our wiki and would like 
>> documentation to keep track of the changes.
>> Any help would be greatly appreciated.
>
> Click on the "All recent changes" link in the wiki, isn't that what you need?
>
> Best regards,
> Johan Bengtsson
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
>
> The statutes and regulations governing PERA may change at any time. If there 
> is a discrepancy between the law governing PERA and the information contained 
> in this e-mail, the statutes and regulations shall govern. This e-mail and 
> attachments are intended only for the addressee and may contain privileged or 
> not-public data. If you are not the addressee, do not review, forward or use 
> the information in this e-mail. If you received this e-mail in error, contact 
> the sender and delete this e-mail and attachments.
>
> Public Employees Retirement Association of Minnesota
>
> 
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Cross-site variables

[ABClf]

If that can help, for the alternative way,
one quick step might be to evaluate if that old and tiny recipe would
get the job done :
http://www.pmwiki.org/wiki/Cookbook/IncludeWikiPage
(I believe, because it is a sort of include, grabbing to siteA the
source from external siteB page, it must have include limitations.)

You might also consider of a file transfer/synchronization tool which
would automatically copy file from site A to site B.

You might also need to set up a farm, then use a specific file sharing recipe.

Gilles.


2016-07-24 23:03 GMT+02:00 ki...@kirpi.it :
> I have two websites in a cheap, shared hosting service, so most probably
> running in different servers outside my control.
> Say one is example.com and the other one is example.org
>
> Is there any way to "read" the PTVs of one site and show them on the other
> one?
> If I set $:VariableX on www.example.com/Group/Page there is absolutely no
> way to let someone type www.example.org/Group1/Page1 and have the
> $:VariableX displayed?
>
> As an alternative, no way to "rewrite" the www.example.com/Group/Page url to
> appear www.example.org/Group1/Page1 ?
>
> Thanks!
>
> Luigi
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] spreading out my table rows?

[ABClf]

If it can help, why not adjusting default table with css, in you
skin's css or local.css, if you agree to set such behaviour globally
(or use a class if you prefer "on request" behaviour) ?

td {
  padding-right: 5px;
}

Gilles.

2016-07-21 19:47 GMT+02:00 erik burggraaf :
> Hi all,  This is probably very simple, but it's visual and I've never learned 
> to do it because it's never come up.  I have a table that looks very nice in 
> pmwiki, except that the rows are too close together for visual appeal.  I 
> want to space the rows out a bit, but I don't want a visual border or 
> gridlines.  I also don't want the columns to change.
>
> I looked for a rowspacing tag in the table directives but all I found was 
> cell spacing.  I'm afraid this would proportionally adjust my columns and 
> throw them off while making my rows look nice.  Am I going to have to take 
> care of this in the CSS?
>
> Thanks,
>
> Erik
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] The PmWiki Confluence Project

[ABClf]

Latest change in 2008 and using pmwiki-2.2.0-beta65 : status is
inactive I guess ;)

2016-06-18 1:58 GMT+02:00 Simon :
> http://pmwiki.confluence.free.fr/
>
> Is anyone aware of the status of this project?
>
> tia
>
> Simon
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Issue with blocklist regex (for /\bcialis\b/), blocking word spécialisé

[ABClf]

Bingo, "é" was the culprit, good shot ;
just writing
block:/\bcialis\b/u
in blocklist makes the job done.

(Yes, I've got already the locale set to french utf-8 in XLPage :
  ### Character encoding, e.g. 'iso-8859-2' or 'utf-8'
  'xlpage-i18n' => 'utf-8',
  ### Locale identifier, e.g. 'de' or 'cs_CZ.ISO-8859-2'
  'Locale' => 'fr_FR.utf8',)

One more question, do I have to add /u at the end of all possible
regex set up with word "boundaries" ?

Thank you.

2016-05-03 2:34 GMT+02:00 Petko Yotov <5...@5ko.fr>:
> If your PHP installation permits it, you can use the /u (Unicode/utf8)
> modifier:
>
>   block:/\bcialis\b/u
>
> Some installations crash or hang, so test it.
>
> Additionally, you may need to set the locale to French/UTF-8:
>
>   setlocale(LC_ALL,'fr_FR.UTF-8');
>
> (unless your XLPage page takes care of it, eg. you see the diff dates in
> French)
>
>
> If that doesn't help, remove the block: line. If your wiki automatically
> downloads the blocklist, you can unblock some expressions locally, in your
> Blocklist page, use the expression
>
>   unblock:/\bcialis\b/
>
> See http://www.pmwiki.org/wiki/PmWiki/Blocklist#unblock .
>
> 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
>
>
> On 2016-05-03 01:16, ABClf wrote:
>>
>> Not a big issue, but a strange one : my blocklist has an entry copied
>> from PmWiki's :
>>
>> block:/\bcialis\b/
>>
>> This wrongly blocks the word "spécialisé" on my website whereas
>> everything is fine in PmWiki, where "spécialisé" is allowed, as
>> expected.
>> (Can check the issue in www.languefrancaise/Test group).
>>
>> Does anyone have an idea why I encounter such an issue ? It looks like
>> the boundaries of the regex (only block full word) is not well
>> interpreted on my host. (Yet it should be working :
>> http://www.languefrancaise.net/phpinfo.php)
>>
>> In top of my config :
>> $EnableBlocklist   = 1;  # This tells PmWiki to scan
>> the SiteAdmin.Blocklist page and the SiteAdmin.Blocklist-Farm
>> $EnableWhyBlocked  = 1;
>>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Issue with blocklist regex (for /\bcialis\b/), blocking word spécialisé

[ABClf]

Hello,

Not a big issue, but a strange one : my blocklist has an entry copied
from PmWiki's :

block:/\bcialis\b/

This wrongly blocks the word "spécialisé" on my website whereas
everything is fine in PmWiki, where "spécialisé" is allowed, as
expected.
(Can check the issue in www.languefrancaise/Test group).

Does anyone have an idea why I encounter such an issue ? It looks like
the boundaries of the regex (only block full word) is not well
interpreted on my host. (Yet it should be working :
http://www.languefrancaise.net/phpinfo.php)

In top of my config :
$EnableBlocklist   = 1;  # This tells PmWiki to scan
the SiteAdmin.Blocklist page and the SiteAdmin.Blocklist-Farm
$EnableWhyBlocked  = 1;

Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] thumblist, jpg.jpg.lock

[ABClf]

>> Every time I edit page, it's name is reported in Home page and I'm
>> quite sure the newly edited pages are often quickly visited (it
>> happens the edited pages are cached before I have finished writing a
>> quote in another, which shoud be agregated by pagelist.)
>
>
> If PageA has a pagelist that extracts content from PageB, when you modify
> PageB, is PageA automatically updated (do you see in PageA what you expect
> to see, with the new content from PageB)? If yes, caching is probably done
> correctly.

As an admin/author, yes, because fastcache doesn't apply to me (it is
slow, yet usable ; might be better with faster server) ;
as an anonym user, no no : if a quote is created in group B, linking
to pages in group A, the linked pages in group A won't show the new
quote in pagelist, unless I edit or regen them (which I do most of the
time).

(Because I have to many pages, I have set up fastcache so that it
doesnt delete all cached pages ; I use a cron task to delete 500
oldest pages in cache every day).

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] thumblist, jpg.jpg.lock

[ABClf]

Thank you very much for your great explanation Petko.

> About your problem, I suspect the AutoPurge has progressively deleted some
> of the oldest thumbnails, but users were served the cached HTML pages with
> links to now deleted thumbnails.

That was something I thought that might have happened. Yet is was not
possible to track it, first because I didn't give attention to
autopurge until I made use of fastcache. And there is no Thumblist
hidden activity log I am aware of.
How does Thumblist know how many thumbnails have been created and
which ones to delete (I store files per page) ?

> Setting  $ThumbList['AutoPurgeDelay'] = 0; should prevent this from now on,
> but you may need to once revisit all your pages with the Admin account, or
> maybe simply clear the existing FastCache cache, and let it rebuild itself
> once again.

I have recently deleted a big bunch of cached files and I confirm it
looks like the regenerated files are fine, concerning thumbnails,
although I have not checked all ; browsed samples were fine.

> Now, I haven't used or reviewed FastCache, but it must not cache a page when
> the thumbnail is not yet created. Thumblist issues a NoCache() call to
> notify about this: I hope FastCache respects it.

As for this paragraph, I dont know ; I suspect fastcache saves
uncached page as soon as a visitor browse that page, but I dont know
if it does take care of any delaying request.
As a remark, if I'm not mistaken, I guess I have at least one cached
page saved with createthumbnail action :
http://www.languefrancaise.net/Bob/58707
which has a thumbnail coming from :
http://www.languefrancaise.net/Bob/58707?action=createthumb==th200---ff--58707.jpg.jpg

(and 58707 folder has :
./Bob/5/58707
./Bob/5/58707/th200---ff--58707.jpg.jpg
./Bob/5/58707/.thumblist-trail.Bob.58707.2.cache
./Bob/5/58707/58707.jpg
./Bob/5/58707/.thumblist-trail.Bob.58707.1.cache)

> P.S. This should be rare: If a thumbnail lock exists, but not the thumbnail,
> this may mean that the person who edited the page, after saving it, moved
> away from it, before the thumbnails were generated (appeared in the page).
> Or, s/he used a text browser, and the browser never requested the thumbnail.
> Or, used an ad-blocker that thought that the thumbnail was an advertisement
> and stopped the browser from requesting it. Or, the server process crashed
> and didn't send the thumbnail, and the editor moved away. In any of these
> cases, the next visitor on that page should generate the missing thumbnails.
> There may be other reasons I haven't thought of, but probably less common.

Are robots (Google and others) text browsers ?
Every time I edit page, it's name is reported in Home page and I'm
quite sure the newly edited pages are often quickly visited (it
happens the edited pages are cached before I have finished writing a
quote in another, which shoud be agregated by pagelist.)

Last word, I remark that, in my first example,
Listing directory after ?action=regen :

./2/27572
./2/27572/27572.jpg
./2/27572/.thumblist-trail.Bob.27572.1.cache
./2/27572/th200---ff--27572_20cm.jpg.jpg
./2/27572/27572_20cm.jpg
./2/27572/.thumblist-trail.Bob.27572.2.cache

there is only 1 thumbnail created for 2 pictures, because one of them
is smaller than the expected thumbnail (just to mention).

Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] thumblist, jpg.jpg.lock

[ABClf]

Hello hello,

I'm using Thumblist for conveniently listing image thumbnails, with
links to big images, using a dedicated template. Great toolbox. I have
recently set the autopurge to 0 to be sure the program is not going to
delete thumbnails (I use –and strongly need– the fastcache recipe thus
I dont want the thumbnails to be deleted).
(uploads are stored page by page).

For a few pages, issue is that the thumbnail is not printed out, while
the link to the big image is working ; only the thumbnail is wrong, as
if there is a missing picture (I am given the empty frame for the
thumbnail, yet not the thumbnail itself).
If I run ?action=regen to the page, all gets better and all thumbnails
are printed out, as expected.
I'm willing to find out where is the issue and how to solve it.
Please note the issue happens to unidentified users, for pages saved
in the cache. As an admin/author, if I browse the page which doesn't
fully work for visitors, I get all the thumbnails and, my visit done,
the issue will be solved for unidentified visitors who are still given
the same cached page as before.

At first, I thought the culprit is the autopurge, which may
automatically delete some images. But now I'm sure the issue has
something to do with the ..lock extension given to some
thumbnails.
I have compared one directory, before regen and after regen. This way,
I see the missing thumbnail is .locked.
I'm not sure why this .lock extension (and dot at the beginning)
happens, and wether is is possible to get rid of it ? Is that because
the server has ended his thumbnailing task before it was done ?

Listing directory for page 27572 when 1 thumbnail –for image named
27572_20cm– doesnt work :
./2/27572
./2/27572/.th200---ff--27572_20cm.jpg.jpg.lock
./2/27572/27572.jpg
./2/27572/.thumblist-trail.Bob.27572.1.cache
./2/27572/27572_20cm.jpg
./2/27572/.thumblist-trail.Bob.27572.2.cache

Listing directory after ?action=regen, all is working :
./2/27572
./2/27572/27572.jpg
./2/27572/.thumblist-trail.Bob.27572.1.cache
./2/27572/th200---ff--27572_20cm.jpg.jpg
./2/27572/27572_20cm.jpg
./2/27572/.thumblist-trail.Bob.27572.2.cache

In Thumblist documentation, "lock" word comes for the
$ThumbList['EnableThumbs'] = 1; setting, which I dont use in my
config.

/config/
# ThumbList
$ThumbList['AutoPurgeDelay'] = 0; # to completely disable the AutoPurge function
$ThumbList['UseTmpl']=1; # to always use the template ; set
usetemplate=0 to override this eventually.
include_once("$FarmD/cookbook/thumblist2.php");

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki can't process your request

[ABClf]

--quoted--

if I add utf-8 support in config.php, by adding

include_once("scripts/xlpage-utf-8.php");
$DefaultPageCharset = array(''=>'ISO-8859-1');

after

# per group subdirectories
$WikiDir = new PageStore('wiki.d/$Group/$FullName');
--end--

Hans, try disabling
$DefaultPageCharset = array(''=>'ISO-8859-1');

It is commented in my config and I dont have issue with french (using utf-8).

You may want to do some tests with that recipe as well :
http://www.pmwiki.org/wiki/Cookbook/ISO8859MakePageNamePatterns?from=Cookbook.ISO8859PageNameConversionPatterns

Gilles.

2016-04-14 15:15 GMT+02:00 Hans :
>
>
>> The site is bilingual: English and French (Quebecian site).
>> French text with accented characters will stop a page being saved.
>> Page character set is iso-8859-1
>> The wiki ids not set up for utf-8
>> There are no accented characters in page names.
>
> if I add utf-8 support in config.php, by adding
>
> include_once("scripts/xlpage-utf-8.php");
> $DefaultPageCharset = array(''=>'ISO-8859-1');
>
> after
>
> # per group subdirectories
> $WikiDir = new PageStore('wiki.d/$Group/$FullName');
>
> I get a different error response from PmWiki when saving the old HomePage:
> not anymore
>  PmWiki can't process your request
>  ?invalid page name
>
> but a redirect to a non-existing page, but with the original URL:
> The page "406.shtml" doesn't exist.
> (Create 406.Shtml).
>
> and no save of changes
>
> more puzzled.
> ~Hans
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] languages

[ABClf]

Hello,

Cookbooks
http://www.pmwiki.org/wiki/Cookbook/MultiLanguage
http://www.pmwiki.org/wiki/Cookbook/MultiLanguageViews
look like they are built to do so.

Second cookbook is compatible with the first one.

Gilles.

2016-04-01 9:22 GMT+02:00 jdd :
> Hello,
>
> Is there a way to manage two languages on the same wiki?
>
> More precisely, I mean having two languages on the same page with only the
> good one shown at the same time, may be with switch somewhere (and with same
> images, maps...).
>
> May be something like:
>
> {:lang french:}
> Texte en français
>
> {:lang english:}
> English text
>
> thanks
> jdd
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Make "M. Name" work for profil link

[ABClf]

Perfect ; thank you for your help (and for mentioning the use of double $$).
Gilles.

2016-03-31 17:42 GMT+02:00 Hans <desi...@softflow.uk>:
> Hello ABClf,
>
> Thursday, March 31, 2016, 4:04:57 PM, you wrote:
>
>> What I'm willing to do, is to use any value in a form and format in a
>> such a way I get something usable for a profil link.
>> If the given value is G.M. Christopher, I would like [[Profile/G.M.
>> Christopher]] link to Profil/GMChristopher.
>
> you could use the markup expression 'wikiword' by including the cookbook
> recipe
> http://www.pmwiki.org/wiki/Cookbook/MarkupExprPlus
> The wikiword expression will 'sanitise' a text, dots will be stripped, words
> will start with capitals, spaces will be stripped. G.M. Christopher or
> g.m.christopher will become GMChristopher
>
> to post a link via a Fox form using an input field named 'author'
> you could use this in the Fox template the form uses:
>
> [[Profiles/{$$(wikiword '{$$author}')}]]
>
> Note the use of two $$ in the markup expression, which means Fox will
> evaluate the expression when it is posted, not when the page is loaded.
>
>
> Best regards,
> Hans

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Make "M. Name" work for profil link

[ABClf]

Christopher, I'm afraid I don't see what you are pointing with title
directive. Maybe I'm not clear, sorry.
What I'm willing to do, is to use any value in a form and format in a
such a way I get something usable for a profil link.
If the given value is G.M. Christopher, I would like [[Profile/G.M.
Christopher]] link to Profil/GMChristopher.

Thank you.

2016-03-31 4:59 GMT+02:00 Christopher Cox <c...@endlessnow.com>:
> On 03/30/2016 08:48 PM, ABClf wrote:
>>
>> Hello, hello,
>>
>> I have a form built with fox where I ask poster to comment and sign ;
>> signature field is as follows :
>> Signature (:input text author value='{$Author}' :)
>>
>> I would like to use the given author value for linking to the Profile
>> page, yet I don't know how to manipulate that value so that it's
>> giving a regular pagename for PmWiki.
>> Some users use something as M. Smith. And of course [[Group/M. Smith]]
>> won't work.
>>
>> What would be the right way to use / format the Author value in a
>> PmWiki compliant value ?
>>
>
> I've done things like this in the past using (:title ... :) markup to make
> (for example) MarkMcmillian look like Mark McMillian.
>
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Make "M. Name" work for profil link

[ABClf]

Hello, hello,

I have a form built with fox where I ask poster to comment and sign ;
signature field is as follows :
Signature (:input text author value='{$Author}' :)

I would like to use the given author value for linking to the Profile
page, yet I don't know how to manipulate that value so that it's
giving a regular pagename for PmWiki.
Some users use something as M. Smith. And of course [[Group/M. Smith]]
won't work.

What would be the right way to use / format the Author value in a
PmWiki compliant value ?

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] what to do in case of massive spam ?

[ABClf]

Hello,

what can we do in case of massive spam, when dozens of pages are
suddenly spammed (needing many delete or restore action) ?
do pmwiki admins have tools to easily clean the pollution ?

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] SVG cookbook: not displayed when Attach:file.svg is inside hyperlink

[ABClf]

I guess you have to add an image type in config :
http://www.pmwiki.org/wiki/Cookbook/AddImageType

Something like :
$ImgExtPattern = "\\.(?:gif|jpg|jpeg|png|svg|GIF|JPG|JPEG|PNG|SVG)";

Gilles.

2016-03-16 17:56 GMT+01:00 Jo Vermeulen :
> Hi,
>
> I'm having some difficulties displaying SVG's inline, when they're also
> linked. I have installed the SVG cookbook, and made the necessary changes to
> config.php.
>
> My markup used to look like this:
>
> [[http://www.example.com/ | Attach:icon.png]]
>
> I want to replace this by
>
> [[http://www.example.com/ | Attach:icon.svg]]
>
> The SVG displays fine if I don't include it in a link (i.e.,
> Attach:icon.svg), but just displays the linked Attach:icon.svg text when
> it's inside a link.
>
> Any ideas?
>
> Thanks!
>
> Cheers,
>
> -- Jo
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Too many pmwiki.php processes

[ABClf]

>From my naive point of view, 2500 visitors (or page views) a day,
printing out light pages, should be easily managed by a pmwiki
website.
Of course, a robot asking to many pages in a short time might be a
problem. For robots, you can try to adjust robot text (craw-delay ?)
You might try to adjust the meta-tag REVISIT-AFTER as well.

Are your websites getting more visitors now than before, have you
reached some limit ? is your host restrictive ?

No matter what, to my mind, FastCache is still a relevant extension to
set up. Its purpose is to help processor and fasten the page creation.
Very useful if most of your visitors are not editors.

Gilles.

2016-02-24 14:23 GMT+01:00 Rick Cook <r...@rickcook.name>:
> They were complaining about too many processes and claiming it was putting 
> too much load on their server.
>
> The PmWiki sites involved are very simple with no dynamic content.
>
> Most of the "visitors" are robots of various varieties. The most access_log 
> entries for the year so far across my whole account (~10 PmWiki sites and 2 
> WordPress sites) was about 9200 on one day. Typically, it was more like 2500 
> a day. Since this all started, I have put a more restrictive robots.txt file 
> in all of the URL roots and added 192.168 to all of the appropriate .htaccess 
> files (somehow, the non-routeable address 192.168.151.0 was one of the more 
> frequent IP addresses in my access_log files). I think it is running more 
> like 1000 per day now.
>
> They suggested several IP addresses to block. One was the dynamic IP assigned 
> to my home connection and another was their site monitoring service. Most of 
> the other addresses were attached to well known sites like Google.
>
>
> Rick Cook
>
>> On Feb 24, 2016, at 05:59, ABClf <languefranca...@gmail.com> wrote:
>>
>> Why are they complaining : because "too many" (quantitative) or
>> because "too heavy" (your sites cannibalize the server) ?
>>
>> Maybe you use too heavy pagelists ? What I mean is X processes doesn't
>> tell us how much cpu eager they are (printing out a simple page vs
>> building a complex page from multiparameter pagelist). How many users
>> visiting your sites in the busy hours ?
>>
>> In that case, if possible, you might be happy with fastcache recipe.
>> That's a must have for me as I use pagelists and ptv a lot. It works
>> nicely (40 visitors on the busy hours).
>> I never delete all cached pages ; I run a cron which delete 300 oldest
>> cached pages every day.
>>
>> I have been in trouble with my host recently, when my pageindex was
>> lost for unknown reason : hard to rebuild one, process was taking all
>> cpu for minutes. Thus they blocked my site for a few hours. (Shared
>> host, "premium option", 2 cores, 2 go ram, 20 go ssd...).
>>
>> My host didn't give me useful informations I can read to try to
>> understand what was going wrong ; just told me : run htop to see the
>> processes and cpu/memory usage.
>>
>> Gilles.
>>
>> 2016-02-14 11:13 GMT+01:00 Rick Cook <r...@rickcook.name>:
>>> All,
>>>
>>> My hosting provider is complaining about "too many pmwiki.php processes" 
>>> running from my PmWiki sites. By "too many", they meant more than 100. I 
>>> have 10 or so sites active with this provider. With that many sites, having 
>>> a 100 or more pmwiki.php processes doesn't seem excessive.
>>>
>>> Has anyone else had this type complaint from their hosting service?
>>>
>>>
>>> Thanks,
>>>
>>> Rick Cook
>>> ___
>>> pmwiki-users mailing list
>>> pmwiki-users@pmichaud.com
>>> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Too many pmwiki.php processes

[ABClf]

Why are they complaining : because "too many" (quantitative) or
because "too heavy" (your sites cannibalize the server) ?

Maybe you use too heavy pagelists ? What I mean is X processes doesn't
tell us how much cpu eager they are (printing out a simple page vs
building a complex page from multiparameter pagelist). How many users
visiting your sites in the busy hours ?

In that case, if possible, you might be happy with fastcache recipe.
That's a must have for me as I use pagelists and ptv a lot. It works
nicely (40 visitors on the busy hours).
I never delete all cached pages ; I run a cron which delete 300 oldest
cached pages every day.

I have been in trouble with my host recently, when my pageindex was
lost for unknown reason : hard to rebuild one, process was taking all
cpu for minutes. Thus they blocked my site for a few hours. (Shared
host, "premium option", 2 cores, 2 go ram, 20 go ssd...).

My host didn't give me useful informations I can read to try to
understand what was going wrong ; just told me : run htop to see the
processes and cpu/memory usage.

Gilles.

2016-02-14 11:13 GMT+01:00 Rick Cook :
> All,
>
> My hosting provider is complaining about "too many pmwiki.php processes" 
> running from my PmWiki sites. By "too many", they meant more than 100. I have 
> 10 or so sites active with this provider. With that many sites, having a 100 
> or more pmwiki.php processes doesn't seem excessive.
>
> Has anyone else had this type complaint from their hosting service?
>
>
> Thanks,
>
> Rick Cook
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] New recipe: InPageSearch

[ABClf]

Happily tested on desktop ; nice gadget for quickly filtetring long
pages, lists, tables. Fast as well.
One question : is it the expected behaviour it appears on every page,
or do I have to inspect my template ?
Thank you.

2016-02-07 2:50 GMT+01:00 Petko Yotov <5...@5ko.fr>:
> Hello,
>
> I've published a new recipe that allows instant search as-you-type in the
> current page, with highlighting. This was requested by users with mobile
> touch-screen devices where it is harder to find something in a large page.
>
> See/test/get the recipe here:
>
>   http://www.pmwiki.org/wiki/Cookbook/InPageSearch
>
> Your comments are welcome.
>
> 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
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Link for thumbs, in Thumblist (for Petko)

[ABClf]

Indeed, you are right Petko, thank you for pointing the culprit out  ;
I was browsing at work thanks to my 3g and it looks like my provider
(SFR) is modifying the original code.

This (off-topic subject) has been discussed there, by the way :
https://reflets.info/sfr-modifie-le-source-html-des-pages-que-vous-visitez-en-3g/
http://security.stackexchange.com/questions/9368/mobile-carrier-javascript-injection


2016-01-21 16:45 GMT+01:00 Petko Yotov <5...@5ko.fr>:
> The pages are *not* using this kind of pattern. My guess is that your
> internet connection passes through some aggressive
> caching/speeding/recoding/ad-blocking proxy which rewrites the page.
>
> The IP address 91.68.209.8 belongs to "SFR", a French telephone and internet
> provider.
>
> My guess is that if you open other pages with pictures from the same
> connection, non PmWiki, non-thumblist, you will see a similar pattern. For
> example check the source of http://5ko.free.fr/fr/duplitree.html where there
> are 2 pictures.
>
> Rewriting pages by a proxy may cause many side effects, especially if your
> pages use JavaScript (Lightbox...).
>
> 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
>
>
> On 2016-01-21 13:55, ABClf wrote:
>>
>> Petko,
>>
>> please, can you explain the reason why, in your thumblist test pages
>> (http://tl.5ko.fr/T/Sandbox7), the thumblists' url are using this kind
>> of pattern (I'm pointing the 91.68.209.8/bmi part)  :
>>
>>
>> http://91.68.209.8/bmi/tl.5ko.fr/uploads/T/th48---ff--2014-11-29T14.01.20-PB297709-Si%c3n.jpeg.jpg
>>
>> I have this kind of url as well and I would like to have more natural
>> url for loading thumbs.
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Link for thumbs, in Thumblist (for Petko)

[ABClf]

Petko,

please, can you explain the reason why, in your thumblist test pages
(http://tl.5ko.fr/T/Sandbox7), the thumblists' url are using this kind
of pattern (I'm pointing the 91.68.209.8/bmi part)  :

http://91.68.209.8/bmi/tl.5ko.fr/uploads/T/th48---ff--2014-11-29T14.01.20-PB297709-Si%c3n.jpeg.jpg

I have this kind of url as well and I would like to have more natural
url for loading thumbs.

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] How to be sure pageindex is being used for pagelists (using debug messages ?)

[ABClf]

Not easy to say because I don't have access to all relevant
informations (shared hosting) and because all (or almost all) pages
are using pagelists (at least basic PL in the sidebar).
All its working fine now (not blazing fast yet quite usable for me)  ;
I experienced unusual very slow processing yesterday (where it is
usually fine), and the day before, for part of the day only.
I opened this thread to ask how to be sure pageindex is truly used
(ie, not corrupted and not ignored for example).
Because I'm on a shared host, I don't have information about what's
happening in the server (disk usage, files active, memory, etc., i'm
blind)

Here is an hypothesis :

In my setup, I have a lot of (small) pages (around 200k, slowly
growing, often edited), most of them using pagelists for agregating
content (70k words are connected to 100k quotes).
The pagelists used are not complex, but it's true they have to collect
small pieces of data among many pages (some do use ptv). It works
decently most of the time for me (almost all visitors are anonymous
and can enjoy the already-existing cached files).
When I want to collect synonyms for a word, it takes about 10 seconds
(tested just now, when status is fine), to build the result page. Much
much more faster if cached. Say, in a short time, I want to open 3
uncached pages, in 3 new windows, Synonyme.1, Synonyme.2, Synonyme.3,
it takes very very long until I get the 3 result pages done in 3
windows.
I might say the server is not powerful enough (or maybe it can't
handle the pageindex in such a short time).

To make this work for non logged visitors, despite that limitation, I
use fastcache recipe, which is a must have recipe for me.

There is one issue with fastcache though : it can delete all, or
nothing, every time a page is updated, but there is no setup for
deleting the page according to its age. Because I obviously don't want
to delete 70k cached pages every time I update one page in the website
(in that case, website would become unusable for a week, always busy
building cached pages, until most of the pages are cached), I set it
to delete nothing.
And because I need to have oldest pages rebuilt , I manually delete
5000 oldest cached pages every week or so, with that command
(terminal) :
ls -1tr | head -5000 | xargs -d '\n' rm -f

Then, pmwiki, with fastcache, has to rebuild every deleted page every
time a new visitor is visiting it. Some take 10 seconds, or less, or
more...
My hypothesis : it is possible my website has become slow these days
because the server was busy rebuilding the cached pages which have
been mass deleted last time.

I won't mass delete cached this week, to see what happens.

Thank you for your contribution Peter.

Gilles.

If anyone is interested in testing fastcache recipe, here is a pagelist :
http://www.languefrancaise.net/Test/PageListWithCache
http://www.languefrancaise.net/Test/PageListNoCache



2016-01-10 21:18 GMT+01:00 Peter Bowers <pbow...@pobox.com>:
> Are you seeing this performance on all pages or only those with pagelists?
>
> Be aware that some pagelist search requirements require an exhaustive search
> through files rather than using the pageindex (searching for the value of a
> PTV, for instance).
>
> -Peter
>
> On Sat, Jan 9, 2016 at 4:57 PM, ABClf <languefranca...@gmail.com> wrote:
>>
>> Thank you for your clean summary Petko.
>> I'm asking that question because my website has become very slow (30
>> seconds or more, many 502 bad gateway, no reason I can point. Not sure
>> it is my fault or server's fault).
>> According to the data given by diag option, it looks like the scan
>> among all my folders and files took too much time.
>>
>> Thus I suspected the existing pageindex (57,2 mo) to have become
>> altered and useless...
>>
>> I built a new one, and it's still very bad. I must now ask my webhost,
>> and start investigating for a new one.
>>
>> Gilles.
>>
>> 2016-01-09 8:26 GMT+01:00 Petko Yotov <5...@5ko.fr>:
>> > On 2016-01-09 00:05, ABClf wrote:
>> >>
>> >> For new year first question, I would like to know how to be sure
>> >> .pageindex is used for creating pages. Do informations given by
>> >> $EnableDiag help ?
>> >
>> >
>> > For creating pages? .pageindex is used (scanned) when a pagelist or a
>> > visitor searches for terms or link targets in the wiki pages. When
>> > searching, you will see something like:
>> >
>> > 16: 00.17 00.16 PageListTermsTargets begin count=1038
>> > 17: 00.17 00.16 PageIndexGrep begin
>> > 18: 00.28 00.27 PageIndexGrep end
>> > 19: 00.96 00.94 PageListTermsTargets end count=222
>> >
>> > The "PageIndexGrep" lines indicate that .pageindex was used.
>> >
>> &g

Re: [pmwiki-users-fr] recherche "à facettes" suite

[ABClf]

Bonjour Patrice,

Je ne vais pas beaucoup vous aider, mais au moins une réponse générale
pour faire avancer le sujet.

Sauf erreur, la recette sqlite est seulement une recette de stockage ;
elle ne facilite ni les pagelists ni les recherches. Je l'ai utilisée
mais je n'ai pas été heureux avec (pour un grand nombre de pages).
Les recettes zap, dataquery et dataplates sont je crois mal supportées
actuellement, et il peut être risqué de les utiliser toutes à la fois
sans les avoir testées auparavant avec des projets simples, et trouver
de l'aide sera plus difficile.

Dans votre premier exemple, quel est votre problème ? Une première
recherche filtrée donne les résultats attendus ? Mais quand vous
relancez un nouvelle recherche, les nouveaux résultats sont listées
sous les premiers ? c'est donc un problème de présentation des
résultats ?
Votre site est-il visible ? Pouvez-vous exposez votre souci en anglais
sur l'autre liste (l'auteur de Fox, Hans, qui est abonné, pourrait
vous éclairer).

Pour des recherches filtrées, je ne connais pas de sites utilisant
pmwiki qui pourraient servir de modèle ; peut-être que cette page
pourra vous aider ou vous donner des idées :
http://www.cef-cfr.ca/index.php?n=Equipements.Accueil

Avez-vous pensé à utiliser seulement des catégories plutôt que des ptv
(la taille, le lieu, ça semble bien rentrer dans des catégories) ?
avec la recette Tagger, elles s'utilisent efficacement, sans syntaxe ;
et la recette de Petko,
http://www.pmwiki.org/wiki/Cookbook/PageListMultiTargets
(experimental), permet de faire des recherches avec exclusion de
liens.


Gilles.


Le 9 janvier 2016 à 12:12, Patrice PELLE  a écrit :
> Bonjour
>
>
> j’ai continué à travailler sur mon projet de recherche multicritères
>
> J’ai créé le formulaire suivant sur la page « Poissons.Poissons »
>
> (:fox formulaire  ptvupdate=0 template=CherchePoisson#display  ptvclear=1:)
> !!Caractéristiques
> ||'''Lieu : '''||(:input select name=$:lieu value="*" label="*":)
> (:input select name=$:lieu value="Atlantique" label="Atlantique":)
> (:input select name=$:lieu value="Méditerranée" label="Méditerranée":)
> (:input select name=$:lieu value="Indo-Pacifique" label="Indo-Pacifique":)||
> ||'''Forme :'''||(:input select name=$:forme value="*" label="*":)
> (:input select name=$:forme value="Corps fuselé" label="Corps fuselé":)
> (:input select name=$:forme value="Corps comprimé latéralement" label="Corps
> comprimé latéralement":)
> (:input select name=$:forme value="Corps allongé" label="Corps allongé":)
> (:input select name=$:forme value="Corps en forme de gourdin" label="Corps
> en forme de gourdin":)
> (:input select name=$:forme value="Corps robuste/Ovale" label="Corps
> robuste/ovale":)
> (:input select name=$:forme value="Corps plat" label="Corps plat":)||
> ||'''Taille :'''||(:input select name=taille value="*" label="*":)
> (:input select name=$:taille value="*" label="*":)
> (:input select name=$:taille value="Inférieure 10cm" label="Inférieure
> 10cm":)
> (:input select name=$:taille value="10-20cm" label="10-20cm":)
> (:input select name=$:taille value="20-30cm" label="20-30cm":)
> (:input select name=$:taille value="30-40cm" label="30-40cm":)
> (:input select name=$:taille value="40-50cm" label="40-50cm":)
> (:input select name=$:taille value="50-60cm" label="50-60cm":)
> (:input select name=$:taille value="60-70cm" label="60-70cm":)
> (:input select name=$:taille value="70-80cm" label="60-80cm":)
> (:input select name=$:taille value="80-90cm" label="80-90cm":)
> (:input select name=$:taille value="90-100cm" label="90-100cm":)
> (:input select name=$:taille value="Supérieure 1m" label="Supérieure 1m":)
>
> (:input submit post Enter:)
>
> (:foxend formulaire:)
>
> qui renvoie à la page « Poissons.CherchePoisson » contenant les instructions
> suivantes
>
> (:nogroupheader:)
>
> [[#display]]
> (:pagelist taille={$$taille} lieu={$$lieu}:)
>
> [[#displayend]]
>
> Lorsque j’effectue la première recherche « Lieu=* » « Forme=* » « Taille
> Inférieur 10cm » j’obtiens un résultat qui correspond bien à mon attente,
> mais les résultats des recherches suivantes sont ensuite empilés les uns
> après les autres, ce que confirme le contenu de la page Poissons.Poissons
> (2ème recherche) :
>
> (:fox formulaire  ptvupdate=0 template=CherchePoisson#display  ptvclear=1:)
> !!Caractéristiques
> ||'''Lieu : '''||(:input select name=$:lieu value="*" label="*":)
> (:input select name=$:lieu value="Atlantique" label="Atlantique":)
> (:input select name=$:lieu value="Méditerranée" label="Méditerranée":)
> (:input select name=$:lieu value="Indo-Pacifique" label="Indo-Pacifique":)||
> ||'''Forme :'''||(:input select name=$:forme value="*" label="*":)
> (:input select name=$:forme value="Corps fuselé" label="Corps fuselé":)
> (:input select name=$:forme value="Corps comprimé latéralement" label="Corps
> comprimé latéralement":)
> (:input select name=$:forme value="Corps allongé" label="Corps allongé":)
> (:input 

Re: [pmwiki-users] How to be sure pageindex is being used for pagelists (using debug messages ?)

[ABClf]

Thank you for your clean summary Petko.
I'm asking that question because my website has become very slow (30
seconds or more, many 502 bad gateway, no reason I can point. Not sure
it is my fault or server's fault).
According to the data given by diag option, it looks like the scan
among all my folders and files took too much time.

Thus I suspected the existing pageindex (57,2 mo) to have become
altered and useless...

I built a new one, and it's still very bad. I must now ask my webhost,
and start investigating for a new one.

Gilles.

2016-01-09 8:26 GMT+01:00 Petko Yotov <5...@5ko.fr>:
> On 2016-01-09 00:05, ABClf wrote:
>>
>> For new year first question, I would like to know how to be sure
>> .pageindex is used for creating pages. Do informations given by
>> $EnableDiag help ?
>
>
> For creating pages? .pageindex is used (scanned) when a pagelist or a
> visitor searches for terms or link targets in the wiki pages. When
> searching, you will see something like:
>
> 16: 00.17 00.16 PageListTermsTargets begin count=1038
> 17: 00.17 00.16 PageIndexGrep begin
> 18: 00.28 00.27 PageIndexGrep end
> 19: 00.96 00.94 PageListTermsTargets end count=222
>
> The "PageIndexGrep" lines indicate that .pageindex was used.
>
>> (For example : does this page
>> http://www.pmwiki.org/wiki/Test/PagelistExample use pageindex or no ?)
>
>
> No, this page does not use .pageindex because the pagelist does not need to
> search for terms or link targets.
>
> Moreover, we use $PageListCacheDir so the whole list of pages from the
> pagelist will be saved once and as long as the cache is not obsolete, it
> will use the cache without scanning the pages or .pageindex.
>
>
> If you wonder if .pagelist is updated with the terms and targets of a newly
> created or a modified page, the answer is yes. To see it in the diagnostic
> output, disable redirects ($EnableRedirect=0;) then when you save a page,
> you will see these two lines:
>
> 30: 00.38 00.35 UpdatePage: PostPageIndex (Test.WikiSandbox)
> 31: 00.38 00.35 PageIndexQueueUpdate: queued 1 pages (1 total)
>
> try it here: http://www.pmwiki.org/wiki/Test/WikiSandbox (you can delete and
> recreate this page if you want).
>
> ---
> 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@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] How to be sure pageindex is being used for pagelists (using debug messages ?)

[ABClf]

Hello,

For new year first question, I would like to know how to be sure
.pageindex is used for creating pages. Do informations given by
$EnableDiag help ?

(For example : does this page
http://www.pmwiki.org/wiki/Test/PagelistExample use pageindex or no ?)

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Don't allow saving guest post for 0 modification

[ABClf]

I'm testing this solution now and it looks like it's working fine, yet
(minor issue) the error message doesn't appear with my setup (might be
related to my skin).

This is usefull snippet, merci Dominique.

2015-12-17 0:01 GMT+01:00 Dominique Faure <dominique.fa...@gmail.com>:
> Incidentally the test should be reverted:
>
> ...
> if ($new['text'] == $page['text']) {
> ...
>
>
> On Wed, Dec 16, 2015 at 11:59 PM, Dominique Faure
> <dominique.fa...@gmail.com> wrote:
>>
>> Hi,
>>
>> A solution could be to handle this in the same way it is already done with
>> author requirement: Looking at scripts/author.php, you'll could easily see
>> that the form post is interrupted by setting the $EnablePost variable to 0;
>>
>> Have a try with the following code:
>>
>> array_unshift($EditFunctions, "DeltaPageContent");
>> function DeltaPagecontent($pagename,&$page,&$new) {
>>   global $EnablePost, $ModifiedPageContentRequiredFmt;
>>   if (!$EnablePost) return;
>>
>>   if ($new['text'] != $page['text']) {
>> SDV($ModifiedPageContentRequiredFmt, "$[The
>> page hasn't been modified.]");
>> $MessagesFmt[] = $ModifiedPageContentRequiredFmt;
>> $EnablePost = 0;
>>   }
>> }
>>
>> Regards,
>> Dominique
>>
>>
>> On Wed, Dec 16, 2015 at 2:57 PM, ABClf <languefranca...@gmail.com> wrote:
>>>
>>> Hello,
>>>
>>> I'm facing a bit of spam on my wiki.
>>> For my defense, I use blocklist and Petko's Spamfilters cookbook.
>>>
>>> Problem is I have spammer posting unmodified pages (original text
>>> remains unaltered, yet spammer does appear in the page's history as a
>>> contributor and therefore the page is said to have been newly
>>> revised).
>>>
>>> What would be the right config lines to block such a possibility ?
>>> I would like to implement that rule : for other than admin, if page is
>>> not modified then dont allow saving it.
>>>
>>> Might the deltapagesize function (I'm using
>>> http://www.pmwiki.org/wiki/Cookbook/DeltaBytesRecentChanges) be
>>> completed, so that 0 modification means saving is unallowed ? Or is it
>>> doable to use Spamfilters Post Size option ?
>>>
>>> Thank you.
>>>
>>> ___
>>> pmwiki-users mailing list
>>> pmwiki-users@pmichaud.com
>>> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>>
>>
>>
>>
>> --
>> Dominique
>
>
>
>
> --
> Dominique

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Don't allow saving guest post for 0 modification

[ABClf]

Hello,

I'm facing a bit of spam on my wiki.
For my defense, I use blocklist and Petko's Spamfilters cookbook.

Problem is I have spammer posting unmodified pages (original text
remains unaltered, yet spammer does appear in the page's history as a
contributor and therefore the page is said to have been newly
revised).

What would be the right config lines to block such a possibility ?
I would like to implement that rule : for other than admin, if page is
not modified then dont allow saving it.

Might the deltapagesize function (I'm using
http://www.pmwiki.org/wiki/Cookbook/DeltaBytesRecentChanges) be
completed, so that 0 modification means saving is unallowed ? Or is it
doable to use Spamfilters Post Size option ?

Thank you.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Allow only one IP range at specific page.

[ABClf]

Try the whitelist solution on this page
http://www.pmwiki.org/wiki/PmWiki/Security

Gilles.
Le 17 nov. 2015 18:01, "James Almeida"  a écrit :

> Hello PmWiki users,
>
> I need to only one ip range in an specific page of a wiki. Is that
> possible?
>
> Its a research group wiki. I need to do that to allow viewers within the
> university to access the list of available projects, but not anyone outside
> the university, due to IP concerns.
> I read about the Blocklist implemented in the PmWiki, but it seems to be
> wiki-wide, and not for specific page.
>
> Thank you for your attention!
> --
> _
>  Dr. James Moraes de Almeida
>  Postdoctoral researcher at Theory and Simulation of Materials (THEOS).
>  École Polytechnique Fédérale de Lausanne (EPFL).
>  Direct: +41 21 693 1126
> *¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯*
> *¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯*
> *¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯**¯*
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
>
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Style is not loaded

[ABClf]

adblock might be the culprit. Try disabling it.
At least, on my chrome browser, i dont encounter anymore issue when
visiting your website when having it disabled.
I dont know the reason.

2015-10-22 14:22 GMT+02:00 Rus :
> Rus  gmail.com> writes:
>
>>
>> I'm install pmwiki on my site (wiki.axis.bplaced.net) and site is normally
>> displayed only in IE (11).
>> In Chrome, FireFox, Opera (Presto), Opera (Chromium) site loaded without
>> layout.
>>
>> How I can fix it?
>>
>
> Screenshot problem
> Vivaldi (Chromium)
> http://oi58.tinypic.com/2mfjazk.jpg
>
> IE 11
> http://oi58.tinypic.com/2edqf7c.jpg
>
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PageList vs WikiForm for multi-line variables

[ABClf]

To my knowledge, this :ptv: is not multiline
(see http://pmichaud.com/pipermail/pmwiki-users/2006-September/033404.html)

It might be possible (not by me though) to rewrite the :ptv: regex to
get the result you are expecting (but, how to treat the last
occurence, when there is not anymore :ptv: ?)



2015-10-03 21:06 GMT+02:00 Thierry :
> Hi,
>
> i am using pmwiki to manage various things for a while now and, well,
> thanks a lot for this great tool!
>
> I encountered a problem that i was not able to fix by myself: i am using
> WikiForm to let the users create pages that define some page text
> variables automatically. In particular, one of the variables is named
> 'Abstract', and the corresponding entry in the FormTemplate is
>
> :Abstract:abstract (text=10*62)
>
> so that the user can enter a small multi-lines text, not a single line
> (and the ViewTemplate understands that well).
>
> In my PageList template, i want to list those pages according to some
> variables (e.g. "Date", "Room", ...) and also print the content of the
> "Abstract" variable, so i am using "{=$:Abstract}" in the
> PageListTemplates.
>
> The problem is that, PageList only prints the first line of the abstract,
> since, unlike WikiForm, it probably considers that only what is on the
> same line that "^:Abstract:" is the content of the "Abstract" variable,
> not the following lines.
>
> My question is: how to let PageList understand that the content of the
> "Abstract" field is all the lines that appear between ":Abstract:" and the
> definition of the next variable in the page ?
>
> Ciao,
> Thierry
>
>
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki for a Writer? (Long)

[ABClf]

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 :
> 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@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Strange issue with PageListSortCmp

[ABClf]

I'm playing with data, and I'm facing a strange issue with PageListSortCmp :

I want to pagelist in Words group (named : Bob), extract numerical ptv
(named : registre_origine, which value, when not empty, is set from 1
to 10) and order the result from 1 to 10, or 10 to 1.

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).

http://www.languefrancaise.net/Test/Registre

When I edit the page stocking the broken data (in my example, it would
be the page stocking the x (empty) value, I don't see the problem, the
ptv registre_origine is not empty and has a regular value).


I note that the same pagelist, with no order param, has no issue
(:pagelist group=Bob link=Source.2048  $:registre_origine=- fmt=#registre:)


That is not a huge pagelist yet it's a quite big one. Might it be the issue ?
(:pagelist group=Bob link=Source.2048  $:registre_origine=-
fmt=count:) gives me : 1332
and
(:pagelist group=Bob link=Source.2048  fmt=count:) gives me 2817.

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] AuthUser / Multiple login's required ?

[ABClf]

Have you tried to fix it and how ?

2 paragraphs in http://www.pmwiki.org/wiki/PmWiki/Troubleshooting for
similar kind of trouble ;
you might want to investigate session and order in config php.

(I dont use such password system ; just suggesting something you might
not be aware of.)

Gilles.

2015-08-20 19:42 GMT+02:00 William Langford unf...@gmail.com:
 'lo!

 Been using pmwiki for some time.  Big thumbs up :D

 For a particular wiki, it's a private one (gotta log in even for read
 access).

 A month ago or so, I moved this wiki's to AuthUser based logins.  My users
 have noted that when accessing the wiki, they'll typically have to login
 multiple times in order to do stuff.

 Lets say that user 'bob' wants to access the wiki.  Bob goes to
 http://my.wiki/

 It demands a password.  Bob logs in as 'bob' with password 'whatever'.  And
 he is presented with the main page as expected.

 Somewhere on this main page is :

 * [[Main.HomePage?action=logout | Log Out: {$AuthId}]]

 And it renders in the browser just fine as Log Out: bob.

 Bob then tries to click on (read/browse) on any of the existing wiki groups
 ( such as [[SuperSecret/SuperSecret]] or [[PmWiki/FAQ]] ), and is asked to
 log in again.  Of if Bob had attempted to search, it would ask for login
 information again.

 I've tried searching on pmwiki.org and through the mailing list without too
 much luck on finding out if getting rid of this log in twice to do
 anything stuff is all me or something simple I'm missing, or what ?

 Thanks!

 -Will / unfy

 -

 This is a stand a lone wiki (not apart of a farm).

 PHP 5.3.28 / Apache 2.2.3

 Status   PmWiki version pmwiki-2.2.77 (VersionNum?=2002077)

 SiteAdmin/AuthList  doesn't appear to have anything magical in it.

 Most group attributes (save siteadmin etc) are:

 Set new read password:(set by site) id:*
 Set new edit password:(set by site) id:*
 Set new attribute password:(using edit password)
 Set new upload password:(set by site) id:*

 config.php:
 $DefaultPasswords['admin'] = ...;
 $DefaultPasswords['edit'] = ...;
 ... etc ...
 $DefaultPasswords['read'] = 'id:*';
 ... etc ...

 include_once($FarmD/scripts/authuser.php);

 #EOF

 ___
 pmwiki-users mailing list
 pmwiki-users@pmichaud.com
 http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Foldered wiki.d Page Store for more than 100k pages in a group

[ABClf]

Great ;)

tested and working ;
I have had to update the dir upload as well :
$UploadPrefixFmt = '/$Group/{$DirPrefix}/$Name';

Thank you so much for your support.


2015-08-06 22:42 GMT+02:00 Petko Yotov 5...@5ko.fr:
 On 2015-08-06 19:10, ABClf wrote:

 $WikiDir = new PageStore('wiki.d/{$Group}/{$Name1}/{$FullName}');

 My biggest group is for Quotes ; pages are named numerically, from 1,
 2, 3, etc., to 99500 (still growing) ;
 I would like the coming next pages named 10 and up to be saved in
 folder /11, /12, etc., rather than in folder /1 ;


 You can create a custom PageVariable and use it when defining the PageStore
 class.

   function DirPrefix($group, $name) {
 if ($group == 'Quotes'  preg_match('/^(\\d+)\\d{4}$/', $name, $m))
   return $m[1]; # = 10

 return function_exists(utf8string)
   ? utf8string($name, 0, 1)
   : $name{0};
   }
   $FmtPV['$DirPrefix']  = 'DirPrefix($group, $name)';
   $WikiDir = new PageStore('wiki.d/{$Group}/{$DirPrefix}/{$FullName}');

 This will keep the current directories with the first letter, in all groups.
 For pages in the Quotes group, for names longer than 4 digits, it will
 remove the last 4 digits, so

   Quotes.9will go into wiki.d/Quotes/9/
   Quotes.11   will go into wiki.d/Quotes/10/   (not /11)
   Quotes.99   will go into wiki.d/Quotes/99/
   Quotes.222  will go into wiki.d/Quotes/222/
   Quotes.98765432 will go into wiki.d/Quotes/9876/

 This will also take care of the same problem when you go above 99. :-)

 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).


 ___
 pmwiki-users mailing list
 pmwiki-users@pmichaud.com
 http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Hide or avoid message error for pagelist format using a new markup

[ABClf]

Hello hello,

I have set up a new basic custom markup for repeating a given string X times.
In config :

# markup {(repeat + 10)} - ++
$MarkupExpr['repeat'] = 'str_repeat($args[0],$args[1])';

Now, I'm defining a new pagelist format, in Site/LocalTemplates page,
which is going to take a numerical ptv as a quantifier for my repeat
markup, this way (I'm willing to repeat the sign plus X times) :

{(repeat + {=$NbSource})}

It's working, but an error message does now appear on my
Site/LocalTemplates page, because the new markup is expecting a
numerical value (I guess) :

 Warning: str_repeat() expects parameter 2 to be long, string given in
/home/www/dev6/scripts/markupexpr.php(101) : eval()'d code on line 1

How to get this cosmetic issue solved, the best way ?
Is it possible to hide error messages for that page or for that kind
of error (using dedicated error_reporting maybe ?)
or to get custom markup, on that page, non interpreted by pmwiki ?

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Hide or avoid message error for pagelist format using a new markup

[ABClf]

Perfect. Thank you Petko.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Foldered wiki.d Page Store for more than 100k pages in a group

[ABClf]

Hello,

because I use a lot of small files, I have choosen a foldered wiki.d ;
so, in config :

$FmtPV['$Name1']  = 'function_exists(utf8string) ? utf8string($name,
0, 1) : $name{0}';
$WikiDir = new PageStore('wiki.d/{$Group}/{$Name1}/{$FullName}');

My biggest group is for Quotes ; pages are named numerically, from 1,
2, 3, etc., to 99500 (still growing) ;
I would like the coming next pages named 10 and up to be saved in
folder /11, /12, etc., rather than in folder /1 ;

Well, well, well ;)
does someone know an easy way to get it done ?
Maybe something like that would be fine ?

define a new Name2 variable and use if else switch depending on the
name's length :

$FmtPV['$Name2']  = 'function_exists(utf8string) ? utf8string($name,
0, 2) : $name{0}';
if name [0-9]{6} new PageStore('wiki.d/{$Group}/{$Name2}/{$FullName}');
else
new PageStore('wiki.d/{$Group}/{$Name1}/{$FullName}');

If yes, how to write the if else statement in config ?

Thank you,
Gilles.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Access to Profiles group gets redirected

[ABClf]

I would suggest, as a first step, you disable your config.php (rename it),
then recheck your website.

If all is fine, thus you have to control your config file, especially what
is related to rights and users.

I suspect you will have to reread documentation about user authentification
script you use.
Profiles group might be protected such a way non logged in visitors will be
redirected to default page.

Gilles.



2015-07-15 23:34 GMT+02:00 Alex alexw...@szokesandor.hu:

 Hi Everybody,

 I have a silly situation. I have just installed a brand new pmwiki and
 after creating some User pages in the Profiles group, I cannot access
 without logging in.I can read and edit after logging in.
 When I request the page e.g.
 http://eltajolok.hu/index.php?n=Profiles.Alex It gets redirected to the
 default group.home page Why???


 The other strange thing is the cookbook analyze.php. I have installed
 and added the secret code, but does not work

 I have pmwiki-2.2.77.tgz installed.

 Alex

 ___
 pmwiki-users mailing list
 pmwiki-users@pmichaud.com
 http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Pagelist Question

[ABClf]

I guess I get it working with these 2 steps :
in config :


function IntegerNameCompare($x, $y) {
  # get integer value of the page name or title
  $xval = intval(PageVar($x, '$RevCount'));
  $yval = intval(PageVar($y, '$RevCount'));
  # compare integer values
  if($xval  $yval) $c = 1;
  elseif($xval  $yval) $c = -1;
  else $c = 0;
  return $c;
}
$PageListSortCmp['revcount'] = 'IntegerNameCompare($x, $y)';


And working pagelist example :

(:pagelist group=Argot count=20 order=-revcount:)



2015-07-15 17:06 GMT+02:00 Monte Padget m_pad...@hotmail.com:

 I am trying to make a page that would show the pages with the most
 revisions. I have added $RevCount into my config.php and have tried various
 iterations of the line:

 (:pagelist group=Group order=$RevCount count=10 fmt=#simple list=normal:)

 but not getting the expected list. I have added {$RevCount} to a couple
 pages I know have high revision counts, but the list doesn't reflect.

 Any help or direction would be greatly appreciated.

 Thanks,
 -Monte

 ___
 pmwiki-users mailing list
 pmwiki-users@pmichaud.com
 http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] table of contents on pmwiki.org

[ABClf]

Tables of content are not very frequent on pmwiki website pages.
Many of them, if not all, are hard coded : see source code for these pages,
for example :
http://www.pmwiki.org/wiki/PmWiki/AvailableActions?action=source
http://www.pmwiki.org/wiki/PmWiki/Features?action=source

A few recipes may be of help when you need something more automatic :
http://www.pmwiki.org/wiki/Category/TOC

In my case I like very much Petko's recipe, discreet and full of features :
http://www.pmwiki.org/wiki/Cookbook/AutoTOC

Gilles.

2015-07-09 18:31 GMT+02:00 Selah Lynch selah.w...@gmail.com:

 Hi,
 I really like the table of contents that is used by pmwiki.org
 Anybody know which cookbook is used to generate it?

 Thanks!
 Selah

 ___
 pmwiki-users mailing list
 pmwiki-users@pmichaud.com
 http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PHP version for PmWiki

[ABClf]

Or try to update your php version on ovh ; this should be easy step :
try https://www.ovh.com/fr/g1207.configurer-php-web

2015-06-19 15:27 GMT+02:00 Bernard Bel bernar...@gmail.com:

 Hello,

 I was a subscriber of this list in 2012 after enthusiastically converting
 old wikis to PmWiki.  I have just subscribed again because I am facing a
 serious problem. My apologies if the issue has already been raised on this
 list!

 In France, OVH, the foremost service provider, announced that after 24
 September 2015 they will no longer support PHP 5.3 and earlier versions.

 I upgraded the wikis I am in charge of and noticed that they still run
 under PHP 5.3.  Version 5.4 yields error messages due to an obsolete manner
 of passing variable pointers in functions. In my conventional web design,
 for instance, I had to replace calls such as

str_replace($this,$that,$line,$count)

 with:

str_replace($this,$that,$line,$count)

 I notice that PHP code is often using the '' addressing and it does not
 look easy to change all occurrences...

 So, my question is: is there a chance that we get a new version of PmWiki
 supporting PHP = 5.4 before September 24?

 Otherwise, which new piece of software should we use to migrate from the
 obsolete PmWiki?

 Your advice will be greatly appreciated!

 Bernard Bel bernard@lpl-aix.fr
 Ingénieur de recherche
 Laboratoire Parole et Langage
 http://lpl-aix.fr
 UMR 7309 CNRS - Université d'Aix-Marseille
 13604 Aix-en-Provence (France)

 Founder member, Special Interest Group on Speech Prosody (SProSIG)

 Designer and curator, Speech  Language Data Repository (SLDR)
 http://sldr.org

 Bol Processor project
 http://bolprocessor.sourceforge.net
 ___
 pmwiki-users mailing list
 pmwiki-users@pmichaud.com
 http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PHP version for PmWiki

[ABClf]

Hummm... according to PmWiki/Requirements, what you need for running pmwiki
new install is pretty basic and I guess all recent versions support php 5.3
thus you might not be targeting the real issue


   1. PHP http://php.net/ 4.3 or later
  - PHP 5 or later is recommended
  - for PHP 5.5 compatibility use the current version of PmWiki


In real life, just install a new independant pmwiki instance somewhere on
your account, so you can test.
If it's working, try copying there in wiki.d some data. Check what trouble
are happening. Pay special attention to encoding (utf8).

​Issues you encounter are likely to be related to something else than php
version : your own modifications maybe ? or the recipes you use ? or
encoding trouble ?​



2015-06-19 16:28 GMT+02:00 Bernard Bel bernar...@gmail.com:

 Thank you Michael!

 I had installed PmWiki version 2.2.74 on 31 March 2015 and it would not
 run under PHP 5.4

 Version 2.2.76 accepting PHP 5.5 is very good news!

 We use the Barthelme theme (http://www.plaintxt.org/themes/barthelme/),
 no particular cookbook.

 I found it worrying not to find a list of PmWiki versions along with
 supported PHP versions.

 All the best

 Bernard Bel


 On 19 juin 2015, at 15:50, michael paulukonis xraysmalev...@gmail.com
 wrote:

  The current version of PmWiki - 2.2.76 - is compatible with PHP 5.5 per
 http://www.pmwiki.org/wiki/PmWiki/Requirements
 
  Are you referring to code in PmWiki, or of cookbook extensions?
 
  What version of PmWiki are you running?
 
  -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 Fri, Jun 19, 2015 at 9:27 AM, Bernard Bel bernar...@gmail.com
 wrote:
  Hello,
 
  I was a subscriber of this list in 2012 after enthusiastically
 converting old wikis to PmWiki.  I have just subscribed again because I am
 facing a serious problem. My apologies if the issue has already been raised
 on this list!
 
  In France, OVH, the foremost service provider, announced that after 24
 September 2015 they will no longer support PHP 5.3 and earlier versions.
 
  I upgraded the wikis I am in charge of and noticed that they still run
 under PHP 5.3.  Version 5.4 yields error messages due to an obsolete manner
 of passing variable pointers in functions. In my conventional web design,
 for instance, I had to replace calls such as
 
 str_replace($this,$that,$line,$count)
 
  with:
 
 str_replace($this,$that,$line,$count)
 
  I notice that PHP code is often using the '' addressing and it does not
 look easy to change all occurrences...
 
  So, my question is: is there a chance that we get a new version of
 PmWiki supporting PHP = 5.4 before September 24?
 
  Otherwise, which new piece of software should we use to migrate from the
 obsolete PmWiki?
 
  Your advice will be greatly appreciated!
 
  Bernard Bel bernard@lpl-aix.fr
  Ingénieur de recherche
  Laboratoire Parole et Langage
  http://lpl-aix.fr
  UMR 7309 CNRS - Université d'Aix-Marseille
  13604 Aix-en-Provence (France)
 
  Founder member, Special Interest Group on Speech Prosody (SProSIG)
 
  Designer and curator, Speech  Language Data Repository (SLDR)
  http://sldr.org
 
  Bol Processor project
  http://bolprocessor.sourceforge.net
  ___
  pmwiki-users mailing list
  pmwiki-users@pmichaud.com
  http://www.pmichaud.com/mailman/listinfo/pmwiki-users
 


 ___
 pmwiki-users mailing list
 pmwiki-users@pmichaud.com
 http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] name a page Gb or GB makes encoding chinese issue (fastcache recipe involved)

[ABClf]

Hello,

I'm struggling for hours with an annoying and strange encoding issue for a
few pages, at this time only for pages which are cached by fastcache recipe
AND (that is the funny part) are named Gb or GB (my initials).

This is probably be a fastcache recipe limited issue, but there is
something very special here as it sounds like it does happen only for pages
names Gb or GB, no matter the group they belong to (tested with Profils and
Test).

For these pages, when user is anonym, fastcache quickly serves a cached
version of the page where special characters have become chinese ones.
For other pages, including GbTest, all is fine (if I'm not wrong).

After struggling and struggling, I found out that gb2312 and gbk (and maybe
others) are chinese encoding and I guess I have found the culprit ; thus it
might have to do with some function used by fastcache for generating its
cached page. Many of them use PmWiki mecanism.

What do you think ? is gb used for pagename the culprit ?
Any idea how to fix it, or do I have to change my name ? ;)
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Text extract, Hans' recipe

[ABClf]

Hans,

I donwloaded Text Extract last version 2015-06-05 and now I'm getting some
error messages which don't appear when using version 2014-02-22 (same host,
same config) :

Warning: Cannot modify header information - headers already sent by (output
started at /home/www/dev6/cookbook/extract.php:1) in
/home/www/dev6/scripts/caches.php on line 32

Warning: Cannot modify header information - headers already sent by (output
started at /home/www/dev6/cookbook/extract.php:1) in
/home/www/dev6/pmwiki.php on line 1229

I'm using last pmwiki and php 5.4.

Thank you,

Gilles.
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users