Patrick
a thoroughly reasoned discussion, a result of which is that I support the
approach of using a page text variable, where the variable is automatically
added to the page when it is saved for the first time (either as a draft or
a final version).
thanks
Simon
On 23/02/2008, Patrick R. Michaud
Em Sexta 22 Fevereiro 2008 19:31, você escreveu:
> Interesting. I added SiteFooter in there because I saw it in some other
> skins during my learning process. Of course, now I don't remember which
> ones :)
Please try to remember, at least one skin. :)
Carlos
>> I didn't realize that. So, as a skin creator, what would a 'standard'
>> skin header/footer look like? Simply like this?
>
>>
>
> What use does it have?
>
> I don't think we have a standard nomenclature for skin subpages.
> I use PageHeader, PageFooter, PageTopMenu, PageFootMenu et
On Thu, Feb 21, 2008 at 04:48:59PM -0500, Sameer Kumar wrote:
> Kathryn wrote:
> > If you want links to non-existent pages to link to the page, but without
> > the edit action, then add the following to your local/config.php:
> >
> >$LinkPageCreateFmt = "\$LinkText";
>
>That works. Howev
Saturday, February 23, 2008, 12:39:56 AM, Jody Klymak wrote:
> I found the documentation a little vague in that "posting" would add
> incrementally to a page. I would have benefited from a paragraph
> explaining the basic functionality before going into the parameters,
> etc. Perhaps this is
Thanks Hans and Randy,
> using Fox a form could look something like this in markup:
>
> (:fox frm target=TargetPageName redirect=1:)
> (:foxtemplate "||{$$name}} ||{$$address} ||{$$email ||":)
> ||
> || Name:||(:input text name size=30:) ||
> || Address:||(:input text address size=30:) ||
On Fri, Feb 22, 2008 at 05:36:34PM +, imoc wrote:
> In wiki logic, I do understand what Marc concerned. But the 'page creator'
> is not just for pure wiki collaborating environment. It was asked for a
> website engine which can be used to build wiki as well as blog and forum.
> And the logic
Friday, February 22, 2008, 10:31:23 PM, DaveG wrote:
> I didn't realize that. So, as a skin creator, what would a 'standard'
> skin header/footer look like? Simply like this?
>
What use does it have?
I don't think we have a standard nomenclature for skin subpages.
I use PageHeader, Pa
Not using PmWiki, but Trac (http://trac.edgewall.org/) integrates very
well with Subversion (and other source control systems).
~ ~ Dave
Jan Erik Moström wrote:
> I want to set up a issue tracker on personal site. I looked at
> the cookbook and found three recipes PITS, JITS and Yeats ...
>
Firstly, as the creator of the Marinee port, sorry you had so much
trouble with the skin. Glad we now have a solution -- I'll update the
skin with a permanent fix (plus others I've done).
> Try to replace every call in the skin for SiteHeader and SiteFooter as shown
> bellow.
>
> replace this
Em Sexta 22 Fevereiro 2008 13:35, David Spitzley escreveu:
> Ok, it appears that the skin was to blame; I've now got comments and
> comment forms showing up only once, and in the content area in the where I
> want them, so I'm happy. I'm still puzzled at the difference in behavior
> between http:/
I want to set up a issue tracker on personal site. I looked at
the cookbook and found three recipes PITS, JITS and Yeats ...
should I use one of these (recommendations?) or should I do it
in some other way?
I'm the only user of this site and the issue tracker is going to
be used for software d
In the sample-config.php section dealing with $AutoCreate, is there a way of
having automatically created pages in the Category group use the GroupTemplate?
I haven't been able to find any on $AutoCreate variable syntax in the
documentation.
David
In wiki logic, I do understand what Marc concerned. But the 'page creator'
is not just for pure wiki collaborating environment. It was asked for a
website engine which can be used to build wiki as well as blog and forum.
And the logic on authorship in those kinds of website are not that same.
On Fri, Feb 22, 2008 at 10:24 AM, <[EMAIL PROTECTED]> wrote:
>
> Tegan Dowling wrote:
> > Organization wants a calendar that volunteers can use to sign up for
> > available slots on the schedule. The calendar would display which
> > slots are taken, but not by whom. The mechanism for taking a
Hans wrote:
>> change the footer section from this:
>>
>>
>>
>>
>>
>> To this:
>>
>>
>>
>>
>>
>> And see how it goes.
>
> There should really not be any inclusion of Groupfooter or SiteFooter
> and GroupHeader or SiteHeader in a skin template.
>
> GroupHeader and GroupFooter
marc wrote:
> My view on this is that it should not be part of PmWiki's core, but a
> recipe for those that really need it - although I think they should
> fight it long and hard.
>
> As an aside, the original author can always be derived from action=diff.
No, it cannot. The history expires a
Ok, it appears that the skin was to blame; I've now got comments and comment
forms showing up only once, and in the content area in the where I want them,
so I'm happy. I'm still puzzled at the difference in behavior between
http://www.davidaspitzley.org/potatopatch/ and
http://www.davidaspitz
What skin are you using? It may list it twice.
Does the group footer (:include:) the site footer?
There are many ways to do headers and footers, and sometimes they end up
being done twice.
Sandy
David Spitzley wrote:
> At this point my basic question still remains: why does the Site Footer
>
Tegan Dowling wrote:
> Organization wants a calendar that volunteers can use to sign up for
> available slots on the schedule. The calendar would display which
> slots are taken, but not by whom. The mechanism for taking a slot
> would somehow provide the volunteer's name, etc, to the organizatio
Peter & Melodye Bowers said...
> > My view on this is that it should not be part of PmWiki's core, but a
> > recipe for those that really need it - although I think they should
> > fight it long and hard.
> >
> > As an aside, the original author can always be derived from action=diff.
> > In this
> change the footer section from this:
>
>
>
>
>
> To this:
>
>
>
>
>
> And see how it goes.
There should really not be any inclusion of Groupfooter or SiteFooter
and GroupHeader or SiteHeader in a skin template.
GroupHeader and GroupFooter pages are included in the normal
> My view on this is that it should not be part of PmWiki's core, but a
> recipe for those that really need it - although I think they should
> fight it long and hard.
>
> As an aside, the original author can always be derived from action=diff.
> In this case, at least it's in context to the chang
Hans said...
> Thursday, February 21, 2008, 6:46:40 PM, David Spitzley wrote:
>
> > Based on some earlier discussions of extending pmwiki's
> > functionality, it would probably be helpful if you were to define
> > what you think an official "page creator" role should entail.
>
> 'page creator' is
> although I found references to $EnableHTMLCache and $PageCacheDir in
> this list, I'm missing any documentation about them and about PmWiki
> internal HTML caching generally.
It definitely the official function in PmWiki, but, you are right, I can't
find any documentation either.
Here is a m
Hello All,
although I found references to $EnableHTMLCache and $PageCacheDir in
this list, I'm missing any documentation about them and about PmWiki
internal HTML caching generally.
Is this an unofficial feature or only the documentation missing?
Oliver
26 matches
Mail list logo
