phpwiki-talk

[Phpwiki-talk] phpwiki 1.3.12p2_2 and https

[asko <ask...@ul...>]

Hi,

is anybody running phpwiki over https? I'm having slight problems..

Firstly, the wiki is for private use and is protected by .htaccess ..


phpwiki-1.3.12p2_2,
apache-2.2.2 and php4-4.4.2_2

virtualhost looks something like this:

<VirtualHost *:443>
   ServerName    phpwiki
   ServerAdmin   webmaster@server
   DocumentRoot  /usr/local/www/phpwiki
   ErrorLog      /var/log/apache/phpwiki-https-error.log
   CustomLog     /var/log/apache/phpwiki-https-access.log common
</VirtualHost>

Usually web applications are able to detect the correct URL for internal 
links, but now after authentication all the wiki urls point to 
http://phpwiki. Basically I get http wikilinks, but I need https ;-)

I was not able to force https in URL parameters in config file,
setting 'SERVER_NAME = https://phpwiki' produces bad links like 
'http://https://phpwiki/SomePage' ..

Btw, https worked in phpwiki 1.2 with similar configuration if it 
counts, it broke after upgrade.

Please help, what am I missing.. It probably has to do something with 
URL detection?

thank you
asko

[Phpwiki-talk] =?iso-8859-15?q?phpWiki-configuration=3A_=22_missi?= =?iso-8859-15?q?ng_config_setting_for_ADMIN=5FUSER_=28=2E=2E=2Erepeated_2?= =?iso-8859-15?q?_times=29=22?=

[<Fl...@we...>]

Hello all, 


- realtively new to this list - this is my second posting. The PHPWIKI is a supergreat thing. 

I am right in the mids of the installaton process - but i am willing to go thorough; what bout the editing of the files; 

i have tried the following

i edited the following in the config-dist.ini 


- DATABASE_TYPE = SQL
- DATABASE_DSN = "mysql://root:myOwnPASSWD@unix(/var/run/mysql.sock)/php_wiki"

note; with that statement an older wiki runs like a charme - so i wonder what is wrong here?

Afterwards I copied the two files into the foleder config/ 

the I tried to call the phpwiki- 


Fatal Error:
lib/FileFinder.php:193: Error: /tmp: file not found 
lib/IniConfig.php:220: Notice: missing config setting for ADMIN_USER (...repeated 2 times)
lib/FileFinder.php:193: Error: /tmp: file not found 


note; with that  statement an older wiki runs like a charme - so i wonder what is wrong here?


with or without renaming the file to config.ini - nothing was gained - the behaviour stays 
the same. 

Note; all the statements are witout any special quoting - totally - i post you the 
whole text of config-dist.ini  here into the mail 

do you have an idea. I am totally glueless...  

the installation-doc notes; 

 ..... 4. Edit the DATABASE settings in config/config.ini to reflect your settings.
 
 a) DATABASE_TYPE should be set to 'SQL' or 'ADODB'.
 b) DATABASE_DSN should be set to something like
'mysql://guest@unix(/var/lib/mysql/mysql.sock)/phpwiki".
 (where 'phpwiki' is the mysql database name.)
 c) Note that if you set DATABASE_PREFIX to a 
 non-empty string, you will have to edit
 schemas/mysql-initialize.sql before you perform step
 three (above). (Sorry.) (You might also edit
 schemas/mysql-destroy.sql at the same time, so you
 don't forget.)
 
yyyyyyyyyyyyyyyyyyyyyyyyyyyy


btw:  
 the config/config-default.ini has a bunch of options but i am pretty sure that i have an ADODB layer....
I don't think you need to use the ADODB stuff for MySQL (though you can use it if you wish). I'd suggest not using it.


i look forward to hear from you 

regards 




by the way; the db-tables are created allready; 
this was done.... without any problems ... i will figure out when i run the wiki-script weather all is 
 all right now; But as for now it looks good. 
 
 
 finally i have the following set of tables 
 
 php_wiki: 
 accesslog
 link
 member
 nonempty
 page
 pref
 rating
 recent
 session
 version





_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000071

Re: [Phpwiki-talk] config/config-default.ini - editing the file correct

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

2006/6/12, Manuel Vacelet <man...@gm...>:
> 2006/6/11, jobst m=FCller <Fl...@we...>:
> > by the way: all i have to do is the fourth step of the installation-adv=
ices:
> >
> > ..... 4. Edit the DATABASE settings in config/config.ini to reflect you=
r settings.
> >
> > a) DATABASE_TYPE should be set to 'SQL' or 'ADODB'.
> > b) DATABASE_DSN should be set to something like
> > 'mysql://guest@unix(/var/lib/mysql/mysql.sock)/phpwiki".
> > (where 'phpwiki' is the mysql database name.)
> > c) Note that if you set DATABASE_PREFIX to a
> > non-empty string, you will have to edit
> > schemas/mysql-initialize.sql before you perform step
> > three (above). (Sorry.) (You might also edit
> > schemas/mysql-destroy.sql at the same time, so you
> > don't forget.)
> >
> > yyyyyyyyyyyyyyyyyyyyyyyyyyyy
> >
> > the config/config-default.ini has a bunch of options but i am pretty su=
re that i have an ADODB layer....

dont look at config-default.ini, look at config/config.ini and
better read the INSTALL docs first.

>
> Sure you have it, it's shiped with Phpwiki tarball.
> It's just a matter of choice for your, do you want to rely on PearDb
> backend (so choose SQL) or ADODB (so choose ... ADODB).
>
> > wha t does mean the statement i c) - my DATABASE is called php_Wiki - w=
hat should i take for the prefix!?
>
> I would say: nothing.
> Statment 'c)' is only useful if you are just one DB shared by many
> application in order to avoid table name conflicts.
>
> > is it enough if i set the following lines
> >
> >
> > DATABASE_TYPE =3D dba
> > DATABASE_PREFIX =3D ""
> > DATABASE_SESSION_TABLE =3D session
> > DATABASE_DIRECTORY =3D /tmp
> > DATABASE_DBA_HANDLER =3D gdbm
> > DATABASE_TIMEOUT =3D 20
> > DATABASE_PERSISTENT =3D false
> >
>
> With these parameters, you won't use your SQL database.

DATABASE_TYPE =3D ADODB

> > is the config/config-default.ini the correct file - am i right if i cha=
nge here? guess so!?
>
> config/config-default.ini won't change wiki's parameters. The right
> file is config/config.ini (that you can copy from
> config/config-default.ini).

almost right. you have to copy config/config-dist.ini to config/config.ini

but better start the browser with the directory of phpwiki and run
configurator.php then.
this will create config/config.ini.

you have to install apache with php, and point your browser to the
directory with phpwiki.

> But I think you should use the graphical configurator shiped with phpwiki=
.
> Just unpack phpwiki's tarball in your website and go on this page with
> your browser. A well documented page will help you to configure your
> wiki.
--=20
Reini Urban
http://phpwiki.org/
http://spacemovie.mur.at/   http://helsinki.at/

Re: [Phpwiki-talk] config/config-default.ini - editing the file correct

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

2006/6/11, jobst m=FCller <Fl...@we...>:
> by the way: all i have to do is the fourth step of the installation-advic=
es:
>
> ..... 4. Edit the DATABASE settings in config/config.ini to reflect your =
settings.
>
> a) DATABASE_TYPE should be set to 'SQL' or 'ADODB'.
> b) DATABASE_DSN should be set to something like
> 'mysql://guest@unix(/var/lib/mysql/mysql.sock)/phpwiki".
> (where 'phpwiki' is the mysql database name.)
> c) Note that if you set DATABASE_PREFIX to a
> non-empty string, you will have to edit
> schemas/mysql-initialize.sql before you perform step
> three (above). (Sorry.) (You might also edit
> schemas/mysql-destroy.sql at the same time, so you
> don't forget.)
>
> yyyyyyyyyyyyyyyyyyyyyyyyyyyy
>
> the config/config-default.ini has a bunch of options but i am pretty sure=
 that i have an ADODB layer....

Sure you have it, it's shiped with Phpwiki tarball.
It's just a matter of choice for your, do you want to rely on PearDb
backend (so choose SQL) or ADODB (so choose ... ADODB).

> wha t does mean the statement i c) - my DATABASE is called php_Wiki - wha=
t should i take for the prefix!?

I would say: nothing.
Statment 'c)' is only useful if you are just one DB shared by many
application in order to avoid table name conflicts.

> is it enough if i set the following lines
>
>
> DATABASE_TYPE =3D dba
> DATABASE_PREFIX =3D ""
> DATABASE_SESSION_TABLE =3D session
> DATABASE_DIRECTORY =3D /tmp
> DATABASE_DBA_HANDLER =3D gdbm
> DATABASE_TIMEOUT =3D 20
> DATABASE_PERSISTENT =3D false
>

With these parameters, you won't use your SQL database.

> is the config/config-default.ini the correct file - am i right if i chang=
e here? guess so!?

config/config-default.ini won't change wiki's parameters. The right
file is config/config.ini (that you can copy from
config/config-default.ini).

But I think you should use the graphical configurator shiped with phpwiki.
Just unpack phpwiki's tarball in your website and go on this page with
your browser. A well documented page will help you to configure your
wiki.

-- Manuel

Re: [Phpwiki-talk] Comments on reStructuredText Syntax?

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

2006/6/12, Reini Urban <ru...@x-...>:
> Manuel Vacelet schrieb:
> > I wonder if it's mandatory -or at least just useful- to support a new
> > syntax. Unless if you plan to allow phpwiki to support lot's of syntax
> > (as it support now plenty of storage backend).
>
> That's the idea longterm.

Ok, it's intresting.

> > Now, if you really want to support an other syntax, I think mediawiki
> > flavour is almost mandatory as it's a kind of "standard" (many people
> > know it).
>
> But it deliberately throughs away syntax options, which makes it
> possible to adapt it as standard. For historical and technical reasons.
>
> The strongest: pagename url <=> internal mapping does not survive
> roundtrips. The problematic _ for space, no quote mechanism.
> Some stupid magic pagename limitations. (lowercase beginning not
> allowed, a.s.o.)

I totally agree with you!
Mediawiki's syntax is counter productive and -from my pov- very
difficult to read in text mode.

> If we make the syntax move, mediawiki will be of course the first, to
> attract more people and to convince the wikipedia guys that phpwiki is
> just better.

;)
Some kind of embrace and extends  tactic ?

Anyway, it raises some questions:
* Do you plan to support n syntax in the same wiki ? (and people
choose the syntax they prefer ?)
* In this case, how to deal with limitation of some syntax (as you
highlighted) ?
* Is this useful with the development of more powerful wysiwyg approach ?

> > BTW, did you already heard about an exchange format between wiki's ?
> > I've read few info on mediawiki site months ago but what about phpwki ?
>
> There was some discussion and a mailing-list at wi...@fr...
>
> http://piclab.com/lee/index.php/Wiki_syntax_examples
>
> But there was no solution yet.
>
> There exists a solution, which is based on the easiest format: html.
> every wiki has a html output format.
> david iberri's cpan package:
> http://search.cpan.org/~diberri/HTML-WikiConverter-0.55/
>
> and also http://search.cpan.org/~tels/Convert-Wiki-0.05/

Ok, thank you for the links.
I wonder if sth based on OpenDocument standards is a good way.

-- Manuel

Re: [Phpwiki-talk] Comments on reStructuredText Syntax?

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

Manuel Vacelet schrieb:
> 2006/6/3, Reini Urban <ru...@x-...>:
>> http://docutils.sourceforge.net/docs/user/rst/quickref.html
>>
>> Maybe I want to try to support a new/seperate syntax: reStructuredText
>> when time permits or someone else jumps in.
>>
>> lib/InlineParser.php, lib/BlockParser.php,
>> pgsrc/Help%2FTextFormattingRules%2FreStructuredText
>>
>> I especially like the two table formats: grid-style and simple-style,
>> which can be easily accomplished via plugins for now.
>>
>> But thinking of syntax and the problems within the wysiwyg editors a
>> proper integration, maybe also of the mediawiki syntax rules should be
>> necessary.
>> Now our syntax supports old and new markup rules, markup=0 and 1.
> 
> Hi all,
> 
> I wonder if it's mandatory -or at least just useful- to support a new
> syntax. Unless if you plan to allow phpwiki to support lot's of syntax
> (as it support now plenty of storage backend).

That's the idea longterm.

> Now, if you really want to support an other syntax, I think mediawiki
> flavour is almost mandatory as it's a kind of "standard" (many people
> know it).

But it deliberately throughs away syntax options, which makes it 
possible to adapt it as standard. For historical and technical reasons.

The strongest: pagename url <=> internal mapping does not survive 
roundtrips. The problematic _ for space, no quote mechanism.
Some stupid magic pagename limitations. (lowercase beginning not 
allowed, a.s.o.)

If we make the syntax move, mediawiki will be of course the first, to 
attract more people and to convince the wikipedia guys that phpwiki is 
just better.

> BTW, did you already heard about an exchange format between wiki's ?
> I've read few info on mediawiki site months ago but what about phpwki ?

There was some discussion and a mailing-list at wi...@fr...

http://piclab.com/lee/index.php/Wiki_syntax_examples

But there was no solution yet.

There exists a solution, which is based on the easiest format: html. 
every wiki has a html output format.
david iberri's cpan package:
http://search.cpan.org/~diberri/HTML-WikiConverter-0.55/

and also http://search.cpan.org/~tels/Convert-Wiki-0.05/

-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/
http://helsinki.at/  http://spacemovie.mur.at/

[Phpwiki-talk] config/config-default.ini - editing the file correct

[<Fl...@we...>]

hello all, 


new to this list - yesterday i posterd a question on the list.

i delted the part for the CHARSET - since it is not necessary for the mysql 3.xx 


PRIMARY KEY ( id ) ,
UNIQUE KEY ( pagename )
);
CHARSET is for newer mysql servers.

<<<<<<<<<<<<<<<<


btw: Many thanks Reini for the help and the important hints. 

- the new version of the statement that runs: 


CREATE TABLE page(
id INT NOT NULL AUTO_INCREMENT ,
pagename VARCHAR( 100 ) BINARY NOT NULL ,
hits INT NOT NULL DEFAULT 0,
pagedata MEDIUMTEXT NOT NULL DEFAULT '',
PRIMARY KEY ( id ) ,
UNIQUE KEY ( pagename ) 
) 

this was done.... without any problems ... i will figure out when i run the wiki-script weather all is 
all right now; But as for now it looks good. I  finally i have the following set of tables 

php_wiki: 

accesslog
link
member
nonempty
page
pref
rating
recent
session
version


10 tables - so far so good: 



by the way: all i have to do is the fourth step of the installation-advices: 

..... 4. Edit the DATABASE settings in config/config.ini to reflect your settings.

a) DATABASE_TYPE should be set to 'SQL' or 'ADODB'.
b) DATABASE_DSN should be set to something like
'mysql://guest@unix(/var/lib/mysql/mysql.sock)/phpwiki".
(where 'phpwiki' is the mysql database name.)
c) Note that if you set DATABASE_PREFIX to a 
non-empty string, you will have to edit
schemas/mysql-initialize.sql before you perform step
three (above). (Sorry.) (You might also edit
schemas/mysql-destroy.sql at the same time, so you
don't forget.)

yyyyyyyyyyyyyyyyyyyyyyyyyyyy

the config/config-default.ini has a bunch of options but i am pretty sure that i have an ADODB layer....

wha t does mean the statement i c) - my DATABASE is called php_Wiki - what should i take for the prefix!?

is it enough if i set the following lines 


DATABASE_TYPE = dba
DATABASE_PREFIX = ""
DATABASE_SESSION_TABLE = session
DATABASE_DIRECTORY = /tmp
DATABASE_DBA_HANDLER = gdbm
DATABASE_TIMEOUT = 20
DATABASE_PERSISTENT = false


these lines are out of the the config/config-default.ini: 


; $Id: config-default.ini,v 1.38 2005/09/17 08:17:18 rurban Exp $
; This is the default PhpWiki configuration for undefined config.ini entries.

; recent development and debugging features:
DEBUG = 0
ENABLE_USER_NEW = true
ENABLE_PAGEPERM = true
ENABLE_EDIT_TOOLBAR = true
JS_SEARCHREPLACE = true
ENABLE_DOUBLECLICKEDIT = false
ENABLE_XHTML_XML = false
USECACHE = true
; calculated dynamically, but need a default
WIKIDB_NOCACHE_MARKUP = false
ENABLE_SPAMASSASSIN = false
; deprecated
ENABLE_LIVESEARCH = false
ENABLE_ACDROPDOWN = false
GOOGLE_LINKS_NOFOLLOW = true
NUM_SPAM_LINKS = 20
USE_SAFE_DBSESSION = false
ENABLE_DISCUSSION_LINK = false
ENABLE_CAPTCHA = false
USE_CAPTCHA_RANDOM_WORD = false

WIKI_NAME = PhpWiki
ENABLE_REVERSE_DNS = true
ENCRYPTED_PASSWD = true
ZIPDUMP_AUTH = false
ENABLE_RAW_HTML = true
ENABLE_RAW_HTML_LOCKEDONLY = true
ENABLE_RAW_HTML_SAFE = true
STRICT_MAILABLE_PAGEDUMPS = false
DEFAULT_DUMP_DIR = /tmp/wikidump
HTML_DUMP_DIR = /tmp/wikidumphtml
HTML_DUMP_SUFFIX = .html
MAX_UPLOAD_SIZE = 16777216
MINOR_EDIT_TIMEOUT = 604800
; DISABLED_ACTIONS = "dumpserial : loadfile"
ENABLE_MODERATEDPAGE_ALL = false
ACCESS_LOG = ""
; ACCESS_LOG_SQL: on SQL or ADODB 2, else 0
; ACCESS_LOG_SQL = 0
; COMPRESS_OUTPUT = true
CACHE_CONTROL = LOOSE
CACHE_CONTROL_MAX_AGE = 600


<<<<<<<<<< snipsnap <<<<<< snipsnap <<<<<< snipsnap <<<<<<<<<


DATABASE_TYPE = dba
DATABASE_PREFIX = ""
DATABASE_SESSION_TABLE = session
DATABASE_DIRECTORY = /tmp
DATABASE_DBA_HANDLER = gdbm
DATABASE_TIMEOUT = 20
DATABASE_PERSISTENT = false

<<<<<<<<< snipsnap <<<<<< snipsnap <<<<<< snipsnap <<<<<<<<<


; let all revisions be stored
MAJOR_MIN_KEEP = 2147483647
MINOR_MIN_KEEP = 2147483647
; older fine-tuned settings for low-storage systems. 
; just comment the two lines above to enable it.
MAJOR_MAX_AGE = 32
MAJOR_KEEP = 8
MINOR_MAX_AGE = 7
MINOR_KEEP = 4
AUTHOR_MAX_AGE = 365
AUTHOR_KEEP = 8
AUTHOR_MIN_AGE = 7
AUTHOR_MAX_KEEP = 20

COOKIE_EXPIRATION_DAYS = 365
COOKIE_DOMAIN = "/"

ALLOW_ANON_USER = true
ALLOW_ANON_EDIT = true
ALLOW_BOGO_LOGIN = true
ALLOW_USER_PASSWORDS = true
USER_AUTH_ORDER = PersonalPage
PASSWORD_LENGTH_MINIMUM = 0
USER_AUTH_POLICY = stacked
;LDAP_AUTH_HOST = "ldap://localhost:389"
;LDAP_BASE_DN = "ou=Users,o=Development,dc=mycompany.com"
;LDAP_SET_OPTION = ""
;LDAP_AUTH_USER = "CN=ldapuser,CN=Users"
;LDAP_AUTH_PASSWORD = ""
;LDAP_SEARCH_FIELD = "uid"
;IMAP_AUTH_HOST = "localhost:143/imap/notls"
;POP3_AUTH_HOST = "localhost:110"
;AUTH_USER_FILE = /etc/passwd
AUTH_USER_FILE_STORABLE = false
AUTH_SESS_USER = userid
AUTH_SESS_LEVEL = 2
GROUP_METHOD = WIKIPAGE
;CATEGORY_GROUP_PAGE = CategoryGroup
;AUTH_GROUP_FILE = /etc/groups
DBAUTH_AUTH_CHECK = "SELECT IF(passwd='$password',1,0) as ok FROM pref WHERE userid='$userid'"
DBAUTH_AUTH_CRYPT_METHOD = plain
DBAUTH_AUTH_USER_EXISTS = "SELECT userid FROM pref WHERE userid='$userid'"
DBAUTH_AUTH_CREATE = "INSERT INTO pref SET passwd='$password',userid='$userid'"
DBAUTH_PREF_SELECT = "SELECT prefs FROM pref WHERE userid='$userid'"
DBAUTH_PREF_UPDATE = "UPDATE pref SET prefs='$pref_blob' WHERE userid='$userid'"
DBAUTH_PREF_INSERT = "INSERT INTO pref (prefs,userid) VALUES ('$pref_blob','$userid')"
DBAUTH_IS_MEMBER = "SELECT userid FROM pref WHERE userid='$userid' AND groupname='$groupname'"
DBAUTH_GROUP_MEMBERS = "SELECT userid FROM pref WHERE groupname='$groupname'"
DBAUTH_USER_GROUPS = "SELECT groupname FROM pref WHERE userid='$userid'"
EDITING_POLICY = "EditingPolicy"
; old WikiUser options:
ALLOW_HTTP_AUTH_LOGIN = false
ALLOW_LDAP_LOGIN = false
ALLOW_IMAP_LOGIN = false

THEME = default
; DEFAULT_LANGUAGE = 
CHARSET = iso-8859-1
WIKI_PGSRC = pgsrc
DEFAULT_WIKI_PGSRC = pgsrc
; untranslated pgsrc pages to always include
DEFAULT_WIKI_PAGES = "ReleaseNotes:SandBox:PhpWiki:SteveWainstead"

ALLOWED_PROTOCOLS = "http|https|mailto|ftp|news|nntp|ssh|gopher"
INLINE_IMAGES = "png|jpg|gif"
WIKI_NAME_REGEXP = "(?SUBPAGE_SEPARATOR = "/"
INTERWIKI_MAP_FILE = lib/interwiki.map
WARN_NONPUBLIC_INTERWIKIMAP = false
KEYWORDS = "Category* OR Topic*"
COPYRIGHTPAGE_TITLE = "GNU General Public License"
COPYRIGHTPAGE_URL = "http://www.gnu.org/copyleft/gpl.html#SEC1"
; COPYRIGHTPAGE_TITLE = GNU Free Documentation License
; COPYRIGHTPAGE_URL = http://www.gnu.org/copyleft/fdl.html
; COPYRIGHTPAGE_TITLE = Creative Commons License 1.0
; COPYRIGHTPAGE_URL = http://creativecommons.org/licenses/by/1.0/
AUTHORPAGE_TITLE = "The PhpWiki Programming Team"
AUTHORPAGE_URL = "http://phpwiki.org/ThePhpWikiProgrammingTeam"

TOC_FULL_SYNTAX = true
ENABLE_MARKUP_COLOR = true
ENABLE_MARKUP_TEMPLATE = false

; these not:
; DBAUTH_AUTH_DSN =
; SERVER_NAME = 
; SERVER_PORT = 
; SCRIPT_NAME = 
; DATA_PATH = 
; PHPWIKI_DIR = 
; VIRTUAL_PATH = 
; USE_PATH_INFO = 
; TEMP_DIR = /tmp

DISABLE_HTTP_REDIRECT = false
DISABLE_GETIMAGESIZE = false
; FORTUNE_DIR = /usr/share/fortune
; GOOGLE_LICENSE_KEY = "..."
; DBADMIN_USER = 
; DBADMIN_PASSWD = 
BLOG_DEFAULT_EMPTY_PREFIX = true
; TOOLBAR_PAGELINK_PULLDOWN = *
; TOOLBAR_TEMPLATE_PULLDOWN = Template*

; External executables:
; USE_EXTERNAL_HTML2PDF = "htmldoc --quiet --format pdf14 --no-toc --no-title %s"
BABYCART_PATH = /usr/local/bin/babycart
; GRAPHVIZ_EXE = /usr/local/bin/dot

PLUGIN_CACHED_DATABASE = file
; PLUGIN_CACHED_CACHE_DIR = /tmp/cache
PLUGIN_CACHED_FILENAME_PREFIX = phpwiki
PLUGIN_CACHED_HIGHWATER = 4194304
PLUGIN_CACHED_LOWWATER = 3145728
PLUGIN_CACHED_MAXLIFETIME = 2592000
PLUGIN_CACHED_MAXARGLEN = 1000
PLUGIN_CACHED_USECACHE = true
PLUGIN_CACHED_FORCE_SYNCMAP = true
PLUGIN_CACHED_IMGTYPES = "png|gif|gd|gd2|jpeg|wbmp|xbm|xpm"



is the config/config-default.ini the correct file - am i right if i change here? guess so!?




the question - are the lines that i have to edit the following?

<<<<<<<<<< snipsnap <<<<<< snipsnap <<<<<< snipsnap <<<<<<<<<


DATABASE_TYPE = dba
DATABASE_PREFIX = ""
DATABASE_SESSION_TABLE = session
DATABASE_DIRECTORY = /tmp
DATABASE_DBA_HANDLER = gdbm
DATABASE_TIMEOUT = 20
DATABASE_PERSISTENT = false

<<<<<<<<< snipsnap <<<<<< snipsnap <<<<<< snipsnap <<<<<<<<<



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000071

Re: [Phpwiki-talk] cant wait to get on board - i am totally happy

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

[question from a fan forwarded to the phpwiki-talk list]

jobst müller schrieb:
>   hello Rurban, good day 
> 
> 
> just saw your name on the subscriber - confrimation page over at sourceforge.
> 
> just subscribed to the list - and now i am waitin for more instructions - i am totally happy that 
> i found the wiki-script and that i found this great great open source-community; 

Waiting is wrong, reading is better. And asking the wrong email 
addresses is bad. I forwarded your question to the list.
Please first subscribe, then ask. If you don't like it, unsubscribe.
It's a matter of minutes.

> Rurban,  many thanks for creating the wiki-module ! i love it very much! It gives me the  right tool for my community! Rurban i want to ask for a little help in installation matters: I wanna set up the base wiki module and run it as a standalone!
> 
> I have grabbed the newest release 1.3.12 p2 
>  
> 
>  I created a db with the phpMyadmin-frontend tool. AFterwards i wanted to create the tables. 
> 
> while doing that; i ran into troubles. well 
> 
> irun MySQL 3.23.58  
> 
> 
> and while proceeding /(executing ) the -- $Id: mysql-initialize.sql,v 1.8 2005/06/21 05:59:18 rurban Exp $
> 
> i got the following result ,,,, Error in proceeding the sql-statement:
> 
> CREATE TABLE page(
> 
> id INT NOT NULL AUTO_INCREMENT ,
> -- for mysql => 4.1 define the charset here
> -- this is esp. needed for mysql 4.1.0 up to 4.1.6. 
> -- not yet confirmed, at least since 4.1.8 it's okay with binary.
> -- pagename VARCHAR(100) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL,
> -- otherwise use the old syntax to do case-sensitive comparison
> pagename VARCHAR( 100 ) BINARY NOT NULL ,
> hits INT NOT NULL DEFAULT 0,
> pagedata MEDIUMTEXT NOT NULL DEFAULT '',
> -- dont add that by hand, better let action=upgrade convert your data
> cached_html MEDIUMBLOB,
> PRIMARY KEY ( id ) ,
> UNIQUE KEY ( pagename ) 
> ) CHARSET = latin1 
> 
> MySQL responds 
> 
> 
> #1064 - You have an error in your SQL syntax near 'CHARSET=latin1' at line 12 
> 
> well Rurban i want to run it in Germany (good old Europe) - should i set up something with the 
> language or shouldn Žt i?! I am pretty glueless. 
> 
> Well if i - how should i to do that?  

delete the offending property from this statement.

...
   PRIMARY KEY ( id ) ,
   UNIQUE KEY ( pagename )
  );

CHARSET is for newer mysql servers.

> Rurban many thanks in advance for any and all help - keep up the great project - it rocks !! 
> 
> 
> hopefully i am soon on the list - then i can post this on the list! 
> 
> dear Rurban - i love the great great wiki-script.
> 
> 
> regards 
> 
> 
> flobee you wiki -fan
-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/
http://helsinki.at/  http://spacemovie.mur.at/

[Phpwiki-talk] troubles while running the installation - cant create the tables

[<Fl...@we...>]

Hello Dear Wiki user


new to this list- just subscribed to the list=20

many thanks for creating the wiki-module ! i love it very much! It gives m=
e the  right tool for my ideas. I want to ask for a little help in install=
ation matters: again; i found the wiki-script and that i found this great =
great open source-community;=20
I wanna set up the wiki and run it on my website:=20

I have grabbed the newest release 1.3.12 p2  I created a db with the phpMy=
admin-frontend tool.   =20

Afterwards i wanted to create the tables.=20

while doing that; i ran into troubles. well=20

I run MySQL 3.23.58  on my server.

And while proceeding /(executing ) the -- $Id: mysql-initialize.sql,v 1.8 =
2005/06/21 05:59:18 rurban Exp $

i got the following result ,,,, Error in proceeding the sql-statement:

CREATE TABLE page(

id INT NOT NULL AUTO=5FINCREMENT ,
-- for mysql =3D> 4.1 define the charset here
-- this is esp. needed for mysql 4.1.0 up to 4.1.6.=20
-- not yet confirmed, at least since 4.1.8 it's okay with binary.
-- pagename VARCHAR(100) CHARACTER SET latin1 COLLATE latin1=5Fbin NOT NULL,=

-- otherwise use the old syntax to do case-sensitive comparison
pagename VARCHAR( 100 ) BINARY NOT NULL ,
hits INT NOT NULL DEFAULT 0,
pagedata MEDIUMTEXT NOT NULL DEFAULT '',
-- dont add that by hand, better let action=3Dupgrade convert your data
cached=5Fhtml MEDIUMBLOB,
PRIMARY KEY ( id ) ,
UNIQUE KEY ( pagename )=20
) CHARSET =3D latin1=20

MySQL responds=20


#1064 - You have an error in your SQL syntax near 'CHARSET=3Dlatin1' at line=
 12=20

well I want to run it in Germany (good old Europe) - should i set up somet=
hing with the language or shouldn =B4t i=3F! I am pretty glueless.  Well if i =
- how should i to do that=3F =20


Ahhh dear Wiki-fans, many thanks in advance for any and all help - keep up=
 the great project - it rocks=20


regards=20

flobee you wiki-fan
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/=3Fmc=3D021193

Re: [Phpwiki-talk] Comments on reStructuredText Syntax?

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

2006/6/3, Reini Urban <ru...@x-...>:
> http://docutils.sourceforge.net/docs/user/rst/quickref.html
>
> Maybe I want to try to support a new/seperate syntax: reStructuredText
> when time permits or someone else jumps in.
>
> lib/InlineParser.php, lib/BlockParser.php,
> pgsrc/Help%2FTextFormattingRules%2FreStructuredText
>
> I especially like the two table formats: grid-style and simple-style,
> which can be easily accomplished via plugins for now.
>
> But thinking of syntax and the problems within the wysiwyg editors a
> proper integration, maybe also of the mediawiki syntax rules should be
> necessary.
> Now our syntax supports old and new markup rules, markup=0 and 1.

Hi all,

I wonder if it's mandatory -or at least just useful- to support a new
syntax. Unless if you plan to allow phpwiki to support lot's of syntax
(as it support now plenty of storage backend).

Now, if you really want to support an other syntax, I think mediawiki
flavour is almost mandatory as it's a kind of "standard" (many people
know it).

BTW, did you already heard about an exchange format between wiki's ?
I've read few info on mediawiki site months ago but what about phpwki ?

My 2 eurocents !
Manuel

[Phpwiki-talk] RichTable at al: links are now detected

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

I just found and fixed the bug, which prevented some links, esp. for 
plugins but from everywhere else also, to be updated into the links table.

array_merge doesn't handle numeric arrays of arrays, array_unique ditto.
This problem was added when I introduced semantic relations into the 
link structure. But I vaguely remember that RichTable users also 
complained. This should be fixed now.

I also added some cleanup code to the ADODB backend which purges empty, 
non-referenced pagaes from the tables when a link is deleted.
For now only when DEBUG is specified.
-- 
Reini Urban
http://phpwiki.org/
http://helsinki.at/  http://spacemovie.mur.at/

[Phpwiki-talk] Comments on reStructuredText Syntax?

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

http://docutils.sourceforge.net/docs/user/rst/quickref.html

Maybe I want to try to support a new/seperate syntax: reStructuredText
when time permits or someone else jumps in.

lib/InlineParser.php, lib/BlockParser.php,
pgsrc/Help%2FTextFormattingRules%2FreStructuredText

I especially like the two table formats: grid-style and simple-style,
which can be easily accomplished via plugins for now.

But thinking of syntax and the problems within the wysiwyg editors a
proper integration, maybe also of the mediawiki syntax rules should be
necessary.
Now our syntax supports old and new markup rules, markup=0 and 1.
-- 
Reini Urban
http://phpwiki.org/
http://helsinki.at/  http://spacemovie.mur.at/

Re: [Phpwiki-talk] Fatal error with phpwiki cvs + wysiwyg patch

[Jean-Nicolas G. <jea...@st...>]

Reini Urban wrote:
> Jean-Nicolas GEREONE schrieb:
>   
>> I am going to make a new release of the wysiwyg editor.
>> I will post it in the patch tracker on sourceforge today. Could you put
>> it in the cvs please ? I still don't have a cvs access.
>> The patch can be applied on a cvs checkout.
>>     
>
> dada, ok, here you are.
> Please welcome a new developer jeannicolas.
> You have now cvs access.
>
> Now we'll you will be first in putting this into CVS :)
>   
Great,

Thanks a lot.

I will use it right  : )



>   
>> Thanks.
>> Regards.
>> Jean-Nicolas.
>>
>>
>> Reini Urban wrote:
>>     
>>> yes, i haven't fixed that yet.
>>>
>>> it came from the patch introducing pear sequences, which of course do
>>> not work.
>>> as everything with pear db. such a crap.
>>> I'll revert to our manual sequences as before.
>>>
>>> 2006/5/24, Jean-Nicolas GEREONE <jea...@st...>:
>>>       
>>>> Hi all,
>>>>
>>>> I am using phpwiki cvs and sometimes a fatal error appears when I am
>>>> saving a wikipage with lots of modifications.
>>>>
>>>> Here is the error :
>>>>
>>>> Fatal Error:
>>>>
>>>> lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql:
>>>> fatal database error
>>>>
>>>>     * DB Error: not locked
>>>>     * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100
>>>> ** Table 'page_id_seq' was not locked with LOCK TABLES])
>>>>     *
>>>>
>>>>
>>>> Fatal PhpWiki Error
>>>>
>>>> lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql:
>>>> fatal database error
>>>>
>>>>     * DB Error: not locked
>>>>     * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100
>>>> ** Table 'page_id_seq' was not locked with LOCK TABLES])
>>>>
>>>>
>>>> Has someone heard about it ?
>>>>         

Re: [Phpwiki-talk] Fatal error with phpwiki cvs + wysiwyg patch

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

Reini Urban schrieb:
> dada, ok, here you are.
> Please welcome a new developer jeannicolas.
> You have now cvs access.
> 
> Now we'll you will be first in putting this into CVS :)

Oh god! The magic word eater is wandering around. Let's see if I get it
out with only a few chars missing...

I think I wanted to write smthg like this:
"Now we'll see who will be the first in putting this into CVS :)"

Re: [Phpwiki-talk] Fatal error with phpwiki cvs + wysiwyg patch

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

Jean-Nicolas GEREONE schrieb:
> I am going to make a new release of the wysiwyg editor.
> I will post it in the patch tracker on sourceforge today. Could you put
> it in the cvs please ? I still don't have a cvs access.
> The patch can be applied on a cvs checkout.

dada, ok, here you are.
Please welcome a new developer jeannicolas.
You have now cvs access.

Now we'll you will be first in putting this into CVS :)

> Thanks.
> Regards.
> Jean-Nicolas.
> 
> 
> Reini Urban wrote:
>> yes, i haven't fixed that yet.
>>
>> it came from the patch introducing pear sequences, which of course do
>> not work.
>> as everything with pear db. such a crap.
>> I'll revert to our manual sequences as before.
>>
>> 2006/5/24, Jean-Nicolas GEREONE <jea...@st...>:
>>> Hi all,
>>>
>>> I am using phpwiki cvs and sometimes a fatal error appears when I am
>>> saving a wikipage with lots of modifications.
>>>
>>> Here is the error :
>>>
>>> Fatal Error:
>>>
>>> lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql:
>>> fatal database error
>>>
>>>     * DB Error: not locked
>>>     * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100
>>> ** Table 'page_id_seq' was not locked with LOCK TABLES])
>>>     *
>>>
>>>
>>> Fatal PhpWiki Error
>>>
>>> lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql:
>>> fatal database error
>>>
>>>     * DB Error: not locked
>>>     * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100
>>> ** Table 'page_id_seq' was not locked with LOCK TABLES])
>>>
>>>
>>> Has someone heard about it ?
-- 
Reini Urban
http://phpwiki.org/
http://helsinki.at/  http://spacemovie.mur.at/

[Phpwiki-talk] Current wiki errors...

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

Reini,
  Here are a few errors I'm seeing with the latest CVS version (note: I have
not performed an upgrade, so if I need to do that, please tell me, I was
running a cvs version from a few months ago).

Using the page TextFormattingRules the following errors are at the bottom of
the page:

f:\inetpub\wwwroot\phpwiki_cvs\lib\DbSession\ADODB.php:113: Notice: Only
variables should be assigned by reference

f:\inetpub\wwwroot\phpwiki_cvs\lib\CachedMarkup.php (In template 'browse' <
'body' < 'html'):499: Notice: Only variables should be assigned by reference

f:\inetpub\wwwroot\phpwiki_cvs\lib\CachedMarkup.php (In template 'body' <
'html'):499: Notice: Only variables should be assigned by reference



f:\inetpub\wwwroot\phpwiki_cvs\lib\CachedMarkup.php (In template
'html'):499: Notice: Only variables should be assigned by reference

I'm running IIS6, php 4.4.2 with MySQL 4.0.27 on W2K3 Server SP1 and phpWiki
from CVS this morning with the CRAO theme.

Thanks,

John
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 sender. 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] phpWiki issues...

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

Reini,
  I was wondering what the status was on a few issues with phpWiki:

1) It's been about a year since the admin tools worked (/Rename, /Replace,
etc...) have these been looked at?

2)  What about the PDF support?  I haven't ever seen it work yet :-)  The
cvs version isn't giving the same error, now the file created by phpWiki is
throwing an error with acrobat (does not start with %PDF).  Downloading the
link to a file, here are the contents:

<div class="hint"><p>f:\inetpub\wwwroot\phpwiki_cvs\lib\CachedMarkup.php (In
template 'browse' &lt; 'body' &lt; 'html'):499: Notice: Only variables
should be assigned by reference </p>
</div>

As you can see, this isn't a pdf file :-)  I had to change the command line
but I know this works, as I dumped a file from the wiki and ran this to make
a pdf file:

USE_EXTERNAL_HTML2PDF = "C:\Program Files\Easy Software
Products\HTMLDOC\htmldocd.exe --quiet --format pdf14 --no-toc --no-title
--no-links --webpage %s"

But I get the above output through the wiki (latest cvs version.

3)  We are generating all of our documentation via phpWiki and docbook, and
need to do some organization of those pages.  In above to getting 1)
working, it would be nice to have a /Copy pages admin function, but getting
1) and 2) working soon would be fantastic!

Thanks,

John
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 sender. 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] Fatal error with phpwiki cvs

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

yes, i haven't fixed that yet.

it came from the patch introducing pear sequences, which of course do not work.
as everything with pear db. such a crap.
I'll revert to our manual sequences as before.

2006/5/24, Jean-Nicolas GEREONE <jea...@st...>:
> Hi all,
>
> I am using phpwiki cvs and sometimes a fatal error appears when I am
> saving a wikipage with lots of modifications.
>
> Here is the error :
>
> Fatal Error:
>
> lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql:
> fatal database error
>
>     * DB Error: not locked
>     * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100
> ** Table 'page_id_seq' was not locked with LOCK TABLES])
>     *
>
>
> Fatal PhpWiki Error
>
> lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql:
> fatal database error
>
>     * DB Error: not locked
>     * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100
> ** Table 'page_id_seq' was not locked with LOCK TABLES])
>
>
> Has someone heard about it ?
>
>
> Regards.
>
> Jean-Nicolas.
>
>
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>


-- 
Reini Urban
http://phpwiki.org/
http://spacemovie.mur.at/   http://helsinki.at/

[Phpwiki-talk] Fatal error with phpwiki cvs

[Jean-Nicolas G. <jea...@st...>]

Hi all,

I am using phpwiki cvs and sometimes a fatal error appears when I am 
saving a wikipage with lots of modifications.

Here is the error :

Fatal Error:

lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql: 
fatal database error

    * DB Error: not locked
    * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100 
** Table 'page_id_seq' was not locked with LOCK TABLES])
    *


Fatal PhpWiki Error

lib/WikiDB/backend/PearDB.php:1042: Error: wikidb_backend_peardb_mysql: 
fatal database error

    * DB Error: not locked
    * (UPDATE page_id_seq SET id=LAST_INSERT_ID(id+1) [nativecode=1100 
** Table 'page_id_seq' was not locked with LOCK TABLES])


Has someone heard about it ?


Regards.

Jean-Nicolas.

[Phpwiki-talk] New wikiElement howto

[Stefan <son...@ba...>]

i need to insert two different types of horizontal lines. The default 
way is to insert "----" but i need a secont way like "===" to do this 
with different styles. (Example result: <hr> and <hr class=clearall> 
Whould also a nice feature for <br>

Can you tell me which files i have to change to add this type too.
Stefan

[Phpwiki-talk] Want to make a new wiki, but...

[Nomad of N. (D. C Hall) <nom...@jo...>]

...I am a complete noob.

Has anyone here installed phpwiki onto an ipowerweb.com hosted website?

What is the best approach for this? Should I set it up via mySQL or as a
flat database?  And can someone who has done it before at this provider
give me a hand with it and/or some guidelines?  They have a web-based
interface for running things, but their interactive tutorial thingy
isn't as helpful as I might like, and when I try to follow their
instructions _4. MySQL Databases › Creating a Database_ while acting
upon them on another browser page, after a certain point, it diverts
from what, according to their instructions, is supposed to come up.



-- 
    no...@jo... ----- http://www.joshua-wopr.com    |
  Nomad of Norad (David C. Hall) -- *TeamAmiga* -- Club Amiga |
  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
   For a dementedly wacky sci-fi continue-the-story project,  |
  join my WebBBS. http://www.joshua-wopr.com/phpBB/index.php  |
-------------------------------------------------------------+
  "My life has a superb cast but I can't figure out the plot." \
    --Ashleigh Brilliant                                       /
-------------------------------------------------------------+

[Phpwiki-talk] Problem with e-mail notification

[<hen...@es...>]

Hi!

I use phpwiki-1.3.12p2 and have a problem regarding email notification. When I edit a page marked for mail notification no mail is send. I use 

ALLOW_ANON_USER = true
ALLOW_BOGO_LOGIN = true
ALLOW_USER_PASSWORDS = false
ALLOW_ANON_EDIT = true

because the wiki is protected by external http authentication against sql. The user name is also set by the external authentication (e.g. if the user name is John Doe, it is set to JohnDoe). Do I need to change my authentication settings to use mail notification? The mail server runs on the same machine and works perfectly so this is not the problem.

Regards,
Henning Sahlbach

RE: [Phpwiki-talk] ACL question

[joel s. <joe...@sb...>]

Remeber, I was trying to subtract view permissions.
So I thought -_BOGOUSER looked correct for what I wanted.
But the problem was that in spite of this, I could still view pages after
signing out.

Joel Schaubert


-----Original Message-----
From: php...@li...
[mailto:php...@li...]On Behalf Of Reini
Urban
Sent: Wednesday, May 17, 2006 12:56 AM
To: php...@li...
Subject: Re: [Phpwiki-talk] ACL question


2006/5/16, joel schaubert <fox...@gm...>:
> My wiki is setup to allow anyone to view, but only auth'ed users to edit
>
>  For one page I want to set it so that only auth'ed users can view.
>  I currently am showing this on the ACL page which makes me think it is
set
> the way I want.
>  Notice how view and edit both have  -_BOGOUSER.
>  But I find that when I sign out, I can still view, but I cannot edit.
>
>  Are there known issues with some of the details of using ACL lists?
>  Thanks,
>  Joel Schaubert
>
>  Type: invidual page permission
> getfacl: rw----rw-+
> ACL: view:_AUTHENTICATED,-_BOGOUSER; edit:_AUTHENTICATED,-_BOGOUSER;
> create:_AUTHENTICATED,-_BOGOUSER; list:_EVERY;
> remove:_ADMIN,_OWNER; change:_ADMIN,_OWNER; dump:_EVERY

Everything ok, but "-_BOGOUSER" should be "_BOGOUSER"

Wonder how that slipped in. I'll check.
--
Reini


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] Problem to convert links with http

[Jean-Nicolas G. <jea...@st...>]

Reini Urban wrote:
> 2006/5/16, Jean-Nicolas GEREONE <jea...@st...>:
>> Reini Urban wrote:
>> > 2006/5/12, Jean-Nicolas GEREONE <jea...@st...>:
>> >> For the development of the wysiwyg editor, I have an issue for the
>> >> conversion from wikitext to html of links.
>> >>
>> >> To convert wikitext to html, I use the code bellow :
>> >>
>> >>       require_once("lib/BlockParser.php");
>> >>       $output = new Wikitext($this->_wikitext);
>> >>       $xmlcontent = new XmlContent($output->getContent() );
>> >>       $this->_html = $xmlcontent->AsXML();
>> >
>> > Did you actually look into the WysiwygEdit framework?
>> > This is done in WysiwygEdit ->ConvertBefore()
>> >
>> >        require_once("lib/BlockParser.php");
>> >        $xml = TransformText($text, 2.0,
>> > $GLOBALS['request']->getArg('pagename'));
>> >        return $xml->AsXML();
>>
>> Yes. The problem is that it convert plugins in html too.
>
> Ah, I see! Okay, we can temp. disable the plugin type for this kind of
> conversion.
> For the moment maybe with a global, later the API has to be enhanced.
>
Finally I have changed my view.

I will use :

       require_once("lib/BlockParser.php");
       $xml = TransformText($text, 2.0,
      $GLOBALS['request']->getArg('pagename'));
      return $xml->AsXML();

And to avoid converting plugins I will send :
~<?plugin ... and not
<?plugin ...

for the moment.

So links will be ok too.


>> And for the moment conversion of plugins (in html form)  to wikitext is
>> not supported. And this will require a particular development for each
>> plugin. That's why I 've chosen this code.

Re: [Phpwiki-talk] ACL question

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

2006/5/16, joel schaubert <fox...@gm...>:
> My wiki is setup to allow anyone to view, but only auth'ed users to edit
>
>  For one page I want to set it so that only auth'ed users can view.
>  I currently am showing this on the ACL page which makes me think it is s=
et
> the way I want.
>  Notice how view and edit both have  -_BOGOUSER.
>  But I find that when I sign out, I can still view, but I cannot edit.
>
>  Are there known issues with some of the details of using ACL lists?
>  Thanks,
>  Joel Schaubert
>
>  Type: invidual page permission
> getfacl: rw----rw-+
> ACL: view:_AUTHENTICATED,-_BOGOUSER; edit:_AUTHENTICATED,-_BOGOUSER;
> create:_AUTHENTICATED,-_BOGOUSER; list:_EVERY;
> remove:_ADMIN,_OWNER; change:_ADMIN,_OWNER; dump:_EVERY

Everything ok, but "-_BOGOUSER" should be "_BOGOUSER"

Wonder how that slipped in. I'll check.
--=20
Reini