phpwiki-talk

Re: [Phpwiki-talk] Automatic categorisation/topicisation

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

Alec Thomas wrote:

>On Tue, Mar 02, 2004 at 02:09:29PM +0100, Reini Urban wrote:
>  
>
>>Yes,
>>please try to write such a feature and post it at the sf.net website
>>under RFE (Request Feature Enhancement)
>>    
>>
>
>Okay, I will do so.
>
>  
>
>>http://sourceforge.net/projects/phpwiki/
>>
>>Can you specify exactly your feature request?
>>Automatically add a certain CategoryWord to the bottom of some pages?
>>    
>>
>
>Actually, the opposite of that. If I add a wikiword to a page in the
>form CategoryFoo, I would like PhpWiki to automatically create a page
>called CategoryFoo, listing all the backlinks to it. Similarly with
>TopicBar, etc.
>  
>

In other words, topic names that start with "Category" are special? This 
feels unfortunate to me. It is a semi-hidden behavior.

What if you had a "Create Category page" button where you type in the 
name of the category, and it creates the page with the BackLinks plug-in 
on it? Or more generally, if you have a page you want to start with a 
certain pattern or template, a "Create Page" plug-in that can take a 
template argument? Then you just make a CategoryTemplate page with the 
"Backlinks" goo on it, make a Wiki page with the "CreatePage" 
plugin-form with a template=CategoryTemplate parameter. What do you say?

I made a CreatePage plug-in, because I consider less confusing for a new 
user (who doesn't know wikis) to have an explicit interface as an 
option. However, my CreatePage doesn't currently grab a template from 
anywhere.

I attach the CreatePage plug-in, which can be used with "<?plugin-form 
CreatePage?>". In my wiki, I also put CreatePage at the bottom of every 
search form, so people can create the page if it is not found if they want.

Dan F

Re: [Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings)

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

I fixed now CreateToc to link to the headers and
optionally link back to the TOC.

I had to pass the preparsed markup through a lot of expand calls to the 
plugin as $dbi->_markup (hack alert), but I didn't have to change any 
user-dependent argument numbers and now we are able to see the markup as 
XmlElement tree and even change it.

The nesting is not implemented yet and the DHTML expand/collapse also not.
And the worst: I couldn't find the problem in the section extracter, 
with the hairy regex yet. Maybe we have to get rid of the regex and use 
the new preparsed tree to get at the section borders. It's already 
parsed anyway.


Micki Kaufman schrieb:
> More CreateToc feedback:
> 
> 1. the toc should indent to represent the heading depth. I know it's 
> annoying, because level 3 headings (!!!) would get no indent, level 2 
> headings (!!) would get one indent, and level 1 headings (!) would get 2...
> 
> 2. We may want to allow folks to have the output as a bulleted or 
> non-bulleted list.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Automatic categorisation/topicisation

[Alec T. <li...@sw...>]

On Tue, Mar 02, 2004 at 02:09:29PM +0100, Reini Urban wrote:
> Yes,
> please try to write such a feature and post it at the sf.net website
> under RFE (Request Feature Enhancement)

Okay, I will do so.

> http://sourceforge.net/projects/phpwiki/
>
> Can you specify exactly your feature request?
> Automatically add a certain CategoryWord to the bottom of some pages?

Actually, the opposite of that. If I add a wikiword to a page in the
form CategoryFoo, I would like PhpWiki to automatically create a page
called CategoryFoo, listing all the backlinks to it. Similarly with
TopicBar, etc.

--
Evolution: Taking care of those too stupid to take care of themselves.

Re: [Phpwiki-talk] Automatic categorisation/topicisation

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

Yes,
please try to write such a feature and post it at the sf.net website 
under RFE (Request Feature Enhancement)

http://sourceforge.net/projects/phpwiki/

Can you specify exactly your feature request?
Automatically add a certain CategoryWord to the bottom of some pages?

Alec Thomas schrieb:
> Is there a way to automatically generate category/topic pages? By this,
> I mean, the pages that generally contain:
> 
> 	<?plugin BackLinks page=[pagename] noheader=1?>
> 
> eg. CategoryProjects, TopicMail, etc.
> 
> If I heavily categorise my pages, it becomes quite aggravating having to
> perform the same procedure over and over.
> 
> If this feature is not in place, I'd be happy to add it.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] bug report from phpwiki.nightly...

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

thanks for your report!

三重想健身 schrieb:
> phpwiki.nightly.tar.gz 1764954
> hi , I come from Taiwan,
> Yesterday I downloaded phpwiki from 
> http://phpwiki.sf.net/nightly/phpwiki.nightly.tar.gz
> 
> Work with UTF-8 charset encoding in Chinese and MySQL
> 4.0.17 php 4.3.4 apache 2.0.48
> 
> installation procedure along with documents is very
> smoothly.
> 
> HERE SOMETHING WRONG ARE:
> 
> PhotoAlbumPlugin
> 
> lib/plugin/PhotoAlbum.php (In template 'browse') (In
> template 'body') (In template 'html'):271:
> Notice[1024]: Unable to
> getimagesize(http://phpwiki.sourceforge.net/demo/themes/Hawaiian/images/pictures/#
> Sample file for PhotoAlbum plugin)

getimagesize is a php builtin, not gd dependent.
so it seems like that you provided the wrong src for the album.
I will have a look to make the default settings more foolproof, but you
have to play with the src argument.

> Php Wiki Administration/Remove
> 
> lib/plugin/WikiAdminRemove.php (In template 'browse')
> (In template 'body') (In template 'html'):82:
> Warning[2]: Missing argument 4 for collectpages()

I fixed that yesterday at 14:38 CET
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Re: Bugs! - IncludeSiteMap

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

Micki Kaufman schrieb:
> Was wondering if you'd had a chance to bulletproof 'IncludeSiteMap' yet.

I'm just fighting with the culprit extractSection().
Some other plugins use that also.

PS: from this wednesday on I am on a film festival for one week.
So I will have not much time there.

> Thanks so much for bringing it into the code base - it's so close to 
> being complete!
> Micki
> 
>> Reini's rewrite of IncludeSiteMap looks great, but needs a bit more 
>> bugproofing.
>>
>> Right now, it appears not to load the included pages on the second 
>> page load. In addition, it's unclear how to bypass the reclimit and 
>> includepages defaults, to allow inclusion of a page's full content and 
>> modify the depth of recursion.
>>
>> Anyone else using IncludeSiteMap - can you verify?
>>
>> Thanks!
>> Micki
>>
>>> Hi Reini. Testing my migrated wiki in my test environment - 1.3.8 
>>> looks good!
>>>
>>> One question with my tests re: 'IncludeSiteMap' - For document 
>>> chunking (Single-source), we need full, quiet includes as in the 
>>> original.
>>>
>>> Currently, it's defaulted to 50 words, and I can't seem to make a 
>>> change by editing the IncludeSiteMap source. If you have a moment, do 
>>> you mind helping me figure out how can I accomplish this?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings) (Reini Urban)

[Micki K. <mic...@co...>]

More CreateToc feedback:

1. the toc should indent to represent the heading depth. I know it's 
annoying, because level 3 headings (!!!) would get no indent, level 2 
headings (!!) would get one indent, and level 1 headings (!) would 
get 2...

2. We may want to allow folks to have the output as a bulleted or 
non-bulleted list.

Great job!
Micki

>
>
>Forgot to mention. One thing I really liked in Reini's 'pre-spec' 
>was the 'headers' option in:
>  >>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>
>
>With that, one can create Toc's of 'questions' on the page below, 
>and ignore intermediate headings - this would be great for online 
>frequently asked questions, etc.
>
>Looking forward!
>Micki
>
>>
>>
>>Reini:
>>
>>The CreateToc looks good! I'm gonna test it on erratic section 
>>patterns (! with !! but no intermediate !!, etc.)
>>
>>Yes, the anchors are an important next step. Joby - maybe your code 
>>could be helpful!
>>
>>Rocking job!
>>Micki
>>
>>At 10:25 AM -0800 3/1/04, php...@li... wrote:
>>>Message: 11
>>>Date: Mon, 01 Mar 2004 19:19:43 +0100
>>>From: Reini Urban <ru...@x-...>
>>>To: php...@li...
>>>Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings)
>>>
>>>Joby Walker schrieb:
>>>  > I implemented a table of contents in my fork of Phpwiki as a function of
>>>  > using headings ('!').  So if in your page you have:
>>>
>>>Like the CreateToc plugin I just checked in :)
>>>Can I see your source?
>>>For now I didn't change the pagecache, so there are no anchors (a name)
>>>for the links.
>>>
>>>  > !!! Major Section
>>>  > !! minor section
>>>  > ! sub section
>>>  > ! another sub section
>>>  > !! another minor Section
>>>  > ! sub section
>>>  > !!! Last major Section
>>>  >
>>>  > The following TOC would be generated:
>>>  >
>>>  > * Major Section
>>>  >    * minor section
>>>  >       * sub section
>>>  >       * another sub section
>>>  >    * another minor section
>>>  > * Last major section
>>>  >
>>>  > I used unordered lists so that we can control the numbering, but it
>>>  > would be easy to change it to an ordered list.
>>>  >
>>>  > jbw
>>>  >
>>>  > Reini Urban wrote:
>>>  >
>>>  >> I would do it this way:
>>>  >>
>>>  >> ! any page content
>>>  >> <?plugin AnyPlugin ?>
>>>  >> ! more headers
>>>  >> <?plugin AutoToc ?>
>>>  >> nothing really important here at the footer
>>>  >>
>>>  >> AutoToc sees the HTML tree from the previous plugin's and page
>>>  >> content, and modifies it accordingly by recursively stepping through
>>>  >> the tree.
>>>  >>
>>>  >> This seems to be fun to code and the most painless solution.
>>>  >> (I am a former lisp programmer :)
>>>  >>
>>>  >> Micki Kaufman schrieb:
>>>  >>
>>>  >>> What if we approached it differently:
>>>  >>>
>>>  >>> 1. The plugin is an include of the basepage, but only the headings.
>>>  >>> Each is formatted with an anchor href, according to a nomenclature to
>>>  >>> be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4,
>>>  >>> etc.). Since one recursive include is allowed, this should be
>>>  >>> possible (except for TextFormattingRules).
>>>  >>>
>>>  >>> 2. The page belowis rendered as usual, but the presence of the
>>>  >>> AutoToc modifies the display so that the sections are rendered out
>>>  >>> with invisible anchor tags, named using the exact same nomenclature
>>>  >>> as in 1.
>>>  >>>
>>>  >>> This way you don't need two passes, or jscript.
>>>  >>>
>>>  >>> A known limitation: any !'s above the plugin declaration would
>>>  >>> perhaps not have anchors, since they'd be rendered before the
>>>  >>> appearance of the declaration.
>>>  >>>
>>>  >>> What do you think?
>>>  >>> Micki
>>>  >>>
>>>  >>>> Message: 9
>>>  >>>> Date: Wed, 25 Feb 2004 00:53:29 +0100
>>>  >>>> From: Reini Urban <ru...@x-...>
>>>  >>>> To: php...@li...
>>>  >>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto
>>>  >>>> IncludeHeadings)
>>>  >>>>
>>>  >>>> Micki Kaufman schrieb:
>>>  >>>>  > I frequently have use for a bunch of named links - to function
>>>  >>>> like an
>>>  >>>>  > online table of contents.
>>>  >>>>  >
>>>  >>>>  > For an example, see the beginning of the latest build's
>>>  >>>>  > PhpWikiAdministration.
>>>  >>>>
>>>  >>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>
>>>  >>>>
>>>  >>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator.
>>>  >>>> The only problem is that such targets must provide the appropriate
>>>  >>>> <a name=""> tags and gyriations as in PhpWikiAdministration.
>>>  >>>>
>>>  >>>>  > Would be great to be able to insert a code like %%TOC%% or the
>>>  >>>>  > equivalent, and have a series of links display based on heading
>>>  >>>> 1, 2 and
>>>  >>>>  > 3. Named links aren't as important here, because one can use the
>>>  >>>> desired
>>>  >>>>  > text for the headings themselves.
>>>--
>>>Reini Urban
>>>http://xarch.tu-graz.ac.at/home/rurban/
>>>
>>>
>>>
>>>
>>>--__--__--
>>>
>>>_______________________________________________
>>>Phpwiki-talk mailing list
>>>Php...@li...
>>>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>>>
>>>
>>>End of Phpwiki-talk Digest
>>

-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Automatic categorisation/topicisation

[Alec T. <li...@sw...>]

Hello all,

Is there a way to automatically generate category/topic pages? By this,
I mean, the pages that generally contain:

	<?plugin BackLinks page=[pagename] noheader=1?>

eg. CategoryProjects, TopicMail, etc.

If I heavily categorise my pages, it becomes quite aggravating having to
perform the same procedure over and over.

If this feature is not in place, I'd be happy to add it.

Regards,
Alec

--
Evolution: Taking care of those too stupid to take care of themselves.

[Phpwiki-talk] errors while RichTablePlugin in phpwiki.nightly.tar.gz

[<wi...@ya...>]

I got some lines at footer of webpage 

Fatal error: Call to undefined function:
transformtext() in
/var/www/html/lib/plugin/RichTable.php on line 76

regards
http://wi777.com

=====


_________________________________________________________
Do You Yahoo!?
登記免費的 @yahoo.com 中文電子郵件 @ http://chinese.mail.yahoo.com
Get your free @yahoo.com address at http://chinese.mail.yahoo.com

[Phpwiki-talk] bug report from phpwiki.nightly...

[<wi...@ya...>]

phpwiki.nightly.tar.gz 1764954

hi , I come from Taiwan,
Yesterday I downloaded phpwiki from 
http://phpwiki.sf.net/nightly/phpwiki.nightly.tar.gz

Work with UTF-8 charset encoding in Chinese and MySQL
4.0.17 php 4.3.4 apache 2.0.48

installation procedure along with documents is very
smoothly.

HERE SOMETHING WRONG ARE:

PhotoAlbumPlugin

lib/plugin/PhotoAlbum.php (In template 'browse') (In
template 'body') (In template 'html'):271:
Notice[1024]: Unable to
getimagesize(http://phpwiki.sourceforge.net/demo/themes/Hawaiian/images/pictures/#
Sample file for PhotoAlbum plugin)

Php Wiki Administration/Remove

lib/plugin/WikiAdminRemove.php (In template 'browse')
(In template 'body') (In template 'html'):82:
Warning[2]: Missing argument 4 for collectpages()

Regards
http://wi777.com

=====


_________________________________________________________
Do You Yahoo!?
登記免費的 @yahoo.com 中文電子郵件 @ http://chinese.mail.yahoo.com
Get your free @yahoo.com address at http://chinese.mail.yahoo.com

Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings)

[Joby W. <joby@u.washington.edu>]

Looks much more elegant than my pretty brutal hack.   On the anchors one thing 
that was a requirement was a link back to the table of contents -- so I turned 
the heading into an anchor and link back to the TOC.

One thing to consider is how will this interact with the IncludePage Plugin.

jbw

Reini Urban wrote:

> Joby Walker schrieb:
> 
>> I implemented a table of contents in my fork of Phpwiki as a function 
>> of using headings ('!').  So if in your page you have:
> 
> 
> Like the CreateToc plugin I just checked in :)
> Can I see your source?
> For now I didn't change the pagecache, so there are no anchors (a name) 
> for the links.
> 
>> !!! Major Section
>> !! minor section
>> ! sub section
>> ! another sub section
>> !! another minor Section
>> ! sub section
>> !!! Last major Section
>>
>> The following TOC would be generated:
>>
>> * Major Section
>>    * minor section
>>       * sub section
>>       * another sub section
>>    * another minor section
>> * Last major section
>>
>> I used unordered lists so that we can control the numbering, but it 
>> would be easy to change it to an ordered list.
>>
>> jbw
>>
>> Reini Urban wrote:
>>
>>> I would do it this way:
>>>
>>> ! any page content
>>> <?plugin AnyPlugin ?>
>>> ! more headers
>>> <?plugin AutoToc ?>
>>> nothing really important here at the footer
>>>
>>> AutoToc sees the HTML tree from the previous plugin's and page 
>>> content, and modifies it accordingly by recursively stepping through 
>>> the tree.
>>>
>>> This seems to be fun to code and the most painless solution.
>>> (I am a former lisp programmer :)
>>>
>>> Micki Kaufman schrieb:
>>>
>>>> What if we approached it differently:
>>>>
>>>> 1. The plugin is an include of the basepage, but only the headings. 
>>>> Each is formatted with an anchor href, according to a nomenclature 
>>>> to be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, 
>>>> h-4, etc.). Since one recursive include is allowed, this should be 
>>>> possible (except for TextFormattingRules).
>>>>
>>>> 2. The page belowis rendered as usual, but the presence of the 
>>>> AutoToc modifies the display so that the sections are rendered out 
>>>> with invisible anchor tags, named using the exact same nomenclature 
>>>> as in 1.
>>>>
>>>> This way you don't need two passes, or jscript.
>>>>
>>>> A known limitation: any !'s above the plugin declaration would 
>>>> perhaps not have anchors, since they'd be rendered before the 
>>>> appearance of the declaration.
>>>>
>>>> What do you think?
>>>> Micki
>>>>
>>>>> Message: 9
>>>>> Date: Wed, 25 Feb 2004 00:53:29 +0100
>>>>> From: Reini Urban <ru...@x-...>
>>>>> To: php...@li...
>>>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto 
>>>>> IncludeHeadings)
>>>>>
>>>>> Micki Kaufman schrieb:
>>>>>  > I frequently have use for a bunch of named links - to function 
>>>>> like an
>>>>>  > online table of contents.
>>>>>  >
>>>>>  > For an example, see the beginning of the latest build's
>>>>>  > PhpWikiAdministration.
>>>>>
>>>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>
>>>>>
>>>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator.
>>>>> The only problem is that such targets must provide the appropriate
>>>>> <a name=""> tags and gyriations as in PhpWikiAdministration.
>>>>>
>>>>>  > Would be great to be able to insert a code like %%TOC%% or the
>>>>>  > equivalent, and have a series of links display based on heading 
>>>>> 1, 2 and
>>>>>  > 3. Named links aren't as important here, because one can use the 
>>>>> desired
>>>>>  > text for the headings themselves.

[Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings) (Reini Urban)

[Micki K. <mic...@co...>]

Forgot to mention. One thing I really liked in Reini's 'pre-spec' was 
the 'headers' option in:
>>>>  <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>

With that, one can create Toc's of 'questions' on the page below, and 
ignore intermediate headings - this would be great for online 
frequently asked questions, etc.

Looking forward!
Micki

>
>
>Reini:
>
>The CreateToc looks good! I'm gonna test it on erratic section 
>patterns (! with !! but no intermediate !!, etc.)
>
>Yes, the anchors are an important next step. Joby - maybe your code 
>could be helpful!
>
>Rocking job!
>Micki
>
>At 10:25 AM -0800 3/1/04, php...@li... wrote:
>>Message: 11
>>Date: Mon, 01 Mar 2004 19:19:43 +0100
>>From: Reini Urban <ru...@x-...>
>>To: php...@li...
>>Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings)
>>
>>Joby Walker schrieb:
>>  > I implemented a table of contents in my fork of Phpwiki as a function of
>>  > using headings ('!').  So if in your page you have:
>>
>>Like the CreateToc plugin I just checked in :)
>>Can I see your source?
>>For now I didn't change the pagecache, so there are no anchors (a name)
>>for the links.
>>
>>  > !!! Major Section
>>  > !! minor section
>>  > ! sub section
>>  > ! another sub section
>>  > !! another minor Section
>>  > ! sub section
>>  > !!! Last major Section
>>  >
>>  > The following TOC would be generated:
>>  >
>>  > * Major Section
>>  >    * minor section
>>  >       * sub section
>>  >       * another sub section
>>  >    * another minor section
>>  > * Last major section
>>  >
>>  > I used unordered lists so that we can control the numbering, but it
>>  > would be easy to change it to an ordered list.
>>  >
>>  > jbw
>>  >
>>  > Reini Urban wrote:
>>  >
>>  >> I would do it this way:
>>  >>
>>  >> ! any page content
>>  >> <?plugin AnyPlugin ?>
>>  >> ! more headers
>>  >> <?plugin AutoToc ?>
>>  >> nothing really important here at the footer
>>  >>
>>  >> AutoToc sees the HTML tree from the previous plugin's and page
>>  >> content, and modifies it accordingly by recursively stepping through
>>  >> the tree.
>>  >>
>>  >> This seems to be fun to code and the most painless solution.
>>  >> (I am a former lisp programmer :)
>>  >>
>>  >> Micki Kaufman schrieb:
>>  >>
>>  >>> What if we approached it differently:
>>  >>>
>>  >>> 1. The plugin is an include of the basepage, but only the headings.
>>  >>> Each is formatted with an anchor href, according to a nomenclature to
>>  >>> be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4,
>>  >>> etc.). Since one recursive include is allowed, this should be
>>  >>> possible (except for TextFormattingRules).
>>  >>>
>>  >>> 2. The page belowis rendered as usual, but the presence of the
>>  >>> AutoToc modifies the display so that the sections are rendered out
>>  >>> with invisible anchor tags, named using the exact same nomenclature
>>  >>> as in 1.
>>  >>>
>>  >>> This way you don't need two passes, or jscript.
>>  >>>
>>  >>> A known limitation: any !'s above the plugin declaration would
>>  >>> perhaps not have anchors, since they'd be rendered before the
>>  >>> appearance of the declaration.
>>  >>>
>>  >>> What do you think?
>>  >>> Micki
>>  >>>
>>  >>>> Message: 9
>>  >>>> Date: Wed, 25 Feb 2004 00:53:29 +0100
>>  >>>> From: Reini Urban <ru...@x-...>
>>  >>>> To: php...@li...
>>  >>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto
>>  >>>> IncludeHeadings)
>>  >>>>
>>  >>>> Micki Kaufman schrieb:
>>  >>>>  > I frequently have use for a bunch of named links - to function
>>  >>>> like an
>>  >>>>  > online table of contents.
>>  >>>>  >
>>  >>>>  > For an example, see the beginning of the latest build's
>>  >>>>  > PhpWikiAdministration.
>>  >>>>
>>  >>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>
>>  >>>>
>>  >>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator.
>>  >>>> The only problem is that such targets must provide the appropriate
>>  >>>> <a name=""> tags and gyriations as in PhpWikiAdministration.
>>  >>>>
>>  >>>>  > Would be great to be able to insert a code like %%TOC%% or the
>>  >>>>  > equivalent, and have a series of links display based on heading
>>  >>>> 1, 2 and
>>  >>>>  > 3. Named links aren't as important here, because one can use the
>>  >>>> desired
>>  >>>>  > text for the headings themselves.
>>--
>>Reini Urban
>>http://xarch.tu-graz.ac.at/home/rurban/
>>
>>
>>
>>
>>--__--__--
>>
>>_______________________________________________
>>Phpwiki-talk mailing list
>>Php...@li...
>>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>>
>>
>>End of Phpwiki-talk Digest
>

-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings) (Reini Urban)

[Micki K. <mic...@co...>]

Reini:

The CreateToc looks good! I'm gonna test it on erratic section 
patterns (! with !! but no intermediate !!, etc.)

Yes, the anchors are an important next step. Joby - maybe your code 
could be helpful!

Rocking job!
Micki

At 10:25 AM -0800 3/1/04, php...@li... wrote:
>Message: 11
>Date: Mon, 01 Mar 2004 19:19:43 +0100
>From: Reini Urban <ru...@x-...>
>To: php...@li...
>Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings)
>
>Joby Walker schrieb:
>>  I implemented a table of contents in my fork of Phpwiki as a function of
>>  using headings ('!').  So if in your page you have:
>
>Like the CreateToc plugin I just checked in :)
>Can I see your source?
>For now I didn't change the pagecache, so there are no anchors (a name)
>for the links.
>
>>  !!! Major Section
>>  !! minor section
>>  ! sub section
>>  ! another sub section
>>  !! another minor Section
>>  ! sub section
>>  !!! Last major Section
>>
>>  The following TOC would be generated:
>>
>>  * Major Section
>>     * minor section
>>        * sub section
>>        * another sub section
>>     * another minor section
>>  * Last major section
>>
>>  I used unordered lists so that we can control the numbering, but it
>>  would be easy to change it to an ordered list.
>>
>>  jbw
>>
>>  Reini Urban wrote:
>>
>>>  I would do it this way:
>>>
>>>  ! any page content
>>>  <?plugin AnyPlugin ?>
>>>  ! more headers
>>>  <?plugin AutoToc ?>
>>>  nothing really important here at the footer
>>>
>>>  AutoToc sees the HTML tree from the previous plugin's and page
>>>  content, and modifies it accordingly by recursively stepping through
>>>  the tree.
>>>
>>>  This seems to be fun to code and the most painless solution.
>>>  (I am a former lisp programmer :)
>>>
>>>  Micki Kaufman schrieb:
>>>
>>>>  What if we approached it differently:
>>>>
>>>>  1. The plugin is an include of the basepage, but only the headings.
>>>>  Each is formatted with an anchor href, according to a nomenclature to
>>>>  be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4,
>>>>  etc.). Since one recursive include is allowed, this should be
>>>>  possible (except for TextFormattingRules).
>>>>
>>>>  2. The page belowis rendered as usual, but the presence of the
>>>>  AutoToc modifies the display so that the sections are rendered out
>>>>  with invisible anchor tags, named using the exact same nomenclature
>>>>  as in 1.
>>>>
>>>>  This way you don't need two passes, or jscript.
>>>>
>>>>  A known limitation: any !'s above the plugin declaration would
>>>>  perhaps not have anchors, since they'd be rendered before the
>>>>  appearance of the declaration.
>>>>
>>>>  What do you think?
>>>>  Micki
>>>>
>>>>>  Message: 9
>>>>>  Date: Wed, 25 Feb 2004 00:53:29 +0100
>>>>>  From: Reini Urban <ru...@x-...>
>>>>>  To: php...@li...
>>>>>  Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto
>>>>>  IncludeHeadings)
>>>>>
>>>>>  Micki Kaufman schrieb:
>>>>>   > I frequently have use for a bunch of named links - to function
>>>>>  like an
>>>>>   > online table of contents.
>>>>>   >
>>>>>   > For an example, see the beginning of the latest build's
>>>>>   > PhpWikiAdministration.
>>>>>
>>>>>  <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>
>>>>>
>>>>>  Yes, MoinMoin (I think) has a cool jscript based heading navigator.
>>>>>  The only problem is that such targets must provide the appropriate
>>>>>  <a name=""> tags and gyriations as in PhpWikiAdministration.
>>>>>
>>>>>   > Would be great to be able to insert a code like %%TOC%% or the
>>>>>   > equivalent, and have a series of links display based on heading
>>>>>  1, 2 and
>>>>>   > 3. Named links aren't as important here, because one can use the
>>>>>  desired
>>>>>   > text for the headings themselves.
>--
>Reini Urban
>http://xarch.tu-graz.ac.at/home/rurban/
>
>
>
>
>--__--__--
>
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
>
>End of Phpwiki-talk Digest


-- 

Micki
mailto:mic...@co...

RE: [Phpwiki-talk] Odd ADODB error...

[electron <ele...@mg...>]

Delete your cookie as well or in substitution of login/logout

-Jtp




I've stopped 7,414 spam messages. You can too!
One month FREE spam protection at http://www.cloudmark.com/spamnetsig/}
-----Original Message-----
From: php...@li...
[mailto:php...@li...] On Behalf Of Reini =
Urban
Sent: Monday, March 01, 2004 12:14 PM
To: John Cole
Cc: php...@li...
Subject: Re: [Phpwiki-talk] Odd ADODB error...

John Cole schrieb:
>>From the current CVS version, I have encountered an odd error using =
ADODB:
>  Fatal error: Unknown(): The script tried to execute a method or =
access a
> property of an incomplete object. Please ensure that the class =
definition
> <b>wikiuser</b> of the object you are trying to operate on was loaded
> _before_ the session was started in C:\Program Files\Apache
> Group\Apache2\htdocs\phpwiki\lib\main.php on line 539=20
>=20
> Switching back and forth between ADODB and SQL fixes or duplicates the
> problem.  Today was the first time I had turned on ADODB with phpWiki
(I've
> used ADODB in the past and like it a lot) and had seen other using it
lately
> so I decided to give it a try.  It seem to work fine for the past few
hours
> and suddenly came up with this error.  Like I said, really odd.  No =
recent
> edits and no changes to anything.

Yes, That's the a question in the new auth FAQ.
See doc/README.phpwiki-auth

php internal session problem, now known workaround yet, restart browser.
only happens when you try out different pref objects in one session.

logout - change - login helps also.



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings)

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

Joby Walker schrieb:
> I implemented a table of contents in my fork of Phpwiki as a function of 
> using headings ('!').  So if in your page you have:

Like the CreateToc plugin I just checked in :)
Can I see your source?
For now I didn't change the pagecache, so there are no anchors (a name) 
for the links.

> !!! Major Section
> !! minor section
> ! sub section
> ! another sub section
> !! another minor Section
> ! sub section
> !!! Last major Section
> 
> The following TOC would be generated:
> 
> * Major Section
>    * minor section
>       * sub section
>       * another sub section
>    * another minor section
> * Last major section
> 
> I used unordered lists so that we can control the numbering, but it 
> would be easy to change it to an ordered list.
> 
> jbw
> 
> Reini Urban wrote:
> 
>> I would do it this way:
>>
>> ! any page content
>> <?plugin AnyPlugin ?>
>> ! more headers
>> <?plugin AutoToc ?>
>> nothing really important here at the footer
>>
>> AutoToc sees the HTML tree from the previous plugin's and page 
>> content, and modifies it accordingly by recursively stepping through 
>> the tree.
>>
>> This seems to be fun to code and the most painless solution.
>> (I am a former lisp programmer :)
>>
>> Micki Kaufman schrieb:
>>
>>> What if we approached it differently:
>>>
>>> 1. The plugin is an include of the basepage, but only the headings. 
>>> Each is formatted with an anchor href, according to a nomenclature to 
>>> be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4, 
>>> etc.). Since one recursive include is allowed, this should be 
>>> possible (except for TextFormattingRules).
>>>
>>> 2. The page belowis rendered as usual, but the presence of the 
>>> AutoToc modifies the display so that the sections are rendered out 
>>> with invisible anchor tags, named using the exact same nomenclature 
>>> as in 1.
>>>
>>> This way you don't need two passes, or jscript.
>>>
>>> A known limitation: any !'s above the plugin declaration would 
>>> perhaps not have anchors, since they'd be rendered before the 
>>> appearance of the declaration.
>>>
>>> What do you think?
>>> Micki
>>>
>>>> Message: 9
>>>> Date: Wed, 25 Feb 2004 00:53:29 +0100
>>>> From: Reini Urban <ru...@x-...>
>>>> To: php...@li...
>>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto 
>>>> IncludeHeadings)
>>>>
>>>> Micki Kaufman schrieb:
>>>>  > I frequently have use for a bunch of named links - to function 
>>>> like an
>>>>  > online table of contents.
>>>>  >
>>>>  > For an example, see the beginning of the latest build's
>>>>  > PhpWikiAdministration.
>>>>
>>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>
>>>>
>>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator.
>>>> The only problem is that such targets must provide the appropriate
>>>> <a name=""> tags and gyriations as in PhpWikiAdministration.
>>>>
>>>>  > Would be great to be able to insert a code like %%TOC%% or the
>>>>  > equivalent, and have a series of links display based on heading 
>>>> 1, 2 and
>>>>  > 3. Named links aren't as important here, because one can use the 
>>>> desired
>>>>  > text for the headings themselves.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Odd ADODB error...

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

John Cole schrieb:
>>From the current CVS version, I have encountered an odd error using ADODB:
>  Fatal error: Unknown(): The script tried to execute a method or access a
> property of an incomplete object. Please ensure that the class definition
> <b>wikiuser</b> of the object you are trying to operate on was loaded
> _before_ the session was started in C:\Program Files\Apache
> Group\Apache2\htdocs\phpwiki\lib\main.php on line 539 
> 
> Switching back and forth between ADODB and SQL fixes or duplicates the
> problem.  Today was the first time I had turned on ADODB with phpWiki (I've
> used ADODB in the past and like it a lot) and had seen other using it lately
> so I decided to give it a try.  It seem to work fine for the past few hours
> and suddenly came up with this error.  Like I said, really odd.  No recent
> edits and no changes to anything.

Yes, That's the a question in the new auth FAQ.
See doc/README.phpwiki-auth

php internal session problem, now known workaround yet, restart browser.
only happens when you try out different pref objects in one session.

logout - change - login helps also.

RE: [Phpwiki-talk] LDAP Authentication...

[John C. <joh...@ua...>]

Reini,
  I updated to the latest editpage.tmpl and tried to look at
OldTextFormattingRules, but I can't load that page, apache cores (it cores
with line 121 removed in editpage.tmpl removed too).

  Since there were a lot of post related to this problem, I assume that it
is common to php 4.3/win32 users.  I don't know if it happens with IIS or
Apache 1.3 or if it is only with Apache 2 (I'm running Apache 2.0.48)  

  Have you been able to duplicate this issue or does your development
enviroment work as expected?

  I undertsand about setting priorities and RichTable.  I was looking for a
little more formatting control on our HomePage while allowing everyone the
ability to edit it, and RichTable looked perfect :-)

Thanks,

John Cole

-----Original Message-----
From: Reini Urban [mailto:ru...@x-...]
Sent: Monday, March 01, 2004 10:41 AM
To: John Cole; php...@li...
Subject: Re: [Phpwiki-talk] LDAP Authentication...


John Cole schrieb:
> --- Reini Urban <ru...@x-...> wrote:
> I have a fresh copy from CVS this morning and things seem to look very
good.
> Here is a small list of things I have noticed so far:
> 
> *  Line 121 of themes\default\templates\editpage.tmpl causes PHP 4.3.4 on
> windows to core apache when you attempt to edit a page.  Removing this
line
> fixes this.

yep. thanks. the fix is to check the content of your 
OldTextFormattingRules page.

But really IncludePage has to be foolproof. same with UnfoldSubpages.
I'm just looking into that. CreateToc is similar to IncludePage, so that 
will ready soon too.

> * RichTable plugin is not working correctly (it does not parse plugins or
> wiki words) and it throws a dozen warnings at the bottom of the page like:
> 
> C:\Program Files\Apache
> Group\Apache2\htdocs\phpwiki\lib\plugin\RichTable.php (In template
'browse')
> (In template 'body') (In template 'html'):139: Notice[8]: Undefined
offset:
 > 1

This is not priority for me now. It's a hack anway.


-------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

[Phpwiki-talk] Odd ADODB error...

[John C. <joh...@ua...>]

From the current CVS version, I have encountered an odd error using ADODB:

 Fatal error: Unknown(): The script tried to execute a method or access a
property of an incomplete object. Please ensure that the class definition
<b>wikiuser</b> of the object you are trying to operate on was loaded
_before_ the session was started in C:\Program Files\Apache
Group\Apache2\htdocs\phpwiki\lib\main.php on line 539 

Switching back and forth between ADODB and SQL fixes or duplicates the
problem.  Today was the first time I had turned on ADODB with phpWiki (I've
used ADODB in the past and like it a lot) and had seen other using it lately
so I decided to give it a try.  It seem to work fine for the past few hours
and suddenly came up with this error.  Like I said, really odd.  No recent
edits and no changes to anything.

Thanks,

John Cole

-------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

Re: [Phpwiki-talk] LDAP Authentication...

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

John Cole schrieb:
> --- Reini Urban <ru...@x-...> wrote:
> I have a fresh copy from CVS this morning and things seem to look very good.
> Here is a small list of things I have noticed so far:
> 
> *  Line 121 of themes\default\templates\editpage.tmpl causes PHP 4.3.4 on
> windows to core apache when you attempt to edit a page.  Removing this line
> fixes this.

yep. thanks. the fix is to check the content of your 
OldTextFormattingRules page.

But really IncludePage has to be foolproof. same with UnfoldSubpages.
I'm just looking into that. CreateToc is similar to IncludePage, so that 
will ready soon too.

> * RichTable plugin is not working correctly (it does not parse plugins or
> wiki words) and it throws a dozen warnings at the bottom of the page like:
> 
> C:\Program Files\Apache
> Group\Apache2\htdocs\phpwiki\lib\plugin\RichTable.php (In template 'browse')
> (In template 'body') (In template 'html'):139: Notice[8]: Undefined offset:
 > 1

This is not priority for me now. It's a hack anway.

> I really like the themes your freinds had.  It would be great if the
> artistic folk could increase the number of default themes included with
> phpWiki.  The project really does look like its reaching critical mass.
> Great work.

I added now "smaller", my default AcadWiki theme, which adds the SignIn 
button at the bottom (as some years ago), because lots of my users 
complained that they cannot change any page, and didn't know how to login.
For not signedin users there's only a "Info" bottom at the bottom, 
behind the Info botton is the whole range of actionbar buttons: edit, 
diff, history, ...
At the top of the PageInfo page I also have a statement to login,
when someone wants to change something.
And the navbar at the top has only short names (News, Search:) and links 
instead of  buttons.

It just looks cleaner this way. it's not yet 10pt as the others CMS 
have, but less than before.

The nuke theme is some major grafical work, esp. for the consistent look 
of WikiForum, WhoIsOnline and WikiBlog, which I cannot finish now.
Also the sidebars. I wanted to do a standard 3 columns layout.

I have to get rid of the remaining auth problems on the sf.net server. 
On my servers it works ok.
I fixed the demo virtual hosts again (adodb,dba,de,en,fr,...) but 
gettext localization is broken again. Even with the patch suggestion on 
the sf.net site.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] feature idea - TOC (de facto IncludeHeadings)

[Joby W. <joby@u.washington.edu>]

I implemented a table of contents in my fork of Phpwiki as a function of using 
headings ('!').  So if in your page you have:


!!! Major Section
!! minor section
! sub section
! another sub section
!! another minor Section
! sub section
!!! Last major Section

The following TOC would be generated:

* Major Section
    * minor section
       * sub section
       * another sub section
    * another minor section
* Last major section

I used unordered lists so that we can control the numbering, but it would be 
easy to change it to an ordered list.

jbw

Reini Urban wrote:
> I would do it this way:
> 
> ! any page content
> <?plugin AnyPlugin ?>
> ! more headers
> <?plugin AutoToc ?>
> nothing really important here at the footer
> 
> AutoToc sees the HTML tree from the previous plugin's and page content, 
> and modifies it accordingly by recursively stepping through the tree.
> 
> This seems to be fun to code and the most painless solution.
> (I am a former lisp programmer :)
> 
> Micki Kaufman schrieb:
> 
>> What if we approached it differently:
>>
>> 1. The plugin is an include of the basepage, but only the headings. 
>> Each is formatted with an anchor href, according to a nomenclature to 
>> be decided (like perhaps h-1, h-11, h-111, h-2, h-22, h-23, h-3, h-4, 
>> etc.). Since one recursive include is allowed, this should be possible 
>> (except for TextFormattingRules).
>>
>> 2. The page belowis rendered as usual, but the presence of the AutoToc 
>> modifies the display so that the sections are rendered out with 
>> invisible anchor tags, named using the exact same nomenclature as in 1.
>>
>> This way you don't need two passes, or jscript.
>>
>> A known limitation: any !'s above the plugin declaration would perhaps 
>> not have anchors, since they'd be rendered before the appearance of 
>> the declaration.
>>
>> What do you think?
>> Micki
>>
>>> Message: 9
>>> Date: Wed, 25 Feb 2004 00:53:29 +0100
>>> From: Reini Urban <ru...@x-...>
>>> To: php...@li...
>>> Subject: Re: [Phpwiki-talk] feature idea - TOC (de facto 
>>> IncludeHeadings)
>>>
>>> Micki Kaufman schrieb:
>>>  > I frequently have use for a bunch of named links - to function 
>>> like an
>>>  > online table of contents.
>>>  >
>>>  > For an example, see the beginning of the latest build's
>>>  > PhpWikiAdministration.
>>>
>>> <?plugin AutoToc jscript_hide=1 headers=1,2,3 ?>
>>>
>>> Yes, MoinMoin (I think) has a cool jscript based heading navigator.
>>> The only problem is that such targets must provide the appropriate
>>> <a name=""> tags and gyriations as in PhpWikiAdministration.
>>>
>>>  > Would be great to be able to insert a code like %%TOC%% or the
>>>  > equivalent, and have a series of links display based on heading 1, 
>>> 2 and
>>>  > 3. Named links aren't as important here, because one can use the 
>>> desired
>>>  > text for the headings themselves.
>>> -- 
>>> Reini Urban
>>> http://xarch.tu-graz.ac.at/home/rurban/
>>
>>
>>
>>
> 
> 

Re: [Phpwiki-talk] LDAP Authentication...

[John C. <joh...@ua...>]

--- Reini Urban <ru...@x-...> wrote:
> John Cole schrieb:
> 
> > Reini,
> >   Here is the patch and the lines needed for AD in
> the
> > index.php.  Both are zipped so hopefully they will
> be
> > readable.
> > 
> >   Note:  you will need to rename the extension to
> zip,
> > as SF is blocking all zip files.
> 
> 
> Can you live with the most recent WikiUserNew
> constants?
> 
> I don't think that you need the 2nd port argument to
> ldap_connect
> "ldap://server:port" should be enough, can you
> verify?
> 

Reini,
  You are correct, the ldap port does not need to be specified.  I cleaned
up some of the code so it doesn't throw php warnings about undefined
constants:

$LDAP_SET_OPTION = array(LDAP_OPT_PROTOCOL_VERSION => 3,
                         LDAP_OPT_REFERRALS, 0);
if (!defined('LDAP_AUTH_USER')) define('LDAP_AUTH_USER', "CN=a ldap
user,CN=Users,DC=company,DC=com");
if (!defined('LDAP_AUTH_PASSWORD')) define('LDAP_AUTH_PASSWORD', 'your
password');
if (!defined('LDAP_SEARCH_FIELD')) define('LDAP_SEARCH_FIELD',
'sAMAccountName'); // might be different from uid, 

I have a fresh copy from CVS this morning and things seem to look very good.
Here is a small list of things I have noticed so far:

*  Line 121 of themes\default\templates\editpage.tmpl causes PHP 4.3.4 on
windows to core apache when you attempt to edit a page.  Removing this line
fixes this.

* RichTable plugin is not working correctly (it does not parse plugins or
wiki words) and it throws a dozen warnings at the bottom of the page like:

C:\Program Files\Apache
Group\Apache2\htdocs\phpwiki\lib\plugin\RichTable.php (In template 'browse')
(In template 'body') (In template 'html'):139: Notice[8]: Undefined offset:
1

I really like the themes your freinds had.  It would be great if the
artistic folk could increase the number of default themes included with
phpWiki.  The project really does look like its reaching critical mass.
Great work.

John Cole

-------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

Re: [Phpwiki-talk] Re: Standard Content Storage API

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

SF Markus Elfring schrieb:
>>PhpWiki has now experimental SOAP support, using the nusoap library.
>>The first plugin is using the Google API, the Amazon plugin will come soon.
> 
> How will the web service definitions for PhpWiki itself look like?

http://phpwiki.sourceforge.net/phpwiki/PhpWiki.wdsl

This will probably need more credentials arguments.

I believe each call must have a credentials hash.
(username + optional password), though the whole credtential argument is 
optional. Depends on the wiki permission settings.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Re: Standard Content Storage API

[SF M. E. <el...@us...>]

> > I would like to see a PHP class library that can be used like the Java API.
> syntax or feature-wise or quality?

I'm excited so see and use all the functionality that is provided by Java already to become available for PHP.

Re: [Phpwiki-talk] Re: Standard Content Storage API

[SF M. E. <el...@us...>]

> PhpWiki has now experimental SOAP support, using the nusoap library.
> The first plugin is using the Google API, the Amazon plugin will come soon.

How will the web service definitions for PhpWiki itself look like?

Re: [Phpwiki-talk] Error after installing. New with wikiwiki and php, please help

[Sebastian B. <s-b...@gm...>]

Jorge,

you give pretty less information about what you did. I am ready to assist as
long as I can get thru it - you might wish to contact me privately in order
to not to flood this list. As a starting point, this looks pretty much like a
database connection issue. Are you sure the database is setup correctly? Did
you give the correct credentials in your index.php? Which of the necessary
install steps have you done, which were done by the provider?

Kind regards,

Sebastian

> I just contracted a hosting with onhost.ws and as an option you can
> install 
> the wikiwiki, however, after doing that, I got the following error:
> 
> 
> lib/WikiDB/backend/PearDB.php:32: Fatal[256]: Can't connect to database: 
> wikidb_backend_mysql: fatal database error
> 
> DB Error: connect failed
> ( [nativecode=Access denied for user: 'visiongp_phpwiki1@localhost' (Using
> 
> password: YES)] ** 
> mysql://visiongp_phpwiki1:XXXXXXXX@localhost/visiongp_phpwiki1)
> 
> 
> I've been looking for this problem but I had no luck. Unfortunatelly the 
> hosting company does not provide any assistance to the matter.
> 
> I will appreciate if somebody can help me (for dummies) how to fix this 
> problem.
> 
> Thank you for your time.
> 
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
> http://join.msn.com/?page=features/featuredemail
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>