and stop fragmented efforts
to do it via special markups etc.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
templates.
Not yet possible is the use of
(:include templatepage var=some data value:)
or
(:include templatepage basepage=datapage#section:)
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo
Tuesday, May 1, 2007, 10:57:20 PM, [EMAIL PROTECTED] wrote:
I can read in Fox pages on the pmwiki site, Hans, that a new version is
in dev. Can you tell us when ? Can you tell us if new cookbooks will be
compatible with old data ?
It will be a very different forum, using display templates, so
to the page the form is on, or included, by checking a string of
the markup.
Hope this makes sense. Please send in your comments about these
changes, as these security issues have been highlighted so much in
other topics, and I am striving to get Fox as secure as I can.
~Hans
.
Are you sure you got the right upload?
The recipe version is 2007-04-19 in zap.php on pmwiki.org
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
authentication system.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
You could try http://www.pmwiki.org/wiki/Cookbook/SectionEdit
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
to a document page. So maybe it is better
to leave it blank. But I would be curious to hear others about this.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Thursday, May 3, 2007, 8:41:42 PM, Hans wrote:
I am just mulling over this choice, and suspect it is no good.
As we seen, it is enough to include a form into a page by having it
added to the GroupFooter for instance. Then someone can post to the
page, even if it was protected.
Hmm, I just
can add it to pages.
The pattern array is under admin control.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
to insert a
posting permission marker on every page?
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
as
well.
For me your problem highlights that it may be better when setting up
discussion or comment pages to always use a separate group for these,
as it is difficult to change later an existing system.
But Pm might have a trick up his sleeve to answer your question
directly.
~Hans
Friday, May 4, 2007, 4:32:37 PM, marc wrote:
Hans said...
I use a group.php i.e. local/Forum.php which has a lot of group
customisations, and includes an entry to the pattern array:
$FoxNameFmt[] = 'Forum.*';
allowing posting to any page in group Forum.
I could still exempt some pages
}.*', // all pages in current group
*/
This will leave a default setup for maximum protection.
It is up to the admin to loosen the restrictions.
What do you think?
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com
is safe because he can trust all editors, and sets a '*.*' pattern
for allowing posting to all pages (still excluding the pages excluded
with - prefixes, like '-Site.*', '-PmWiki.*'.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http
to use
no string check pattern for target pages. How would you allow for
these?
That's why I did not want to mix string check patterns with pagename
patterns.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com
, and not force one way.
I will test all this with a new type forum in development, to see
these new rules at work, and see how much a hassle it is, if any.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman
, but I don't see the need yet.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Saturday, May 5, 2007, 12:21:46 PM, Hans wrote:
'Site.*' = 'none', //disallow any form actions to Site.*
'*-Talk' = 'add,delete', //we can add and delete posts to *-Talk
'Test.*' = 'all',//all form actions are allowed to Test.* pages
'*.*'= 'newedit',//new pages
the $DiffCountPerPage variable and a link to
PITS/00544
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
is
in.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
points to the AllGroupHeader page. Where have I
gone wrong?
PS: use the * for all occurrences of {*$Group} and {*$Name} or
{*$Namespaced} in your code.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman
Sunday, May 6, 2007, 10:06:00 AM, Hans wrote:
PS: use the * for all occurrences of {*$Group} and {*$Name} or
{*$Namespaced} in your code.
PPS: I meant the code in AllGroupHeader.
sorry if I am causing confusion!
~Hans
___
pmwiki-users mailing
, and some of those will
make there way into the way Fox will work and forum posts are handled.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
script?
Normally I would try to use a div with a class style:
right
Last Modified {*$LastModified} by {*$LastModifiedBy}
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
, and now hiding all
pages except what has been added.
BTW deleting Main.WikiSandbox does not remove it, as it is in
wikilib.d pagestore. I had to add it to the exclusion pattern for
normal searches.
~Hans
___
pmwiki-users mailing list
pmwiki-users
to be made in various places, and it
would be good to document this. Maybe this needs a new Cookbook page?
WikiInDisguise?
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
']['read']) /* visitor has read permission */
if ($page['=auth']['edit']) /* visitor has edit permission */
if ($page['=auth']['attr']) /* visitor has attr permission */
if ($page['=auth']['admin']) /* visitor has admin permission */
Which is the better or correct approach?
~Hans
of
pages in the Main group, as specified with default patterns.
I just fell into the trap of not logging out to see it, and
as I was logged in as editor I did see all site pages!
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http
well be to go through all page sand rewrite the
formatting to suit the new system. That is why I think with recipes like
BlogSimple which work with CommentBoxPlus the blogs are not going to
be easy to transform, as all the formatting is written into the pages.
~Hans
Friday, May 11, 2007, 9:03:45 AM, Hans wrote:
I just released a new FoxForum version
PS: I am working on the ForumX version of FoxForum, which stores each
post as a separate data page. It is nearly ready for release, I just
did not had time this week to wrap it all up.
This I would
one or the other, as they use the same markup.
No point installing both.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Saturday, May 12, 2007, 8:48:57 AM, Hans wrote:
One should only use one or the other, as they use the same markup.
No point installing both.
Sorry, the recipes use a different markup, but there is no point in
using both I think.
~Hans
add a note to the cookbook pages, if you feel the need,
about the differences.
Steven Leite wrote includeSite.php, I wrote includeurl.php.
(author names are in the files)
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http
into the template (directly into HTML)
it works.
object
data=http://www.example.com/;
width=100%
height=100%
type=text/html
/object
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com
Saturday, May 12, 2007, 12:35:54 PM, Hans wrote:
Setting height=100% in (:includeurl ...:) does not seem to work though.
I will try to fix it if possible.
It seems one needs to set a specific height for the containing div
surrounding the object, in order for a percentage height in the object
Saturday, May 12, 2007, 12:48:06 PM, Hans wrote:
It seems one needs to set a specific height for the containing div
surrounding the object, in order for a percentage height in the object
to work.
With the pmwiki default skin i managed to get
(:includeurl height=100% ...:)
to work
.
Inspired and adapted from the breakpage recipe.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
or use (:include...:) and use PTVs only on the
data-post pages. Perhaps the latter. Any thoughts on this?
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
, especially for the
breakpage feature and the count.
I know I can wrap ForumX up with using FFE, as I did for FoxForum.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
{$Group}:)
(:tableend:)(:if:)
[[#recentchanges]]
@]
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
:){=$LastModifiedBy}
(:cell class=messageitem :){=$ChangeSummary}
(:if equal {$Group}:){$$PageCount}
(:tableend:)(:if:)
[[#recentchanges]]
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki
Tuesday, May 15, 2007, 11:56:42 AM, Hans wrote:
[[#recentchanges]]
(:if expr equal {$Group}:)
(:table class=forum width=100% cellpadding=0px cellspacing=4px :)
(:cell class=messagehead :)%thd%'''Page'''
(:cell class=messagehead :)%thd%'''Last Modified'''
(:cell class=messagehead :)%thd
Tuesday, May 15, 2007, 12:07:25 PM, Hans wrote:
PS: I think the pagelist with order=$LastModified works precisely
because it is processed as order= i.e. with no order specified.
So it shows the trail links in their natural order, which is latest
changed page first.
PPS: You better ignore
may muck up the count, and please
use the conditional in the pagelist instead.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
then in the second list to
create the count range for display, and in the (:breakpagelist:)
markup to create the right number of links to all the subpages.
I hope this can be simplified in future.
Please check it out and send your comments!
~Hans
things internally--working off it's own
list of pages--which is essentially what Han's solution does (via a
preliminary pagelist).
If you refer to 'Hans solution' as the new breakpagelist.php script on
http://www.pmwiki.org/wiki/Cookbook/BreakPageList
then I need to say that this recipe does
from number 4. So this gives you an indication of the
previous and next subpage (pagelist part) to view.
It is really the same way the BreakPage recipe provides links to parts
of the page.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
are set, i.e. put your include_once lines
near the bottom of the config.php files.
If there was a reason why all these cookbook scripts need to be
loaded from farmconfig.php I apologise, as I read only these last
posts.
~Hans
___
pmwiki-users mailing
could create a farmconfig-late.php
file which holds all the include_once lines to load cookbook scripts
common to all wikis, and then add to the bottom or after the initial
customisations in the wiki's config.php:
include_once($FarmD/local/farmconfig-late.php);
~Hans
:
(:include Site.BlogTemplate heading=new entry author=Jim text=$:comment1 :)
(:comment1:
Some text
from a textarea input box.
:)
Will you still add this capability?
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http
the second example works, i.e. using the PTV in
curly brackets as option value. But it does not work on pmwiki.org,
whereas your example does.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki
textarea now
supports $InputValues
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Is fmt=count for pagelists still not part of the pmwiki core,
i.e. must be installed as separate recipe?
I had the impression it was added, but it seems not to be??
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http
('textvar::', 'split',
'/\\(::\\w[-\\w]*:(?!\\)).*?::\\)/s', '');
# add new PTV pattern for text PTV (::var:...::)
$PageTextVarPatterns['(::var:...::)'] = '/(\\(:: *(\\w[-\\w]*)
*:(?!\\))\\s?)(.*?)(::\\))/s';
~Hans
___
pmwiki-users mailing list
.
If you don't have one, create one in that directory.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
in the site group, which of course include
a few Triad skin-subpages.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
in the group, even though they are initially hidden with
the showhide toggle switch.
Hope this helps! I answered your question yesterday on the
Cookbook.CommentBoxPlus-Comments page, but you must have missed it.
~Hans
___
pmwiki-users mailing list
%;
text-decoration:underline;
}
How do I have to specify the selectquery class in the css file?
try either
.selectquery { ... } or
table.selectquery { ... }
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
PS: PmCalendar is usual installed in a group just for the calendar
pages.
http://www.pmwiki.org/wiki/Cookbook/PmCalendar
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
/a/li
/ul';
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
:
!--PageRightFmt (by Laszlo) --
!--/PageRightFmt (by Laszlo) --
could you change this to
!--PageRightFmt--
!--/PageRightFmt--
in order for (:noright:) markup to work, which uses
SetTmplDisplay('PageRightFmt', 0);
thanks!
~Hans
styles? I noticed also
than one can't search for xxx (the result is always zero)
I think there is no list of available styles.
Styles can be defined in so many different places:
wiki pages, php scripts, as css classes in css files.
~Hans
the question is how to marry popwin with gallerypicture markup.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Line2
Line3
:)
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Tuesday, June 5, 2007, 6:47:42 PM, Christophe David wrote:
Don't know why I was convinced they had to be defined on a single line ;-)
They used to be. One of the many wonderful late 2.2beta changes.
~Hans
___
pmwiki-users mailing list
pmwiki
prebuilt wiki pages with the forum system.
The folder information in the zip file should tell you the placement
of each file as well.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
%[[PageName| Label]]
or
%popwin%[[Page Name]]
without spaces after %popwin%.
Otherwise pmwiki will treat it as a wiki style, which it is not,
even though it may look like one (by design).
~Hans
___
pmwiki-users mailing list
pmwiki-users
?
I don't know.
You could try and change wikigallery markup rules in the php file
so that they get translated before popwin:
replace all instances of '|' with 'popwin1'
(make a backup first, this change may not work, I have not tested it)
~Hans
these changes to the svn repository?
I would not recommend this as a permanent change to the gallery script,
as then the gallery markup would only work if the popwindow script is
installed. It is a custom fix for you, and still needs a permanent
better solution.
~Hans
($pagename) {
$page = RetrieveAuthPage($pagename, 'read', false, READPAGE_CURRENT);
if($page[passwdread]) return true;
else return false;
}
Use in wiki page:
(:if pwread:)Page is read protected(:if:)
~Hans
___
pmwiki-users mailing list
for if a read
password is set in the page.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
be.
I did start a while back a Cookbook.DivisionsExplained page:
http://www.pmwiki.org/wiki/Cookbook/DivisionsExplained
This page is still in a raw state, but info could go there about all
things to do with division markup.
~Hans
___
pmwiki-users
to that page and add ?action=attr to the url in th ebrowser's
address bar. That will open the page attributes, where you can set a
password for 'edit'.
The layout which defines SideBar as part of the page is the skin's
tmpl template page. But you don't need to do anything there.
~Hans
it?
That may be nice, but not so easy to do.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
.
Sorry this is sketchy and needs to be filled out.
Another approach would be to use (:input:) markup to define a
commentbox, and include the captcha markup with it.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com
as an object
in a wiki page I would think.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
!
O where are you going, said reader to rider?
I am preparing a site for someone who wants to travel round the world
on bike, to promote sustainable travel.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman
be the challenge.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
the regularity of the list=normal
parameter, excluding both GroupHeader and AllGroupHeader.
Good. Site.AllGroupHeader gets my vote.
Sites using it already can just drop the recipe.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http
such information.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Friday, June 15, 2007, 11:07:43 PM, The Editor wrote:
Oops, my mistake. I thought they were being deleted as well.
well, that's why it is confusing.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman
, and there is
a Site.SiteHeader page, then that page gets used. If there is a
GroupHeader page, SiteHeader will not be used. Similar to
Group.SideBar and Site.SideBar.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com
content change.
Now this is recorded as entry in RecentChanges
and in the page history with an empty entry.
What changed is the LastModified time stamp and
LastModifiedBy author name, even though no modification has happened.
It would be nice if this behaviour could be suppressed.
~Hans
Monday, June 18, 2007, 8:50:43 PM, Patrick R. Michaud wrote:
Personally, I think that if we just suppressed the
updating of RecentChanges on same-text edits, then
everything would probably work out okay. But I'm open for
opinions here.
That would work for me.
~Hans
FoxBlog to
work?
I don't know about this modification. Where is it mentioned, and for
what purpose?
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Wednesday, June 27, 2007, 9:51:22 PM, Hans wrote:
I have a Site.FoxConfig with
*.*: all
I have a Config.php with:
$FoxAuth = 'ALWAYS';
I should point out that this will allow any site visitor
to post and change any page on the wiki.
So I would not use it for security reasons.
If you want
think it is fine to have form pages in the Site group, like a
FoxCommentForm page, and use it anywhere with a
(:include Site.FoxCommentForm:).
But the target pages should be outside Site and PmWiki groups,
as both are explicitly excluded from being permitted for posting
in fox.php.
~Hans
:
$EnableAccessCode = true;
if(CondAuth($pagename,'edit')) $EnableAccessCode = false;
to disable the access code for when you are logged in as editor,
provided you can use NewBlogPage also only if logged in.
~Hans
___
pmwiki-users mailing list
pmwiki
you
individual RightBar pages for those pages A and B.
I am not sure what you mean with if the first page shows up.
If page A is displayed, and you got a A-RightBar page, that RightBar
will be displayed.
~Hans
___
pmwiki-users mailing list
pmwiki
:)
and a Profiles.Hans page with a
[[#contact]]
Hans\\
Tel: 1234567\\
Address:\\
blabla
[[#contactend]]
The (:include ... :) markup in the group's RightBar will include the
anchored section from the Profiles page of the author named with the
Author PTV.
You don't need to use conditional markup!
I think
, the admin can loosen that restriction.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
that this will then require id=something name=something in the
markup! To make it truly optional would need some conditionals in the
script.
I did not understand why you need id and name in the form tag, so I
have no plans to change the script at this point, to provide these
options.
~Hans
more customisations straight from the markup.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
link code uses the shorter url syntax, but your wiki does
not, therefor it results in apage not found error, i believe.
This is probably a bug in Fox, as it does only cope with one form of
url at present.
~Hans
___
pmwiki-users mailing list
pmwiki
, add !--HTMLFooter-- before the /body tag in the skin
template, so the botom of the yourskin.tmpl file looks like:
!--HTMLFooter--
/body
/html
see if that helps.
Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com
by It works just like one forum for all
groups.
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
=triad
(I added ?skin=triad so you can see it from the Triad skin, and see
the relation of it to the top menu)
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
301 - 400 of 1949 matches
Mail list logo
