phpwiki-talk

[Phpwiki-talk] ADOdb backends...

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

Reini,

The ADOdb/Oracle backend is working more or less (still have to fix a 
couple of things), but I am not too happy with the current state...

So here are a couple of questions about WikiDB and backends:

1. Table names / database objects: where do the 'abstraction' happens?
I was initially thinking that the backends were responsible for the 
'physical' implementation -- including table naming (e.g. _table_names 
hash), but it looks it is not the case, since we find back table names 
in WikiDB.php.
Given the fact that WikiDB is not using the same names ('links' io 
'link') and does not uses prefixes, I am missing some 'translation 
table' here...
Can you comment on this?

2. locking mechanism
This is looking a bit weird to me: we are locking all over the place: 
WikiDB, backends, inside and outside transactions, ...
Is there a rationale behind this?
It does not look very compatible with a transactional DBMS which does 
not hold locks longer than a transaction (and cannot unlock without 
ending the transaction). The notion of transaction and locking are 
tighly bound.

3. ADOdb generic backend
We do have a lot of mysql specifics testing in there...
eg:
    if ((substr($dbh->databaseType,0,5) == 'mysql')....

Shouldn't we try to have a backend which is really generic, and have all 
the database specifics in the ADODB_<db>.php subclass?

Current situation is relatively messy (no offense -- just my impressions)

--
Philippe

Re: [Phpwiki-talk] Wiki

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

Terry Toms wrote:
> I would really like to contribute to this but so far have not even been 
> able to sign my name as visiting. ; 

"visiting" is not a valid wikiword, so it doesn't qualify as valid 
BogoUser userid. Please choose a better userid.
(If your elaborate quirt meant contributing to 
http://phpwiki.sourceforge.net/phpwiki.)

This is already explained at the signin page:
"You may sign in using any WikiWord as a user id. (Any characters in 
ÀñíçéàÖãæôßøü etc. may be used too) ..." so a little reading would have 
helped also.

> I am not a geek. but do you want a 
> book only written by geeks. ; Please help! ; There are times on ecademy 
> when I seem to wander into geekland - too often. ; If ecademy is to 
> fulfil it's potential a higher level of empathy for the non geek would 
> go a long way. ; I will persist. ; But if you get too far ahead of me I 
> will get lost. ; A good servant leader should not be out of reach of 
> those he serves.
>  ;
> Much appreciated.
>  ;
> Terry Toms  ;
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] <div> tag for plugins?

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

John Cole wrote:
>   I'm working on my docbook conversion and things are going pretty good so
> far.  I'm rendering out htmlhelp and pdf's now.
> 
>   I'd like to suggest a small change that I hope won't impact anything, but
> would make converting xhmtl with xsl stylesheets easier (as far as I know
> how with xsl stylesheets).
>   Would it be possible to put a <div> tag around each plugin with an id or
> class name of the plugin?  

Good idea.

Not the classname and not another div tag, but the ID of the plugin DIV 
is now the plugin->getName().
Like so:
<div class="plugin tightenable" id="AddComment">

Note, that we don't enumerate the id as we do in anchors for CreateToc, 
so duplicate plugins get the same id.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Email notification question.

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

Bill White wrote:

> I have not looked too hard at the Phpwiki source code, but I am
> interested in creating a plugin.  I want to be able to put a plugin
> something like this:
>   <?plugin EmailNotification ?>
> on a page, and have appear there:
>   o A list, perhaps a combo box, of the people who are currently
>     scheduled for email notification when the page changes, and
>   o A button which will add the currently signed in user to the
>     list.
> From my 10 minute perusal of the code it was not clear to me how
> to get the first list, or how to accomplish the second task.  If
> I had those two bits of data, I think it would be trivial to code
> up the rest.  So, does anybody have a suggestion?


This seems like a good idea, not only for a page, but more likely for 
part of a theme template, like the header or navbar. This would be like 
Wikipedia's "Watch this page."

I don't know much about answering your question, tho. Here's what I do know:

- The code that generates the notifications is in WikiDB, in 
getPageChangeEmails(), sendPageChangeNotification().

- A perusal of the code shows that there is a global setting 'notify' 
that is a list of users and what pages they should be notified of. This 
global setting is stored in a page called 'global_data' (see WikiDB::get()).

- I believe this setting is also stored by the UserPreferences plugin in 
the pagedata for the user. UserPreferences seems to call 
$user->setPreferences().

So, perhaps you can use $user->setPreferences() to set the 'notify' 
preference to include a page. Try it and see. Look at the DB and see if 
the pagedata for the user and 'global_data' are properly mutated.

Dan

[Phpwiki-talk] Email notification question.

[Bill W. <bil...@et...>]

I have not looked too hard at the Phpwiki source code, but I am
interested in creating a plugin.  I want to be able to put a plugin
something like this:
   <?plugin EmailNotification ?>
on a page, and have appear there:
   o A list, perhaps a combo box, of the people who are currently
     scheduled for email notification when the page changes, and
   o A button which will add the currently signed in user to the
     list.
 From my 10 minute perusal of the code it was not clear to me how
to get the first list, or how to accomplish the second task.  If
I had those two bits of data, I think it would be trivial to code
up the rest.  So, does anybody have a suggestion?

Thanks in advance.
-- 
Bill White                 bil...@et...
Etnus, LLC                 http://www.etnus.com
24 Prime Park Way
Natick, MA 01760-1528
508-652-7724

[Phpwiki-talk] bug in blog plugin...

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

There seems to be a bug in the blog plugin (maybe it's a feature, but it
messes up UnfoldSubpages) :-).

  If you create a blog entry, say jcole /Blog /2004-07-02 /12:37:42-05:00 it
also creates a jcole /Blog /2004-07-02 page with a redirect to your starting
page (jcole in this case).

  The blog viewer doesn't seem to mind this, but the UnfoldSubpages plugin
can't handle that if you have it on the page that you submitted the blog
from (like a last 5 blogs section).  There you get a recursive loop and it
shows an error.

  To try it out put the following on a page and put a few entries in it.

<?plugin WikiBlog mode=add?>

<?plugin UnfoldSubpages sortby=-mtime words=50 maxpages=5 ?>

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 system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

[Phpwiki-talk] problem with flat file install: doesn't archive pages

[Dan M. <dmc...@la...>]

(oops - should have said i'm using phpwiki-1.2.4
unfortunately the php on the server i'm using doesn't have any dbm =
support compiled in)

hi=20

i've set up a flat file version of phpwiki on a server where i don't =
have root access.=20

i used the trick from INSTALL.flatfile to make some directories (like =
pages, archive) which are writeable by the webserver.=20

i edited lib/config.php and set $DBdir to the correct directory.=20

now i can make and edit pages OK, and they are stored in the 'pages' =
directory.=20

but the 'archive' directory only contains the default phpwiki pages =
(e.g. FrontPage).=20
if i create a new page it doesn't appear in 'archive'.=20

so if i edit one of the default pages, i can see previous versions by =
doing a diff, but if i edit a new page and then try diff all i get is =
"Archived page:None"

can anyone advise?

many thanks
dan mcquillan

[Phpwiki-talk] problem with flat file install: doesn't archive pages

[Dan M. <dmc...@la...>]

hi=20

i've set up a flat file version of phpwiki on a server where i don't =
have root access.=20

i used the trick from INSTALL.flatfile to make some directories (like =
pages, archive) which are writeable by the webserver.=20

i edited lib/config.php and set $DBdir to the correct directory.=20

now i can make and edit pages OK, and they are stored in the 'pages' =
directory.=20

but the 'archive' directory only contains the default phpwiki pages =
(e.g. FrontPage).=20
if i create a new page it doesn't appear in 'archive'.=20

so if i edit one of the default pages, i can see previous versions by =
doing a diff, but if i edit a new page and then try diff all i get is =
"Archived page:None"

can anyone advise?

many thanks
dan mcquillan

RE: [Phpwiki-talk] <div> tag for plugins?

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

Reini,
  I made a mistake in my modification, you should only change line 187 to
the following

$div = HTML::div(array('id'=>'unfoldsubpages plugin'));
$div->pushContent($content);
return $div;

Thanks,

John

-----Original Message-----
From: php...@li...
[mailto:php...@li...]On Behalf Of John Cole
Sent: Friday, July 02, 2004 11:02 AM
To: 'Reini Urban'
Cc: php...@li...
Subject: [Phpwiki-talk] <div> tag for plugins?


Reini,
  I'm working on my docbook conversion and things are going pretty good so
far.  I'm rendering out htmlhelp and pdf's now.

  I'd like to suggest a small change that I hope won't impact anything, but
would make converting xhmtl with xsl stylesheets easier (as far as I know
how with xsl stylesheets).
  Would it be possible to put a <div> tag around each plugin with an id or
class name of the plugin?  I'm using the UnfoldSubpages plugin as docbook
books, with each page included as a chapter.  In order to have this work, I
need each invocation of the UnfoldSubpages plugin to be in a tag.  I have
modified my UnfoldSubpages plugin like so:

(changed lines 174-184 like so)
$div = HTML::div(array('id'=>'unfoldsubpages plugin'));
if (! $smalltitle) {
    $div->pushContent(HTML::p(array('class' => $quiet ?
    '' : 'transclusion-title'),
    fmt("Included from %s:",
    WikiLink($page))));
}
$div->pushContent(HTML(HTML::div(array('class' => $quiet ?
'' : 'transclusion'),
false, $ct)));
$content->pushContent($div);

so that the contents of the plugin are in a <div id="unfoldsubpages
plugin">plugin content</div> tags.

This allows my xls stylesheet to convert this into a docbook <book></book>
tag :-)

Is this doable for all plugins?  That would give me a lot of flexablity with
my stylesheets.

Thanks,

John Cole

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


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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.

[Phpwiki-talk] <div> tag for plugins?

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

Reini,
  I'm working on my docbook conversion and things are going pretty good so
far.  I'm rendering out htmlhelp and pdf's now.

  I'd like to suggest a small change that I hope won't impact anything, but
would make converting xhmtl with xsl stylesheets easier (as far as I know
how with xsl stylesheets).
  Would it be possible to put a <div> tag around each plugin with an id or
class name of the plugin?  I'm using the UnfoldSubpages plugin as docbook
books, with each page included as a chapter.  In order to have this work, I
need each invocation of the UnfoldSubpages plugin to be in a tag.  I have
modified my UnfoldSubpages plugin like so:

(changed lines 174-184 like so)
$div = HTML::div(array('id'=>'unfoldsubpages plugin'));
if (! $smalltitle) {
    $div->pushContent(HTML::p(array('class' => $quiet ?
    '' : 'transclusion-title'),
    fmt("Included from %s:",
    WikiLink($page))));
}
$div->pushContent(HTML(HTML::div(array('class' => $quiet ?
'' : 'transclusion'),
false, $ct)));
$content->pushContent($div);

so that the contents of the plugin are in a <div id="unfoldsubpages
plugin">plugin content</div> tags.

This allows my xls stylesheet to convert this into a docbook <book></book>
tag :-)

Is this doable for all plugins?  That would give me a lot of flexablity with
my stylesheets.

Thanks,

John Cole

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

Thanks (WAS: Re: [Phpwiki-talk] [Fwd: [phpwiki-checkins] CVS: phpwiki/lib/wikilens PageListColumns.php,1.3,1.4])

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

Reini Urban wrote:

> Everything okay.
> They finally came to our server in the upgrade process.


Thanks to Reini and John for the info.

Dan

[Phpwiki-talk] Wiki

[Terry T. <ter...@bt...>]

I would really like to contribute to this but so far have not even been =
able to sign my name as visiting.  I am not a geek. but do you want a =
book only written by geeks.  Please help!  There are times on ecademy =
when I seem to wander into geekland - too often.  If ecademy is to =
fulfil it's potential a higher level of empathy for the non geek would =
go a long way.  I will persist.  But if you get too far ahead of me I =
will get lost.  A good servant leader should not be out of reach of =
those he serves.

Much appreciated.

Terry Toms=20

Re: [Phpwiki-talk] Other files in PHPWiki

[Matthew P. <mp...@he...>]

On Thu, Jul 01, 2004 at 10:19:50AM +0200, Reini Urban wrote:
> Matthew Palmer wrote:
> 
> >Is there any way to upload / include non-Wiki content within a PHPWiki?  A
> >bloke here at work has suddenly decided he wants this feature to build a
> >dynamic reference library -- with direct links to the source PDFs (a la
> >footnotes).
> >
> >I've got him throwing the pages into his homedir (/~user etc), but it would
> >be a bit easier to have a file upload thing going on.  Anyone know about 
> >it,
> >or should I just write one up to sit next to the wiki?
> 
> * just type urls (as you already advised)
> * http://phpwiki.sourceforge.net/phpwiki/UpLoadPlugin and use the 
> Upload: interwiki map then. (just a shortcut)
> * http://phpwiki.sourceforge.net/phpwiki/TranscludePlugin (iframe)

Cool, it looks like one of those two plugins will do what we want to have
done.  Thanks.

- Matt

Re: [Phpwiki-talk] Other files in PHPWiki

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

Matthew Palmer wrote:

> Is there any way to upload / include non-Wiki content within a PHPWiki?  A
> bloke here at work has suddenly decided he wants this feature to build a
> dynamic reference library -- with direct links to the source PDFs (a la
> footnotes).
> 
> I've got him throwing the pages into his homedir (/~user etc), but it would
> be a bit easier to have a file upload thing going on.  Anyone know about it,
> or should I just write one up to sit next to the wiki?

* just type urls (as you already advised)
* http://phpwiki.sourceforge.net/phpwiki/UpLoadPlugin and use the 
Upload: interwiki map then. (just a shortcut)
* http://phpwiki.sourceforge.net/phpwiki/TranscludePlugin (iframe)

If you add pdf to INLINE_IMAGES it can be inlined also (not tested)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Other files in PHPWiki

[Matthew P. <mp...@he...>]

Is there any way to upload / include non-Wiki content within a PHPWiki?  A
bloke here at work has suddenly decided he wants this feature to build a
dynamic reference library -- with direct links to the source PDFs (a la
footnotes).

I've got him throwing the pages into his homedir (/~user etc), but it would
be a bit easier to have a file upload thing going on.  Anyone know about it,
or should I just write one up to sit next to the wiki?

- Matt

Re: [Phpwiki-talk] Re: [phpwiki - Help] FileFinder.php - var: Deprecated

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

Reini Urban wrote:
> SourceForge.net wrote:
>> Read and respond to this message at: 
>> https://sourceforge.net/forum/message.php?msg_id=2641817
>> By: agatho
>>
>> Well when I want zu call the page i got the following errormessage:
>> lib/FileFinder.php:18: Fatal[2048]: var: Deprecated. Please use the
>> public/private/protected modifiers
>>
>> I'm using php5 RC3
> 
> You cannot yet run phpwiki with php5rc3, unless the var issues are 
> resolved. sorry. php's fault. we don't want to support two complete 
> seperated source trees.
> 
> They had it on for older beta versions, which was a major headache for 
> all projects which wanted to support php4 and php5, then for rc2 they 
> put it off, now they put it on again.
> maybe there's a php.ini switch to allow this kind old syntax.

Please try "zend.ze1_compatibility_mode = On" in php.ini and report back.
I had no time to test that yet.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] [Fwd: [phpwiki-checkins] CVS: phpwiki/lib/wikilens PageListColumns.php,1.3,1.4]

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

Everything okay.
They finally came to our server in the upgrade process.

https://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1
The SourceForge.net team is working to complete our second major CVS 
infrastructure upgrade (the first was done more than a year ago). This 
infrastructure upgrade will eliminate the delay between developer and 
non-developer CVS (presently a 5 hour sync delay). In coming weeks, a 
significant amount of new hardware will be installed and other service 
enhancements will be rolled out. This notice is being posted to alert 
you to our revised schedule. We are confident that the end-product will 
exceed the performance requirements we originally devised. This upgrade 
is happening in pieces; new features and fixes are already being rolled 
out. The hardware cutover will occur at the end of this upgrade process 
(we are waiting for the replacement hardware to arrive). To monitor the 
progress of this project, please watch Site Doc I9 for announcements.

https://sourceforge.net/docman/display_doc.php?docid=19242&group_id=1#enhancements-200406

Dan Frankowski wrote:
> Folks,
> 
> I tried committing changes to Phpwiki that would make the wikilens theme 
> finally work. Exciting! However, it looks to me as if the commits didn't 
> actually get in. Very bizarre. Any ideas?
> 
> More detail:
> 
> I had trouble before because I was trying to use CVS with pserver-- I'm 
> using :ext: with ssh now. Here's my CVS/Root: 
> :ext:dfr...@cv...:/cvsroot/phpwiki.
> 
> I committed 7 files (none core), and even got phpwiki-checkins emails, 
> once I subscribed to that list. One of them is attached. Furthermore, 
> when I do a "cvs status", I see new versions of the files (e.g., 
> lib/wikilens/PageListColumns.php used to be version 1.3, now shows 
> version 1.4).
> 
> However, when do a "cvs update -d" in another SourceForge tree (a 
> pserver tree, so read-only), it looks as if the changes aren't there! 
> For example, PageListColumns.php is still version 1.3, and is not updated.
> 
> Has anyone seen this?!
> Dan
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

RE: [Phpwiki-talk] [Fwd: [phpwiki-checkins] CVS: phpwiki/lib/wiki lens PageListColumns.php,1.3,1.4]

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

Dan, there is a delay from when the developer cvs machines are updated to
when the public pserver cvs machines are update.  Wait a while (a couple of
hours) and it will show up.

John Cole

-----Original Message-----
From: php...@li...
[mailto:php...@li...]On Behalf Of Dan
Frankowski
Sent: Wednesday, June 30, 2004 4:39 PM
To: PhpWiki discussion
Subject: [Phpwiki-talk] [Fwd: [phpwiki-checkins] CVS:
phpwiki/lib/wikilens PageListColumns.php,1.3,1.4]


Folks,

I tried committing changes to Phpwiki that would make the wikilens theme 
finally work. Exciting! However, it looks to me as if the commits didn't 
actually get in. Very bizarre. Any ideas?

More detail:

I had trouble before because I was trying to use CVS with pserver-- I'm 
using :ext: with ssh now. Here's my CVS/Root: 
:ext:dfr...@cv...:/cvsroot/phpwiki.

I committed 7 files (none core), and even got phpwiki-checkins emails, 
once I subscribed to that list. One of them is attached. Furthermore, 
when I do a "cvs status", I see new versions of the files (e.g., 
lib/wikilens/PageListColumns.php used to be version 1.3, now shows 
version 1.4).

However, when do a "cvs update -d" in another SourceForge tree (a 
pserver tree, so read-only), it looks as if the changes aren't there! 
For example, PageListColumns.php is still version 1.3, and is not updated.

Has anyone seen this?!

Dan


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

[Phpwiki-talk] [Fwd: [phpwiki-checkins] CVS: phpwiki/lib/wikilens PageListColumns.php,1.3,1.4]

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

Folks,

I tried committing changes to Phpwiki that would make the wikilens theme 
finally work. Exciting! However, it looks to me as if the commits didn't 
actually get in. Very bizarre. Any ideas?

More detail:

I had trouble before because I was trying to use CVS with pserver-- I'm 
using :ext: with ssh now. Here's my CVS/Root: 
:ext:dfr...@cv...:/cvsroot/phpwiki.

I committed 7 files (none core), and even got phpwiki-checkins emails, 
once I subscribed to that list. One of them is attached. Furthermore, 
when I do a "cvs status", I see new versions of the files (e.g., 
lib/wikilens/PageListColumns.php used to be version 1.3, now shows 
version 1.4).

However, when do a "cvs update -d" in another SourceForge tree (a 
pserver tree, so read-only), it looks as if the changes aren't there! 
For example, PageListColumns.php is still version 1.3, and is not updated.

Has anyone seen this?!

Dan

Re: [Phpwiki-talk] pmwiki

[Whit B. <wh...@tr...>]

On Wed, Jun 30, 2004 at 08:49:02PM +0200, Oliver Betz wrote:

> Right, one page, one file. Could lead to problems, and maybe has some 
> impact on performance and maintenance.

Which would largely depend on the file system. Reiser4? I've run file-based
PHP discussion systems on slow hardware with a hundred or so people actively
on at a time with no latency problems at all, mostly on Reiser3. No doubt a
system with thousands active at once would be more demanding. But with a
file system which behaves like a database in its own operation, not sure
that database storage of random blocks of text will always have a clear
advantage.

> I was missing also basic things like backlinks! I don't know how one 
> can make categories.

The claim is there that it does have category functions.

> PhpWiki has much more advanced features.

It would be great if PhpWiki developed a similar emphasis on modifiability -
including the user documentation of mods. The collection of skins and
plugins is good - the plugins go far beyond PmWiki - but it looks like
adding a _new_ behavior may be easier with PmWiki than PhpWiki, for someone
who's not a core developer? If so, that's a big thing, and something it
would be fun to see PhpWiki catch up on.

Whit

Re: [Phpwiki-talk] pmwiki

[Oliver B. <ob...@de...>]

Dan Frankowski <dfr...@cs...> wrote:

> Has anyone ever looked at pmwiki (http://www.pmwiki.org)?

Yes, me.

> It looks quite beautiful.

And it's _tiny_ - 138KB! PhpWiki is rather fat these days.

> Nice docs. I like the "WikiGroups" too 
> (http://www.pmwiki.org/wiki/PmWiki/WikiGroup); I think it is very close 
> to the multi-purpose thing my user was hoping for (which has been 
> discussed under 'multiple instances of Phpwiki'). It doesn't seem to 
> have a DB behind it, though.

Right, one page, one file. Could lead to problems, and maybe has some 
impact on performance and maintenance.

I was missing also basic things like backlinks! I don't know how one 
can make categories.

PhpWiki has much more advanced features.

Oliver
-- 
Oliver Betz, Muenchen

[Phpwiki-talk] Re: [phpwiki - Help] FileFinder.php - var: Deprecated

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

SourceForge.net wrote:
> Read and respond to this message at: 
> https://sourceforge.net/forum/message.php?msg_id=2641817
> By: agatho
> 
> Well when I want zu call the page i got the following errormessage:
> lib/FileFinder.php:18: Fatal[2048]: var: Deprecated. Please use the
> public/private/protected modifiers
> 
> I'm using php5 RC3

You cannot yet run phpwiki with php5rc3, unless the var issues are 
resolved. sorry. php's fault. we don't want to support two complete 
seperated source trees.

They had it on for older beta versions, which was a major headache for 
all projects which wanted to support php4 and php5, then for rc2 they 
put it off, now they put it on again.
maybe there's a php.ini switch to allow this kind old syntax.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: test dir name (WAS: Re: [Phpwiki-talk] cvs access to dfrankow)

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

Dan Frankowski wrote:
> I am blocked on this until we choose a name for 'testbox'.
> Comments?

let's just keep "testbox" then.

> Dan Frankowski wrote:
>> Reini Urban wrote:
>>> Dan Frankowski schrieb:
>>>
>>>> One of the changes is to add an error handler (instead of just an 
>>>> assert handler). This is useful because then if there is incorrect 
>>>> PHP syntax, vars missing, etc., the tests don't run. In other words, 
>>>> the tests get more picky, which is good. When they get more picky, 
>>>> they want an existing testbox with some stuff in it (InterWikiMap, 
>>>> global_data, a few other things). Thus, I want to make a "testbox" 
>>>> in CVS with the right stuff and check it in, as I did on our local 
>>>> copy.
>>>>
>>>> Since I do not wish to make changes that you don't want, please tell 
>>>> me that you approve. Then I'll go ahead and make the unit test 
>>>> changes, including adding a CVS-tracked "testbox" with stuff in it.
>>>
>>>
>>>
>>>
>>> approved.
>>
>>
>>
>>
>> Cool. I won't add it until we have a name you like (see below).
>>
>>> but the name "testbox" compared to out intermediate ".testbox"
>>> might not fully understandable. can you think of a better name?
>>
>>
>>
>>
>> I'm sorry, I didn't understand this.
>>
>> I picked "testbox" to mean a "test sandbox." I agree it is not a great 
>> name, but I'm having a hard time thinking of better ones. A list of 
>> possibilities:
>>
>> 1. testbox
>> 2. test_sandbox
>> 3. sandbox
>> 4. backend_dir
>> 5. backend_data
>> 6. testdb
>>
>> Any preferences? I'm not sure any are very good.
>>
>>> In a perl CPAN test framework the call it "t" (for the logic) and 
>>> "output" (for the output which should be tested against).
>>
>>
>>
>>
>> Neither "t" nor "output" is appropriate here. It's more like "input". 
>> I guess that's another possibility.
>>
>>> i'm not quite accustomed to the java unittest structure.
>>
>>
>>
>>
>> Java has no standard proposal for the input data upon which to base 
>> unit tests.
>>
>> Dan
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Inline Images

[<EAG...@RE...>]

Hi, I want to see bmp files but is not working...

I modified the config.ini in this way:

INLINE_IMAGES =3D "bmp|png|jpg|gif"

And edit a page like this:

[http://hostxxx/phpwiki/images/imagen.bmp]


But when see this page only the link is showing, and if I put a jpg  the =
images is showing.

Do I only need change config.ini file or anything else ?

Thank in advance.
-----------------------------------------------------------------------
Eduardo A. G=F3mez Ceballos=20
Soporte T=E9cnico de Aplicaciones de Geociencia=20
Repsol-YPF=20
Regional Argentina Oeste=20
Talero 360 - (8300) Neuqu=E9n - Argentina=20
Tel: 54 299 4492800 int. 42621=20
-----------------------------------------------------------------------=20



=0DAVISO LEGAL:=0A=
=0DEsta informaci=F3n es privada y confidencial y est=E1 dirigida =
=FAnicamente a su destinatario. Si usted no es el destinatario original =
de este mensaje y por este medio pudo acceder a dicha informaci=F3n por =
favor elimine el mensaje. La distribuci=F3n o copia de este mensaje =
est=E1 estrictamente prohibida. Esta comunicaci=F3n es s=F3lo para =
prop=F3sitos de informaci=F3n y no debe ser considerada como propuesta, =
aceptaci=F3n ni como una declaraci=F3n de voluntad oficial de REPSOL YPF =
S.A. y/o subsidiarias y/o afiliadas. La transmisi=F3n de e-mails no =
garantiza que el correo electr=F3nico sea seguro o libre de error. Por =
consiguiente, no manifestamos que esta informaci=F3n sea completa o =
precisa. Toda informaci=F3n est=E1 sujeta a alterarse sin previo aviso. =0A=
=0DThis information is private and confidential and intended for the =
recipient only. If you are not the intended recipient of this message =
you are hereby notified that any review, dissemination, distribution or =
copying of this message is strictly prohibited. This communication is =
for information purposes only and shall not be regarded neither as a =
proposal, acceptance nor as a statement of will or official statement =
from REPSOL YPF S.A. and/or subsidiaries and/or affiliates. Email =
transmission cannot be guaranteed to be secure or error-free. Therefore, =
we do not represent that this information is complete or accurate and it =
should not be relied upon as such. All information is subject to change =
without notice.

[Phpwiki-talk] problem with dumpthml urls

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

Reini,
There is a problem with dumped subpages and the urls linking to those sub
pages.

If I dump *UtilityCenter* it does dump all of the subpages like this one:

file:///C:/Documents%20and%20Settings/jcole/My%20Documents/docbook/UC/manual
/UtilityCenter%252FUserManual%252FStaking%2520and%2520Sketching.html

but the link in the root page to this page is:

file:///C:/Documents%20and%20Settings/jcole/My%20Documents/docbook/UC/manual
/UtilityCenter%2FUserManual%2FStaking%2520and%2520Sketching.html

note that the slashes have been escaped in both and the escaped slashes in
the first url have been escaped again :-)

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 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.