phpwiki-talk

Re: [Phpwiki-talk] Solved my LDAP auth issues

[Reini U. <rei...@gm...>]

config-dist.ini already has it:

; Some LDAP servers need some more options, such as the Windows Active
; Directory Server.  Specify the options (as allowed by the PHP LDAP module=
)
; and their values as NAME=3Dvalue pairs separated by colons.
;LDAP_SET_OPTION=3D"LDAP_OPT_PROTOCOL_VERSION=3D3:LDAP_OPT_REFERRALS=3D0"

On 10/27/05, Tim Bates <ti...@ne...> wrote:
> Can I recommend adding something about setting
> "LDAP_OPT_PROTOCOL_VERSION=3D3" for LDAP_SET_OPTIONS in the comments abou=
t
> that option?
> It might help for people like me that dont think of that.

[Phpwiki-talk] Authentication issues

[Yan S. <ya...@se...>]

I'm trying to set up a wiki with the following requirements:

Anyone can see pages
Anyone can sign up (bogologins)
Passwords are required
Only authenticated users can edit pages

ALLOW_ANON_USER = true
ALLOW_ANON_EDIT = false
USER_AUTH_ORDER = "File : PersonalPage : BogoLogin"
USER_AUTH_POLICY = stacked
AUTH_USER_FILE = /xxxx/passwd
AUTH_USER_FILE_STORABLE = true
AUTH_SESS_USER = userid
AUTH_SESS_LEVEL = 2

But no matter what I do, I get

*Insufficient permissions.*

------------------------------------------------------------------------

DEBUG: ALLOW_ANON_EDIT = false, ALLOW_BOGO_LOGIN = true, 
ALLOW_USER_PASSWORDS = true USER_AUTH_ORDER: File => PersonalPage => 
BogoLogin => Forbidden, USER_AUTH_POLICY: stacked, 
PASSWORD_LENGTH_MINIMUM: 0

The issue seems to be USER_AUTH_ORDER - it's always forbidden.

What's the correct combination to do what I need to do?

Thanks,

--Yan

Re: [Phpwiki-talk] WYSIWIKI

[Manuel V. <man...@gm...>]

2005/10/27, Reini Urban <rei...@gm...>:
> > But this work is intresting, I think there are 2 ways that can easily
> > solve the current limitations:
> > * generate wiki markups instead of HTML
> > * keep the current 'edit' button and allow section edition.
>
> Section editing is quite hard within the current HtmlObject tree. Not
> impossible,
> but much harder than with the simple mediawiki architecture.

Can you details how it's harder (I didin't yet study this part of PhpWiki) =
?
Do you think it's reasonably feasible or not ?

Re: [Phpwiki-talk] WYSIWIKI

[Reini U. <rei...@gm...>]

On 10/25/05, Manuel Vacelet <man...@gm...> wrote:
> 2005/10/19, Dan Frankowski <dfr...@cs...>:
> > - Do it in a way so people don't have to hit an "edit" or "save" button
> > anymore (!!). It just auto-saves every few seconds (to the same
> > revision, so it doesn't create huge numbers of revisions)
> >
> > Some limitations to be solved, with proposals for solutions for each:
> >
> > - Lack of plugin support
> > - HTML vulnerability
>
> I don't see why doubleclick on textarea to edit is more obvious than
> click on an 'edit' button. A wiki is not a text editor like OpenOffice
> Writer or Microsoft Word, it can be dangerous to try to hide this fact
> to people, all the more since they are not confident with wiki
> approach.

doubeclick in textarea is now off by default and can be enabled in the
users prefs.
so the user should now that this feature exists when he explictly turned it=
 on.

> But this work is intresting, I think there are 2 ways that can easily
> solve the current limitations:
> * generate wiki markups instead of HTML
> * keep the current 'edit' button and allow section edition.

Section editing is quite hard within the current HtmlObject tree. Not
impossible,
but much harder than with the simple mediawiki architecture.

> For the first one, I think the objective of Scott (one wysiwyg
> front-end to run them all) is not a good one because the current state
> is: *there are differencies between wiki syntax*. So, adoption of
> wysiwiki imply a modification of something somewhere:
> * You can adapt the server to try to validate the submitted XML/HTML.
> * You can adapt the client to be able to take in account different wiki m=
arkups.
> I believe the second one is much safe and much acceptable for engine
> maintainers than the first one.
>
> The second proposition is to provide a "mix" between mediawiki and
> gmail approach. From mediawiki, the section edition is really useful,
> expecially on large documents. From gmail I take the 'edit inline'.

Edit inline via AJAX can always be done.
It just makes an internal edit response without user-visible refresh,
but almost
the same delay of course.

> Now let's imagine: you are reading a large document, you want to edit
> a small paragraph, just click on 'edit section' (mediawiki) you get a
> wysiwyg interface (wysiwiki) instead of the current paragraph *with
> other sections around* (gmail). You can now make your changes, save it
> and continue reading the text without reloading the page (ajax).
> Obviously, the legacy edit mode (without buzz technology) should be
> always available.
>
> I don't know if I was clear enough.
> Is this proposition acceptable ?

Of course, but hard to implement.
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Solved my LDAP auth issues

[Tim B. <ti...@ne...>]

Can I recommend adding something about setting 
"LDAP_OPT_PROTOCOL_VERSION=3" for LDAP_SET_OPTIONS in the comments about 
that option?
It might help for people like me that dont think of that.

TB


**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************

[Phpwiki-talk] Revert attack?

[Miklos S. <mi...@sz...>]

I started a PhpWiki about a month ago (http://fuse.sourceforge.net/wiki/) 
and recently there was a strange "revert flood".  I don't think it's
malicious, my best guess is that it's a web crawler systematically
reverting everything.

Is this possible?  Can this be prevented?

Thanks,
Miklos

Re: [Phpwiki-talk] Cloning a wikit

[Yan S. <ya...@se...>]

Matt Brown wrote:

>Are you using any external authentication methods?
>  
>

Ha!

It appears that *any* authentication methods cause it to fail....

I had "file : imap"; and required authentication - when I allowed 
anonymous users it started to work....

OK, now to fix authentication.

Thanks.

--Yan

Re: [Phpwiki-talk] Cloning a wikit

[Matt B. <ma...@ma...>]

On Wed, 2005-10-26 at 08:59 -0700, Yan Seiner wrote:

> I get my loging screen, and when I log in I get a blank page.  I mean 
> totally blank - not even headers or anything.  No errrors either.

Are you using any external authentication methods?

I recently had a bug on the Debian package where the user was presented
with a completely blank page when trying to login because they had
configured IMAP authentication but neglected to install the IMAP
extensions for PHP4. 

I filed a bug on PHPwiki at:
http://sourceforge.net/tracker/index.php?func=detail&aid=1334024&group_id=6121&atid=106121
to ask for improved error handling in this situation. 

Until that is fixed you can double check your authentication configs and
PHP setup incase this is the problem you're encountering.

HTH. 

Regards

-- 
Matt Brown
ma...@ma...
Mob +64 275 611 544 www.mattb.net.nz

[Phpwiki-talk] Your Web Placement

[<gtj...@ib...>]

CnBocHdpa2ktdGFsa0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKCgoKU3ViamVjdCBMaW5lOiBSZTog
WW91ciBXZWIgUGxhY2VtZW50CgpEZWFyIEN1c3RvbWVyLAogCldlIGNhbiBwdXQgeW91IGF0IHRo
ZSB0b3Agb2YgWWFob28hIEFORCBHb29nbGUgdG9kYXkuCiAKT3VyIGNvbXBhbnkgaGFzIGV4Y2x1
c2l2ZSB0ZWNobm9sb2d5IHRoYXQgY2FuIHB1dCB5b3VyIHdlYnNpdGUocykgYWJvdmUgZXZlcnkg
b3RoZXIgY29tcGFueSBvbiBhbGwgdGhlIG1ham9yIHNlYXJjaCBlbmdpbmVzLiAgVG95b3RhLCBl
QmF5LCBXZWxsc0ZhcmdvIGFuZCBEZWxsIChqdXN0IHRvIG5hbWUgYSBmZXcpIGFscmVhZHkgdXNl
IHRoaXMgdGVjaG5vbG9neS4gIFdlIGFyZSBub3cgb2ZmZXJpbmcgaXQgZGlyZWN0IHRvIHlvdS4g
VGlyZWQgb2YgU0VPIHBsYW5zIHRoYXQgZ2V0IHlvdSBub3doZXJlPyAgVGlyZWQgb2YgYmxvd2lu
ZyB5b3VyIGJ1ZGdldCBvbiBwYXkgcGVyIGNsaWNrIG9ubHkgdG8gbG9zZSBwb3NpdGlvbiBpbW1l
ZGlhdGVseT8gIFdlIG9mZmVyIGd1YXJhbnRlZWQgcmVzdWx0cyBhbmQgcHJvbW90aW9uYWwgcHJp
Y2luZyB0aGF0IHdpbGwgYmVhdCBhbnkgb3RoZXIgcHJvZ3JhbSB5b3UgaGF2ZSB1c2VkLiAKCkNv
bnRhY3QgdXMgaW1tZWRpYXRlbHkgYXQgICBTZWFyY2g1QHRlbGVmb25pY2EubmV0LnBlICAgaWYg
eW91IGFyZSBpbnRlcmVzdGVkIGluIGdldHRpbmcgdW5saW1pdGVkIHRyYWZmaWMgYW5kIGd1YXJh
bnRlZWQgcG9zaXRpb25pbmcgd2l0aCBkaXNjb3VudGVkIHByaWNpbmcuICBUaGlzIHByb21vdGlv
biB3aWxsIG5vdCBsYXN0IGxvbmcgYW5kIGlzIG9uIGEgZmlyc3QgY29tZSAvIGZpcnN0IHNlcnZl
IGJhc2lzLiAgUGxlYXNlIGluY2x1ZGUgdGhlIFVSTChzKSB5b3UgYXJlIGludGVyZXN0ZWQgaW4g
cHJvbW90aW5nLiAgRXhhbXBsZXMvRGVtbyBjYW4gYmUgcHJvdmlkZWQuICAKClNpbmNlcmVseSwK
CldlYiBSZXN1bHRzIFRlYW0KCklmIHlvdSB3aXNoIHRvIGJlIHJlbW92ZWQgZnJvbSB0aGlzIGxp
c3QsIHBsZWFzZSByZXNwb25kIHRvIHRoZSBmb2xsb3dpbmcgZW1haWwgYWRkcmVzcyBhbmQgdHlw
ZSB0aGUgd29yZCCTUkVNT1ZFlCBpbiB5b3VyIHN1YmplY3QgbGluZTogc2VhcmNoMkB0ZWxlZm9u
aWNhLm5ldC5wZQogCgoK

Re: [Phpwiki-talk] bullet list ... don't tell me it's a feature

[Reini U. <rei...@gm...>]

That's probably a limitation in the BlockParser, but unfortunately
Jeff's building site.
Similar problems appear on the new tables.

On 10/26/05, Arnaud Fontaine <ar...@cr...> wrote:
> *Puce 1
> *Puce 2
> *puce de test
> **deux puces
=3D>
> <ul><li class=3D"tightenable bottom">Puce 1</li>
> <li class=3D"tightenable top">Puce 2</li>
> <li class=3D"tightenable bottom"><p class=3D"tightenable top bottom">puce=
 de
> test</p>
> <ul><li class=3D"tightenable top bottom">deux puces</li>
> </ul>
> </li>
> </ul>
> What is this <p></p> doing there ?????
>
> I'm sure Reini already answered ... :)
--
Reini Urban

[Phpwiki-talk] Cloning a wikit

[Yan S. <ya...@se...>]

I have a phpwiki-based wiki.  I've modified the source a bit to allow my 
custom theme to work, and I'd like to clone it.

I've copied all of the wiki files, set up the database and edited the 
config.ini for the new config.

I get my loging screen, and when I log in I get a blank page.  I mean 
totally blank - not even headers or anything.  No errrors either.

So.... I'm guessing that's because the database is totally empty.  How 
do I populate the database with the welcome screen?  IIRC there is some 
magic at first startup that populates the database.  How do I rerun it?

I guess I can always set up a new wiki with the correct database info, 
and then dump phpwiki code over it, but I'd like to figure it out this 
way....

Any suggestions?

--Yan

Re: [Phpwiki-talk] RSS

[Arnaud F. <ar...@cr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Reini Urban wrote:
> Hi Walter,
> [I'm just in Vienna at the Viennale, BTW]
> 
> Sure it is possible. It's even on my plan for 1.3.12,
> together with the other blog-like services: TalkBack and PingBack.
> RSS and ATOM for the latest blog entries (plugin BlogJournal) is the easiest.
> 
> The starting points would be RecentChanges and XmlRpcServer.
> 
> 
> On 10/17/05, Walter Rafelsberger <wa...@ra...> wrote:
> 
>>I was wondering if it's possible to adjust the phpwiki-rss-solution
>>for other purposes.
>>The RSS-Feed via RecentChanges is great, but I'm looking for a
>>solution to create a Feed which has more "Blog-Style".
>>For example an RSS-Feed generated from WikiBlogPlugin or from
>>UnfoldSubPages which contains not just a summary but the actual page
>>content also.

You also have the RSS feed from the RelatedChanges plugin.

Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDX6V5yAf3wgFyy1ARAp5JAKCrUC4c40W4ZjdYYPGRrr41jTEHBACfWn6N
RCsIrpHuXXolvgxS39knChc=
=h+gQ
-----END PGP SIGNATURE-----

[Phpwiki-talk] locale ...

[Arnaud F. <ar...@cr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all

on my server (debian sid + apache 2 + php 4.4.0), the last CVS doesnt
handle locale correctly (switch back to lang en ... locale "C" I guess).

I found in lib/IniConfig.php line 669 commented.

I uncommented it to:
    update_locale(isset($LANG) ? $LANG : DEFAULT_LANGUAGE);

and it worked.

Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDX5rHyAf3wgFyy1ARAqHAAKCzUyN50b3SnRg3ztqyK7T5Iiu+yACeMhCQ
7Y3DyvlDOQRUBkHZ1WUe1fI=
=FnF+
-----END PGP SIGNATURE-----

Re: [Phpwiki-talk] bullet list ... don't tell me it's a feature

[Arnaud F. <ar...@cr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arnaud Fontaine wrote:
> Well ...
> 
> Can someone tell me why when I have :
> 
> 
> *Puce 1
> *Puce 2
> 
> *puce de test
> **deux puces
> 
> 
> I get :
> 
> <ul><li class="tightenable bottom">Puce 1</li>
> <li class="tightenable top">Puce 2</li>
> <li class="tightenable bottom"><p class="tightenable top bottom">puce de
> test</p>
> <ul><li class="tightenable top bottom">deux puces</li>
> </ul>
> </li>
> </ul>
> 
> What is this <p></p> doing there ?????
> 
> I'm sure Reini already answered ... :)
> 
> Arnaud

By the way,


*Puce 1
*Puce 2
*puce de test
**deux puces

produces the same html code (with our friend <p> running around)

Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDX2AhyAf3wgFyy1ARAtQFAKDqncUMMsXnkHhbCbLkNAT4nxijzQCg8o0H
5fBk2611oPgCIgBMr/FNv64=
=dau6
-----END PGP SIGNATURE-----

[Phpwiki-talk] bullet list ... don't tell me it's a feature

[Arnaud F. <ar...@cr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well ...

Can someone tell me why when I have :


*Puce 1
*Puce 2

*puce de test
**deux puces


I get :

<ul><li class="tightenable bottom">Puce 1</li>
<li class="tightenable top">Puce 2</li>
<li class="tightenable bottom"><p class="tightenable top bottom">puce de
test</p>
<ul><li class="tightenable top bottom">deux puces</li>
</ul>
</li>
</ul>

What is this <p></p> doing there ?????

I'm sure Reini already answered ... :)

Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDX187yAf3wgFyy1ARAvVmAJ9mjCCCu8Bs+xNwk+PlEkR1YjuzOwCg4ckB
tKwv8ruJcjFham5GvdRej2A=
=gT4s
-----END PGP SIGNATURE-----

Re: [Phpwiki-talk] LDAP Authentication?

[Arnaud F. <ar...@cr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim Bates wrote:
> Hello
> 
> I have a few hundred user accounts (as in Unix and Samba accounts) in an
> LDAP database. Is it possible to use these same details for phpwiki? Is
> the LDAP support in phpwiki working at the moment? I've tried to do it
> but Im really just guessing since the documentation is pretty vague
> about authentication.

Yes LDAP support works at the moment but ... I haven't test ldaps access.

We use ldap in production for authentification but we still use wiki
pages to deal with groups (flexibility).

Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDX06PyAf3wgFyy1ARApETAKDWB3lnQ9V6kPiJoj6L+ijQLlt2JACeIJRN
vAjq2t4oGEG+TS+iQ7unvK0=
=EP2P
-----END PGP SIGNATURE-----

[Phpwiki-talk] LDAP Authentication?

[Tim B. <ti...@ne...>]

Hello

I have a few hundred user accounts (as in Unix and Samba accounts) in an 
LDAP database. Is it possible to use these same details for phpwiki? Is 
the LDAP support in phpwiki working at the moment? I've tried to do it 
but Im really just guessing since the documentation is pretty vague 
about authentication.

Tim


**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************

Re: [Phpwiki-talk] css classes, ids in markup

[John K. <jo...@ke...>]

At 19:55 +0100 16/10/05, John Kershaw wrote:
>At 19:12 +0200 16/10/05, Joel Uckelman wrote:
>>So, what I'm suggesting is:
>>
>>1. Extending the markup syntax to permit classes and ids, perhaps like this:
>>
>>markupelement{class1 class2... #id}
>>...
>>Comments?
>
>Wow - that would be excellent :)
>
>One suggestion I'd add would be the option to define styles on the 
>fly, maybe using "..." eg

Thought just occurred to me - rather than reinventing the wheel (aka 
making more mismatched markup) does anyone know if MediaWiki et al 
have tackled the issue of div/span/style wiki markup? If it already 
exists, we should do it their way. Or at least discuss markup 
possibilities with them*

*them = any/all wiki markup honchos

John.
-- 
-------------------------------------------------------------------
T:01274 581519 / M:07944 755613   www.kershaw.org  jo...@ke...
skype:johnmkershaw  AIM:johnkershaw  MSN:joh...@ho...

Re: [Phpwiki-talk] More spam filtering

[Robert C. J. <ro...@ar...>]

On 25 Oct 2005 at 8:55, Dan Frankowski wrote:

> 
> I don't know what "Revert" does, but if it's just to the previous
> version, that's no good. Sometimes the spammers have changed the page
> multiple revisions before I see it.
> 
> Anyway, I don't have time to constantly guard myself, and 
> our community is not large. I need something to significantly 
> reduce the amount of incoming spam. I closed my site to 
> anonymous edits, but I'm getting killed again the last couple 
> of days.
> 
> I don't know if it's bots or not. I have to suspect bots. It looks
> kind of like bots.

My Wiki got annihilated by a (or several) bots at the end of last week. From the 
logs, I see up to three different IP addresses working at the same time. It 
appears that one or two IP addresses do the scanning, and the third IP address 
immediately submits the change.

I'll ban the IP addreses at the server level, but that's not going to fool them for 
long. They're probably zombie bots.

They replaced every page in my wiki, including all the help and style pages, 
and added spam to the first day of every month of the current year on all pages 
that used the calendar plugin.

Reverting this totally sucked.

> I am trying to enable a captcha upon login, but my PHP has 
> libgd issues at the moment. If that's not enough, I'll try to take the
> captcha-on-edit feature, too.
> 
> Right now, I'm in trouble.

I'm tryig to upgrade to 1.3.11p1, but I simply cannot get the upgrade to work. 
The ?action=upgrade does nothing, and all the pages come up blank. I've had 
to revert to 1.3.10.

-- 
Rob Croson (ro...@ar...)
Member of the Pegasus Mail and Mercury/32 Beta Test Teams
Pegasus Mail and Mercury/32 Portal: http://email.arcm.com
Visit the MailWiki: http://email.arcm.com/wiki
Support Pegasus Mail: http://www.cafeshops.com/pegasusmail

Re: [Phpwiki-talk] More spam filtering

[Dan F. <dfr...@cs...>]

I don't know what "Revert" does, but if it's just to the previous 
version, that's no good. Sometimes the spammers have changed the page 
multiple revisions before I see it.

Anyway, I don't have time to constantly guard myself, and our community 
is not large. I need something to significantly reduce the amount of 
incoming spam. I closed my site to anonymous edits, but I'm getting 
killed again the last couple of days.

I don't know if it's bots or not. I have to suspect bots. It looks kind 
of like bots.

I am trying to enable a captcha upon login, but my PHP has libgd issues 
at the moment. If that's not enough, I'll try to take the 
captcha-on-edit feature, too.

Right now, I'm in trouble.

Dan

Joel Uckelman wrote:

>>At 18:04 +0200 15/10/05, Joel Uckelman wrote:
>>    
>>
>>>Can you tell how the spammers are doing it? If it's being done by a bot,
>>>then at least we can keep doing things to confuse it. But if it's become
>>>cost-effective for spammers to spam wikis by hand, then the game is over
>>>and we've lost.
>>>      
>>>
>>My wikis send me an email whenever anyone makes a change, showing the 
>>new page text. Would it be possible to mail out a diff each time a 
>>page is edited, with a link at the bottom to revert to previous?
>>    
>>
>
>The current version sends a diff instead of the full page text.
>
>This happens in sendPageChangeNotification() in lib/WikiDB.php. All you'd
>need to do is add a line to create the link:
>
>$revertlink = WikiURL($this->_pagename, array('action'=>'revert','version'=>$previous), true);
>
>and then make sure that $revertlink ends up in the mail which goes out at
>toward the end of the function.
>
>
>  
>

Re: [Phpwiki-talk] WYSIWIKI

[Manuel V. <man...@gm...>]

2005/10/19, Dan Frankowski <dfr...@cs...>:
> - Do it in a way so people don't have to hit an "edit" or "save" button
> anymore (!!). It just auto-saves every few seconds (to the same
> revision, so it doesn't create huge numbers of revisions)
>
> Some limitations to be solved, with proposals for solutions for each:
>
> - Lack of plugin support
> - HTML vulnerability

I don't see why doubleclick on textarea to edit is more obvious than
click on an 'edit' button. A wiki is not a text editor like OpenOffice
Writer or Microsoft Word, it can be dangerous to try to hide this fact
to people, all the more since they are not confident with wiki
approach.

But this work is intresting, I think there are 2 ways that can easily
solve the current limitations:
* generate wiki markups instead of HTML
* keep the current 'edit' button and allow section edition.

For the first one, I think the objective of Scott (one wysiwyg
front-end to run them all) is not a good one because the current state
is: *there are differencies between wiki syntax*. So, adoption of
wysiwiki imply a modification of something somewhere:
* You can adapt the server to try to validate the submitted XML/HTML.
* You can adapt the client to be able to take in account different wiki mar=
kups.
I believe the second one is much safe and much acceptable for engine
maintainers than the first one.

The second proposition is to provide a "mix" between mediawiki and
gmail approach. From mediawiki, the section edition is really useful,
expecially on large documents. From gmail I take the 'edit inline'.

Now let's imagine: you are reading a large document, you want to edit
a small paragraph, just click on 'edit section' (mediawiki) you get a
wysiwyg interface (wysiwiki) instead of the current paragraph *with
other sections around* (gmail). You can now make your changes, save it
and continue reading the text without reloading the page (ajax).
Obviously, the legacy edit mode (without buzz technology) should be
always available.

I don't know if I was clear enough.
Is this proposition acceptable ?

-- Manuel

[Phpwiki-talk] Themes, and how to create one

[John S. <jst...@gm...>]

Hi All,
I need to develop a theme that matches our corporate themes and was
wondering if someone with experience wouldn't mind assisting me with some
pointers. As I understand that there is no real themes howto doc, I figure
the best way to find out is to ask.

I wouldn't mid basing it on an existing theme, and users would still be abl=
e
to change the theme to whatever they prefer, but it must at least start out
looking like the rest of our intranets.

Thanks in advance.

PS, the good news is I have finally convinced my superiors of the merits of
a wiki;)

Re: [Phpwiki-talk] InterWikiMap

[Reini U. <rei...@gm...>]

To shut up the warning login as admin and lock the page in question.

On 10/23/05, Massimiliano Pagani <ma...@gm...> wrote:
> Hello,
>      after installation of phpWiki 1.3p1 with flat file database, I get
> consistently the following warning:
>
>  lib/PageType.php:140: Notice: WARNING: InterWikiMap page is unlocked, so
> not using those links.
>
>      is there something wrong with my configuration? Apparently there is =
no
> problem, if it is really so, is there a way to shut up the warning?
>
>      Thank you in advance.
>
>
>  Best Regards
>
> --
> Massimiliano Pagani
> http://www.maxpagani.org/


--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Migration Script for Old Configurations

[Reini U. <rei...@gm...>]

On 10/23/05, Matt Brown <ma...@ma...> wrote:
> On Sat, 2005-10-22 at 21:28 +0200, Reini Urban wrote:
> > BTW: The config-template.ini is not needed, since the required info
> > is already in config-dist.ini and config-default.ini
> > But it's a good and easy to follow start.
>
> The problem with config-dist is that it contains multiple copies of some
> of the directives, the migration script isn't really smart enough to
> handle that nicely.
>
> config-template just contains a single entry for each directive. Maybe
> config-default would have been appropriate... I didn't actually consider
> that.

True.
I did most of the logic to combine these two already in configurator.php,
and will change that in your perl script. Looks easy to me.
--
Reini Urban

[Phpwiki-talk] InterWikiMap

[Massimiliano P. <ma...@gm...>]

Hello,
after installation of phpWiki 1.3p1 with flat file database, I get
consistently the following warning:

lib/PageType.php:140: Notice: WARNING: InterWikiMap page is unlocked, so no=
t
using those links.

is there something wrong with my configuration? Apparently there is no
problem, if it is really so, is there a way to shut up the warning?

Thank you in advance.


Best Regards

--
Massimiliano Pagani
http://www.maxpagani.org/