phpwiki-talk

[Phpwiki-talk] mysqli extension

[Arthaey A. <ar...@gm...>]

I'm trying to view the virgin wiki setup of a newly installed PhpWiki,
but it's coming up blank. Debugging and googling as much as I could, I
think that the problem is related to my using the mysqli extension
with PHP, rather than mysql.

Below is the error message I get normally:

Fatal Error:

lib/WikiDB/backend/PearDB.php:35: Error[256]: Can't connect to
database: WikiDB_backend_PearDB_mysql: fatal database error

    * DB Error: extension not found
    * (mysql://wikiuser:XXXXXXXX@127.0.0.1/phpwiki)
    *

lib/WikiDB/backend/PearDB.php:35: Error[256]: Can't connect to
database: WikiDB_backend_PearDB_mysql: fatal database error

    * DB Error: extension not found
    * (mysql://wikiuser:XXXXXXXX@127.0.0.1/phpwiki)


And this is what I get is I try changing

    DATABASE_DSN = "mysql://wikiuser:password@127.0.0.1/phpwiki"

to

    DATABASE_DSN = "mysqli://wikiuser:password@127.0.0.1/phpwiki"

Fatal error: Class 'WikiDB_backend_PearDB_mysqli' not found in
/home/arthaey/workspace/PhpWiki/lib/WikiDB/SQL.php on line 20

I also tried, just for the heck of it, renaming all mysql_* function
calls in lib/WikiDB/backend/PearDB_mysql to mysqli_*, without any
effect.

Advice at this point would be much appreciated.


SYSTEM INFO
============

I've reinstalled my system, where I had a working version of PhpWiki
1.3.10, MySQL 3-something, PHP 4.3.8, Apache 2.0.50, and Mandrake 9.2.

My new system runs Mandrake 10.1, MySQL 4.1.5 gamma, PHP 5.0.1, Apache
2.0.52, and the current CVS version of PhpWiki. The Apache-PHP-MySQL
combination works fine -- or at least phpMyAdmin works fine.

My phpinfo() can be seen at:

   http://arthaey.mine.nu:8080/~arthaey/

-- 
AA

Re: [Phpwiki-talk] Some memory tests

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

Reini Urban schrieb:
> http://phpwiki.sourceforge.net/phpwiki/PhpMemoryExhausted/Testresults

Ok, backporting the unittest suite to 1.3.4 found the memory hog:

// test	                nr      USECACHE (t/f)
beforePEAR		1	6644	6640
beforePhpWiki		2	6872	6868
PhpWikiLoaded		3	9064	9064
PhpWikiInitialized	4	9420	9432
testimportoldmarkup	5	10388	10380
testsetupwiki		6	11996	11976
testallpages		7	12200	12172
test02orphanedpages	8	12208	12176
test03textformattingru	9	12208	12176
test99dumphtml		10	12208	12180

// PARAMS:
// PHPWIKI_VERSION=1.3.4
// PHP_SAPI=cgi
// PHP_OS=WINNT
// PHP_VERSION=4.1.2
// test=SetupWiki,AllPagesTest,DumpHtml
// db=dba
// debug=9
// level=2
// pid=1756
// USE_DB_SESSION=false
// CREATED=Thu Oct 21 02:58:52 GMT 2004

against:

// test        nr      USECACHE (t/f)  WIKIDB_NCM(t/f) USERNEW (t/f) 
beforePEAR     1       6636    6636    6636    6636    6636    6636 
beforePhpWiki  2       6864    6864    6880    6880    6876    6876 
PhpWikiLoaded  3       11924   11920   11932   11932   11912   11112 
PhpWikiInitial 4       12376   12364   12368   12368   12376   11544 
testimportoldm 5       14968   14928   14952   14964   14948   14120 
testsetupwiki  6       15264   15104   15240   15260   15248   14424 
test01rateit   7       16496   16196   16504   16508   16480   15672 
test02orphaned 8       16540   16232   16544   16556   16548   15716 
test03oldtextf 9       16592   16256   16540   16564   16568   15728 
test99dumphtml 10      32972   32644   33060   33108   -1      -1

// PARAMS:
// PHPWIKI_VERSION=1.3.11pre-20041020
// PHP_SAPI=cgi
// PHP_OS=WINNT
// PHP_VERSION=4.1.2
// test=SetupWiki,DumpHtml
// db=dba
// debug=9
// level=2
// CREATED=Wed Oct 20 21:16:52 GMT 2004


What do you see?
Well, that phpwiki-1.3.11 is 5068KB large and phpwiki-1.3.4 only 2196KB.
During huge runs (SetupWiki,AllPages) there's a 4MB difference.

But 1.3.4 needed no additional memory at all for our biggest memory hog, 
dumphtml.
Why? clearly because of our new output buffering.
1.3.4 uses no buffering, at 1.3.7 buffering was introduced.
And any ob_clean() doesn't release any memory!
These are the 4.1.2 results, the sf.net platform.
4.3.9 is only 4MB better at dumphtml. (12MB <=> 16MB)

Yes, I've already tried:
       if (!empty($this->_is_buffering_output)) {
           while (@ob_end_flush());
           ob_clean();
           ob_start();
       }
dumphtml always need 16MB on the default pageset, even with ob restarts 
in the loop.

So it looks like we have to turn this ob buffering off.
At least add a constant to do without, so that it can work on servers 
with memory-limit = 8MB.
At least I've found the real culprit. no stupid refs or object tricks.

And I've found tons of otherwise undetected bugs.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Some memory tests

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

http://phpwiki.sourceforge.net/phpwiki/PhpMemoryExhausted/Testresults
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Getting phpWiki help

[Tom H. <ha...@sp...>]

Dear Developers,

I appreciate your efforts on phpWiki.  It is extremely difficult to get any
help administering a phpWiki site.

* I would like to change the title of the default home page.
* I would like to change the global access preferences, but I don't see
anything in the Admin area.  I do remember something about this somewhere,
but I can no longer find it.

Can you help?

Thanks so much,

Tom Haws

[Phpwiki-talk] Funky people wanted!

[METSTUDENT <ma...@me...>]

START WORK FRIDAY NIGHT?

We are currently looking for intelligent, trendy, fun, outgoing individuals to join our street PR team in Soho (central London). Earn up to £200 in just 3-4 hours work promoting exclusive nights & events. We are arranging interviews throughout this week to find the perfect team for our new night at Click & subsequent nights in the future.  If you think you got what it takes, & you would like to work for one of London's top events companies, send an email immediately to opp...@me...  with you contact details or call Val or Dihan on 0870 750 6374

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

This week Fly @ trap goes off with a BANG! To place yourself & friends on the guestlist email names to: guestlist@metparties.,com 


To become a metparties members or to find out more about us vist www.metparties.com & subscribe your personal email address for up to date news & exclusive invites.



--

You may automatically unsubscribe from this list at any time b visiting the following URL:

<http://www.metparties.com/cgi-bin/newsletter/mail.cgi?f=u&l=students&e=php...@li...&p=18127001>

If the above URL is inoperable, make sure that you have copied the entire address. Some mail readers will wrap a long URL and thus break this automatic unsubscribe mechanism.

Re: [Phpwiki-talk] phpwiki-1.3.11pre, php-warning in session.

[ReymanX <re...@gm...>]

The problem is,  it's my new installation. I just install with mysql
and phpwiki-1.3.11pre. I've try to reinstall it, drop the database,
create new database and install again, but still had the same problem.
In my hosting server /tmp is not accessible, so i try to redirect
session_path to my homedir, but still no luck. Is it have something to
do with where the session should be stored ?

> Hey,
> 
> i'd updated my phpwiki and had forget to update the database structure.
> 
> So i had the same problem and no idea why.
> After creating a new Database with the new DB-Modell and inserting the
> old content all works fine.
> 
> cheerio
> 
> ReymanX schrieb am 15.10.2004 04:07  folgendes:
> 
> 
> > I just successfully install phpwiki-1.3.11pre in my debian, with
> > apache 1.3.x. And now, i'd like to install in my hosting server, when
> > Iit load a virgin wiki, it runs well. But when I go to HomePage or any
> > pages, there always php-warning something like this:
> > lib/DbSession.php:75: Warning[2]: ini_set(): A session is active. You
> > cannot change the session module's ini settings at this time.
> > And I always promtp username-password even when I log as admin
> > everytime I go to any page.
> > FYI, my hosting server not allow apache to write in home-directory,
> > does it cause this problem ?
> >
> > regards,
> >
> 
> 


-- 
Arie Reynaldi Zanahar
reymanx at gmail.com
http://www.reynaldi.com

Re: [Phpwiki-talk] yet another strange problem with themes

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

Arnaud Fontaine schrieb:
> Le sam 09/10/2004 à 17:39, Reini Urban a écrit :
> 
>>Arnaud Fontaine schrieb:
>>
>>>I was migrating a 1.3.4/gdbm running wiki using my own theme to a cvs
>>>export version with MySQL as a backend.
>>
>>gdbm locking problems also? those php guys should be beaten!
> 
> No. But a gdbm based wiki is VERY slow on RecentChanges, for exemple,
> when you are around 1000 pages. Or you need a damned amount of RAM ...
> Only have 1.5 GB on my server.

hmm, I always test with about 1500 pages, with various databases.
also db3 and gdbm. And I have only 500MB physical RAM. But this is on 
windows.

>>local import would have been much faster. just give source=... to 
>>action=loadfile. anyway.
>>upload is not very good.
> 
> 
> Yes but how do you specify the admin login and password ??
> http://user:pass@site/ ??

what for?
edit config/config.ini (define the DATABASE_TYPE and optionally the 
DATABASE_DSN)

browse to http://mywiki/PhpWikiAdministration
sign in as admin,
scroll to [ Load File ]
enter the local filesystem path to the saved pgsrc dir and click on [ 
Load File ].

or as shortcut, use 
http://mywiki/?action=loadfile&source=/home/user/phpwiki/pgsrc&overwrite=1


>>>I also noted that the UserPreferences looks to the list of themes in this
>>>directory and not in the local themes directory ...

>>For the themes loader see below:
>>So either PHPWIKI_DIR is empty or wrong. NormalizeLocalFileName is in 
>>FileFinder.php, and adds PHPWIKI_DIR if defined.
> 
> hmmm .... is PHPWIKI_DIR your wiki local dir or your phpwiki install dir
> ???

I always have only one php source directory. with one themes directory. 
Just variosu starter scripts, and optionally various config.ini.

> I might have misunderstood this since ... the very begining :)
> 
> But well ...
> 
> The real problem is : when I use my migrated theme, phpwiki ALWAYS
> switches to the default theme.
> 
> I tried with some other themes like sidebar, wordpress, crao, etc ...
> they are all fine. And when I try wikilens theme ... it switches to the
> default theme ...
> 
> Did you change some fundamental stuffs in the theme API ??

Yes, I renamed $Theme to $WikiTheme.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] yet another strange problem with themes

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

Le sam 09/10/2004 =E0 17:39, Reini Urban a =E9crit :
> Arnaud Fontaine schrieb:
> > I was migrating a 1.3.4/gdbm running wiki using my own theme to a cvs
> > export version with MySQL as a backend.
>=20
> gdbm locking problems also? those php guys should be beaten!

No. But a gdbm based wiki is VERY slow on RecentChanges, for exemple,
when you are around 1000 pages. Or you need a damned amount of RAM ...
Only have 1.5 GB on my server.


> local import would have been much faster. just give source=3D... to=20
> action=3Dloadfile. anyway.
> upload is not very good.

Yes but how do you specify the admin login and password ??
http://user:pass@site/ ??

> > I also noted that the UserPreferences looks to the list of themes in th=
is
> > directory and not in the local themes directory ...
>=20
> For the themes loader see below:
> So either PHPWIKI_DIR is empty or wrong. NormalizeLocalFileName is in=20
> FileFinder.php, and adds PHPWIKI_DIR if defined.

hmmm .... is PHPWIKI_DIR your wiki local dir or your phpwiki install dir
???

I might have misunderstood this since ... the very begining :)


But well ...

The real problem is : when I use my migrated theme, phpwiki ALWAYS
switches to the default theme.

I tried with some other themes like sidebar, wordpress, crao, etc ...
they are all fine. And when I try wikilens theme ... it switches to the
default theme ...

Did you change some fundamental stuffs in the theme API ??
--
Arnaud Fontaine
ar...@cr...
Jabber: sh...@ra...
ICQ: 3504789

[Phpwiki-talk] Re: [phpwiki - Help] How do display SF icons on every page in wiki

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

SourceForge.net schrieb:
> Read and respond to this message at: 
> https://sourceforge.net/forum/message.php?msg_id=2807763
> By: rmanocha
> 
> Hey guys,
> I was wondering how I could dispay the sourceforge icons on a phpwiki powered
> site. I wanted to insert these icons so that statistics could be accumulated
> for my site.
> I tried inserting the code at the end of index.php but that did not work out.
> Any other way to do this??

in the template:

themes/default/templates/body.tmpl for example.

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

Re: [Phpwiki-talk] phpwiki-1.3.11pre, php-warning in session.

[Johannes R. <ru...@fb...>]

Hey,

i'd updated my phpwiki and had forget to update the database structure.

So i had the same problem and no idea why.
After creating a new Database with the new DB-Modell and inserting the 
old content all works fine.

cheerio

ReymanX schrieb am 15.10.2004 04:07  folgendes:
> I just successfully install phpwiki-1.3.11pre in my debian, with
> apache 1.3.x. And now, i'd like to install in my hosting server, when
> Iit load a virgin wiki, it runs well. But when I go to HomePage or any
> pages, there always php-warning something like this:
> lib/DbSession.php:75: Warning[2]: ini_set(): A session is active. You
> cannot change the session module's ini settings at this time.
> And I always promtp username-password even when I log as admin
> everytime I go to any page.
> FYI, my hosting server not allow apache to write in home-directory,
> does it cause this problem ?
> 
> regards,
> 

[Phpwiki-talk] PhpMemoryExhausted update

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

Hmm, I think I found the culprit for our sf.net memory problems:
http://phpwiki.sourceforge.net/phpwiki/PhpMemoryExhausted

Just tested parallel 1.3.10 and 1.3.11 installations here 
(http://phpwiki.sourceforge.net/phpwiki11/PhpMemoryExhausted) and found 
out that the latest 1.3.11-pre fixes didn't improve the memory situation 
that much. Same messages all over.
Same after switching to a dba/gdbm backend.
But then I lurked around and found something very interesting:
Our .htaccess had some interesting RewriteRules, which might have causes 
phpwiki to loop.
After disabling these rewrite rules it works much faster and almost like 
a charm. Only AllUsers fails because of some other problems.
For me it seems to react much faster now.

.htaccess:
<Files phpwiki>
   SetHandler application/x-httpd-php
</Files>
<Files phpwiki11>
   SetHandler application/x-httpd-php
</Files>


#RewriteEngine on
#RewriteBase /
# Redirect old style (with index.php) URLs to new ("pretty") style URLs.
#RewriteRule ^phpwiki/index.php3?([?/].*)?$ phpwiki$1 [R=301]
# Redirect from /wiki to /phpwiki
#RewriteRule ^wiki([?/].*)?$ phpwiki$1 [R=301]

AddType image/x-icon ico


The previous assumption was that php is not able to garbage collect 
references to objects. refs cannot be refcounted, and if the gc is 
unreliable it will just sum up the memory for every function call with a 
ref object. I removed some of these.

The old assumption was that objects refs need much less memory in a 
function call than the copied object (pointer vs. struct).
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Tips on authentication

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

Jack Twilley schrieb:
> I have a desire for a slightly complicated system of authentication, and 
> I do not know whether phpwiki will handle it.
> 
> A guestbook-type page would be global read and write.  A personal page 
> would be locked down for write to the particular user, but globally 
> readable.  Some privileged pages may be read/write restricted to all 
> authenticated users, or any subset of them.  And so on.
> 
> The phpwiki page on authentication seems to provide a single setting for 
> everything -- what am I missing?

Our auth can do that, but you need perms.

We do have ACL's: See http://phpwiki.org/PagePermissions

Default is the change perm for admin and owner.

So you only have to change the edit perms for the personal pages.
Best if you put all of them as subpages and set the ACL's of the 
basepage for these protected pages.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Email Verification messages over and over

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

Philip J. Hollenback schrieb:
> I'm running phpwiki cvs from 10/7/2004, crao theme, mysql backed.
> 
> After I applied the patch from a couple days ago to enable user prefs, I
> logged in to the wiki as my user and changed my preferences.  This
> included entering my email address.

this is not really needed. just for PageChangeNotification.

> When I checked back the next day, I had received an email from the wiki,
> and I saw on the user prefs page that my user was now authenticated.
> 
> All good.  However, the authorization email seems to be stuck in a loop.
>  Every time I log back on as my user, the wiki generates another email
> saying "welcome to the wiki!" and sends it to me.

That's no loop.
That's an indiction that your prefs are not persistent.
Your prefs cannot be safed.

> This is with my admin user, which has a password set.

Admin user?
I have to investigate this. ADMIN_USER has a different logic. Thanks for 
reporting this.

dbprefs or personalpage prefs?
what is your USER_AUTH_ORDER?

> Any ideas how to turn this off?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Tips on authentication

[Jack T. <jm...@tw...>]

I have a desire for a slightly complicated system of authentication, and 
I do not know whether phpwiki will handle it.

A guestbook-type page would be global read and write.  A personal page 
would be locked down for write to the particular user, but globally 
readable.  Some privileged pages may be read/write restricted to all 
authenticated users, or any subset of them.  And so on.

The phpwiki page on authentication seems to provide a single setting for 
everything -- what am I missing?

Jack.
-- 
Jack Twilley
jmt at twilley org

[Phpwiki-talk] Email Verification messages over and over

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

I'm running phpwiki cvs from 10/7/2004, crao theme, mysql backed.

After I applied the patch from a couple days ago to enable user prefs, I
logged in to the wiki as my user and changed my preferences.  This
included entering my email address.

When I checked back the next day, I had received an email from the wiki,
and I saw on the user prefs page that my user was now authenticated.

All good.  However, the authorization email seems to be stuck in a loop.
 Every time I log back on as my user, the wiki generates another email
saying "welcome to the wiki!" and sends it to me.

This is with my admin user, which has a password set.

Any ideas how to turn this off?

Thanks,
P.
--  
Philip J. Hollenback
ph...@po...
www.hollenback.net

Re: [Phpwiki-talk] wikiword link repetition causing timeouts in 1.3.11pre in PHP 5.0.2

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

John Shen schrieb:
> I looked at the output of PhpWikiDoc page and it seems
> that links are repeating in a (n+2) sequence, i.e., 5,
> 5+2, 5 +2 +2 etc.
> 
> Therefore, PhpWikiDocumentation with its many links
> eventually times out after 30 seconds.
> 
> It looks like an interation issue, but I still have
> not read the code enough to pinpoint where the problem
> is. I am hoping to either get some hints or help
> someone else find the problem.

It's indeeed a very interesting issue with our extremly hairy 
BlockParser code. I already fixed that once. I believe it
was some XmlContent object initialization magic.
The only chance to fix that is to step through it
in a visual php5 debugger.

I'll try to download another zend beta for testing. xdebug gets better 
and better, but still no free visual ide for that new protocol.

I wish Jeff would have some time to spare,
because he wrote it, and my attempts so far to optimize that, failed,
so I had to revert back.

> Thanks,
> 
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
>     * Please sign your name in RecentVisitors.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
>     * Please sign your name in RecentVisitors.
>     * See RecentChanges for the latest page additions
> and changes.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
>     * Please sign your name in RecentVisitors.
>     * See RecentChanges for the latest page additions
> and changes.
>     * Find out which pages are MostPopular.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
>     * Please sign your name in RecentVisitors.
>     * See RecentChanges for the latest page additions
> and changes.
>     * Find out which pages are MostPopular.
>     * Read the ReleaseNotes and RecentReleases.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
>     * Please sign your name in RecentVisitors.
>     * See RecentChanges for the latest page additions
> and changes.
>     * Find out which pages are MostPopular.
>     * Read the ReleaseNotes and RecentReleases.
>     * Administer this wiki via PhpWikiAdministration.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
>     * Please sign your name in RecentVisitors.
>     * See RecentChanges for the latest page additions
> and changes.
>     * Find out which pages are MostPopular.
>     * Read the ReleaseNotes and RecentReleases.
>     * Administer this wiki via PhpWikiAdministration.
>     * See more PhpWikiDocumentation.
> 
>     * What is a WikiWikiWeb? A description of this
> application.
>     * Learn HowToUseWiki and learn about AddingPages.
>     * Use the SandBox page to experiment with Wiki
> pages.
>     * Please sign your name in RecentVisitors.
>     * See RecentChanges for the latest page additions
> and changes.
>     * Find out which pages are MostPopular.
>     * Read the ReleaseNotes and RecentReleases.
>     * Administer this wiki via PhpWikiAdministration.
>     * See more PhpWikiDocumentation.

[Phpwiki-talk] wikiword link repetition causing timeouts in 1.3.11pre in PHP 5.0.2

[John S. <joh...@uc...>]

I looked at the output of PhpWikiDoc page and it seems
that links are repeating in a (n+2) sequence, i.e., 5,
5+2, 5 +2 +2 etc.

Therefore, PhpWikiDocumentation with its many links
eventually times out after 30 seconds.

It looks like an interation issue, but I still have
not read the code enough to pinpoint where the problem
is. I am hoping to either get some hints or help
someone else find the problem.

Thanks,


    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.
    * Please sign your name in RecentVisitors.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.
    * Please sign your name in RecentVisitors.
    * See RecentChanges for the latest page additions
and changes.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.
    * Please sign your name in RecentVisitors.
    * See RecentChanges for the latest page additions
and changes.
    * Find out which pages are MostPopular.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.
    * Please sign your name in RecentVisitors.
    * See RecentChanges for the latest page additions
and changes.
    * Find out which pages are MostPopular.
    * Read the ReleaseNotes and RecentReleases.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.
    * Please sign your name in RecentVisitors.
    * See RecentChanges for the latest page additions
and changes.
    * Find out which pages are MostPopular.
    * Read the ReleaseNotes and RecentReleases.
    * Administer this wiki via PhpWikiAdministration.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.
    * Please sign your name in RecentVisitors.
    * See RecentChanges for the latest page additions
and changes.
    * Find out which pages are MostPopular.
    * Read the ReleaseNotes and RecentReleases.
    * Administer this wiki via PhpWikiAdministration.
    * See more PhpWikiDocumentation.

    * What is a WikiWikiWeb? A description of this
application.
    * Learn HowToUseWiki and learn about AddingPages.
    * Use the SandBox page to experiment with Wiki
pages.
    * Please sign your name in RecentVisitors.
    * See RecentChanges for the latest page additions
and changes.
    * Find out which pages are MostPopular.
    * Read the ReleaseNotes and RecentReleases.
    * Administer this wiki via PhpWikiAdministration.
    * See more PhpWikiDocumentation.



=====
--John Shen

The Lord is my shepard.  I shall not want.

[Phpwiki-talk] Re: do you still need developers?

[John S. <joh...@uc...>]

Hi, Reini and others,

I am not sure if the format is correct, but this is my
first contribution to the project, if someone else has
not beaten me to it yet :-)

This will make WikiWord links appear again after it
disappeared yesterday.

Ciao,


*** Theme.php.~1.109.~	2004-10-14 19:03:06.000000000
-0700
--- Theme.php	2004-10-14 19:03:09.300681096 -0700
***************
*** 511,516 ****
--- 511,521 ----
  
          $link = HTML::a(array('href' => $url));
          
+         if (isa($wikiword, 'WikiPageName'))
+             $default_text = $wikiword->shortName;
+         else
+             $default_text = $wikiword;
+ 
          if (!empty($linktext)) {
              $link->pushContent($linktext);
              $link->setAttr('class', 'named-wiki');





=====
--John Shen

The Lord is my shepard.  I shall not want.

[Phpwiki-talk] phpwiki-1.3.11pre, php-warning in session.

[ReymanX <re...@gm...>]

I just successfully install phpwiki-1.3.11pre in my debian, with
apache 1.3.x. And now, i'd like to install in my hosting server, when
Iit load a virgin wiki, it runs well. But when I go to HomePage or any
pages, there always php-warning something like this:
lib/DbSession.php:75: Warning[2]: ini_set(): A session is active. You
cannot change the session module's ini settings at this time.
And I always promtp username-password even when I log as admin
everytime I go to any page.
FYI, my hosting server not allow apache to write in home-directory,
does it cause this problem ?

regards,

-- 
Arie Reynaldi Zanahar
reymanx at gmail.com
http://www.reynaldi.com

[Phpwiki-talk] Quarantined Mail: attachment from phpwiki-talk@lists.sourceforge.net

[<MAI...@mx...>]

This is an automated message from the BorderWare MXtreme Mail Firewall
at host mxtreme.wbduisburg.de.

A mail from you (php...@li...) to (s.s...@wb...) 
was stopped and Quarantined because it contains one or more 
forbidden attachments.

Summary of email contents:

Queue ID: 4FD360DA1E
message_part2.pif
    forbidden attachment 

[Phpwiki-talk] Re: do you still need developers?

[John S. <joh...@uc...>]

in the newest cvs with php 5.0.2, in addition to the
script timeout, all the wiki links inside the body are
now blank. i looked at the source and the link
repetition i reported on the forum is now gone, and
the links are actually all there, so i think it is
probably a style or html issue.

=====
--John Shen

The Lord is my shepard.  I shall not want.

[Phpwiki-talk] Re: do you still need developers?

[John S. <joh...@uc...>]

I updated from cvs, and the non-object error
disappeared in running test.php.

now i am getting a timeout error 
--- Reini Urban <ru...@x-...> wrote:

> [private msg redirected to the list]
> 
> John Shen schrieb:
> > Thanks, how should I get started?
> > 
> > Since I am mostly an admin, the first thing I
> would
> > like to fix is the nightly snapshoot. It should be
> a
> > simple cron job if I can guess, or any other
> system/db
> > admin work you have.
> 
> that's entirely a (partially broken) sf.net service.
> most other cronjobs run as non-active users, which
> left the project 
> years ago, and didn't hand over their cronjobs or
> file perms.
> we can live with it though.
> 
> > Since this would be my first attempt to contribute
> to
> > a sourceforge project, I may have to ask some
> silly
> > questions.
> 
> then you have to study the sf.net docs in
> administration of projects.
> cvs, shell, web services.
> most of them is out of our reach, so we have to
> eitehr fill out request 
> forms in the tracker or do it by our own.
> 
> > Then I would like to try to contribute to bug
> > fixing/feature development for the next release.
> How
> > does the team operate? 
> 
> communicating in the phpwiki-talk ml.
> 
> > 1. How to take on something (I will start with
> > something simple first)? Is there a todo list that
> no
> > one is working on but needs to be worked on? 
> 
> yes. please see the ml archives, the HomePage and
> ReleaseNotes in the 
> demo site,
> then my internal TODO list:
> 
> fix:
> * javascript search&replace
> * test httpauth, and reported personalpage auth
> problems
> * test against php-5.0.2 (block parser)
> * test against apache2
> do all unit tests:
>    all langs, all db backends, all pages import and
> export
> improvements:
> * PageChangeNotification other actions also (to
> test: rename, remove).
>    better subject on create.
> * collapse page change notification on LoadAny
> * restrict certain action to groups: RawHtml (could
> be a define)
> * db.timeout: force mysql.connect_timeout = 60
> * rewrite OldTextFormattingRules,
> AnciennesR%E8glesDeFormatage
>    for proper importing (done?)
> * test WikiPluginCached support for image maps and
> svg, swf, eps, ... 
> (partially done)
>    defer header logic
> * don't print php notices and warnings as red
> errors. (done)
>    just green or grey
> * pagerank algo: HITS
> http://www2002.org/CDROM/refereed/643/node1.html
> maybe (probably defer):
> * iniconfig helpers (create config.ini, installer)
> * and and fix more wikilens libs and plugins, layout
> improvements
>    there's a wikilens.org page describing the todo
> items.
> * SqlResult paging
> * plugin\WikiAdminSetAclSimple
> * plugin\NewUserWelcomePage.php
> * plugin\SearchHighlight
> * logfile stuff:
> *   plugin\RecentReferrers
> *   WikiAccessRestrictions
> * PageModeration
> * SpamAssassinIntegration
> 
> already done lately:
> * pdf button when an external html2pdf app is
> defined
>    (enabled at PhpWikiDemo)
> * enhanced WikiPluginCached (static, ondemand)
> * added LdapSearchPlugin
> * more PageList options
> 
> 1.3.11 Goals: (expected date: end of June 2004)
> 
>      * fix more sf.net bugs and patches (90%)
>      * fix LDAP with USER_AUTH_POLICY=old (100%)
>      * ADODB lock and transaction fixes (50%)
>      * some more theme beautification, new crao and
> nuke theme,
>        cut or split long sidebar links somehow
> (100%)
>      * add some basic Recommender engine to enable
> rating recommendations,
>        fix metadata getAvg and test it. (100%)
>      * fix metadata RateIt methods and RateIt
> usergroups, (100%)
>      * rewrite WikiGroup to be current_user
> independent to be able
>        to ask for group membership of any user.
> (100%)
>      * more action=upgrade (diffs, multi-page
> interface) (60%)
>      * finish PdfOutput plugin and button (80%)
>      * add editpage javascript toolbar (90%)
>      * try the php-internal soap extension, test
> SOAP, fix 
> GooglePlugin+AmazonPlugin (0%)
>      * iniconfig helpers (JobyWalker) (0%)
>      * improve more plugins caching (90%)
> 
>      * change remove_page in WikiDb API, so that
> RecentChanges displays it.
>        (just purge all revisions?)
>      * rename global $Theme to $WikiTheme (gforge
> nameclash) (100%)
> 
> 1.4.0 Goals: (expected date: June-July 2004)
> 
>      * fix WikiAdminSetAcl (least common ACL
> denominator) (90%)
>      * enable ACL's in the mime dumps (100%)
>      * force strict PagePermissions on all plugins,
> which require now
>        admin and some more administrative actions
> (90%)
>      * complete full paging support (limit=,
> prev/next buttons in
>        PageList) (80%)
>        fix paging in MostPopular
>      * fix possibly remaining WikiGroup problems
> (100%)
>      * fix possibly remaining RateIt problems (0%)
>      * finalize PdfOutput (0%)
>        external works fine
>      * finalize editpage javascript toolbar (90%)
>        fix search/replace bug
>      * finalize SOAP support (0%) (test native soap
> module)
>      * better utf-8 support (50%) (this is hard:
> strstr, substr, ...)
>      * format=rdf and a new owl PageType (similar to
> InterWikiMap)
>        to statically define predicates used by
> PhpWiki:SemanticWeb
>        (semantically enriched links, like interwiki
> links).
> 
> > 2. How do I contribute code. Do I just send you
> > patches to files against the cvs files?
> 
> yes, to the patch tracker or the ml.
> 
> > 3. How do you debug phpwiki code in general? (php
> does
> > not have a debug as far as I know, but php5 might
> have
> > something, print_r/echo is the only method I know
> of).
> 
> php has some very advanced IDE debuggers.
> zend studio, komodo, ...
> php5 only has xdebug so far, with a new protocol
> which only komodo 
> understands.
> zend beta also has some php5 cgi support.
> 
> > --- Reini Urban <ru...@x-...> wrote:
> >>John Shen schrieb:
> >>>I have developed in the lamp environment for the
> >>>past 4 years. I am also a Linux sys admin.
> >>>I would like to contribute to the development of
> >>>phpwiki if you still need someone.
> 
> >sure. go on.
> -- 
> Reini Urban
> 
> 
> 
> 
=== message truncated ===


=====
--John Shen

The Lord is my shepard.  I shall not want.

[Phpwiki-talk] Re: do you still need developers?

[John S. <joh...@uc...>]

Reini, 

thanks.

I would like to take up 5.0.2 testing, or at least
contribute to it, and find fixes whenever I can. This
is because we are going to use the combination so it
serves our interest to get it working.

i will start with php testing (the java testing seems
to be more involved to set up).

in php 5.0.2, it seems that in general i am running
into a lot of errors both in viewing phpwiki pages and
in testing of the following type:

PHP Fatal error:  Call to a member function
deletePage() on a non-object in
/var/www/html/phpwiki/tests/unit/lib/SetupWiki.php on
line 15

Fatal error: Call to a member function deletePage() on
a non-object in
/var/www/html/phpwiki/tests/unit/lib/SetupWiki.php on
line 15


the call is $dbi->deletePage

$dbi = $request->getDbh()

when i looked at $dbi, it is just an integer 1,
clearly not an object.

It looks as though instances that were instantiated in
php4 is now not getting instatiated, or rather
instance variables were not getting properly assigned.
is it because of the way php5 parses code?

i will investigate, but if anyone knows that it is
just something simple, it could save me a lot of
digging.

thanks!

--- Reini Urban <ru...@x-...> wrote:

> [private msg redirected to the list]
> 
> John Shen schrieb:
> > Thanks, how should I get started?
> > 
> > Since I am mostly an admin, the first thing I
> would
> > like to fix is the nightly snapshoot. It should be
> a
> > simple cron job if I can guess, or any other
> system/db
> > admin work you have.
> 
> that's entirely a (partially broken) sf.net service.
> most other cronjobs run as non-active users, which
> left the project 
> years ago, and didn't hand over their cronjobs or
> file perms.
> we can live with it though.
> 
> > Since this would be my first attempt to contribute
> to
> > a sourceforge project, I may have to ask some
> silly
> > questions.
> 
> then you have to study the sf.net docs in
> administration of projects.
> cvs, shell, web services.
> most of them is out of our reach, so we have to
> eitehr fill out request 
> forms in the tracker or do it by our own.
> 
> > Then I would like to try to contribute to bug
> > fixing/feature development for the next release.
> How
> > does the team operate? 
> 
> communicating in the phpwiki-talk ml.
> 
> > 1. How to take on something (I will start with
> > something simple first)? Is there a todo list that
> no
> > one is working on but needs to be worked on? 
> 
> yes. please see the ml archives, the HomePage and
> ReleaseNotes in the 
> demo site,
> then my internal TODO list:
> 
> fix:
> * javascript search&replace
> * test httpauth, and reported personalpage auth
> problems
> * test against php-5.0.2 (block parser)
> * test against apache2
> do all unit tests:
>    all langs, all db backends, all pages import and
> export
> improvements:
> * PageChangeNotification other actions also (to
> test: rename, remove).
>    better subject on create.
> * collapse page change notification on LoadAny
> * restrict certain action to groups: RawHtml (could
> be a define)
> * db.timeout: force mysql.connect_timeout = 60
> * rewrite OldTextFormattingRules,
> AnciennesR%E8glesDeFormatage
>    for proper importing (done?)
> * test WikiPluginCached support for image maps and
> svg, swf, eps, ... 
> (partially done)
>    defer header logic
> * don't print php notices and warnings as red
> errors. (done)
>    just green or grey
> * pagerank algo: HITS
> http://www2002.org/CDROM/refereed/643/node1.html
> maybe (probably defer):
> * iniconfig helpers (create config.ini, installer)
> * and and fix more wikilens libs and plugins, layout
> improvements
>    there's a wikilens.org page describing the todo
> items.
> * SqlResult paging
> * plugin\WikiAdminSetAclSimple
> * plugin\NewUserWelcomePage.php
> * plugin\SearchHighlight
> * logfile stuff:
> *   plugin\RecentReferrers
> *   WikiAccessRestrictions
> * PageModeration
> * SpamAssassinIntegration
> 
> already done lately:
> * pdf button when an external html2pdf app is
> defined
>    (enabled at PhpWikiDemo)
> * enhanced WikiPluginCached (static, ondemand)
> * added LdapSearchPlugin
> * more PageList options
> 
> 1.3.11 Goals: (expected date: end of June 2004)
> 
>      * fix more sf.net bugs and patches (90%)
>      * fix LDAP with USER_AUTH_POLICY=old (100%)
>      * ADODB lock and transaction fixes (50%)
>      * some more theme beautification, new crao and
> nuke theme,
>        cut or split long sidebar links somehow
> (100%)
>      * add some basic Recommender engine to enable
> rating recommendations,
>        fix metadata getAvg and test it. (100%)
>      * fix metadata RateIt methods and RateIt
> usergroups, (100%)
>      * rewrite WikiGroup to be current_user
> independent to be able
>        to ask for group membership of any user.
> (100%)
>      * more action=upgrade (diffs, multi-page
> interface) (60%)
>      * finish PdfOutput plugin and button (80%)
>      * add editpage javascript toolbar (90%)
>      * try the php-internal soap extension, test
> SOAP, fix 
> GooglePlugin+AmazonPlugin (0%)
>      * iniconfig helpers (JobyWalker) (0%)
>      * improve more plugins caching (90%)
> 
>      * change remove_page in WikiDb API, so that
> RecentChanges displays it.
>        (just purge all revisions?)
>      * rename global $Theme to $WikiTheme (gforge
> nameclash) (100%)
> 
> 1.4.0 Goals: (expected date: June-July 2004)
> 
>      * fix WikiAdminSetAcl (least common ACL
> denominator) (90%)
>      * enable ACL's in the mime dumps (100%)
>      * force strict PagePermissions on all plugins,
> which require now
>        admin and some more administrative actions
> (90%)
>      * complete full paging support (limit=,
> prev/next buttons in
>        PageList) (80%)
>        fix paging in MostPopular
>      * fix possibly remaining WikiGroup problems
> (100%)
>      * fix possibly remaining RateIt problems (0%)
>      * finalize PdfOutput (0%)
>        external works fine
>      * finalize editpage javascript toolbar (90%)
>        fix search/replace bug
>      * finalize SOAP support (0%) (test native soap
> module)
>      * better utf-8 support (50%) (this is hard:
> strstr, substr, ...)
>      * format=rdf and a new owl PageType (similar to
> InterWikiMap)
>        to statically define predicates used by
> PhpWiki:SemanticWeb
>        (semantically enriched links, like interwiki
> links).
> 
> > 2. How do I contribute code. Do I just send you
> > patches to files against the cvs files?
> 
> yes, to the patch tracker or the ml.
> 
> > 3. How do you debug phpwiki code in general? (php
> does
> > not have a debug as far as I know, but php5 might
> have
> > something, print_r/echo is the only method I know
> of).
> 
> php has some very advanced IDE debuggers.
> zend studio, komodo, ...
> php5 only has xdebug so far, with a new protocol
> which only komodo 
> understands.
> zend beta also has some php5 cgi support.
> 
> > --- Reini Urban <ru...@x-...> wrote:
> >>John Shen schrieb:
> >>>I have developed in the lamp environment for the
> >>>past 4 years. I am also a Linux sys admin.
> >>>I would like to contribute to the development of
> >>>phpwiki if you still need someone.
> 
> >sure. go on.
> -- 
> Reini Urban
> 
> 
> 
> 
=== message truncated ===


=====
--John Shen

The Lord is my shepard.  I shall not want.

[Phpwiki-talk] Re: do you still need developers?

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

[private msg redirected to the list]

John Shen schrieb:
> Thanks, how should I get started?
> 
> Since I am mostly an admin, the first thing I would
> like to fix is the nightly snapshoot. It should be a
> simple cron job if I can guess, or any other system/db
> admin work you have.

that's entirely a (partially broken) sf.net service.
most other cronjobs run as non-active users, which left the project 
years ago, and didn't hand over their cronjobs or file perms.
we can live with it though.

> Since this would be my first attempt to contribute to
> a sourceforge project, I may have to ask some silly
> questions.

then you have to study the sf.net docs in administration of projects.
cvs, shell, web services.
most of them is out of our reach, so we have to eitehr fill out request 
forms in the tracker or do it by our own.

> Then I would like to try to contribute to bug
> fixing/feature development for the next release. How
> does the team operate? 

communicating in the phpwiki-talk ml.

> 1. How to take on something (I will start with
> something simple first)? Is there a todo list that no
> one is working on but needs to be worked on? 

yes. please see the ml archives, the HomePage and ReleaseNotes in the 
demo site,
then my internal TODO list:

fix:
* javascript search&replace
* test httpauth, and reported personalpage auth problems
* test against php-5.0.2 (block parser)
* test against apache2
do all unit tests:
   all langs, all db backends, all pages import and export
improvements:
* PageChangeNotification other actions also (to test: rename, remove).
   better subject on create.
* collapse page change notification on LoadAny
* restrict certain action to groups: RawHtml (could be a define)
* db.timeout: force mysql.connect_timeout = 60
* rewrite OldTextFormattingRules, AnciennesR%E8glesDeFormatage
   for proper importing (done?)
* test WikiPluginCached support for image maps and svg, swf, eps, ... 
(partially done)
   defer header logic
* don't print php notices and warnings as red errors. (done)
   just green or grey
* pagerank algo: HITS http://www2002.org/CDROM/refereed/643/node1.html
maybe (probably defer):
* iniconfig helpers (create config.ini, installer)
* and and fix more wikilens libs and plugins, layout improvements
   there's a wikilens.org page describing the todo items.
* SqlResult paging
* plugin\WikiAdminSetAclSimple
* plugin\NewUserWelcomePage.php
* plugin\SearchHighlight
* logfile stuff:
*   plugin\RecentReferrers
*   WikiAccessRestrictions
* PageModeration
* SpamAssassinIntegration

already done lately:
* pdf button when an external html2pdf app is defined
   (enabled at PhpWikiDemo)
* enhanced WikiPluginCached (static, ondemand)
* added LdapSearchPlugin
* more PageList options

1.3.11 Goals: (expected date: end of June 2004)

     * fix more sf.net bugs and patches (90%)
     * fix LDAP with USER_AUTH_POLICY=old (100%)
     * ADODB lock and transaction fixes (50%)
     * some more theme beautification, new crao and nuke theme,
       cut or split long sidebar links somehow (100%)
     * add some basic Recommender engine to enable rating recommendations,
       fix metadata getAvg and test it. (100%)
     * fix metadata RateIt methods and RateIt usergroups, (100%)
     * rewrite WikiGroup to be current_user independent to be able
       to ask for group membership of any user. (100%)
     * more action=upgrade (diffs, multi-page interface) (60%)
     * finish PdfOutput plugin and button (80%)
     * add editpage javascript toolbar (90%)
     * try the php-internal soap extension, test SOAP, fix 
GooglePlugin+AmazonPlugin (0%)
     * iniconfig helpers (JobyWalker) (0%)
     * improve more plugins caching (90%)

     * change remove_page in WikiDb API, so that RecentChanges displays it.
       (just purge all revisions?)
     * rename global $Theme to $WikiTheme (gforge nameclash) (100%)

1.4.0 Goals: (expected date: June-July 2004)

     * fix WikiAdminSetAcl (least common ACL denominator) (90%)
     * enable ACL's in the mime dumps (100%)
     * force strict PagePermissions on all plugins, which require now
       admin and some more administrative actions (90%)
     * complete full paging support (limit=, prev/next buttons in
       PageList) (80%)
       fix paging in MostPopular
     * fix possibly remaining WikiGroup problems (100%)
     * fix possibly remaining RateIt problems (0%)
     * finalize PdfOutput (0%)
       external works fine
     * finalize editpage javascript toolbar (90%)
       fix search/replace bug
     * finalize SOAP support (0%) (test native soap module)
     * better utf-8 support (50%) (this is hard: strstr, substr, ...)
     * format=rdf and a new owl PageType (similar to InterWikiMap)
       to statically define predicates used by PhpWiki:SemanticWeb
       (semantically enriched links, like interwiki links).

> 2. How do I contribute code. Do I just send you
> patches to files against the cvs files?

yes, to the patch tracker or the ml.

> 3. How do you debug phpwiki code in general? (php does
> not have a debug as far as I know, but php5 might have
> something, print_r/echo is the only method I know of).

php has some very advanced IDE debuggers.
zend studio, komodo, ...
php5 only has xdebug so far, with a new protocol which only komodo 
understands.
zend beta also has some php5 cgi support.

> --- Reini Urban <ru...@x-...> wrote:
>>John Shen schrieb:
>>>I have developed in the lamp environment for the
>>>past 4 years. I am also a Linux sys admin.
>>>I would like to contribute to the development of
>>>phpwiki if you still need someone.

>sure. go on.
-- 
Reini Urban

Re: [Phpwiki-talk] 1.3.11 release date?

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

Aaron R. Short schrieb:
> I was informed back in September that the 1.3.11
> release will be coming out within a week. Since our
> wiki is experienceing problems I've been a bit anxious
> to get the fixes. Whats the current timeline on the
> new release?

Yes, I was in testing the remaining auth/session problems, and thought 
that all the serious memory problems had been fixed.

But now with schorni's latest report (20041011 "Memory Problem still 
alive !!!") it seems to be, that is is not yet fixed, so I started to 
rewrite PageList sorting and WikiDB_Page, to get rid of unneeded upward 
references which might cause wikis with more than 500 pages to fill the 
allowed memory of 8MB.

It already works fine locally (not in CVS), but I have to start a new 
detailled test round, which can last up to two weeks.
Then about another more two weeks for the other remaining minor issues.
(jscript, ...)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/