phpwiki-talk

Re: [Phpwiki-talk] load failed

[aphid <me...@ap...>]

On Saturday, November 23, 2002, at 04:09  PM, aphid wrote:

> When trying to save or load a page above a certain length, I'm getting 
> (after about 4 seconds):
>
> "The attempt to load 'Accessing URL: 
> http://localhost/testwiki/index.php/SomeThing' failed.
> "

I can still open the pages if I put ?action=edit afterwards, though it 
crashes again if I try to save the page... though it does seem to 
update the page content.


I've got a lil more info on this..
in the apache log, I'm getting

[Sat Nov 23 15:42:29 2002] [notice] child pid 452 exit signal Illegal 
instruction (4)

every time this happens (with a different pid #).  has anyone else seen 
this?

cheers
a

Re: [Phpwiki-talk] Facilitating recipes with phpwiki

[Russ M. <rm...@no...>]

You might want to think about making ingredients lists (what I imagine are
the most line-break intensive part of recipes) into actual unordered lists.

russ

Re: [Phpwiki-talk] Facilitating recipes with phpwiki

[Margie R. <mro...@ch...>]

Thanks for your thoughts. Note:  I actually want linebreaks ("not <br>")
to convert to <br>.

my thinking is if that "wikis confuse people a lot," apart from training,
there is probably more that can be done on the user-interface end to make
it less confusing.

One thing I want to do is to move EditThis to the top of the page, for
instance. Haven't dissected how to do that yet, actually. Clues welcome.

Another item I forgot to mention is the desire to print only the recipe
(one of the nested tables...) Very minor point. Major points are:

- want html input
- want EditThis at the top of the page
- want single returns to be linebreaks. (that would negate the need for a
special recipe input form.)
-<small> didn't work for me at the beginning of a line.

Someone pointed out that I forgot to mention the URL.

It's rawfoodwiki.org.

Best Regards,

Margie


--
Margie Roswell
3443 Guilford Terrace
Baltimore, MD 21218
H: 410-467-3727
W: 410-455-6802
E: mro...@ch...
W: http://hello.to/maps

On Mon, 25 Nov 2002, Adam Shand wrote:

> Marjorie Roswell wrote:
>
> >I've concluded that since people aren't using my site, it could
> >probably be made easier to use. Looking for ideas, and also code.
> >
> >I've announced the site to a raw foods listserv twice, to a raw food
> >seminar of people who cared enough to pay $40 to be there, and to
> >(great) vegetarian thanksgiving meal, and to this listserv, of course.
> >Of more than 600 people receiving the announcement, only three people
> >have added content to it, including someone on this list.
> >
> Just as an FYI, that's actually not too bad.  wiki's confuse people ...
> a lot.  despite the fact that they are incredibly simple a lot of people
> really resist the idea of using them.  it took me months to get people
> regularly adding contect to the personaltelco.net wiki and that's
> despite the fact that my audience was fairly hardcore geek and there
> were 70+ people on a mailing list specifically working on a project.
>
> wiki's build slowly, give it time.  in the mean time make sure that
> *you* use it as much as possible, as it becomes more and more useful
> people will use it more and more.
>
> my personal recommendation would be that if you want to use wiki, resist
> the temptation to make a special recipe module.  the strength of wiki
> comes from it's ability to do everything.  if you did want to do
> something to make importing recipies easier maybe a good way of doing it
> would be to setup a little web form which would convert other formats
> into wiki markup, so they can just cut and paste it into the wiki.  this
> way you preserve the strength of wiki and still make peoples lives easier.
>
> some of your other concerns are totally valid, i'd love to see %%%
> replaced with <br> etc.
>
> Adam.
>
> >
> >
>

Re: [Phpwiki-talk] PhpWeather plugin fixes

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

On Sun, 03 Nov 2002 22:53:19 +0100
Martin Geisler <gim...@gi...> wrote:

> >> The PhpWeather plugin was a bit outdated. I made it work with the
> >> current CVS version and added some new features.

I've just checked your changes (and new PhpWeatherPlugin pgsrc) into CVS.

I had to make two small changes (calling conventions of get_languages()
and get_languages_select()) to get it to work with phpweather-2.0.0.

Re: [Phpwiki-talk] Facilitating recipes with phpwiki

[Adam S. <ad...@pe...>]

Marjorie Roswell wrote:

>I've concluded that since people aren't using my site, it could probably be made easier to use. Looking for ideas, and also code.
>
>I've announced the site to a raw foods listserv twice, to a raw food seminar of people who cared enough to pay $40 to be there, and to (great) vegetarian thanksgiving meal, and to this listserv, of course. Of more than 600 people receiving the announcement, only three people have added content to it, including someone on this list. 
>
Just as an FYI, that's actually not too bad.  wiki's confuse people ... 
a lot.  despite the fact that they are incredibly simple a lot of people 
really resist the idea of using them.  it took me months to get people 
regularly adding contect to the personaltelco.net wiki and that's 
despite the fact that my audience was fairly hardcore geek and there 
were 70+ people on a mailing list specifically working on a project.

wiki's build slowly, give it time.  in the mean time make sure that 
*you* use it as much as possible, as it becomes more and more useful 
people will use it more and more.

my personal recommendation would be that if you want to use wiki, resist 
the temptation to make a special recipe module.  the strength of wiki 
comes from it's ability to do everything.  if you did want to do 
something to make importing recipies easier maybe a good way of doing it 
would be to setup a little web form which would convert other formats 
into wiki markup, so they can just cut and paste it into the wiki.  this 
way you preserve the strength of wiki and still make peoples lives easier.

some of your other concerns are totally valid, i'd love to see %%% 
replaced with <br> etc.

Adam.

>  
>

Re: [Phpwiki-talk] Another fix for nestled emphasis

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

On Sat, 23 Nov 2002 01:51:55 +0100
Martin Geisler <gim...@gi...> wrote:

>   http://gimpster.com/phpwiki/pgsrc.tar.bz2
>   http://www.gimpster.com/phpwiki/index.php/PhpHighlightPlugin#patch


All checked into CVS just now...
Thanks for all the work, Martin!

[Phpwiki-talk] Facilitating recipes with phpwiki

[Marjorie R. <mro...@ma...>]

I've concluded that since people aren't using my site, it could probably be made easier to use. Looking for ideas, and also code.

I've announced the site to a raw foods listserv twice, to a raw food seminar of people who cared enough to pay $40 to be there, and to (great) vegetarian thanksgiving meal, and to this listserv, of course. Of more than 600 people receiving the announcement, only three people have added content to it, including someone on this list. 

Here are some ideas I've got:

Recipes are a pain in the neck. Especially for people who don't know html. And for those who understand the need for a line break, adding %%% and lower-case <br> is just not fun. <pre> is not intuitive. So one thing that might be helpful is a module to automatically add the line break codes. (It might be a check box in the edit form called "recipe format.")

(I still would rather have a line break universally be a line break, actually, though when I mentioned that before, the answer, I think, was that it would mess up other tags. Any way around that? I think I really do want line breaks to be line breaks, without needing the ugly and time-consuming %%% and lower-case <br> codes.

Maybe some dialog box could help facilitate recipes. A spot for ingredients, a spot for instructions...

Maybe a utility for importing standard recipe formats (Meal-MasterTM v7.x or v8.x recipes and Mastercook 3.x).
Now You're Cooking (which imports these formats) is my favorite standalone recipe software, by the way. http://www.ffts.com/features.htm

Of course, html import would be helpful, as then I could invite people who have rawfood web pages to submit their recipes, without requiring that they spend time reformatting stuff.

Maybe could be some easier way to both add a new recipe, and add a link to it on the recipes page. (The average non-wiki user might not figure out the bracket idea for adding a new page, even if I tell them.)

Anyhow, I'm not a good enough php programmer to do _any_ of these things. I'm simply identifying a problem (people aren't using the site, and one person also emailed me and said she couldn't figure out how to use it, and recipes are a pain to enter) and some possible solutions. (including easier ways to add recipes via easier line breaks, importing recipe formats, importing html, and any other ideas or practical solutions you may have.

People respond favorably to this website when they hear about it. They just aren't using it yet. Ideas, and solutions welcome. 

(I might be willing to pay someone to add some good recipe solution to phpwiki, if it seems that the solution will require considerable time. Could be kind of a cool addition. I don't want to supervise the project too closely, and of course, I don't want to pay huge sums of money, but talk to me on list or off, if you have ideas.)

Send personal email to mro...@ch..., or respond to this list.

Margie

Re: [Phpwiki-talk] built-in sourceforge list advertising

[<ph...@de...>]

On Mon, 25 Nov 2002 12:25:53 -0500, "Marjorie Roswell"  wrote:

	<snip content and looking at mailing list sig>

=> -------------------------------------------------------
=> This SF.net email is sponsored by: Get the new Palm Tungsten T 
=> handheld. Power & Color in a compact size! 
=> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en

	So much for filtering email here with procmail to easily
eliminate incoming SPAM messages containing links in the body
such as:	"http://ads.example.com"

	<sigh> Sure wish they hadn't done that,

	- Don

[Phpwiki-talk] Facilitating recipes with phpwiki

[Marjorie R. <mro...@ma...>]

I've concluded that since people aren't using my site, it could probably be made easier to use. Looking for ideas, and also code.

I've announced the site to a raw foods listserv twice, to a raw food seminar of people who cared enough to pay $40 to be there, and to (great) vegetarian thanksgiving meal, and to this listserv, of course. Of more than 600 people receiving the announcement, only three people have added content to it, including someone on this list. 

Here are some ideas I've got:

Recipes are a pain in the neck. Especially for people who don't know html. And for those who understand the need for a line break, adding %%% and lower-case <br> is just not fun. <pre> is not intuitive. So one thing that might be helpful is a module to automatically add the line break codes. (It might be a check box in the edit form called "recipe format.")

(I still would rather have a line break universally be a line break, actually, though when I mentioned that before, the answer, I think, was that it would mess up other tags. Any way around that? I think I really do want line breaks to be line breaks, without needing the ugly and time-consuming %%% and lower-case <br> codes.

Maybe some dialog box could help facilitate recipes. A spot for ingredients, a spot for instructions...

Maybe a utility for importing standard recipe formats (Meal-MasterTM v7.x or v8.x recipes and Mastercook 3.x).
Now You're Cooking (which imports these formats) is my favorite standalone recipe software, by the way. http://www.ffts.com/features.htm

Of course, html import would be helpful, as then I could invite people who have rawfood web pages to submit their recipes, without requiring that they spend time reformatting stuff.

Maybe could be some easier way to both add a new recipe, and add a link to it on the recipes page. (The average non-wiki user might not figure out the bracket idea for adding a new page, even if I tell them.)

Anyhow, I'm not a good enough php programmer to do _any_ of these things. I'm simply identifying a problem (people aren't using the site, and one person also emailed me and said she couldn't figure out how to use it, and recipes are a pain to enter) and some possible solutions. (including easier ways to add recipes via easier line breaks, importing recipe formats, importing html, and any other ideas or practical solutions you may have.

People respond favorably to this website when they hear about it. They just aren't using it yet. Ideas, and solutions welcome. 

(I might be willing to pay someone to add some good recipe solution to phpwiki, if it seems that the solution will require considerable time. Could be kind of a cool addition. I don't want to supervise the project too closely, and of course, I don't want to pay huge sums of money, but talk to me on list or off, if you have ideas.)

Send personal email to mro...@ch..., or respond to this list.

Margie

Re: [Phpwiki-talk] WYSIWYG and Phpwiki

[Reini U. <ru...@x-...>]

Oliver Zancul Prado schrieb:
> Sorry If this has been talked before, I dont read all messages and could not
> search in sourceforge website.
> 
> I wonder if a WYSIWYG module has been ported to phpwiki.
> 
> Even if its easy to most of us to write with wiki code, some people find it
> hard. I've used phpwiki in an online course and the wiki code prevent some
> student's to write their assignments.
> 
> Also, with WYSIWYG you can copy and paste formated text that you already
> have in HTML or even in .doc.
> 
> I know a great WYSIWYG package for IE called richtext:
> http://richtext.sourceforge.net/
> The Richtext Editor project is an Open Source project hosted by
> SourceForge.net.  The editor is an Internet Explorer based WYSIWYG HTML Text
> Editor which can be hosted in a web page or form.  It requires no additional
> components as it is written entirely in DHTML and JavaScript.
> 
> For those who love Mozilla I've found a WYSIWYG editor also:
> http://wysiwyg.skybuilders.com/ (they have one for IE too)
> Dont know about the licence of this.
> Also I think here has another editor: http://composite.mozdev.org/ (I cant
> check it out because I dont have mozilla)
> 
> I want so much to have my personal web site made with phpwiki, but the huge
> amount of text that I have , prevent me to write everything again.
> 
> Is there a way to import pre formated data to phpwiki?

Interesting project since I want to include richtext / 
wysiwyg.skybuilders into squirrelmail also.
I used it successfully with ariadne http://ariadne.muze.nl/ and I liked 
it a lot.
phpBB also has a nice formatted input textarea with some bold/italic/... 
buttons.

Maybe an optional preference to use this editor (or something else) and 
convert the generated HTML code to new markup. (a converter plugin?)
Users can then just paste some html code also. The converter should 
check some malicious html code and remove it.
I started with some perl HTML::Parser/HTML::TreeBuilder once, but never 
finished it, since it was easy enough to convert my html pages manually.

But I have to finish my squirrelmail work first. This needs only html 
output.
-- 
Reini Urban
http://e-mail.inode.at/newwebmail/

[Phpwiki-talk] WYSIWYG and Phpwiki

[Oliver Z. P. <web...@ps...>]

Sorry If this has been talked before, I dont read all messages and could not
search in sourceforge website.

I wonder if a WYSIWYG module has been ported to phpwiki.

Even if its easy to most of us to write with wiki code, some people find it
hard. I've used phpwiki in an online course and the wiki code prevent some
student's to write their assignments.

Also, with WYSIWYG you can copy and paste formated text that you already
have in HTML or even in .doc.

I know a great WYSIWYG package for IE called richtext:
http://richtext.sourceforge.net/
The Richtext Editor project is an Open Source project hosted by
SourceForge.net.  The editor is an Internet Explorer based WYSIWYG HTML Text
Editor which can be hosted in a web page or form.  It requires no additional
components as it is written entirely in DHTML and JavaScript.

For those who love Mozilla I've found a WYSIWYG editor also:
http://wysiwyg.skybuilders.com/ (they have one for IE too)
Dont know about the licence of this.
Also I think here has another editor: http://composite.mozdev.org/ (I cant
check it out because I dont have mozilla)


I want so much to have my personal web site made with phpwiki, but the huge
amount of text that I have , prevent me to write everything again.

Is there a way to import pre formated data to phpwiki?

Thanks

Oliver

Re: [Phpwiki-talk] HTML in plugins

[Reini U. <ru...@x-...>]

Jeff Dairiki schrieb:
>>I believe the HTML object is Jeff's own creation so it is really part 
>>of PhpWiki. It is fantastic to work with, I would like to see it become 
>>part of PHP!
> 
> Thanks!
> 
> I use the Xml/HtmlElement is a couple other personal projects,
> but I think PhpWiki is the only public release...

BTW, I'd love to see this in PEAR.

> To give proper credit, most of the ideas come from Perl's
> HTML::Element module (by Gisle Aas.)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] load failed

[aphid <me...@ap...>]

When trying to save or load a page, I'm getting (after about 4 seconds):

"The attempt to load 'Accessing URL: 
http://localhost/testwiki/index.php/Some%20Thing' failed."

in an alert box, but only if the contents the page  are longer than 
about 3 paragraphs.  If I add a fourth, it fails both to save and to 
load as a normal page.  The only way I can actually get at the page is 
by going to 'index.php/Some%20Thing?action=edit' - which will give me 
the same alert box if I try to save - though it seems to be saving the 
changes anyway (thereby making the page unreachable).

I'm thinking this is a db timeout issue, if so how can I beef up the 
time allowed?

cheers
a

ps - same goes with SomeThing.. it's not the %20

New Markup was Re: [Phpwiki-talk] Another fix for nestled emphasis

[Carsten K. <car...@us...>]

Sounds good, having all the default pages in new markup will help 
demonstrate the markup.

Carsten
On Friday, November 22, 2002, at 08:56  pm, Jeff Dairiki wrote:

> (If anyone thinks we shouldn't yet be converting the pgsrc to
> new markup, speak up now!)
>
-- 
Carsten Klapp
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GE d-@+ s+:- a C+++@(---) UB+++ P+>++ L+>++ E>++ W-(++) N-(+) o? K? 
!w----
O M+(++) V? PS+ PE-(--) Y+ PGP+>++ t+@ 5 X+@ R tv+(-) b+ DI++ D-
G e(+) h(---) r y z?
------END GEEK CODE BLOCK------

Re: [Phpwiki-talk] Another fix for nestled emphasis

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

> OK, great. My next patch is this: I've converted the default pages in
> /pgsrc to the new markup.

Very good!  I'll check in your new/converted pgsrc when I get to it on
Monday.

(If anyone thinks we shouldn't yet be converting the pgsrc to 
new markup, speak up now!)

> Yes, everything works beautifully!

That'll never last...

Re: [Phpwiki-talk] Where are the pages stored?

[Loyd G. <lo...@bl...>]

On Fri, 22 Nov 2002 16:17:07 -0800, Jeff Dairiki <da...@da...> =
wrote:

>> Where is the page data stored? I have phpwiki using MySQL to store =
link
>> information, but the page information is not in the SQL database.
>
>If you're using the mysql backend, and PhpWiki is working properly
>(i.e. if you can edit a page and see the results) then the page data
>is in the MySQL database.

OK, I didn't realize they were in the "version" table. I thought they =
were in
the "page" table. Everything's good then.

Thanks,
Loyd
--=20
"Why, you can even hear yourself think." --Hobbes
"This is making me nervous. Let's go in." --Calvin
lo...@bl...  ICQ#504581  http://www.blackrobes.net/

Re: [Phpwiki-talk] Another fix for nestled emphasis

[Martin G. <gim...@gi...>]

Jeff Dairiki <da...@da...> writes:

>> By the way, would you rather have me report these bugs using the
>> SourceForge bug-tracking system, or is it okay to use the mailinglist
>> for this too?
>
> For small bugs with reasonably quick fixes, here is fine. (I
> certainly check this list more often than anything else.)

OK, great. My next patch is this: I've converted the default pages in
/pgsrc to the new markup. I wanted to get rid of the old markup on my
site, so I thought that I might as well start with the default pages.

The pages can be downloaded here:

  http://gimpster.com/phpwiki/pgsrc.tar.bz2
  http://gimpster.com/phpwiki/pgsrc.tar.gz
  http://gimpster.com/phpwiki/pgsrc.zip

I've replaced the old TextFormattingRules with the new one made by
Matti made. I've reformatted it a bit, so that the examples given in
the text are formatted with <tt>...</tt>. I removed TestPage because
it just tested the old markup.

And while I was at it, then I re-flowed all the text, so that the
lines are broken at 70 characters.

Finally I placed the PhpHighlightPlugin page in the tarballs in the
hope that it could be included in CVS... I've just updated the plugin,
and put a patch here:

  http://www.gimpster.com/phpwiki/index.php/PhpHighlightPlugin#patch

> Thanks for the reports.
> I've just committed fixes to CVS.

I saw, thanks. I don't understand how you were able to turn those
regular expressions into something as structured as this - amazing!

> Nestled markup within (*parentheses*) and _*nested* nestled_ markup
> should work now.

Yes, everything works beautifully!

-- 
Martin Geisler                       My GnuPG Key: 0xF7F6B57B

See http://gimpster.com/ and http://phpweather.net/ for:
PHP Weather => Shows the current weather on your webpage and
PHP Shell   => A telnet-connection (almost :-) in a PHP page.

Re: [Phpwiki-talk] Where are the pages stored?

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

> Where is the page data stored? I have phpwiki using MySQL to store link
> information, but the page information is not in the SQL database.

If you're using the mysql backend, and PhpWiki is working properly
(i.e. if you can edit a page and see the results) then the page data
is in the MySQL database.

Re: [Phpwiki-talk] Another fix for nestled emphasis

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

> By the way, would you rather have me report these bugs using the
> SourceForge bug-tracking system, or is it okay to use the mailinglist
> for this too?

For small bugs with reasonably quick fixes, here is fine.  (I certainly 
check this list more often than anything else.) 

Thanks for the reports.
I've just committed fixes to CVS.
Nestled markup within (*parentheses*) and _*nested* nestled_ markup
should work now.

[Phpwiki-talk] Where are the pages stored?

[Loyd G. <lo...@bl...>]

Where is the page data stored? I have phpwiki using MySQL to store link
information, but the page information is not in the SQL database.

Thanks,
Loyd
--=20
"Why, you can even hear yourself think." --Hobbes
"This is making me nervous. Let's go in." --Calvin
lo...@bl...  ICQ#504581  http://www.blackrobes.net/

[Phpwiki-talk] Another fix for nestled emphasis

[Martin G. <gim...@gi...>]

Hallo again,

I think I've found a small but in the regexp that deals with nestled
emphasis. The problem is, that you cannot start the emphasis
immediately after one of (, ", or '. So the following doesn't work:

  (*foo* bar) (foo *bar*) (*foo bar*)

Also, it's now possible to combine bold with italic, but not with
monospace. (And it's also not possible to combine monospace with
italic, but on my system monospace made the font upright, so I've left
that possibility out. That's also why I left out the possibility of
having all three kinds of emphasis in play simultaneously.)

By the way, would you rather have me report these bugs using the
SourceForge bug-tracking system, or is it okay to use the mailinglist
for this too?

Anyway, the revised class is here:

class Markup_nestled_emphasis extends BalancedMarkup
{
    //var $_start_regexp = "(?<! [[:alnum:]] ) [*_=] (?=[[:alnum:]])";
    var $_start_regexp = "(?<= \s | ^ | [\"'(] ) (?: _\\* | \\*_ | =\\* | \\*= | [*_=] ) (?= \S)";

    function getEndRegexp ($match) {
        //return "(?<= [[:alnum:]]) \\$match (?![[:alnum:]])";
        $rev = preg_quote(strrev($match));
        return "(?<= \S) $rev (?= \s | [.,:;\"'?)] | $)";
    }
    
    function markup ($match, $body) {
        switch ($match) {
        case '*': return new HtmlElement('b', $body);
        case '=': return new HtmlElement('tt', $body);
        case '_':  return new HtmlElement('i', $body);
        case '_*': return new HtmlElement('i', new HtmlElement('b', $body));
        case '*_': return new HtmlElement('b', new HtmlElement('i', $body));
        case '=*': return new HtmlElement('tt', new HtmlElement('b', $body));
        case '*=': return new HtmlElement('b', new HtmlElement('tt', $body));
        default:  return new HtmlElement('b', new HtmlElement('i', $body));
        }
    }
}

-- 
Martin Geisler                       My GnuPG Key: 0xF7F6B57B

See http://gimpster.com/ and http://phpweather.net/ for:
PHP Weather => Shows the current weather on your webpage and
PHP Shell   => A telnet-connection (almost :-) in a PHP page.

Re: [Phpwiki-talk] Root directories vs. subdirectories

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

> Now having said that, I don't think the situation is anywhere near as
> complicated as Jeff suggests.  For one thing, there is no namespace
> issue because every wiki operation has to go through index.php.  So to
> take the example of my site, my main css page is at
> http://www.hollenback.net/hollenback-style.css.  A wiki page is at
> http://www.hollenback.net/index.php/HelpfulMuttHints (for example).

I believe Martyn wanted to eliminate the index.php part, 
e.g. http://www.hollenback.net/FrontPage

You're quite right, that as long as you're happy with the 'index.php'
in the URLs, there's no problem.

Re: [Phpwiki-talk] Root directories vs. subdirectories

[Philip J. H. <ph...@ho...>]

I have my phpwiki in the root at http://www.hollenback.net, and
everything works fine.  I did have to futz with it a bit to make it
pick up the themes correctly, but it was long enough ago that I don't
remember what I did.  Check the bug reports on the sourceforge site, I
filed the info there.

Now having said that, I don't think the situation is anywhere near as
complicated as Jeff suggests.  For one thing, there is no namespace
issue because every wiki operation has to go through index.php.  So to
take the example of my site, my main css page is at
http://www.hollenback.net/hollenback-style.css.  A wiki page is at
http://www.hollenback.net/index.php/HelpfulMuttHints (for example).

So there's really no issue of the wiki getting in the way.  index.php
for all things wiki, start from the root (/) for everything else.

Unless I'm missing something?

I see the following in the url options part of my index.php:

define('DATA_PATH', '');
define('PHPWIKI_DIR', '.');

This is phpwiki 1.3.3.

P.

On Sweetmorn, the 34th of The Aftermath, Jeff Dairiki spoke:
> > I'm attempting to install phpwiki-1.33 into the root directory of my
> > virtual web server (which is running Apache 1.3.27).  Note that it is
> > the root directory and not some kind of /wiki or /phpwiki derivative.
> 
> I think I remember hearing some reports of some people being at least
> partially successful doing that, but I'd recommend against it.
> 
> Where PhpWiki is installed (assuming USE_PATHINFO is on), it takes
> over the entire URL-space.   If you install PhpWiki under /wiki, every
> URL beginning with /wiki is a wiki page (or operation on one).
> If you install PhpWiki under /, then every URL on your
> host refers to a wiki page.  There's no place left
> (without hackage) to put style sheets, icons, or anything
> else that's not a wiki page.  (A request for /phpwiki.css
> is interpreted as a request for the wiki page titled
> 'phpwiki.css'.)
> 
> Certainly PhpWiki was not designed with that usage in mind.
> 
> That said, here's a couple ideas:
> 
> Idea 1:
> 
> Recognize certain extensions (.css, .gif, .jpg) as non-wiki page.
> Use mod_rewrite rules to differentiate between those special
> URLs, and everything else.
> 
> Idea 2:
> 
> Put all the non-wiki page things on a different (possible virtual)
> host.  (Or a (virtual) server running off a different (non-standard)
> port.)
> 
> 
> 
> Not having attempted either, I like the second idea better...
> 
> In either case, you'll have to become familiar with the
> configure options in part 5 ("URL options") of index.php
> 
> 
> Write back if you get stuck.
> If you get it to work, please write up a short howto...
> 
> 
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

-- 
Philip J. Hollenback
ph...@po...
http://www.hollenback.net

[Phpwiki-talk] Another tiny fix

[Martin G. <gim...@gi...>]

Hi again,

I just stumbled over this tiny bug on the LinkIcons page: you cannot
label a link with 'png', 'jpg' or 'gif' because PhpWiki then treats
your label as an URL to an image... There's a link to the PNG homepage
on LinkIcons, but this gives a warning about an 'object to string
conversion'.

The fix is simple, just add '\.' in front of '($InlineImages)' twice
in stdlib.php. This should make the test more robust.

-- 
Martin Geisler                       My GnuPG Key: 0xF7F6B57B

See http://gimpster.com/ and http://phpweather.net/ for:
PHP Weather => Shows the current weather on your webpage and
PHP Shell   => A telnet-connection (almost :-) in a PHP page.

Re: [Phpwiki-talk] Root directories vs. subdirectories

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

> I think the easiest thing that I can do would be to install PHPwiki
> under it's own subdirectory of /wiki and in the root directory have an
> immediate HTTP redirect to point to http://xxx/wiki.

As long as you're only redirecting requests for / (or /index.*) to
/wiki/FrontPage, that will work fine.  If you're thinking of trying
to redirect _everything_, then, of course, you're back to the same
problem.

(If you redirect everything except for requests for /*.{gif,css,jpg},
then that's Idea 1.)