phpwiki-talk

[Phpwiki-talk] plugin trouble

[Tara S. <te...@cl...>]

There, the migration to phpwiki 1.3.1 is done!

I have plugin problems, though:=20
http://www.climbtothestars.org/spirolattic/index.php/LikePages?page=3DBac=
kLinks

and if I try inserting <?plugin BackLinks?> in a page, nothing happens.

Is this supposed to be broken?

I was also wondering if there was a WikiPage somewhere about InterWiki=20
(I don't think it's shipped in the PhpWiki 1.3.1 package, but was there=20
one somewhere on PhpWiki?)

Thanks a lot,

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

[Phpwiki-talk] Wiki Archiving feature

[Aredridel <are...@nb...>]

I've been thinking about adding an "Archive this Page" feature to
NBTSWikiWiki.  I'm not sure what it'll do to the community there, having the
effective ability to "hide" what's been said, and "clean the slate" with
almost no effort, and no actual loss.  The archives would be linked to from
the bottom of the page, perhaps, and just a click away, and in sequential
order, and I think, serial numbered -- On our wiki, certain pages tend to be
manually archived often, "Don'tQuoteThat" and "PoetryMarathon" in
particular, since they're a sort of scrolling, newest-post-at-one-end type
of page, very messageboard-like, but more wikiish, since they're not
meta-content but actual content instead.

What do you think?
	Aredridel

Re: [Phpwiki-talk] xhtml-compliant wiki

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:


> Were there changes in the CSS related to xhtml compliance?


well, let's put it like this. I don't support 4.x browsers, so I hide my=20
stylesheet using the so-called @import hack.

the stylesheets which came with the script seemed pretty complex and had=20
lots of useless classes for me, so it was simpler to re-write from=20
scratch. Plus, I simplified the html templates too (I try to avoid using=20
tables for layout, so I look for alternate solutions).

so let's say it would be possible to use templates similar to the=20
existing ones with xhtml-compliant code, but they are uselessly heavy imh=
o.

I guess it wouldn't take too long, based on the html templates I have,=20
to write a css sheet to give the wiki a look similar to the actual 1.3.1=20
  one (give or take a few details).

not sure if I answered your question though. The main reason I redid the=20
css is that I take a "minimalistic" approach towards html and css.

er... not sure that answered either

*goes back to migrating wiki pages*

Tara




--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] xhtml-compliant wiki

[Jeff D. <da...@da...>]

On Sun, 11 Nov 2001 16:52:44 +0100
"Tara Star" <te...@cl...> wrote:


> Actually, I haven't changed DBA.php - were you thinking of PearDB.php?

Yes, that is what I meant.  (Think-o on my part.)
 
> Should I really mail them or can you retrieve them yourself with the 
> links I gave in the last mail? (asking because I have no local copy of 
> them, so I'll have to download-save-rename-email). Don't mind doing it 
> though.

It's not a big deal, so don't go to great lengths.

> I re-did the templates and css almost from scratch, so I'm not sure how 
> useful they'll be to you.

Were there changes in the CSS related to xhtml compliance?

Re: [Phpwiki-talk] Element() and QElement() in lib/stdlib.php - extra OT question

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:

[snip]
> So you should use Element() when the HTML element you're producing
> contains
> sub-elements, and QElement() when the elements contents are plain text.
>=20
> Does that help?


yes!!!

Extra question:

I have two languages on my wiki, often mixed on the same pages. I'd like=20
a way to allow users to specify that a bloc of text is a given language,=20
for example by inserting [en] or [fr] in front of a paragraph.

The wiki would then parse these little tags, and depending on something=20
in the preferences setting, would show one of them (or both!) as a=20
little flag or well... anything (that's not the difficult part). Like=20
that people who only speak one language can make their language (or at=20
least blocks defined as their language) more visible.

My question is: where in the wiki script would such parsing be done? in=20
transform.php? what kind of "tag" could be used, which wouldn't=20
interfere with the rules already in place? (e.g. [en] and [fr] are nice,=20
but the wiki will try to make them into pages...)

If you have any ideas on the question, I'd love to hear them!
Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] xhtml-compliant wiki

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:

> On Sun, 11 Nov 2001 13:22:15 +0100
> "Tara Star" <te...@cl...> wrote:
>=20
>=20
>>As far as I see, my wiki now produces xhtml-compliant code.
>>
>=20
> Cool!  When I have time (probably Wednesday) I'll look at your changes
> and try to merge them into the main code.
>=20
> If you could mail me a copy of all the files you've changed,
> (including lib/WikiDB/backend/DBA.php, too)  it would help a lot.


Actually, I haven't changed DBA.php - were you thinking of PearDB.php?

I don't think I've changed any pages other than the ones I mentioned in=20
my last mail (if I did, it must have been small changes like replace=20
<hr> with <hr />... I have a vague recollection of doing that in another=20
file, but I can't for the life of me remember which one it could have bee=
n).

Should I really mail them or can you retrieve them yourself with the=20
links I gave in the last mail? (asking because I have no local copy of=20
them, so I'll have to download-save-rename-email). Don't mind doing it=20
though.

I re-did the templates and css almost from scratch, so I'm not sure how=20
useful they'll be to you.

Tara aka Steph




--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] Element() and QElement() in lib/stdlib.php

[Jeff D. <da...@da...>]

On Sun, 11 Nov 2001 12:42:35 +0100
"Tara Star" <te...@cl...> wrote:

> Can anybody tell me what the difference between Element() and QElement()

> functions in lib/stdlib.php is? I've seen the code difference, but I'm 
> not sure when one should use Element and when one should use QElement.

It looks like you've figured out the answer already but just in case:
The only difference is that QElement runs the element contents through
htmlspecialchars().  Htmlspecialchars() encodes characters like '<', '>',
'&', etc... as HTML entities ('&lt;', ...).

So you should use Element() when the HTML element you're producing
contains
sub-elements, and QElement() when the elements contents are plain text.

Does that help?

Re: [Phpwiki-talk] xhtml-compliant wiki

[Jeff D. <da...@da...>]

On Sun, 11 Nov 2001 13:22:15 +0100
"Tara Star" <te...@cl...> wrote:

> As far as I see, my wiki now produces xhtml-compliant code.

Cool!  When I have time (probably Wednesday) I'll look at your changes
and try to merge them into the main code.

If you could mail me a copy of all the files you've changed,
(including lib/WikiDB/backend/DBA.php, too)  it would help a lot.

Re: [Phpwiki-talk] extra "www*

[Jeff D. <da...@da...>]

On Sun, 11 Nov 2001 14:13:16 +0100
"Tara Star" <te...@cl...> wrote:

> I usually don't put the "www" in front of my domain name, like 
> http://climbtothestars.org/newwiki/
> 
> Unfortunately, once I am in the wiki, I get an "automatic" www. It's 
> probably got to do with the server settings, but it might make it easier

> for me to explain to the sysadmin if I know where/how BASE_URL is
defined.
> 
> Where does it happen?

If you don't want to bug your sysadmin, you can set
SERVER_NAME in index.php.
Change
//define('SERVER_NAME', 'some.host.com');
to
define('SERVER_NAME', 'climbtothestars.org');

If you don't set SERVER_NAME, it defaults (in lib/config.php) to the
$SERVER_NAME which contains Apache's idea of the canonical server host
name.  This is probably set by a line like:

  ServerName www.climbtothestars.org

somewhere in an Apache config file.

[Phpwiki-talk] extra "www*

[Tara S. <te...@cl...>]

I usually don't put the "www" in front of my domain name, like=20
http://climbtothestars.org/newwiki/

Unfortunately, once I am in the wiki, I get an "automatic" www. It's=20
probably got to do with the server settings, but it might make it easier=20
for me to explain to the sysadmin if I know where/how BASE_URL is defined=
=2E

Where does it happen?

Thanks in advance,

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

[Phpwiki-talk] xhtml-compliant wiki

[Tara S. <te...@cl...>]

As far as I see, my wiki now produces xhtml-compliant code.

http://climbtothestars.org/newwiki/ (there is a validation link on each=20
page, tell me if you find invalid pages)

I changed:

css: http://climbtothestars.org/newwiki/wiki.css
templates: http://climbtothestars.org/newwiki/templates/
transform.php: http://climbtothestars.org/newwiki/lib/transform.phps
stdlib.php: http://climbtothestars.org/newwiki/lib/stdlib.phps

Feel free to peek and use. I've really hacked it nastily, so don't=20
expect it to be elegant. I've tried to comment the places I changed.

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

[Phpwiki-talk] Element() and QElement() in lib/stdlib.php

[Tara S. <te...@cl...>]

Can anybody tell me what the difference between Element() and QElement()=20
functions in lib/stdlib.php is? I've seen the code difference, but I'm=20
not sure when one should use Element and when one should use QElement.

thanks

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] <u>

[Jeff D. <da...@da...>]

On Sat, 10 Nov 2001 22:38:09 +0100
"Tara Star" <te...@cl...> wrote:

> Can somebody tell me in which file the <u>...</u> tags are put around 
> non-linked WikiWords?

In file lib/stdlib.php, function LinkUnknownWikiWord().
(Look for the 'Element('u', $linktext)'.)

Re: [Phpwiki-talk] transform.php

[Jeff D. <da...@da...>]

On Sat, 10 Nov 2001 22:24:55 +0100
"Tara Star" <te...@cl...> wrote:

 
> function wtt_bracketlinks($match, &$trfrm)
> {
>     $link = ParseAndLink($match);
>     if (strstr($link['link'], "</form>")) {
>         // FIXME: BIG HACK: see note in wtm_plugin.
>         return "</p>" . $link['link'] . "<p>";
>     }
>     return $link["link"];
> }

If you read pgsrc/MagicPhpWikiURLs, you'll see that things like
'[phpwiki:TitleSearch?s=()]' gets transformed to a form.
The transformation is done by MakeWikiForm and LinkPhpwikiURL
which get called from ParseAndLink.

I think <form>s are not allowed within <p>s (you probably know
better than I about that) --- in any case, I remember that
<form>s within <p>s caused problems with CSS handling in certain
browsers.

(Of course, most bracket links, like [some page] or [http://a.b.com/c]
just expand to regular <a>'s.)

So the code is there so that if the bracket link expands to a <form>
tag, we close the current <p>, spit out the <form>, then open a new
<p>, so that no one will be the wiser.

It's buggy and ugly.  Sorry.  But I think the MagicPhpWikiURL forms
will be a thing of the past fairly soon, so it's probably not worth
worrying about too much.

As I said before, at some point I plan on taking another crack at
rewriting the transform code.

[Phpwiki-talk] <u>

[Tara S. <te...@cl...>]

Can somebody tell me in which file the <u>...</u> tags are put around=20
non-linked WikiWords?
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

[Phpwiki-talk] transform.php

[Tara S. <te...@cl...>]

Hello again,

after having fiddled enough with my templates to make them xhtml strict=20
compatible, I'm attacking the big bit: transform.php.

I'm having a bit of a hard time figuring out everything (coding there is=20
  wayyyy too complex for my limited php knowledge), but I'm more or less=20
getting an idea of what I need to change.

One part which is resisting (there are probably others to come) is this o=
ne:

function wtt_bracketlinks($match, &$trfrm)
{
    $link =3D ParseAndLink($match);
    if (strstr($link['link'], "</form>")) {
        // FIXME: BIG HACK: see note in wtm_plugin.
        return "</p>" . $link['link'] . "<p>";
    }
    return $link["link"];
}

What is the </form> doing there? do I understand right, are we talking=20
about dealing with bracketed links?

Thanks for any explanations :)

Tara

--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] forcing log in.

[Gary B. <ga...@in...>]

On Fri, 9 Nov 2001, Tara Star wrote:

> Jeff Dairiki wrote:
>
> > On Fri, 9 Nov 2001, Tara Star wrote:
> >
> > > is there a way to "force" contributers to sign in with a UserName
> > > before editing a page?
> >
> > Not currently.  It wouldn't be hard to hack in such a feature,
> > but it doesn't buy you much, since people can sign in with any
> > name they chose.  I'm not going to mess with it until
> > user auth gets more done --- and at that point, I think it's
> > not really a useful feature, since then you'd probably
> > rather someone sign in as a real registered user (registering
> > first if necessary).
>
>
> I don't mind the fact they can choose any name. It's just that if I
> remember well, the diff page will not put the name of the "modifier"
> unless he/she logged in. That's why I want people to log in. When they
> do, they'll use their name, that's not my worry.
>
> see what I mean? it's not nice to see a list of ips next to recent
> changes ;) I don't need a password or security thing - maybe just a
> cookie, yeah, that would be nice. A cookie :)

Cookies are what I use for the GtmWiki (http://inauspicious.org/gtmwiki/);
I never contributed the patch back since a) it is for 1.2, and b) some
config data is hardcoded in one of the files, and I couldn't think of a
cunning way to get it out. Maybe if I do then I will...

Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

[Phpwiki-talk] Calendar plugin for 1.3

[Jeff D. <da...@da...>]

I just checked a calendar plugin into the CVS.

It needs a bit more work, but is functional.

It's basically a clone of Gary's calendar.

Quick howto:

In a wiki-page, say 'MyCalendar', put a line like:
 <?plugin Calendar?>

Now a calendar for the current month will magically appear.
(You can get to the next month, or the previous month,
by clicking on the arrows (actually '<' or '>') on either
side of the month name.)
Clicking on a date gets you to a wiki-page for that date.
By default, the date page names are something like
'MyCalendar:2001-10-09' (you can change this
using the 'prefix' and 'date_format' optional arguments
to the plugin.)  


-- 
--
Jeff Dairiki <da...@da...>

Re: [Phpwiki-talk] Re: rev levels in phpwiki

[Jeff D. <da...@da...>]

The 1.3.1 branch of PhpWiki is a development branch, so things might
change as time goes one, but here's how it works right now:

There are two ways to "delete" pages:

Real Deletion:

Log on as the admin, hit the delete button.  (Same as in 1.2.1.)  Then
the page and all it's archived versions are gone.  There is no way to get 
them back (unless someone is keeping backups external to PhpWiki.)

"Soft" Deletion:

Edit a page, and delete all it's content.  (Save a blank page.)  Anyone
can do this to any page (which isn't locked).  PhpWiki will then (mostly)
behave as if the page does not exist.  Title searches won't find it, 
for example, and wiki-links to the page, will look just like links
to non-existant pages (with the question mark.)    If you browse
the page, it will look like a non-existant page ("Describe ThisPage
here.")  But, if you look at the page History, you'll see that the old
version(s) of the page are still in the archive.

PhpWiki 1.3.1 keeps "a bunch" of previous revisions in the archives.
Deciding how many and which versions are kept is a highly configurable
(and highly complex) affair.

I'm going to leave a detailed description of the algorithm for another
day.
The system was designed to make it very hard for someone to permanently
wipe out a specific version of a page by flooding it with edits.
(See the comments in index.php for details.)

On Fri, 9 Nov 2001 17:36:15 -0500 (EST)
"Steve Wainstead" <sw...@pa...> wrote:

> In 1.2.1 only one previous version is saved, from the previous author.

> On Fri, 9 Nov 2001, Colleen R. Dick wrote:
> 
> > Hi I have a question about phpwiki.  OK if I accidentally delete a
page
> > the admin can get it back from a previous rev, right? 

[Phpwiki-talk] Re: rev levels in phpwiki

[Steve W. <sw...@pa...>]

Hi Colleen,

In version 1.2.1 the page and all its versions are deleted. It might be a
good improvement if we didn't do this... CVS has a way of moving "deleted"
things into the "attic" so nothing is truly ever lost.

In 1.2.1 only one previous version is saved, from the previous author.

hope that helps
~swain

On Fri, 9 Nov 2001, Colleen R. Dick wrote:

> Hi I have a question about phpwiki.  OK if I accidentally delete a page
> the admin can get it back from a previous rev, right?  Exactly howmany
> levels of revs does it maintain, or is that a parameter set by the admin,
> and if so what would a normal or default value be, and if you really
> truly want to erase all the data in a wiki page could you stack down the
> revs by repeatedly editing and saving the page?  I'm sorry I just don't
> have time to install it and see these things for myself this week and the
> page I want to wipe is not on a wiki I control.
>
> Thanks.
>
> Colleen Dick
>
> Laugh your way to the bank at
> http://www.navehumor.com
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

Re: [Phpwiki-talk] forcing log in.

[Jeff D. <da...@da...>]

On Fri, 09 Nov 2001 22:09:31 +0100
"Tara Star" <te...@cl...> wrote:

> see what I mean? it's not nice to see a list of ips next to recent 
> changes ;) I don't need a password or security thing - maybe just a 
> cookie, yeah, that would be nice. A cookie :)

This patch to templates/browse.html will make it so that the user won't
see an 'Edit' button unless he's signed in.  (Beware that it's not
secure: by entering a suitable URL manually, one can still edit a page
without being signed in.)

Cookies are coming some time.

--- cvs.100/templates/browse.html Fri, 14 Sep 2001 13:12:37 -0700 dairiki
(phpwiki/6_browse.htm 1.1.1.1.1.1.1.1.2.1.1.10.1.3.1.14 644)
+++ cvs.100(w)/templates/browse.html Fri, 09 Nov 2001 13:21:54 -0800
dairiki (phpwiki/6_browse.htm 1.1.1.1.1.1.1.1.2.1.1.10.1.3.1.14 644)
@@ -67,6 +67,9 @@
 <table class="toolbar" width="100%"
        cellpadding=0 cellspacing=0 border=0><tr valign="baseline">
   <td>
+    <?php if (!$user->is_authenticated()) { ?>
+      Please sign in before editing.
+    <?php } else { ?>
     <?php if ($page->get('locked') && !$user->is_admin()) { ?>
       Page locked
     <?php } else { ?>
@@ -76,6 +79,7 @@
         <a class="wikiaction" href="${ACTION}edit&amp;version=${VERSION}"
           >Edit old revision</a>
       <?php } ?>
+    <?php } ?>
     <?php } ?>
     <?php if ($user->is_admin()) { ?>
       <?php if ($page->get('locked')) { ?>

Re: [Phpwiki-talk] forcing log in.

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:

> On Fri, 09 Nov 2001 21:15:47 +0100
> "Tara Star" <te...@cl...> wrote:
>=20
>=20
>>is there=20
>>a way to "force" contributers to sign in with a UserName before editing=
=20
>>a page?
>>
>=20
> Not currently.  It wouldn't be hard to hack in such a feature,
> but it doesn't buy you much, since people can sign in with any
> name they chose.  I'm not going to mess with it until=20
> user auth gets more done --- and at that point, I think it's
> not really a useful feature, since then you'd probably=20
> rather someone sign in as a real registered user (registering
> first if necessary).


I don't mind the fact they can choose any name. It's just that if I=20
remember well, the diff page will not put the name of the "modifier"=20
unless he/she logged in. That's why I want people to log in. When they=20
do, they'll use their name, that's not my worry.

see what I mean? it's not nice to see a list of ips next to recent=20
changes ;) I don't need a password or security thing - maybe just a=20
cookie, yeah, that would be nice. A cookie :)




--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] admin.php 1.2.1 problem

[Jeff D. <da...@da...>]

On Fri, 09 Nov 2001 21:15:47 +0100
"Tara Star" <te...@cl...> wrote:

> is there 
> a way to "force" contributers to sign in with a UserName before editing 
> a page?

Not currently.  It wouldn't be hard to hack in such a feature,
but it doesn't buy you much, since people can sign in with any
name they chose.  I'm not going to mess with it until 
user auth gets more done --- and at that point, I think it's
not really a useful feature, since then you'd probably 
rather someone sign in as a real registered user (registering
first if necessary).

Re: [Phpwiki-talk] new site is up

[Jeff D. <da...@da...>]

To show off what one can do with USE_PATH_INFO, I've set up an alternate
index for the new wiki at http://phpwiki.sf.net/wiki/.  So, e.g., the
RecentChanges are at:

  http://phpwiki.sf.net/wiki/RecentChanges

PS: FWIW, I've not encountered any problems locking/unlocking pages.

On Wed, 7 Nov 2001 17:35:06 -0500 (EST)
"Steve Wainstead" <sw...@pa...> wrote:

> 
> Ok, I've ported all the pages over to the new site:
> 
> http://phpwiki.sf.net/phpwiki-1.3/
> 
> This will become the main site after a shakedown. It seems locking one
> page locks them all.

Re: [Phpwiki-talk] admin.php 1.2.1 problem

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:

[snip]
> Oh.  Yes.   PhpWiki's authentication does not mix well with=20
> server handled HTTP authentication.
>=20
> You are just hitting all the problems, aren't you?  :-)


I'm a specialist ;)


> For 1.2.x, I think the solution is to edit admin.php, and
> delete or comment out the $adminpasswd checks.
[snip]


done, it works. Thanks!


> For 1.3.x, at this point the solution is basically the same,
> except you have to edit lib/WikiUser.php.
[snip]


Actually, I'm not going to password-protect 1.3 - just curious, is there=20
a way to "force" contributers to sign in with a UserName before editing=20
a page?


--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/