phpwiki-talk

[Phpwiki-talk] Why Can't I Edit Anything on the SourceForge PhpWiki?

[Bill T. <bt...@gi...>]

I had some problems with installing PhpWiki, so I went to the wiki at the 
PhpWiki homepage to find out what to do. I went to the FAQ, found that 
others also had the problem, but the answer given didn't work. I thought 
it would be a good idea to mention that right there in the wiki, so I 
tried to edit the page.

It wouldn't let me, saying that my privilege level wasn't high enough. So 
then I tried the SandBox. Couldn't edit anything there either. What's the 
deal?

I then tried "signing in" using the edit control on the lower right of the 
first page. Still couldn't edit anything, even the SandBox. Seems to me 
like something's wrong with the wiki at 
http://phpwiki.sourceforge.net/phpwiki. What do I need to do to get high 
enough privilege to contribute to this wiki?

- Bill Thoen

Re: [Phpwiki-talk] HELP: Can't create/write to file

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

I just wrote a detailed email message .. which got lost because of bad 
connectivity.

This is MySQL stuff, not Phpwiki, and it's too hard to teach MySQL admin 
over email.

I will take one more shot, but I can't spend too much time on this.

First, I don't know why you are getting "Link to server lost, unable to 
reconnect." I don't understand.

Understand that MySQL perms are per (user, host) pair, not per user. 
Also, localhost is a special host, probably not included in '%' 
(wildcard). Read maybe http://dev.mysql.com/doc/mysql/en/Privileges.html.

Also, localhost connections are made via a named pipe socket. Read  
http://dev.mysql.com/doc/mysql/en/Problems_with_mysql.sock.html and 
check mysql --help to see what the socket is.

Maybe try:

- Try granting perms to (user, localhost) (I only see perms on (user, %) 
below).
- Try connecting as (user, <machine>) instead of localhost.
- Try granting ALL perms to one of those instead of just documented perms.
- Try running the exact same SQL from the command-line tool, making sure 
to log in with exactly the same user, host, and socket (if localhost).

Dan

Arthaey Angosii wrote:

>Continuing to work at this problem, I set MySQL's my.cnf to include:
>
>====================
>[mysqld]
>tmpdir=/var/lib/mysql/tmp
>====================
>
>After restarting mysqld, I got a different error message, one with a
>surprising about of useless links from Google:
>
>====================
>lib/WikiDB/backend/PearDB.php:35: Fatal[256]: Can't connect to
>database: wikidb_backend_mysql: fatal database error
>
>    * DB Error: connect failed
>    * ( [nativecode=Link to server lost, unable to reconnect] **
>mysql://wiki:XXXXXXXX@localhost(/var/lib/mysql/mysql.sock)/phpwiki)
>    *
>====================
>
>The MySQL user wiki's information is thus, according to phpMyAdmin:
>
>====================
>User   	  Host   	  Type   	  Privileges   	  Grant 
>wiki  	 %  	 database-specific  	  SELECT, INSERT, UPDATE, DELETE,
>LOCK TABLES    	 No
>====================
>
>Which is what doc/INSTALL.mysql says is all that's required for the wiki user.
>
>Dan Frankowski wrote:
>  
>
>>Thus, probably that file doesn't have permissions to be read by the user
>>who's making the Phpwiki request (probably the user running your Apache
>>process).
>>    
>>
>
>Next, I tried investing permissions further. I set apache as the user
>and group of /var/lib (which contains the mysql directory); the
>permissions had previously been set to root. New error message:
>
>====================
>lib/WikiDB/backend/PearDB.php:35: Fatal[256]: Can't connect to
>database: wikidb_backend_mysql: fatal database error
>
>    * DB Error: connect failed
>    * ( [nativecode=Access denied for user: 'wiki@localhost' (Using
>password: YES)] **
>mysql://wiki:XXXXXXXX@localhost(/var/lib/mysql/mysql.sock)/phpwiki)
>====================
>
>This was surprising, since wiki certainly *used* to have permissions.
>But lo and behold, when I tried to access the MySQL database from the
>command line:
>
>====================
>[root@localhost var] $ mysql -u wiki -p phpwiki
>Enter password: **********
>ERROR 1045: Access denied for user: 'wiki@localhost' (Using password: YES)
>====================
>
>The MySQL command "show grants for 'wiki'@'localhost'" showed that
>there were NO privileges for wiki -- but they were set for wiki@%. I
>made a duplicate user, wiki@localhost, that fixed the problem of
>logging in as wiki from the command line.
>
>However, that put me back to the "Link to server lost, unable to
>reconnect" error message. I'm out of ideas; what should I try next?
>
>
>--
>AA
>
>PS -- Thanks for your quick reply. :)
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>  
>

Re: [Phpwiki-talk] HELP: Can't create/write to file

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

These are really not Phpwiki questions, they are MySQL questions. As 
such, I'd advise learning a little more about MySQL in general. Read the 
docs at mysql.com in some detail about configuration. I fear replying to 
any more of this, because I'll just attract further MySQL questions. 
It's too hard to teach over email.

However, I will give one more shot, though it's a guess.

First, you have to realize that MySQL does not grant permissions to 
users. Rather, it grants permission to (user, host) pairs. Furthermore, 
localhost is a special kind of host, different from others. The '%' is a 
wildcard for any host, but I believe it does not include localhost. 
Thus, if you've granted permissions to user@%, that is different from 
permissions for user@localhost. From the below, it looks like you don't 
have any perms for user@localhost, yet your phpwiki config looks like it 
is trying to use that. So you should grant them to user@localhost, or 
change your Phpwiki dsn to use user@<machine>. Sounds like maybe you did 
some of this (you made a "duplicate" user, who's not really duplicate 
since it's a different host, but I'm not sure what its perms are).

Furthermore, if it still doesn't work, I'd try granting all perms 
instead of just what it says in the docs.

Finally, make sure when you test perms at the command line, that you are 
using exactly the same connection as for Phpwiki (e.g., your socket must 
also be the same if you use localhost, not obvious from below; read for 
example http://dev.mysql.com/doc/mysql/en/Problems_with_mysql.sock.html 
and use mysql --help to see which socket it is connecting to).

Please, no more. :-) It's too hard to teach someone how to use MySQL 
over email.

Dan

Arthaey Angosii wrote:

>Continuing to work at this problem, I set MySQL's my.cnf to include:
>
>====================
>[mysqld]
>tmpdir=/var/lib/mysql/tmp
>====================
>
>After restarting mysqld, I got a different error message, one with a
>surprising about of useless links from Google:
>
>====================
>lib/WikiDB/backend/PearDB.php:35: Fatal[256]: Can't connect to
>database: wikidb_backend_mysql: fatal database error
>
>    * DB Error: connect failed
>    * ( [nativecode=Link to server lost, unable to reconnect] **
>mysql://wiki:XXXXXXXX@localhost(/var/lib/mysql/mysql.sock)/phpwiki)
>    *
>====================
>
>The MySQL user wiki's information is thus, according to phpMyAdmin:
>
>====================
>User   	  Host   	  Type   	  Privileges   	  Grant 
>wiki  	 %  	 database-specific  	  SELECT, INSERT, UPDATE, DELETE,
>LOCK TABLES    	 No
>====================
>
>Which is what doc/INSTALL.mysql says is all that's required for the wiki user.
>
>Dan Frankowski wrote:
>  
>
>>Thus, probably that file doesn't have permissions to be read by the user
>>who's making the Phpwiki request (probably the user running your Apache
>>process).
>>    
>>
>
>Next, I tried investing permissions further. I set apache as the user
>and group of /var/lib (which contains the mysql directory); the
>permissions had previously been set to root. New error message:
>
>====================
>lib/WikiDB/backend/PearDB.php:35: Fatal[256]: Can't connect to
>database: wikidb_backend_mysql: fatal database error
>
>    * DB Error: connect failed
>    * ( [nativecode=Access denied for user: 'wiki@localhost' (Using
>password: YES)] **
>mysql://wiki:XXXXXXXX@localhost(/var/lib/mysql/mysql.sock)/phpwiki)
>====================
>
>This was surprising, since wiki certainly *used* to have permissions.
>But lo and behold, when I tried to access the MySQL database from the
>command line:
>
>====================
>[root@localhost var] $ mysql -u wiki -p phpwiki
>Enter password: **********
>ERROR 1045: Access denied for user: 'wiki@localhost' (Using password: YES)
>====================
>
>The MySQL command "show grants for 'wiki'@'localhost'" showed that
>there were NO privileges for wiki -- but they were set for wiki@%. I
>made a duplicate user, wiki@localhost, that fixed the problem of
>logging in as wiki from the command line.
>
>However, that put me back to the "Link to server lost, unable to
>reconnect" error message. I'm out of ideas; what should I try next?
>
>
>--
>AA
>
>PS -- Thanks for your quick reply. :)
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>  
>

Re: [Phpwiki-talk] HELP: Can't create/write to file

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

Continuing to work at this problem, I set MySQL's my.cnf to include:

====================
[mysqld]
tmpdir=/var/lib/mysql/tmp
====================

After restarting mysqld, I got a different error message, one with a
surprising about of useless links from Google:

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

    * DB Error: connect failed
    * ( [nativecode=Link to server lost, unable to reconnect] **
mysql://wiki:XXXXXXXX@localhost(/var/lib/mysql/mysql.sock)/phpwiki)
    *
====================

The MySQL user wiki's information is thus, according to phpMyAdmin:

====================
User   	  Host   	  Type   	  Privileges   	  Grant 
wiki  	 %  	 database-specific  	  SELECT, INSERT, UPDATE, DELETE,
LOCK TABLES    	 No
====================

Which is what doc/INSTALL.mysql says is all that's required for the wiki user.

Dan Frankowski wrote:
> Thus, probably that file doesn't have permissions to be read by the user
> who's making the Phpwiki request (probably the user running your Apache
> process).

Next, I tried investing permissions further. I set apache as the user
and group of /var/lib (which contains the mysql directory); the
permissions had previously been set to root. New error message:

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

    * DB Error: connect failed
    * ( [nativecode=Access denied for user: 'wiki@localhost' (Using
password: YES)] **
mysql://wiki:XXXXXXXX@localhost(/var/lib/mysql/mysql.sock)/phpwiki)
====================

This was surprising, since wiki certainly *used* to have permissions.
But lo and behold, when I tried to access the MySQL database from the
command line:

====================
[root@localhost var] $ mysql -u wiki -p phpwiki
Enter password: **********
ERROR 1045: Access denied for user: 'wiki@localhost' (Using password: YES)
====================

The MySQL command "show grants for 'wiki'@'localhost'" showed that
there were NO privileges for wiki -- but they were set for wiki@%. I
made a duplicate user, wiki@localhost, that fixed the problem of
logging in as wiki from the command line.

However, that put me back to the "Link to server lost, unable to
reconnect" error message. I'm out of ideas; what should I try next?


--
AA

PS -- Thanks for your quick reply. :)

Re: [Phpwiki-talk] HELP: Can't create/write to file

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

Arthaey Angosii wrote:

>(Note: I also posted this to the Sourceforge support forum, but you've
>all said the mailing list gets read more often.)
>
>Everything was working fine with my PhpWiki installation. But today I
>installed phpMyAdmin so I could look at the MySQL tables more easily,
>and after I got that working, the wiki no longer loads. Instead, I get
>this error:
>
><begin error>
>
>Fatal PhpWiki Error
>
>lib/WikiDB/backend/PearDB.php:779: Fatal[256]: wikidb_backend_mysql:
>fatal database error
>
>    * DB Error: unknown error
>    * (SELECT linkee.id as id, linkee.pagename as pagename,
>linkee.hits as hits, linkee.pagedata as pagedata FROM link, page AS
>linker, page AS linkee WHERE linkfrom=linker.id AND linkto=linkee.id
>AND linker.pagename='HomePage' ORDER BY linkee.pagename [nativecode=1
>** Can't create/write to file '/root/tmp/#sql_f5b_0.MYI' (Errcode:
>13)])
>    *
>  
>

I do not know what this error means exactly. However, I'll say this:

1. I think MySQL is sad, not Phpwiki.
2. I Googled for mysql "Can't create/write to file" and found this page. 
Maybe it helps:

http://dev.mysql.com/doc/mysql/en/Cannot_create.html

It says to use "perror" to find out about the error code. I did it with 
yours:

% perror 13
Error code  13:  Permission denied

Thus, probably that file doesn't have permissions to be read by the user 
who's making the Phpwiki request (probably the user running your Apache 
process).

Look into file permissions.

Dan

>
>Warning: Unknown(): A session is active. You cannot change the session
>module's ini settings at this time. in Unknown on line 0
>
></end error>
>
>I'm not very familiar with sql, so any hints on where to start looking
>for the cause of this would be greatly appreciated!
>
>
>  
>

[Phpwiki-talk] HELP: Can't create/write to file

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

(Note: I also posted this to the Sourceforge support forum, but you've
all said the mailing list gets read more often.)

Everything was working fine with my PhpWiki installation. But today I
installed phpMyAdmin so I could look at the MySQL tables more easily,
and after I got that working, the wiki no longer loads. Instead, I get
this error:

<begin error>

Fatal PhpWiki Error

lib/WikiDB/backend/PearDB.php:779: Fatal[256]: wikidb_backend_mysql:
fatal database error

    * DB Error: unknown error
    * (SELECT linkee.id as id, linkee.pagename as pagename,
linkee.hits as hits, linkee.pagedata as pagedata FROM link, page AS
linker, page AS linkee WHERE linkfrom=linker.id AND linkto=linkee.id
AND linker.pagename='HomePage' ORDER BY linkee.pagename [nativecode=1
** Can't create/write to file '/root/tmp/#sql_f5b_0.MYI' (Errcode:
13)])
    *


Warning: Unknown(): A session is active. You cannot change the session
module's ini settings at this time. in Unknown on line 0

</end error>

I'm not very familiar with sql, so any hints on where to start looking
for the cause of this would be greatly appreciated!


-- 
AA

Re: [Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki/schemas Readme.txt,NONE,1.1 minisql-destroy.sql,NONE,1.1 minisql-initialize.sql,NONE,1.1 mysql-destroy.sql,NONE,1.1 mysql-initialize.sql,NONE,1.1 psql-destroy.sql,NONE,1.1 psql-initialize.sql,NONE,1.1 sqlite-destroy.sql,NONE,1.1 sqlite-initialize.sql,NONE,1.1 minisql.sql,1.1,NONE mysql.sql,1.13,NONE psql.sql,1.7,NONE sqlite.sql,1.5,NONE

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

ru...@x-... wrote:

>Dan,
>do you have time to fix the docs in the doc directory also?
>  
>

Sure. I didn't realize it existed. I just checked in those changes 
(including oci8, Philippe).

>Thanks for the Readme.txt
>  
>

You are welcome. My user contributed it (!), and I made minor edits.

Dan

>  
>
>>Added Files:
>>	Readme.txt minisql-destroy.sql minisql-initialize.sql
>>	mysql-destroy.sql mysql-initialize.sql psql-destroy.sql
>>	psql-initialize.sql sqlite-destroy.sql sqlite-initialize.sql
>>Removed Files:
>>	minisql.sql mysql.sql psql.sql sqlite.sql
>>Log Message:
>>Separate into 'initialize' and 'destroy' SQL
>>    
>>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>  
>

Re: [Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki/schemas Readme.txt,NONE,1.1 minisql-destroy.sql,NONE,1.1 minisql-initialize.sql,NONE,1.1 mysql-destroy.sql,NONE,1.1 mysql-initialize.sql,NONE,1.1 psql-destroy.sql,NONE,1.1 psql-initialize.sql,NONE,1.1 sqlite-destroy.sql,NONE,1.1 sqlite-initialize.sql,NONE,1.1 minisql.sql,1.1,NONE mysql.sql,1.13,NONE psql.sql,1.7,NONE sqlite.sql,1.5,NONE

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

Philippe,

I did the OCI ones as well. It was just a different CVS check-in 
message. Take a look in latest CVS, and correct as needed.

Dan

Philippe Vanhaesendonck wrote:

> FYI,
> I'll submit the OCI ones in a couple of days to be consistent...
>
> ru...@x-... wrote:
>
>> Dan,
>> do you have time to fix the docs in the doc directory also?
>> Thanks for the Readme.txt
>>
>>  
>>
>>> Added Files:
>>>     Readme.txt minisql-destroy.sql minisql-initialize.sql
>>>     mysql-destroy.sql mysql-initialize.sql psql-destroy.sql
>>>     psql-initialize.sql sqlite-destroy.sql sqlite-initialize.sql
>>> Removed Files:
>>>     minisql.sql mysql.sql psql.sql sqlite.sql
>>> Log Message:
>>> Separate into 'initialize' and 'destroy' SQL
>>>   
>>
>>
>>  
>>
>

Re: [Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki/schemas Readme.txt,NONE,1.1 minisql-destroy.sql,NONE,1.1 minisql-initialize.sql,NONE,1.1 mysql-destroy.sql,NONE,1.1 mysql-initialize.sql,NONE,1.1 psql-destroy.sql,NONE,1.1 psql-initialize.sql,NONE,1.1 sqlite-destroy.sql,NONE,1.1 sqlite-initialize.sql,NONE,1.1 minisql.sql,1.1,NONE mysql.sql,1.13,NONE psql.sql,1.7,NONE sqlite.sql,1.5,NONE

[Philippe V. <Phi...@to...>]

FYI,
I'll submit the OCI ones in a couple of days to be consistent...

ru...@x-... wrote:

>Dan,
>do you have time to fix the docs in the doc directory also?
>Thanks for the Readme.txt
>
>  
>
>>Added Files:
>>	Readme.txt minisql-destroy.sql minisql-initialize.sql
>>	mysql-destroy.sql mysql-initialize.sql psql-destroy.sql
>>	psql-initialize.sql sqlite-destroy.sql sqlite-initialize.sql
>>Removed Files:
>>	minisql.sql mysql.sql psql.sql sqlite.sql
>>Log Message:
>>Separate into 'initialize' and 'destroy' SQL
>>    
>>
>
>  
>

-- 
Philippe

Key fingerprint = 2B97 90DB 124B C784 FFE8  6EED 6345 A87E 4BBA F57C

[Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki/schemas Readme.txt,NONE,1.1 minisql-destroy.sql,NONE,1.1 minisql-initialize.sql,NONE,1.1 mysql-destroy.sql,NONE,1.1 mysql-initialize.sql,NONE,1.1 psql-destroy.sql,NONE,1.1 psql-initialize.sql,NONE,1.1 sqlite-destroy.sql,NONE,1.1 sqlite-initialize.sql,NONE,1.1 minisql.sql,1.1,NONE mysql.sql,1.13,NONE psql.sql,1.7,NONE sqlite.sql,1.5,NONE

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

Dan,
do you have time to fix the docs in the doc directory also?
Thanks for the Readme.txt

> Added Files:
> 	Readme.txt minisql-destroy.sql minisql-initialize.sql
> 	mysql-destroy.sql mysql-initialize.sql psql-destroy.sql
> 	psql-initialize.sql sqlite-destroy.sql sqlite-initialize.sql
> Removed Files:
> 	minisql.sql mysql.sql psql.sql sqlite.sql
> Log Message:
> Separate into 'initialize' and 'destroy' SQL

Re: [Phpwiki-talk] Some questions about CVS

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

[the net broke down here in poland, while sending the prev. message, so
maybe its twice]

> First, is "configurator.php" deprecated? It seems there is both the
> option to  have the configuration options in index.php and in
> config/config.ini ...  which should I use?

The options in index.php were moved to config/config.ini. There's no
script to move these automatically. so you have to do this manually.

> Second, how doe I get ACL going? The button to set-up access
> restrictions  takes me to a page saying it isn't yet implemented?

Only in earlier versions it was not or partially implemented. With latest
CVS it works okay.

Re: [Phpwiki-talk] Some questions about CVS

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

Tom Chance wrote:

>Hi,
>
>First, is "configurator.php" deprecated?
>

I don't know. Perhaps yes.

> It seems there is both the option to 
>have the configuration options in index.php and in config/config.ini ... 
>which should I use?
>  
>

config.ini is the way going forward.

>Second, how doe I get ACL going? The button to set-up access restrictions 
>takes me to a page saying it isn't yet implemented?
>  
>

Don't know.


>Regards,
>Tom
>  
>

Dan

[Phpwiki-talk] Some questions about CVS

[Tom C. <li...@to...>]

Hi,

First, is "configurator.php" deprecated? It seems there is both the option to 
have the configuration options in index.php and in config/config.ini ... 
which should I use?

Second, how doe I get ACL going? The button to set-up access restrictions 
takes me to a page saying it isn't yet implemented?

Regards,
Tom

Re: [Phpwiki-talk] two Problems: IniConfig.php and XmlElement.php

[Philippe V. <Phi...@to...>]

Johannes Rumpf wrote:

> Ok, i'be made it.
> copied config to a new extracted phpwiki-config Folder and
> had mad a chmod -R 777 on phpwiki-1.3.10 Folder an' all runin' fine. 

Mmmmm....

Can't remember having file perms issues with phpWiki, but it probably 
depend on who you are when you unpack the thing...

Anyway, afaik it does not need any write access, so 'r' on the files and 
'rx' on the directories should be more than enough, you don't need to 
have it wide open ;-)

> But from my point of view thats a real security lag. Is there a chance 
> to get these proper. Some kind of secur.sh? 

Might be usefull!

-- 
Philippe

Key fingerprint = 2B97 90DB 124B C784 FFE8  6EED 6345 A87E 4BBA F57C

Re: [Phpwiki-talk] two Problems: IniConfig.php and XmlElement.php

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

Ok, i'be made it.
copied config to a new extracted phpwiki-config Folder and
had mad a chmod -R 777 on phpwiki-1.3.10 Folder an' all runin' fine.

But from my point of view thats a real security lag. Is there a chance 
to get these proper. Some kind of secur.sh?

cheers Joe

Re: [Phpwiki-talk] two Problems: IniConfig.php and XmlElement.php

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

Hi Philippe,

>> I' deleted the config-*.ini an' that was it.
> <snip>
> 
>> At second, i've got a ton of Warnings without findin' the background:
>> lib/IniConfig.php:101: Warning[2]: array_key_exists(): The second 
>> argument should be either an array or an object
> 
> 
> You are getting this error because you deleted config-default.ini...
> config-default provides defaults setup (!) which can be overridden by 
> your config.ini.

I'd placed it from the tar file back, but the warnings are still there.
other sugestions?

Joe

[Phpwiki-talk] two Problems: IniConfig.php and XmlElement.php

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

Hi,
finaly i'd made the problem with the blank index.

(Was some kind of missconfiguration. I' deleted the config-*.ini an' 
that was it.
But the blank page is reproducable. I suppose it's about servers, which 
offers a selection for an file if its not unique...)

But now i'm hanging on this stuff: First i had to configure the ldap, 
imap and pop3 authentications, that i don't need.

At second, i've got a ton of Warnings without findin' the background:
lib/IniConfig.php:101: Warning[2]: array_key_exists(): The second 
argument should be either an array or an object
~ 6 times

lib/IniConfig.php:120: Warning[2]: array_key_exists(): The second 
argument should be either an array or an object
~ 12 times

at the bottom 4 Times:
lib/Request.php:260: Warning[2]: Cannot modify header information - 
headers already sent by (output started at 
/home/hattde/www/www.stamm-hattstein.de/phpwiki-1.3.10_old/lib/XmlElement.php:326)

and at least these one:
lib/display.php:131: Warning[2]: Cannot modify header information - 
headers already sent by (output started at 
/home/hattde/www/www.stamm-hattstein.de/phpwiki-1.3.10_old/lib/XmlElement.php:326)



So, i'm stuck with those. A little advice would be charming.

cheers Joe

RE: [Phpwiki-talk] Locking text within page

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

Another method would be to lock the page with the protected text and include
a sub page that everyone can change.  That way, no one could remove the
plugin that pulled in the sub pages.

John Cole

-----Original Message-----
From: php...@li...
[mailto:php...@li...]On Behalf Of Arthaey
Angosii
Sent: Thursday, July 22, 2004 11:12 AM
To: Tom Chance; PhpWiki-Talk
Subject: Re: [Phpwiki-talk] Locking text within page


Tom Chance wrote:
> Would it be possible to lock a specific bit of text *within* an unlocked
page?
> I can't see how, but I thought I'd check, since a client I'm working for
> wants it.

Perhaps you could lock a subpage, then expand the text with the
UnfoldSubpages plugin? I haven't actually tested this arrangement
myself, but it's what came to mind.

Hope that helps.


--
AA


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

-------------------------------------
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] Locking text within page

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

Tom Chance wrote:
> Would it be possible to lock a specific bit of text *within* an unlocked page?
> I can't see how, but I thought I'd check, since a client I'm working for
> wants it.

Perhaps you could lock a subpage, then expand the text with the
UnfoldSubpages plugin? I haven't actually tested this arrangement
myself, but it's what came to mind.

Hope that helps.


--
AA

Re: [Phpwiki-talk] Patch submitted

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

Not bad. Thanks a lot.
Now theres only the emacs mode missing.

Note that theres an online version of an office2wiki macro somewhere also,
which helps in cleaning up word documents also.

> I submitted the following patch today.
>
> Word to phpWiki converter
> Macro that converts MSWord documents into phpWiki
> syntax. Modified version of WordToWiki_swythan (for
> Tikiwiki). See:
> http://tikiwiki.org/tiki-index.php?page=WordToWiki_swythan
>
> It handles conversions for the following:
>
> * Headings(1-3)
> * Bold
> * Italics
> * Bullet lists
> * Numbered lists (No fancy styles or continuations)
>
> In Word, go to the Visual Basic Editor (Alt+F11) and do
> a File->Import of the attached file "Word2phpWiki.bas".
> Then just load your document and run the "Word2phpWiki"
> macro. The text of the document is converted (in-place)
> and copied to the clipboard.

[Phpwiki-talk] Locking text within page

[Tom C. <li...@to...>]

Hello,

Would it be possible to lock a specific bit of text *within* an unlocked page? 
I can't see how, but I thought I'd check, since a client I'm working for 
wants it.

Regards,
Tom

Re: [Phpwiki-talk] Patch submitted

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

Sara von Mosch wrote:

>I submitted the following patch today.
>
>
>Word to phpWiki converter
>  
>

By the way, the 'patch' (contribution, really) is Word2phpWiki.bas, a 
file attached to 
http://sourceforge.net/tracker/index.php?func=detail&aid=995435&group_id=6121&atid=306121.

Dan

[Phpwiki-talk] Patch submitted

[Sara v. M. <mo...@cs...>]

I submitted the following patch today.


Word to phpWiki converter
Macro that converts MSWord documents into phpWiki
syntax. Modified version of WordToWiki_swythan (for
Tikiwiki). See:
http://tikiwiki.org/tiki-index.php?page=WordToWiki_swythan

It handles conversions for the following:

* Headings(1-3)
* Bold
* Italics
* Bullet lists
* Numbered lists (No fancy styles or continuations)

In Word, go to the Visual Basic Editor (Alt+F11) and do
a File->Import of the attached file "Word2phpWiki.bas".
Then just load your document and run the "Word2phpWiki"
macro. The text of the document is converted (in-place)
and copied to the clipboard.


Thanks,
~Sara


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

Sara von Mosch
GroupLens Research
University of Minnesota

mo...@cs...

Re: [Phpwiki-talk] Where to Document New Plugins?

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

I wrote:
> I'll add the description to PhpWiki once we agree
> on a name for the plugin.

I've added my plugin's info to PhpWiki under the name
InterlinearTranslationPlugin. I would appreciate comments!

Also, it would be great if more experienced plugin-writers would give
me some suggestions on ways to improve the code. (I'm learning PHP via
my knowledge of Perl and reading the existing PhpWiki plugins. :) )


-- 
AA

Re: [Phpwiki-talk] 10 days absence

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

Dan Frankowski schrieb:
> John Cole wrote:
>> Reini,
>> Is there a doc somewhere that describes how to run the unit tests?  
>> I'd be interested in trying to run them on my test machines.
> 
> John,
> tests/unit/readme.html.

from the cmd line or from the browser.

> However, I must say I have not been able to run the tests completely 
> successfully since Reini got his hands on them. :-) Seriously, I think 
> he added some tests which fail for me. HOWEVER, it is possible that they 
> are failing because of bugs he wishes to fix, so they may be working as 
> designed.

Absolutely.
The new tests SetupWiki and DumpHtml are the most important.
The tests are okay, phpwiki has a problem.

> 
> Dan
> 
>> -----Original Message-----
>> From: php...@li...
>> [mailto:php...@li...]On Behalf Of Reini
>> Urban
>> Sent: Tuesday, July 20, 2004 3:10 AM
>> To: php...@li...
>> Subject: [Phpwiki-talk] 10 days absence
>>
>>
>> Hi
>> From 22.July to 1.August I'll be in Poland (Czieszyn), and will not be 
>> able to react on any support request.
>>
>> Known problems:
>> * unit tests: The current CVS version still crashes on certain special 
>> operations, loading some old markup pages with dba and mysql.
>>
>> * mysql still uses far too much memory on 8M memory-limit systems.
>> A pear system destructor hash was fixed recently (culprit #1), but 
>> there must be more references to huge objects on page iterations 
>> around, which prevent them from being garbage collected.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/