[pmwiki-users] Core and question marks
editor at fast.st
Sun Aug 27 18:15:56 CDT 2006
On 8/27/06, Patrick R. Michaud <pmichaud at pobox.com> wrote:
> FWIW, when people say "you have to patch pmwiki.php", it's almost
> never true in an absolute sense. One can always create a replacement
> function for LinkPage() in a local script, and have it be used
> instead of PmWiki's normal LinkPage() function. Thus
> $LinkFunctions['<:page>'] = 'MyCustomLinkPage';
> will call MyCustomLinkPage (instead of the built-in LinkPage() function)
> whenever PmWiki needs to generate a link to another page.
I was sure there was a way to do it... :) But wouldn't the above
only work for certain groups? I mean if I set this in Profiles or
Catagories.php, would it work if I had a link to ~Caveman over in
Members.SomePage? Of course, I'm willing to do a sitewide thing if
necessary, but not my first choice. And I'm not sure I have enough
info from your line of code to try and tackle this without a bit more
> If we could get PageExists() to always return "yes" for pages
> in the Category, Profiles, or other groups, then the link markup
> would just do the right thing. It also might work better for
> other markups or functions that need to deal with "virtual"
> pages such as these, rather than simply putting special
> exceptions throughout the rest of the code.
This is more what I had in mind. The FAST Data Project is really so
powerful right now I'm thinking about using it for about 90% of my
site. Profiles, Blogs, Forums, etc all dynamically created by
retrieving data from user submitted forms. In other words, a good
portion of my site is soon going to fall into this category of
existing non-existant pages!
Thanks for your help. Even a simple way to disable it sitewide for
now--like somehow changing the style that makes it all dotted
underlined? And by default going to browse not edit.
More information about the pmwiki-users